New Posts

Sunday, May 30, 2010

Tables and Validation

Evil Markup? Maybe not


Tables... The very word sends shivers down any self proclaimed CSS master. Tables are evil, tables should never be used. Tables should be cast into oblivion from this day forth. Baloney!!

Tables like every other tag in HTML have its uses. However like anything in this world it can be misused. Most Web Designers use applications such as Photoshop, or what have you, to design the look of their site, and then have this same application transform it into HTML. Yes it may be HTML it may even look nice in some cases, but is it correct? Is it Valid? Probably not.

Most applications use tables to transform the image rendition of a layout created by a designer into HTML, however these applications will normally use obsolete, difficult and hard to maintain ways of building a website. Like I mentioned in my previous POST, A simple layout is easier to maintain. Most of the time they'll rely on tables to create the layout because that was the technique used years ago. however as the Web has progressed so have the techniques to design and build websites.
A simple 3 column layout like we saw before ends up a mis-mash of cells and columns instead of a nice fluid understandable piece of code.

Tables

<table>
<tr><td colspan=3>Header area</td></tr>
<tr> <td> Left Column</td>
<td>Center Column with lots of content...</td>
<td>Right Column</td>
</tr>
</table>


Vs DIV's


<div id="header"></div>
<div id="leftcol"></div>
<div id="contentcol"></div>
<div id="rightcol"></div>


7 Lines of code vs 4. And this is just a basic skeleton. Now suppose you want to change the look, like we did in the previous post. Move Navigation to be horizontal, you'd need to go in and alter the entire markup. Now its seems reasonably simple without any content, but imagine tons of content in the middle column, and trying to find where the right column begins after all that content with more tags and text etc...

With the proper use of CSS you couldn't care less what the content of the DIV is where it starts or where it ends. You look at your CSS and you modify that.

Now I must make a confession, calling your columns left, right and center is not a good idea, because like with tables you give them a predetermined location or layout position, and as I showed with CSS, they really don't need nor should they have one.

So for an accurate representation, you could call them navigation, content, and maybe "adbar" or extra_content pane ro something that is descriptive of its contents, but not of its position in the page.

If you need to change its location, style, dimensions etc.. it you can look for their style definitions in the style sheet and change those. So Navigation moves to the top horizontally, "adbar" may end up at the bottom heck you could even set it as the left column instead. All without altering the markup.

You don't have a left column, you have a navigation "pane" for lack of a better word, and you can place it anywhere you want to.

All this without altering your base markup. Do it with tables, and you'll be starting from scratch every time.

This does not immediately mean tables no longer have a place in the world of Web development and should never again be used or heard of. Tables play an important role if used properly.

But how do you use tables properly? You use them to display tabular data.
But now, what is tabular data? Well, it can be many things. It can be a directory, it can be a product listing, it can be a roster sheet for a baseball league etc... All that can be considered tabular data. The common factor? Its data, its listings, its information that has that particular display need and structure, and will not change. In this context tables become a tag to markup how data is to be structured, not where its going to be on the page, or what its going to look like.

htm,example,table


<table border=0 cellspacing=0 cellpadding=0 style="border:1px solid #999999;">
<tr><td colspan=3>Players</td></tr>
<tr> <td> Name</td>
<td>Position</td>
<td>Email</td>

</tr>
<tr><td>Peter</td><td>Midfielder</td><td>pete@baseballnuts.com</td></tr>
<tr><td>John</td><td>Rightfielder</td><td>john@baseballnuts.com</td></tr>
<tr><td>Frank</td><td>Pitcher</td><td>frank@baseballnuts.com</td></tr>
<tr><td>Jason</td><td>First Baseman</td><td>jason@baseballnuts.com</td></tr>
</table>


Validation



Validation is simply the product of adhering to the rules and norms set by the W3C for design.

As long as your coding follows those rules it can be considered valid, and stands a good chance of looking the same across all the different platforms.
But hey!, we all make mistakes, and we make even more when we are coding a website. So to help us out the W3C offers a service to check your web pages and make sure it conforms to the set of rules you've specified in your webpage as your Doctype. If you made a mistake and missed something it will tell you and often offer an explanation of the errors.

