From: "Jonas Oberg" <[EMAIL PROTECTED]> > However, HTTP being the wonderful thing that it is, things tend to go > from bad to worse when it comes to actually handling form submissions > and similar things. > > I guess one way of doing what I want to do is to create an XSP for > every page that contains some kind of logic. Then have the XML contain > a tag that calls that XSP, have the XSP do whatever magic is required, > return some XML and then have XSL transform it.
The my system works right now is like this: I have a chrome.xml and chrome.xsl file to allow me to have a common look and feel. These two files contain the various common style elements of pages. The idea is that my content is usually framed by the chrome. Then there is a default.xsl which includes chrome.xsl and loads chrome.xml into $chrome. Default.xsl provides no fancy style except allowing me to put content into the chrome frame with a couple of default style elements i have. For any app that requires special style, i overwrite default.xsl with filename.xsl. My applications subclass AxKit::Provider::Filter, so they can spit out XML and have AxKit deal with them as XML files. I use XML::LibXML::Document to construct and render my XML. Using these parts, any path can now be either a file or an app, dictated by httpd.conf. This way I can change out the look and feel of any one page or even the entire site without ever touching Code, plus I can support HTML and XML clients easily. arne --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
