Tod Harter wrote: > Yep, you just include those StyleChooser's and then you make > your stylesheets > "alternate" stylesheets. So you can have something like > "?style=foo" on the > end of your query string, then you just have an alternate > stylesheet who's > title is "foo". (which you do just by adding the title > attribute to the PI). > Its a pretty dirt simple thing, but real handy. I've taken to > using it as a > way to get into "debug" modes when building apps using XSLT. > You can give all > your stylesheets titles and then turn them on and off with > the query string. > I think really a cookie StyleChooser might be even better for > that though. > You can make a "debug control panel" in javascript that sets > up a cookie to > instruct AxKit on which styles to display, so you can get at > intermediate > parts of the processing pipeline and see what is going on, or > do performance > analysis on each step and not need to take your whole app apart.
Hi Tod, good ideas you have here. I will give them a trial. But there are still some questions remaining: - Do I have to insert the alternative PI's in the XML documents or can I define them via the httpd.conf for the directory the XML content is located in? - How can I change the behavior of AxKit, that it throws out the XML raw data when calling a non existing style-type instead of taking the default stylesheet? Try: http://www.axkit.org/mailinglist.xml?style=foo That exposes all secrets that are behind the site ;-) (Not bad for the AxKit site here, but in my opinion not what I want with my own site) Greetings Jo Seibert --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
