Hi Andrew, Andrew Watt wrote:
I wonder if what has mostly been happening up to now is XSLT-coders dabbling with design? :)
Yup.
I would be interested in any stories about the reactions of "pure" graphics designers in a production setting when first faced with the Cocoon approach and how they and, I suspect, XSLT-programmer colleagues actually worked out a practical workflow.
What we do here is:
- Designers build HTML, WML etc prototypes.
- Programmers modify the prototypes to be XHTML+CSS compliant. Usually, the prototypes are enhanched during this stage (designers are very bad when it comes to download time, accesibility, usability etc. They give you huge images that can be replaced with much smaller versions manipulated with CSS). Many images are removed completely, using some common background image and real text. This is the most tricky stage and talented people are importand; I'm talking about programmers opening Gimp, editing images and code at the same time...
- Programmers translate the prototypes to XSLT.
IMHO, the only reason we need designers is for not eating up even more time from people that can code. Plus we always feed designers to the marketing dpt ;-)
In general, I've been a designer, a programmer and whatever. I think the most valuable people are the ones that can wear many hats, thus able to coordinate the work of different people. Design tools suck and we only use them for prototyping.
If it counts to anything, I believe Cocoon will help a lot in delivering different content from the same data. Doing that with JSP/PHP/ASP/whatever prooves to be a pain in large projects.
Manos
---------------------------------------------------------------------
Please check that your question has not already been answered in the
FAQ before posting. <http://xml.apache.org/cocoon/faq/index.html>
To unsubscribe, e-mail: <[EMAIL PROTECTED]>
For additional commands, e-mail: <[EMAIL PROTECTED]>
