I'm still not clear on the tables vs. CSS issue. Yes, presentation vs semantics - I grok that. I've read the articles, am familiar with the trend. But we already do this with xdocs.
CSS makes sense to me in some ways. I use CSS extensively in my websites to centralize formatting statements. The printing argument is particularly convincing. (it'd be nice to eliminate the ant task for creating printable documents). I just don't get why everyone is moving from tables to CSS for broad page layout - it seems about the same amount of work. (maybe more- CSS can be quirky with cross-browser issues and has trouble with footers).
Best, WILL
----- Original Message ----- From: "Tim Colson (tcolson)" <[EMAIL PROTECTED]>
To: "Velocity Developers List" <[email protected]>
Sent: Friday, May 06, 2005 10:44 AM
Subject: RE: site format
* new logo
FYI -- the attachments died during an atlassian.com upgrade, so I had recreated on the ASF wiki: http://wiki.apache.org/jakarta-velocity/VelocityLogos
* CSS instead of tables (candidly I'm not sure why - to be current with the latest trends, I guess)
http://www.informit.com/articles/article.asp?p=369225&rl=1
* Confirm that all pages print properly. (CSS will help here).
http://www.alistapart.com/articles/goingtoprint/
Cheers, Tim
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
