Re: alternating tags in a list?

[Brandon Ibach <bibach@xxxxxxxxxxxxxx>]

Paul Prescod said:
> 
> > If they wanted to do alternating tags, what would you have told them to do?
> 
> I would have told them to learn Javascript and do it with Javascript.
> 
> What would I have told them with the old XSL, with embedded scripting?
> "Learn Javascript. Do it with Javascript."
> 
and then said:
> 
> What if I'm not doing Java? What if I'm writing an XSL implementation for
> an IBM mainframe? (guess what...I know someone who is) What if I'm writing
> an XSL implementation in Python (guess what...). What if I'm writing an
> XSL implementation in an XML editor (guess what...). What if I'm embedding
> XSL in a document repository?
> 
   Scott has already addressed this issue, stating a very good case
for the fact that Java support is relatively easy to come by, but even
if it isn't an option, there are alternative ways to support
Javascript/ECMAScript in a variety of environments.
   My question is this: If you raise such an issue about the
availability of Javascript on the *server* side (where we generally
have some control over things), how can you so flippantly assume that
we have Javascript *and* DOM on the client side?
   There are still plenty of browsers out there that don't support the
DOM, not to mention that some of us may actually want to target print
media, or more static online (such as PDF) formats.  Do you really want
to eliminate any chance of XSL being a decent solution in these areas?
   I'm not necessarily saying that Javascript-in-XSL is the way to go,
but saying that XSL doesn't need to be able to handle more complicated
tasks like this just because browsers support the DOM doesn't seem
like much of a solution, either.

-Brandon :)


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list