[Michael Morris]

Originally Posted by Princeton

I agree with Bellardia. There's a lot of javascript that you will need to alter. [I] (the main reason why you don't see any vbulletin CSS tableless layout)

I've written massive javascript applications so this doesn't intimidate me - but depending on how much has to be fixed I might start over with a prototype base instead of the yui base that vbulletin ships with.

If you're releasing it to the public be prepared for a lot of support - for each vbulletin upgrade.

That's one of the reasons I've waited until this late in vbulletin's life cycle.

If this is a personal project - be prepared to spend 3 times as much on a typical upgrade.

I've been down this path. At first it's fun and challenging; but the upgrades really get to you after a while. There's also the issue of making it compatible between all browsers (and versions).

Acid 2 or forget them. IE 6 and 7 are the only exceptions that I'm going to give - and if IE 6 gives me too much trouble it will be cut as well.

Personally, I want you to continue. The more vbulletin CSS tableless layouts the better the future looks for vbulletin.

GO FOR IT!

I'm not sure it will be completely tableless. Tabular data, like thread lists, should go into tables. However the nested table after nested table situation that we currently have would be gone.

Last night I got through the navbar - that was a headache. However I have the rollovers working via CSS alone. I haven't tested the IE's yet and probably won't for awhile.

I will probably release this in alpha state with a milestone list.