Craig R. McClanahan wrote:
> Jason Hunter wrote:
>
> > David Wall wrote:
> >>
> > In my opinoin, a graphics artist shouldn't be expected to write this.
> >
>
> Of course, we originally expected page developers to understand raw HTML
codes as
> well, but the creation of a robust tools market made that level of
knowledge
> irrelevant.  The same thing will happen for scripting syntaxes when such
tools
> become available.  An intelligent development tool targeted at JSP will
have
> graceful ways to enter custom tag elements and their attributes, so the
syntax is
> totally invisible.

> How many development tools do we expect to see targeted at JSP syntax vs.
any
> other given scripting language?  :-)

I agree with Jason, graphic artists should not be expected to write this
code however I do not think it is unreasonable for them to be asked to
ignore the <%...%> stuff.  Right now there are thousands of developers using
ASP which uses a very similar syntax.  What are they doing?  In the ideal
model the artists produce static HTML with markers where the data should go
( e.g. <INPUT type="text" name="foo" value="#FOO_VALUE" /> ) and the JSP
developers will go in to change the #* strings to appropriate values and add
scriptlets and <jsp:*> tags to implement the logic the page is supposed to
follow.  If, later, the HTML layout needs to change then the artists will
need to make edits ignoring the JSP scriptlets and expressions.

The programmer's editor that I use ( Visual SlickEdit v5.0 ) has a very
nifty feature of being able to syntax color the embedded java code
differently then it does the HTML.  You just tell it to treat the .JSP files
as .HTML files and make sure you have a @page directive attribute of
language="java" and it does the rest.  The opposite should happen in HTML
editing tools.

In Jason's article he calls the JSP syntax for <jsp:getProperty> confusing
because it requires a />.  This is standard XML.  XML is designed to be
easily manipulated by any software program whether they understand the
semantics or not or, for that matter, have the DTD.  The requirement for the
/> is just so that the code does not need to contain the closing
</jsp:getProperty> tag.  IMHO, if the artist cannot understand that, then
they probably should not be working on web apps since XML is the direction
that all markup languages are going towards.

Dana H. P'Simer, Jr.
x7547
[EMAIL PROTECTED]
[EMAIL PROTECTED]


PSimer, Dana.vcf

Reply via email to