Visual form within code is important when it comes to readability, usability, accessibility, and all those other “bility”s. Many of the W3C’s standards give some visual form guidelines to follow, and there are many more besides these which can help in development.

Beginning What You Started & Pulling Things Together

Much like some poetry uses rhyme to pull together ideas and complete thoughts, the W3C has told us to always close all tags in XHTML (excluding the doctype).

When we don’t close our tags, code is really hard to track and debug. Take a look at this:


<div><ul><li><img src="image.gif"><li><p>test<p>some more text</ul></div>

I closed a few tags because without closing the div and ul things probably wouldn’t even work, though in HTML closing li and p tags are not required. Still, looking at that gives me a headache.

If we close all our tags (by XHTML standards), take a look at how much easier it is to read:


<div><ul><li><img src="image.gif" /></li><li><p>test</p><p>more text</p></li></ul></div>

That allows us to see exactly where things start and where they stop.

Line Breaks

Line breaks are important tools for poets. Can you imagine reading some poem that’s all on one line? Crazy. Same with the code I just showed you above. Look what our code can become with the help of a few linebreaks: 


<div>
<ul>
<li><img src="image.gif" /></li>
<li><p>test</p><p>more text</p></li>
</ul>
</div>

By grouping code by tags and content, it makes it that much easier to follow.

Spacing

Appropriate tabbing and spacing can make all the difference in the world. Lets take our last version of code and add some spacing in it to see what we can do:


<div>
  <ul>
    <li><img src="image.gif" /></li>
    <li><p>test</p><p>more text</p></li>
  </ul>
</div>

By spacing things accordingly, we can actually see where our elements begin and end just by scanning vertically. This gets even more convenient when using a good code editor such as Notepad++, which has built-in indent guides.

Lets compare this to our first version of code:


<div><ul><li><img src="image.gif"><li><p>test<p>some more text</ul></div>

Which would you rather work with?

Now obviously, these examples used a very simple bit of code. When developing some advanced JavaScript, using visual form guidelines such as these can make an even greater impact on the aesthetic qualities of your code. As Snook mentioned in his Rapid DOM Development session, being consistent in your coding style really speeds things up. Examples he gave for JavaScript include using camelCase, uppercase for classes, and all caps for constants.

Some More Advanced Code

Incase you still don’t believe me, I’ll give you an example of some more advanced JavaSript.

Take a look at this mess:


var live = { // ......
close:	function() { Effect.SwitchOff('searchresults', {queue: {position: 'end', scope: 'close'}});
Effect.Fade('closeresults', {duration: .5, queue: {position: 'front', scope: 'close'}});
}, Active	:function() { if(this.Browser == true) {
var indicator = document.createElement('img'); indicator.src = 'indicator.gif';
indicator.id = 'indicator-safari';
indicator.style.display = 'none'; $('search').appendChild(indicator);
Effect.Appear('indicator', {duration: .5, queue: {position: 'end', scope: 'active'}}); }
else { var indicator = document.createElement('img'); indicator.src = 'indicator.gif';
indicator.id = 'indicator';
indicator.style.display = 'none'; $('search').appendChild(indicator); Effect.Fade('searchsubmit',
{duration: .5, queue: {position:'front', scope: 'active'}}); Effect.Appear('indicator', {duration: .5, queue: {position: 'end', scope: 'active'}});}}, // ......
}

And look at what it could be:


var Live = {

// ......

Close	:	function() {
		 Effect.SwitchOff('searchresults', {queue: {position: 'end', scope: 'close'}});
		 Effect.Fade('closeresults', {duration: .5, queue: {position: 'front', scope: 'close'}});
},

Active	:	function() {
		 if(this.Browser == true) {
		 var indicator = document.createElement('img');
			indicator.src = 'indicator.gif';
			indicator.id = 'indicator-safari';
			indicator.style.display = 'none';
		 $('search').appendChild(indicator);
		 Effect.Appear('indicator', {duration: .5, queue: {position: 'end', scope: 'active'}});
		}

		else {
			var indicator = document.createElement('img');
			indicator.src = 'indicator.gif';
			indicator.id = 'indicator';
			indicator.style.display = 'none';
		 $('search').appendChild(indicator);
		 Effect.Fade('searchsubmit', {duration: .5, queue: {position:'front', scope: 'active'}});
		 Effect.Appear('indicator', {duration: .5, queue: {position: 'end', scope: 'active'}});
		}
},

// ......

}

I find the last bit actually enjoyable to look through.

So stick with (most of) the standards, develop your own coding style, and work towards turning your code into a nicely formed bit of poetry. swan

(Stay tuned for Part III which will focus on resourceful and condense coding. If you haven’t read Part I yet, you can catch it here: Making Code Poetry Part I)