• From: Frans Englich <frans.englich@t...>
• To: xml-dev@l...
• Date: Thu, 7 Sep 2006 13:34:22 +0000

On Thursday 07 September 2006 13:10, juanrgonzaleza@c... 
wrote:
> bryan rasmussen said:
> >> And also because XSLT is not all one needs. Can I script in JS an
> >> up-down navigation menu for a website. How could i do that using
> >> client side XSLT (could in XSLT 2)?
> >
> > I guess you could if an up-down navigation menu is done using html. you
> > can of course also generate javascript. This is probably top level
> > clueless question about XSL-T likely to be encountered from people who
> > don't use it.
>
> And sure you can transform XML input docs to SVG or to LaTeX,
> Mathematica... but i cannot think anyone claiming that XSLT draw as SVG,
> print as LaTeX or simbolically integrate expressions.
>
> Sure also you can ***introduce*** JS and other stuff into the XSLT
> template and the final doc will contain the JS code managing the DOM for
> the up-down navigation menu. But the dinamical menu is being managed via
> JS-DOM.
>
> That i said is that you cannot use XSLT (at least 1.0) for the menu in the
> _final_ doc,  you _may_ use JS.
>
> Therefore here XSLT is lacking functionality. Is not?

Sure. Any design lacks something because it is not everything.

If language A is different from language B, A lacks something in B and vice 
versa. Replace A and B with arbitrary programming language.

You can do stuff in ECMAScript that you can't do in XSL-T. And vice versa. You 
can do things in C++ that you cannot do in C#, and so on.


Cheers,

		Frans

• References:
  • RE: SGML complexity
    • From: <juanrgonzaleza@c...>
  • Re: SGML complexity
    • From: "bryan rasmussen" <rasmussen.bryan@g...>
  • Re: SGML complexity
    • From: <juanrgonzaleza@c...>