Comments for Tomos Wyn http://tomoswyn.com Serial ramblings of a freelancer and newbie marketer Sun, 08 Jan 2012 20:09:31 +0000 hourly 1 http://wordpress.org/?v=3.3.1 Comment on Using Thesis and WPAlchemy by Alex Mangini http://tomoswyn.com/thesis/using-thesis-and-wpalchemy/#comment-210 Alex Mangini Sun, 08 Jan 2012 20:09:31 +0000 http://tomoswyn.com/?p=194#comment-210 (my bad, last sentence should be: I think this is the superior way to customize Thesis.) (my bad, last sentence should be: I think this is the superior way to customize Thesis.)

]]> Comment on Using Thesis and WPAlchemy by Alex Mangini http://tomoswyn.com/thesis/using-thesis-and-wpalchemy/#comment-209 Alex Mangini Sun, 08 Jan 2012 20:08:43 +0000 http://tomoswyn.com/?p=194#comment-209 Been meaning to mess around with WPAlchemy, but I think if you went ahead and created a Thesis child theme, you could avoid having to do any of this: http://www.kristarella.com/2010/10/wordpress-child-themes-and-thesis/ I think this is the superior way to customizing Thesis. Been meaning to mess around with WPAlchemy, but I think if you went ahead and created a Thesis child theme, you could avoid having to do any of this:

http://www.kristarella.com/2010/10/wordpress-child-themes-and-thesis/

I think this is the superior way to customizing Thesis.

]]> Comment on Thesis Theme by Creating individual page sliders with Genesis http://tomoswyn.com/go/thesis-theme/#comment-102 Creating individual page sliders with Genesis Fri, 18 Nov 2011 13:48:13 +0000 http://tomoswyn.com/?page_id=23#comment-102 [...] = [];}I’ve recently started to work with the Genesis Framework for WordPress. I still love Thesis, but I thought why not start working with Genesis too. It was a good idea, and I’ve already [...] [...] = [];}I’ve recently started to work with the Genesis Framework for WordPress. I still love Thesis, but I thought why not start working with Genesis too. It was a good idea, and I’ve already [...]

]]> Comment on genesis by Creating individual page sliders with Genesis http://tomoswyn.com/go/genesis/#comment-101 Creating individual page sliders with Genesis Fri, 18 Nov 2011 13:47:14 +0000 http://tomoswyn.com/?page_id=180#comment-101 [...] == "undefined"){ addthis_share = [];}I’ve recently started to work with the Genesis Framework for WordPress. I still love Thesis, but I thought why not start working with Genesis too. It was a [...] [...] == "undefined"){ addthis_share = [];}I’ve recently started to work with the Genesis Framework for WordPress. I still love Thesis, but I thought why not start working with Genesis too. It was a [...]

]]> Comment on Please comment your code by Avinash D'Souza http://tomoswyn.com/thesis/please-comment-your-code/#comment-87 Avinash D'Souza Thu, 27 Oct 2011 11:28:42 +0000 http://tomoswyn.com/?p=108#comment-87 Also, would it be possible to include a 960.gs to Thesis screencast? Also, would it be possible to include a 960.gs to Thesis screencast?

]]> Comment on Using Thesis body classes to target browsers by tomoswyn http://tomoswyn.com/thesis/using-thesis-body-classes-to-target-browsers/#comment-86 tomoswyn Tue, 25 Oct 2011 09:40:26 +0000 http://tomoswyn.com/?p=171#comment-86 Totally agree - I only go for the php option when I really have to. Totally agree – I only go for the php option when I really have to.

]]> Comment on Using Thesis body classes to target browsers by Rick Beckman http://tomoswyn.com/thesis/using-thesis-body-classes-to-target-browsers/#comment-85 Rick Beckman Tue, 25 Oct 2011 02:58:25 +0000 http://tomoswyn.com/?p=171#comment-85 Much better to use conditional statements. Using browser-based classes makes caching impractical unless you're storing a cached file of every page for every browser that hits it. Conditional styling is also much more foolproof; as you said, browser detection can be spoofed. Much better to use conditional statements. Using browser-based classes makes caching impractical unless you’re storing a cached file of every page for every browser that hits it. Conditional styling is also much more foolproof; as you said, browser detection can be spoofed.

]]> Comment on Please comment your code by tomoswyn http://tomoswyn.com/thesis/please-comment-your-code/#comment-84 tomoswyn Mon, 24 Oct 2011 14:19:04 +0000 http://tomoswyn.com/?p=108#comment-84 I agree with some of what you say, especially that "CSS, when properly done tells the coder where that element belongs on the page and what it’s tied into". Most of the code that prompted me to write this post was made up of ID's and classes that made no sense. And yes, I've worked with files much bigger than some of the examples I listed, but the code here was all over the place, unformatted, and a general pain to work with. I normally take the approach of using comments for blocks of code (Header, Navigation e.t.c), and only when needed will add inline comments. With your last sentence, yes I agree that it's only CSS, but I develop with others in mind. What happens if the next developer isn't as proficient, or the client wants to play about with the codes themselves - I have no idea of knowing their skill level and/or proficiency. That's why I'll comment my code quite a bit. Of course, there's nothing stopping you having one CSS file, decently formatted and full of comments, and using a processor to remove al comments and whitespace in order to make the file smaller. I agree with some of what you say, especially that “CSS, when properly done tells the coder where that element belongs on the page and what it’s tied into”. Most of the code that prompted me to write this post was made up of ID’s and classes that made no sense.

