Jason Hunter wrote:
> David Wall wrote:
> > And if you passed the ISP back as an array, it would be more like:
> >
> > <% for ( int i=0; i<isps.length; ++i ) { %>
> > The next name is <%=isps[i].getName()%><br>
> > <% } %>
> >
> > I'll grant none of this meets the simplicity of the webmacro solution,
> > though as a Java programmer I have no problem with it <smile>.
>
> In my opinoin, a graphics artist shouldn't be expected to write this.
A graphic artist shouldn't be expected to write WebMacro either. Indeed,
graphic artists shouldn't be expected to edit raw-html. The graphic
artists I know, use Mac and Windows programs like Photoshop,
PageMill, and Frontpage to layout a page, and generally, it is one
of the technical people who actually boots up Emacs and integrates
the look-and-feel.
That's why XML + XSLT will be superior. A declarative approach makes
it easy to design editors that allow visual manipulation of data
sets through selecting data and styling it, and the lack of side-effects
and variable manipulation in the language, makes it easy for non-programmers
to understand what a particular rule does in isolation, without having
to understand procedural program flow.
Templates are still code.
===========================================================================
To unsubscribe: mailto [EMAIL PROTECTED] with body: "signoff JSP-INTEREST".
FAQs on JSP can be found at:
http://java.sun.com/products/jsp/faq.html
http://www.esperanto.org.nz/jsp/jspfaq.html
