I'm trying to create a system where an end-user can upload their customized
stylesheets (XSTL) so that they can customize the way a given (X)HTML page
looks for them.  But the resulting HTML needs some common code that all
users require, such as common navigation buttons at the top and bottom, an
html form that wraps around it all so that if the user clicks submit it goes
back to our site, etc.

The basic thought might be to create a common "header" xslt that creates the
headers and starts the form that we need, followed by the user's custom look
xslt for forms fields and for the way the data actually is displayed,
followed by a common "footer" xslt that creates the footers and ends the
form.  Obviously, much of this can be accomplished by allowing the user or
common xslt to include the other and let the various rules trigger to create
the resulting page.

Has anybody does this before?  Does it work?  Is there a better approach?

I'm mostly concerned about the added performance overhead of not only
applying the user's xslt, but also having to do some sort of
"include/import" of the common xslt.

Thanks,
David

Reply via email to