Subject: Re: [xsl] Does anyone know how to make IE less useless for XSLT developement?|
From: "Terence Kearns" <terence.kearns@xxxxxxxxxxxxxxx>
Date: Tue, 21 Feb 2006 13:54:00 +1100
On 14/02/06, M. David Peterson <m.david.x2x2x@xxxxxxxxx> wrote: > :D You know me... if it ain't noisy, I must be sleeping ;) :D > You're not wrong. Holy crap, this thread has been busy while I've been away. Dave, you're a wealth of knowledge. Here i was thinking Transformiix was superior until you burst my bubble. Looks like all the while I was just lucky in not requiring features (like different namespaces in imported templates) that made it croak. I'm always amazed at how much I learn from this list. Wendell, thanks for the tip on using Saxon. Currently I am using another processor other than MSMXL and Transformiix to test/debug my XSLT. But Sablotron may not be as conformant as it should be. I'll get saxon and employ it to see if it can help ferret out the problems that other porcessors pass over. This may be the only real answer to my central query regarding debugging in IE. Martin, first time I heard of Sarissa. Sound EXACTLY like the sort of thing I can use. I'm dealing in JS more and more these days, particularly as I gravitate to writing business apps in XUL. Of course I don't need an XML abstraction library for a singular platform like XUL, but for all my non-XUL JS/XML intensive work... David, I could send you all my code, but currently the way i develop an app is to set up a main.xsl template which is kind of like a tree trunk, importing other XSLT templates. This means I bunch of files. I'll zip them up and email you off-list. If anyone else is interested, I can send them a copy too. I still haven't sorted out the parsing problem that IE is so secretive about. Mind you, I still haven't run it through saxon yet - whic I will try shortly.