Hi again.., > -----Original Message----- > From: Hunsberger, Peter [mailto:[EMAIL PROTECTED]] > Sent: Wednesday, November 27, 2002 9:33 AM > > > In-other-words: currently, sitemap has access to context via URI, > parameters, generators, etc. Based on this, sitemap spits out a decision on > what transform to use. What I want instead is to feed an XSLT this same set > of context as XML and have the XSLT pick the subsequent transform to use. > The advantages to me are; 1) I can code in XSLT instead of sitemap language; > 2) I can optimize the entire chain of events since the transform picking > XSLT can pass on the context to the next transform (standard transform > chaining); 3) I get a functional programming model (not an advantage to > some, I know).
I believe what I am doing with livestoryboard is exactly what you want, but I go about it differently. You have many projects going on with all of their own properties. I have the same issue with different sites having their own properties (they could have differnet schemas). A site is defined in a single XML file, site.xml. The transformation to the page view always happens against this cached XML. Since this XML has all the properties handy I can set up the UI controls to use the specific properties (including the appropriate XSL, which can be changed by an authorized user) necessary to do the next thing, whatever that is. What I actually do is transform the site.xml into JS objects (that extend a base object so I can get the benefits of inheritance). I also transform my schema (config and content) into JS objects. The constructors are also created by the schema transform so they can be whatever the project needs. The combination of the schema objects and the site objects lets me do pretty much anything I want, or rather, anything the client wants. Is this on target, this time? best, -Rob --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, email: [EMAIL PROTECTED]
