Forum Moderators: open

Message Too Old, No Replies

Table-based layouts

Hate Hate Hate

         

zCat

5:16 am on May 23, 2007 (gmt 0)

10+ Year Member



Apologies in advance for the rant...

Had a rush job from a client to set up a CMS with some sample pages yesterday... "our designers [apparently one of the top web design firms in client's country] will send you the templates / pages"... What I got was a series of pages which had evidently been created in a wyswiyg editor dating from ca. 2002 or so... Either that or they were being paid by the amount of <td> tags created... Tables within tables within tables, sometimes used just for spacing. And muggins here has to parse the through the whole mess (no indentation or anything) to extrapolate something that can be used as a template. While I'm not averse to using the odd table or two for pragmatic layouting, this gave me a whopping (real) headache just working out where I could safely cut into the layout. Aaargh.

(Still, looks like they'll let me rework the layout into something reasonable, all on billable time ;-)

phranque

7:34 am on May 23, 2007 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



What I got was a series of pages which had evidently been created in a wyswiyg editor dating from ca. 2002 or so... Either that or they were being paid by the amount of <td> tags created... Tables within tables within tables, sometimes used just for spacing. And muggins here has to parse the through the whole mess (no indentation or anything) to extrapolate something that can be used as a template.

get html tidy and you can have some cleaned/formatted code seconds after you open a document...

zCat

10:25 am on May 23, 2007 (gmt 0)

10+ Year Member



get html tidy and you can have some cleaned/formatted code seconds after you open a document...

doh... (slaps forehead) why didn't I think of that. Thanks. That helps somewhat, although I still have to go through the document tree and work out where it's safe to cut out content...

phranque

10:52 am on May 23, 2007 (gmt 0)

WebmasterWorld Administrator 10+ Year Member Top Contributors Of The Month



That helps somewhat, although I still have to go through the document tree and work out where it's safe to cut out content...

in that case you might find Mozilla's DOM Inspector [mozilla.org] to be useful as well as Web Developer 1.1.4

ytswy

12:34 pm on May 23, 2007 (gmt 0)

10+ Year Member



Don't forget the Webdeveloper Toolbar for Firefox - it has a handy outline table cells function.

rocknbil

8:08 pm on May 23, 2007 (gmt 0)

WebmasterWorld Senior Member 10+ Year Member



As a recovering table junkie who still reverts to a scant table framework on occasion, I can say without a doubt you should bring this to the attention of the client and make this the original developer's problem. There's really no excuse for excessive use of tables.

This is important because if you just assume the project and take on the fix, it leads to clients abusing you. They need to be made aware of how much more it's costing them in time and money.

zCat

2:38 am on May 24, 2007 (gmt 0)

10+ Year Member



Just finished the worst of it... even with the tools mentioned and some Perl-ish foo quite a nightmare.

Normally I would protest loudly and request that the client have serious words with the designers, but it was a rush job and there was no time. Fortunately it's fairly lucrative work ;-), and I think the client won't be using those designers again.