The W3C's validator is located here:
http://validator.w3.org/

You can use it to run your pages through and make sure there are no errors.
web,markup,css,html

It has 3 ways of checking your website:

  1. By URL

  2. By File Upload

  3. By Direct Input



By Url is the most direct, you give it a URL or address where it can access your website online, and it verifies it.

By File Upload: Takes your base file directly. Reads it and returns its result.

By Direct Input,: By far the easiest option, just copy and paste your entire code, and press the button.

Options 2 and 3 are only useful if your file is 100% pure HTML. If you are working with a server side language like PHP, ASP or Cold Fusion, then its often better to offer the URL. Otherwise the server side code is not processed, and may cause issues that aren't really there in the final page.

Lets take our example website we used in the last post and give it a whirl:

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>

<head>
<title>Structure Vs Presentation</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">

</head>
<body>

<div id="header">
<h1>This is the Main Website Title</h1>
</div>
<div id="navigation">
<ul>
<li><a href="#">Link 1</a></li>
<li><a href="#">Link 2</a></li>
<li><a href="#">Link 3</a></li>
<li><a href="#">Link 4</a></li>
</ul>
</div>
<div id="content">
<h3>This is Content Title</h3>
<p>
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin odio turpis, hendrerit bibendum fringilla sit amet, lacinia sit amet lacus. Quisque varius tellus vel libero tempor laoreet. Suspendisse vel dignissim tellus. Etiam fringilla consequat eros, in volutpat lectus molestie at. Vivamus vitae mi justo, quis gravida nisi. Tristique senectus et netus et malesuada fames ac turpis egestas...
</p>
<div id='subcontent'>
<p>
Suspendisse potenti. Duis pellentesque, sem varius facilisis vehicula, lectus purus semper mauris, quis laoreet metus sem vel diam. Ut non tellus nulla. Sed egestas dui ac nulla eleifend vulputate. Sed blandit lacus eu arcu luctus et condimentum erat scelerisque...
</p>
<p>
Pellentesque mauris assa, aliquet vel volutpat sed, facilisis vitae urna. Vestibulum consequat metus id magna mollis auctor. Nunc id tellus nec sem auctor convallis ut a quam. Suspendisse vel urna velit, feugiat ultrices leo. Vestibulum orci ipsum, venenatis quis ultrices at, varius sed sem. Nulla facilisi. In porta, nunc vel rutrum adipiscing, dui lectus accumsan... </p>
</div>
<p>
Quisque sit amet dui libero, at pharetra erat. Nullam ante mauris, hendrerit vel accumsan sed, porttitor et purus. Fusce interdum sodales justo, a pretium velit porta eu. In hac habitasse platea dictumst. Etiam semper laoreet dolor quis pharetra. Integer id est vel tortor iaculis laoreet congue non nibh. Cras non dui massa. Sed nulla tortor, volutpat vitae accumsan eget, imperdiet quis nibh. In accums...
</p>
</div>

</body>
</html>

We'll use the Direct Input option, and just copy and paste our website inot the text area as seen in the pic above. Press the button and the Validator Returns 2 Warnings, (about the same thing actually). Our Example Markup is considered valid.
valid,html,wrc,result

The 2 warnings refer to the lack of character encoding. Its an additional line that tells the browser what encoding to use when displaying the page. Most servers send a predefined header for this, and unless you need a specific encoding you can get by with the standard encoding.

<meta http-equiv="Content-Type" content="text/html; charset=utf-8">


I'll get into it more in a future post. For now its just a lesser warning we may safely ignore.

Let's introduce a real error shall we:


<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>

<head>
<title>Structure Vs Presentation</title>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">

</head>
<body>

