Java developers, unless they are EXPERTS in HTML and CSS (and very few are) waste an enormous amount of time trying to line stuff up and make it pretty. My advice and it works for us, DON'T LET THEM!!! We prototype and let the GUI guy do his thang or he creates the sample screen and we convert it to Tapestry.
During the LAST week before we shipped the product the gui guy and CEO sat down and re-did the interface, NO developer involvement (none, zip, nada). And then our customer support person came over and said how much it had improved the usability of the product. It was bitter-sweet. Great to NOT have to sit down and make mind-numbing HTML changes, but it was bitter because it improved the site and the developers couldn't take credit (sigh). It is NOT cost effective to have a Java Developer doing HTML and CSS. If it is, then your developers are getting paid too little ;-). regards, Mark -----Original Message----- From: Geoff Longman [mailto:[EMAIL PROTECTED] Sent: Fri 2/17/2006 9:47 AM To: Tapestry users Subject: Re: Gavin King's comment about presentation code and CSS in Javaposse podcast > > The beauty of Tapestry is that you _shouldn't_ be designing the pages but > instead let your creative web designer do that. Yup. We have that exact work separation and it works *perfectly*. Our output (completed pages) is easily 3 times greater than any other Tapestry project I've done where the java people mess with the html/css. Geoff -- The Spindle guy. http://spindle.sf.net Get help with Spindle: http://lists.sourceforge.net/mailman/listinfo/spindle-user Blog: http://jroller.com/page/glongman Feature Updates: http://spindle.sf.net/updates --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
