An Introduction: Last week we saw just how easy it is to use a nifty combination of Jscript and XPath to "replace" client XSL Transforms. Before we get into it, I'd thought I'd clear up a couple of comments from last week. First, I'm not opposed to XSL on the client. It solves many problems that are a pain in Jscript...like sorting to mention one. However, since you have to jump out to a different language and maybe even a different development environment, I think it's easier to just write it all in Jscript. And remember: XSL only gets you the display. Any binding code you need has to be done in Jscript, and again, I think it's easier to keep all of your code in one place. So hopefully that has answered the inquiries / accusations that I was somehow anti-XSL...on to Episode 3. Serialization, Whiles and XPath... Last week I mentioned serialization in the context of my XML. A question popped up in my inbox that made me realize that I didn't do a good j...
You can only be young once. But you can always be immature. - Dave Barry