<div id="header">
<h1>This is the Main Website Title</h1>
</div>
<div id="navigation">
<ul>
<li><a href="#">Link 1</a></li>
<li><a href="#">Link 2</a></li>
<li><a href="#">Link 3</a></li>
<li><a href="#">Link 4</a></li>
</ul>
</div>
<div id="content">
<h3>This is Content Title</h3>
<p>
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin odio turpis, hendrerit bibendum fringilla sit amet, lacinia sit amet lacus. Quisque varius tellus vel libero tempor laoreet. Suspendisse vel dignissim tellus. Etiam fringilla consequat eros, in volutpat lectus molestie at. Vivamus vitae mi justo, quis gravida nisi. Tristique senectus et netus et malesuada fames ac turpis egestas...
</p>
<div id='subcontent'>
<p>
Suspendisse potenti. Duis pellentesque, sem varius facilisis vehicula, lectus purus semper mauris, quis laoreet metus sem vel diam. Ut non tellus nulla. Sed egestas dui ac nulla eleifend vulputate. Sed blandit lacus eu arcu luctus et condimentum erat scelerisque...
</p>
<p>
Pellentesque mauris assa, aliquet vel volutpat sed, facilisis vitae urna. Vestibulum consequat metus id magna mollis auctor. Nunc id tellus nec sem auctor convallis ut a quam. Suspendisse vel urna velit, feugiat ultrices leo. Vestibulum orci ipsum, venenatis quis ultrices at, varius sed sem. Nulla facilisi. In porta, nunc vel rutrum adipiscing, dui lectus accumsan... </p>
</div>
<p>
Quisque sit amet dui libero, at pharetra erat. Nullam ante mauris, hendrerit vel accumsan sed, porttitor et purus. Fusce interdum sodales justo, a pretium velit porta eu. In hac habitasse platea dictumst. Etiam semper laoreet dolor quis pharetra. Integer id est vel tortor iaculis laoreet congue non nibh. Cras non dui massa. Sed nulla tortor, volutpat vitae accumsan eget, imperdiet quis nibh. In accums...
</p>
</div>
<img src="myimage.jpg">
</body>
</html>


I've added an image. But I neglected to include one of the properties that it requires.

When we run it through the Validator, it spits out a big nasty red error:

validator,w3c,error,alt

And here we have its explanation:
validator,error,wrc,img,alt


Line 38, Column 21: required attribute "ALT" not specified





The attribute given above is required for an element that you've used, but you have omitted it. For instance, in most HTML and XHTML document types the "type" attribute is required on the "script" element and the "alt" attribute is required for the "img" element.


It tells me the line number, the code around the error, and why it may be wrong.
Now I can go back to my code and fix it:


<img src="myimage.jpg" alt="This is an Image" >


Should we run it again, it will validate.

At the end and like with many other things, correct usage of tags for their intended purposes will help produce a nicer looking website that is easier to maintain.


Well that's it for my second entry into this Blog. Hope you enjoyed it.

Saturday, May 15, 2010

Welcome to Web 101

Welcome to Behind the Web or as I like to call it Web 101. My name is Phil B, I'm a IT consultant and specialize in Web development. Specifically applications involving HTML PHP, and Javascript.

I've created this Blog as away of opening up the web development world to people who want to lear about having a website that is easy to maintain and attractive and comfortable to browse.

I've seen through my years many websites that use overly complex markup to present the simplest of designs. When simpler, easier to understand markups can do the same in less time, and consume less resources for the visitor.

In today's World Wide Web we have to cater to a variety of people, Operating systems, and web browsers. This can make it difficult to create a website that looks the same across all these different platforms. The more complex the markup is, the more likely something is going to break, or fail to look the same for everybody.

I'm also of the idea that a simpler site is a better site. I find sites that have all these transitions and effects and things that change and animate around to be kind of annoying. I also completely despise sites that abuse Flash animations.
Flash can be used as an intro movie to the site if required, but basing the entire site around Flash is just overkill.

Additionally Flash based websites alienate an important part of the browsing population: The mobile population.

