Alan, > > But in a nutshell, > > (1) request a page (using a 'layout' markup language): > http:/localhost/controller/member_form.xml > (2) controller (an Embperl CGI script) takes the member_form.xml and parses > it thru the layout2html.xsl > (3) this resultant layout is now an embperl file, and is parsed by the > embperl interpreter to instantiate any values in the markup and handed back > to the requestor > (4) requestor fills in any form values and posts it back > (5) the form that accepts this data processes it, and dispatches back to > the controller to render the response >
A few thoughs that comes to my mind: - In Embperl 2.0b5 a requested is served by providers. A provider can do anything to the data. (Read it from disk, parse it, do xslt or whatever you want). A recipe tells Embperl how to plug the providers together to process the request. Embperl comes with a couple of such recipes, one of them is EmbperlXSLT, which causes the source to be processed and the result is transformed via XSLT. It shouldn't be to hard to change the recipe (look at Embperl/Recipe/*.pm) to do things viceversa i.e. first do the XSLT and then them Embperl part, also I would normaly do the XSLT as the very last step. In the upcoming 2.0b6 it will also be possible to generate both XML and XSLT via Embperl and/or to process the result of the xslt transformation again via Embperl. - In 2.0b6 (which I hopefully release during the next four weeks), I will have reorganized the internal datastrutures and make them publicly available via multiple objects. (Thread, Application, Request, Component and more). The Application object is intended to serve as controller. By overloading it with your own class, you can implement your own controller and control how Embperl serves the pages. The benefit of using the Application object is, that Embperl will do the standart tasks for you (like setting up form data, session data etc.). So when 2.0b6 is out, I would create a custom Application obeject and a Recipe to get your ideas working. Addtionaly 2.0b7 will contain some support for internationalisation, but I currently gathering ideas and I am not quite sure how it will look like. If you take the approach to do internationalisation with xslt, I would suggest to store all text in a speparate xml document and pass a parameter into the xslt stylesheet to let the stylesheet select the correct text out of this document. (I think there is an example for this on www.xml.com, but I am not quite sure) Gerald P.S. I maybe have not answer all your questions. In this case don't hestitate to ask again. ------------------------------------------------------------- Gerald Richter ecos electronic communication services gmbh Internetconnect * Webserver/-design/-datenbanken * Consulting Post: Tulpenstrasse 5 D-55276 Dienheim b. Mainz E-Mail: [EMAIL PROTECTED] Voice: +49 6133 925131 WWW: http://www.ecos.de Fax: +49 6133 925152 ------------------------------------------------------------- --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
