Comments for Tomos Wyn

Comment on Please comment your code by tomoswyn

tomoswyn — Wed, 07 Mar 2012 20:05:49 +0000

Thanks!

Comment on Please comment your code by Not My Real Name

Not My Real Name — Wed, 07 Mar 2012 16:20:10 +0000

I couldn’t help but notice that there is a strikingly similar article posted at:

http://fxcteam.com/blog/importance-having-your-code-commented

Comment on Using Thesis and WPAlchemy by Alex Mangini

Alex Mangini — Sun, 08 Jan 2012 20:09:31 +0000

(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

Alex Mangini — Sun, 08 Jan 2012 20:08:43 +0000

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

Creating individual page sliders with Genesis — Fri, 18 Nov 2011 13:48:13 +0000

[...] = [];}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

Creating individual page sliders with Genesis — Fri, 18 Nov 2011 13:47:14 +0000

[...] == "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

Avinash D'Souza — Thu, 27 Oct 2011 11:28:42 +0000

Also, would it be possible to include a 960.gs to Thesis screencast?

Comment on Using Thesis body classes to target browsers by tomoswyn

tomoswyn — Tue, 25 Oct 2011 09:40:26 +0000

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

Rick Beckman — Tue, 25 Oct 2011 02:58:25 +0000

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

tomoswyn — Mon, 24 Oct 2011 14:19:04 +0000

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.