The Mobile Population are those people that use their phones, PDA's or other mobile devices to access websites. Well if you are one of the many users (like me) of iPhones, or iPod Touches, and now iPads then you know Flash based sites are a big no no because these devices have no Flash support. At least 30% of the mobile users use one of these devices. That means a Flash based site just turned down 30 out of every 100 users. That's a lot of people that can't see the site at all. Add to that the devices that have limited Flash support and there's no guarantee all the features in your Flash site will work. I've tried to navigate through different flash based sites with mobile devices such as Nokia phones, and there's always some type of issue preventing the full functionality of the site. You might be losing 50% of your target audience because of Flash.

Simpler, easier cleaner sites, have a better chance of looking right in mobile browsers. This also has the benefit of allowing you to design a single site instead of 2 or 3 versions for different devices.

The first thing to know when developing a website is that Internet Explorer is almost always wrong in how it renders elements. Sadly Microsoft's own browser still doesn't know how to properly render websites even in their current version 8 browser. Fortunately the statistics show that the usage of IE is declining rapidly. From 2006 where IE6 garnered about 60% of all browser users to a mere 19% now for IE8.

IE's disability can be overcome with properly coded websites.




The first step to a site that works across most platforms is creating Valid HTML, CSS, JS etc.. What is valid code? Valid code is code that adheres to certain standards established by a group called the World Wide Web Consortium or W3C for short. They determine the set of rules and norms that are to be followed to create a site. Valid code follows these rules and guarantees a consistent look across the different platforms.

One must also let the browser know what these rules are so it can render the content appropriately. These rules are contained in files called Doctypes. Short for Document Types these files basically list the rules the browser should follow to render or display the page. Setting this at the top of your page means that any browser loading your page will know how its supposed to render it. This keeps things consistent. Even IE follows these rules when properly set.

The most common Doctype is the Transitional Doctype.

This gives you the most leeway in coding, by giving you access to presentational and stylistic elements within the markup like font tags and other deprecated tags. Other doctypes like the Strict doctype disallow such tags, and demand all presentational and stylistic coding to be done through CSS.


There are other doctypes that can be used in other specific circumstances but for our purposes will stick mostly with Transitional, and Strict.

What this approach wants to achieve is to separate the presentation from the structure of the document. The structure refers to how the information is organized. You have paragraphs, lists, sections etc.. The Presentation is how those structure elements look. Do they have a border? A background? Are they 10 or 50 pixels tall? etc...

Though as mentioned before, the Transitional doctype lets you have the presentational elements within markup, its always a good idea to avoid their placement there as much as possible.

Here's an example of how a full separation of presentation and structure can make having completely different looking websites with the same base markup a simple task.

Base Markup:

<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd">
<html>

<head>
<title>Structure Vs Presentation</title>

</head>
<body>

<div id="header">
<h1>This is the Main Website Title</h1>
</div>
<div id="navigation">
<ul>
<li><a href="#">Link 1</a></li>
<li><a href="#">Link 2</a></li>
<li><a href="#">Link 3</a></li>
<li><a href="#">Link 4</a></li>
</ul>
</div>
<div id="content">
<h3>This is Content Title</h3>
<p>
Lorem ipsum dolor sit amet, consectetur adipiscing elit. Proin odio turpis, hendrerit bibendum fringilla sit amet, lacinia sit amet lacus. Quisque varius tellus vel libero tempor laoreet. Suspendisse vel dignissim tellus. Etiam fringilla consequat eros, in volutpat lectus molestie at. Vivamus vitae mi justo, quis gravida nisi. Tristique senectus et netus et malesuada fames ac turpis egestas...
</p>
<div id='subcontent'>
<p>
Suspendisse potenti. Duis pellentesque, sem varius facilisis vehicula, lectus purus semper mauris, quis laoreet metus sem vel diam. Ut non tellus nulla. Sed egestas dui ac nulla eleifend vulputate. Sed blandit lacus eu arcu luctus et condimentum erat scelerisque...
</p>
<p>
Pellentesque mauris assa, aliquet vel volutpat sed, facilisis vitae urna. Vestibulum consequat metus id magna mollis auctor. Nunc id tellus nec sem auctor convallis ut a quam. Suspendisse vel urna velit, feugiat ultrices leo. Vestibulum orci ipsum, venenatis quis ultrices at, varius sed sem. Nulla facilisi. In porta, nunc vel rutrum adipiscing, dui lectus accumsan... </p>
</div>
<p>
Quisque sit amet dui libero, at pharetra erat. Nullam ante mauris, hendrerit vel accumsan sed, porttitor et purus. Fusce interdum sodales justo, a pretium velit porta eu. In hac habitasse platea dictumst. Etiam semper laoreet dolor quis pharetra. Integer id est vel tortor iaculis laoreet congue non nibh. Cras non dui massa. Sed nulla tortor, volutpat vitae accumsan eget, imperdiet quis nibh. In accums...
</p>
</div>

