Archive for February, 2006

Web Development is not a production line

Thursday, February 23rd, 2006

Matt May recently posted an article on the Blue Flavor blog entitled Tearing down the factory. He speaks of ridding development teams of the production line attitude, where each person is only responsible for one thing, and when they are down it passes to the next person in line. He relates an experience he had that demonstrates this idea:

I could only watch in horror as an art director came in from the outside and froze the developers out of the design process entirely. It was a formula for bad design: the “final” design deliverable not only contained critical technical and interaction flaws, it actually reintroduced some of the very same user experience problems we had worked hard to eliminate.

He goes on to talk about how no one person should ever have full veto control over others in the team, and how communication and respect is a necessity to thrive and be successful.

It’s a great article and I just want to pass it on, as it deserves the attention.

via Digital Web

Google Pages - "Oops!"

Thursday, February 23rd, 2006

Google has released a new product entitled Google Pages, allowing people to create and publish their own web pages. You need to login with your gmail account, and your pages will be published at yourgmailaccount.googlepages.com. I tried to give it a spin to see the templates they have and the sort of code that gets output, but I ran into an “Oops” message:

Thank you for your interest in Google Page Creator! Google Page Creator has experienced extremely strong demand, and, as a result, we have temporarily limited the number of new signups as we increase capacity. In the meantime, please submit your email address and we will notify you as soon as we are ready to add new accounts. Thank you for your patience.

Now, I could have sworn that I just had to login with my gmail account - I’m not sure why I have to enter it again. Anyway, as with most products Google releases demand seems to have already surpassed supply, so we’ll have to wait until another day to see what Google is up to this time.

Microsoft still only cares about Microsoft

Wednesday, February 22nd, 2006

I had checked out Microsoft’s live.com when it was first released, and wasn’t too impressed - I haven’t been back since. One of the things that was a problem for me originally was that it wasn’t compatible with Firefox when first released. I came across it again today, as well as a link to the labs page. If you’re a Firefox user, you’ll certainly be able to tell right away that the developers over at MS are still coding their pages just for IE. I’ll chalk it up to a memory problem, but it’s a shame they can’t remember that IE isn’t the only browser people use anymore.

How to change the world

Wednesday, February 22nd, 2006

Dean Kamen, New Hampshire local and inventor of such life-changing devices as the home dialysis machine and the IBOT, and the not so life-changing Segway, has come up with a way to bring power and clean water to rural villages across the globe. Facinating.

via mattcutts.com

Don't forget your DOCTYPE!

Tuesday, February 7th, 2006

In the course of helping people at Experts Exchange, I’ll see a lot of questions about layouts that don’t work in multiple browsing enviornments. The common theme running through most of them is the lack of a proper DOCTYPE.

If you have a website that looks great in one browser, but different in another, make sure your site has a DOCTYPE!

What’s a DOCTYPE?

A DOCTYPE is a “document type declaration” - it lets the browser know what type of document it’s trying to display.

Why do I need one?

You need a DOCTYPE because if your webpage doesn’t have one, the browser goes into “Quirks Mode.” You don’t want this - it will mean a higher chance of your layout not working the same between different browsers.

But I’ve already got one!

Ok, great! But is it a valid one? Does it include a full URL to a .dtd file on w3.org? If not, it’s not doing you much good as far as the browser is concerned.

Ok - so what do I do to fix it?

While there are a few choices for DOCTYPEs out there, I’m going to recommend you use the one for HTML 4.01 Strict.

<!DOCTYPE html PUBLIC “-//W3C//DTD HTML 4.01//EN”
“http://www.w3.org/TR/html4/strict.dtd”>

This will allow you a bit of leeway in your coding that an XHTML DOCTYPE wouldn’t, but will still force you into good habits, assuming you run your code through the HTML Validator

Your advice broke my page!

I’m sorry. No really, I am. That sucks. But, if you take the time to fix your code to work with your new valid DOCTYPE, you’ll be saving youself a lot of hassles in the future. You’ll have better code that works more consistently in different browsers, you’ll be better prepared for new technology, and you’ll be helping to make the web a better place. Isn’t that worth it?

More Information

There are plenty of resources out there about DOCTYPEs, and this was just meant to be a very basic starting point. If you want to read more into why you need a DOCTYPE, please check out these pages:

Shaping the future of the web through the beginners

Tuesday, February 7th, 2006

Sometimes, we lose track of the beginners. There’s so much information to stay on top of that gets crammed into our minds as web developers, that we sometimes forget where we came from. Thankfully, it’s easy to remind ourselves by offering our time and help to those who are new to the business. Personally, I answer questions over at Experts Exchange when I have free time. There are plenty of other forums or newgroups where one can offer assistence as well.

The quality of questions at EE range from those just starting out, to those needing assistance with some pretty high level stuff. While the high level stuff is fun to assist with, it’s the ones who are just starting out that usually need the help the most. You’ll see a lot of questions about layouts that don’t work in different browsers, CSS that is doing funny things, and people who just really don’t have a good grasp on the web technologies and what they all do.

A big part of helping some of these folks is the teaching aspect that goes along with it. Rather than simply providing a code fix, you can explain to them why they should be doing something a certain way. Why they should be using CSS instead of tables for their layouts, why HTML is different than ASP or PHP, why their should run their site through the validator. A lot of these folks might not care, but if you can impart some knowledge to those that do, you can help the future of the web. You can not only be responsible for making your own web sites better, you can help others make their betters as well.

A lot of questions get asked over and over again, and I’ll hopefully start addressing a few of those in some articles here on the site. One of the big issues I’ve noticed lately are people with layout issues between browsers that are being caused by invalid code and a lack of a DOCTYPE, so stay tuned for the first of the series - “Don’t forget your DOCTYPE!”

IE 7 <label> bug

Thursday, February 2nd, 2006

So I bit the bullet and installed the IE 7 beta preview 2 on an extra machine at work. The install went fairly smoothly, checked out a few pages, a few small rendering issues but nothing major. Nothing, that is, until I check out some pages I had made with forms on them.

Oh no! What has happened to my beautiful forms? Their

(If you have IE 7 you can see the problem on this test page I’ve put up. If you don’t have IE 7 then check out the screenshot.)

Taking the form out of the table, or changing the text alignment to the left fixes the issue. However, the most usable, accessible form will have labels, and normally for usability the text will be aligned to the right.

Ok, ok - why is your form inside a table anyway, you might ask. Well on some of our older sites at work, the basic page layout is still done in tables. I know, I know - but I can’t fix everything all at once. And I’m sure I won’t be the only one with this issue.

I’ve submitted the bug to IETell@microsoft.com as they request on their blog.

Update: I submitted this bug to PPK, and he wrote back with some additional information:

“BTW: the bug seems to be generic: any element with a text-align
inside a TD has these problems.”

Thanks for the extra information!

Update 2: According to Markus at MS, this issue has been fixed in the latest builds.