> I'm a little confused about the processing of xsl.
> Obviously there must be some kind of program that
> parses the xsl and xml file to produce the end
> product, and from what I've seen IE is the only
> browser that fully supports it. Mozilla has a
> processor it it as of May 11 (TransforMiiX ), but it
> seems a little hackish.
It is.
> At any rate, wouldn't it make more sense to have the
> xslt be done on the server, instead of in the
> uncontrollable browser? Possibly with things from the
> xml.apache.org projects (such as combinations of
> xerces, xalan, cocoon).
yes!
which is what all this noise about xsl is about.
IE5 supports client side xslt, but I really have no use for it. The very
idea is frightening :)
> I don't know a lot about what I'm saying here, so just
> give me some direction (and I would consider "read
> more" a valid suggestion, just tell me what to read)
> as perhaps I am missing some of the big picture.
no, you are not missing anything.
you made up what made sense to you, and what you made up was right :)
I think that's the best test of a system: " if I was going to do this, how
would it work" and comparing the implementation to the expectation.
_alex
--
alex black, ceo
en...@tu...
the turing studio, inc.
http://www.turingstudio.com
vox+510.666.0074
fax+510.666.0093
|