</body>
</html>

Our base markup consists of a header bar, a navigation section, a content section, and a sub content section inside the larger content area.

Without any CSS applied to it it looks like this:
web,markup,css,html

That's a very plain website, but as you can see its completely usable. Everything works, and can be used. But suppose we want to give it a little flair. We want the links to be on the left side as a column, and the content in the middle, and maybe even a narrower column on the right. Well CSS can do all that, without touching the basic markup.

Lets add a Stylesheet to our markup, basically a set of instructions of how the markup is supposed to be presented to the user.

This is the stylesheet:


*{
margin:0px;
padding:0px;
border:0px;
}

body{
width:100%;
height:100%;
background-color:#DDDDAA;
}
#header{
width:100%;
height:120px;
background-color:#DDDDFF;
}

#navigation{
float:left;
width:15%;
background-color:#DDDDAA;
text-align:center;
}

#content{
width:78%;
float:left;
text-align:justify;
background-color:#FFFFFF;
}

#content p{
width:80%;
margin-left:auto;
margin-right:auto;
margin-bottom:5px;
}

#content #subcontent{

border:2px inset gray;
background-color:#666666;
color:#FFFFFF;
}

But how do we link it to our markup? There are 3 ways to accomplish this:

  1. Stylesheet Reference
  2. In file Style Section
  3. Inline Styles



Number 1, the one we'll use for this example, is basically a secondary file that is linked to our base HTML file.

We link the stylesheet to our HTML markup file with a LINK tag:



We place this link in our html file, between the head tags of our markup.

<head>
<title>Structure Vs Presentation</title>
<LINK REL=StyleSheet HREF="style.css" TYPE="text/css" MEDIA=screen>
</head>



Lets see how our page looks now:

websitem,CSS,HTML,markup


Look at that, we now have a navigation bar on the left, a colored header bar, and our content section with a defined subsection in dark gray, and the markup is still the same.


Lets try a slightly different stylesheet:

*{
margin:0px;
padding:0px;
border:0px;
}

body{
width:100%;
height:100%;

}
#header{
width:100%;
height:120px;
background-color:#DDDDFF;
}

#navigation{
width:100%;
height:20px;
background-color:#DDDDAA;
text-align:center;
}

#navigation li{
float:left;
width:80px;
height:100%;
}

#content{
text-align:justify;

}

#content p{
width:80%;
margin-left:auto;
margin-right:auto;
margin-bottom:5px;
clear:both;
}

#content #subcontent{
margin-left:auto;
margin-right:auto;
width:40%;
height:200px;
overflow:auto;
border:2px inset gray;
background-color:#666666;
color:#FFFFFF;
}



web,markup,css,html

Now we have a horizontal navigation bar between the header and the content, and we have a scrollable sub section inside our main content area. But the main HTML markup remains the same.

That's the beauty, anyone can look at the code, and immediately understand what each section is, and then just apply their own CSS to make it look however they want to.

This is of course a very basic example, but it shows the power of CSS. And how a simple structure can have different layout designs.

Well that's it for my very first Web development post.

I hope you enjoyed this as much as I enjoyed writing it. I'll be going into some much cooler CSS techniques in up coming blog posts, before moving on to Javascript and finally PHP.

Don't forget to comment.




Appendix


For basic coding, any text editor will suffice. My personal favorites are Notepad for Windows, and TextWrangler for Mac.