And yes, I’ve worked with files much bigger than some of the examples I listed, but the code here was all over the place, unformatted, and a general pain to work with.

I normally take the approach of using comments for blocks of code (Header, Navigation e.t.c), and only when needed will add inline comments.

With your last sentence, yes I agree that it’s only CSS, but I develop with others in mind. What happens if the next developer isn’t as proficient, or the client wants to play about with the codes themselves – I have no idea of knowing their skill level and/or proficiency. That’s why I’ll comment my code quite a bit.

Of course, there’s nothing stopping you having one CSS file, decently formatted and full of comments, and using a processor to remove al comments and whitespace in order to make the file smaller.

]]> Comment on Please comment your code by Ramsez Stamper http://tomoswyn.com/thesis/please-comment-your-code/#comment-83 Ramsez Stamper Mon, 24 Oct 2011 14:09:45 +0000 http://tomoswyn.com/?p=108#comment-83 Commenting is fine, as long as you don't write more lines of comment than you have code. You really shouldn't need nearly any comments at all for a script that's 700 lines of CSS and 450 lines of PHP. That's honestly child's play. Comments should be reserved to explain functionality of a complex algorithm or to note that a function called within this block is stored in some file 3 directories away or something like that. Commenting just because you cannot spot the solution immediately is a waste of bits and doesn't drive you to get faster at decoding code written by other coders. CSS, when properly done tells the coder where that element belongs on the page and what it's tied into (#header_title, or .navlinks for example, instead of #wfdsdwe and .dafdfsd) CSS should only need comments to say "this block of CSS is for items on page X" and comments for common items used for say all popups in a site, or all buttons, or all links. Beyond that...come on, it's CSS...seriously. Commenting is fine, as long as you don’t write more lines of comment than you have code. You really shouldn’t need nearly any comments at all for a script that’s 700 lines of CSS and 450 lines of PHP. That’s honestly child’s play.

Comments should be reserved to explain functionality of a complex algorithm or to note that a function called within this block is stored in some file 3 directories away or something like that. Commenting just because you cannot spot the solution immediately is a waste of bits and doesn’t drive you to get faster at decoding code written by other coders.

CSS, when properly done tells the coder where that element belongs on the page and what it’s tied into (#header_title, or .navlinks for example, instead of #wfdsdwe and .dafdfsd) CSS should only need comments to say “this block of CSS is for items on page X” and comments for common items used for say all popups in a site, or all buttons, or all links. Beyond that…come on, it’s CSS…seriously.

]]> Comment on Please comment your code by tomoswyn http://tomoswyn.com/thesis/please-comment-your-code/#comment-80 tomoswyn Sun, 23 Oct 2011 19:28:21 +0000 http://tomoswyn.com/?p=108#comment-80 Thanks - I think I'm finally settled on a design after all this time. To answer your question, no, the design isn't really gridded. It's based on Thesis, with some reference to the 960 grid system. For example, I like the 16 column grid (http://960.gs/demo.html) offered by 960gs, so I took two values from there that I liked for my content, 580px for the content and 280px for the sidebar. I then let Thesis do its magic on the rest. Thanks – I think I’m finally settled on a design after all this time.

To answer your question, no, the design isn’t really gridded. It’s based on Thesis, with some reference to the 960 grid system.

For example, I like the 16 column grid (http://960.gs/demo.html) offered by 960gs, so I took two values from there that I liked for my content, 580px for the content and 280px for the sidebar. I then let Thesis do its magic on the rest.

]]>