-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Matthias Küspert Sent: Thursday, December 02, 2004 12:10 PM To: andromda-user Subject: Re: R: [Andromda-user] RE: bpm4struts layout suggestions/questions
Hi guys, I like this idea too - it would solve a lot of JSP-management- and layout-problems - including mine :-) As I think along I could imagine bpm4struts being changed to generate code for arbitrary platforms by dividing the output in three parts: - an abstract (platform-independent) GUI-workflow in plain XML files representing the model elements with their data-flow and the actions to call. - the generated (and overwritten) static files for the chosen platform - the (one-shot) generated resource and XSL files for the chosen platform which are meant to be adapted by users. Depending on the chosen GUI the cartridge generates XSL-files producing .java, .jsp or .however-files from the XML-workflow files plus the additional files for the chosen platform. [CB] That's funny you mention this because Matthias, Wouter and I were discussing something similar to this during the conference (well at least the XML files for layout which could be used for any arbitrary platform). This obviously needs a distinction between templates for different platforms in the andromda-cartridge.xml by the andromda-core, but this ain't too bad too implement (I hope). Further it calls for a plugin-mechanism for adding platform-specific templates to a cartridge. One benefit would be that this 'two tier'-generation leads to a clear distinction between PIM and PSM in the cartridges by forcing them to separate PIM and PSM resources. Maybe this approach could be used for other cartridges too. Just ideas while still enjoying Walters approach ... does it make sense? (not regarding the bulk of work it would imply ;-) Cheers, Matthias On Thu, 2004-12-02 at 16:20, Wouter Zoons wrote: > hi Walter, > > I inserted my comments into the reply: > > > > Hi Wouter, > > I have been thinking a lot about the jsp layouts. > > > > Nowadays I just generate the jsp the first time and the webdesigner > > changes its layout freely. The big problem with this approach is, of > > course, the changes made after the first generation. > > > > yup .. exactly > > > I'm very sure I will never generate the very final jsp page, so I'm > > focusing in ways to re-apply the changes made by the webdesigner to the > > individual jsp pages. > > > > I'm all ears > > > One idea (the best I've got until now) is: > > > > First generation - a very basic jsp page is created (xml compatible) and > > the changes are made using a xsl to get the final layout. > > > > Re-generations - the very basic jsp pages are generated again and the > > previous created individual xsl files are applied to each page, recreating > > the final ones. > > > > That's it, what do you think ? > > > > excellent idea! > > so basically what you're saying is to have an optional XSLT file to goes > with each jsp page (for example by taking the same name as the JSP but > just adding a suffix: my-page.jsp will have an XSLT called > my-page.jsp.xsl) > > since I have only XML in the jsp pages (no scriptlets) I can perfectly > transform it elegantly into something else > > I like this idea because I enhances reusability .. and it would be simple > to integrate this feature into the build process > > and I don't think it's a big issue for the developer to write this better > (it definitely beats tagged values, that's for sure) > > I also very much like this idea to make the facades lighter (most > style/layout can be dropped .. stuff such as the tabs for example, which > are a pain in combination with tables and x-y positioning) > > so I'm for: +1 > > > anybody else got an idea ? > > thanks again for your feedback Walter! > > -- Wouter > > ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Andromda-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-user ------------------------------------------------------- SF email is sponsored by - The IT Product Guide Read honest & candid reviews on hundreds of IT Products from real users. Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/ _______________________________________________ Andromda-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/andromda-user
