|
Yeah we still need to explore the options, So to avoid any confusion anyone else
might have.. I am talking about removing heavy layouting and UI logic from the
facades … I am still planning on introducing an XSL solution to the
problem we discussed before: using XSL on the generated page to generate a new
one .. a more specific one with all the fancy features you can imagine -- Wouter From: Carlos Cuenca [mailto:[EMAIL PROTECTED] Hi, Hello everybody, I want to drop support for tabs in bpm4struts, mainly
because it bloats both the facades as the templates and because it is too
tricky to properly maintain. It’s pretty easy to support in your custom jsps
but it’s much harder for generaic page templates like the ones in the
cartridge. So I was wondering, who is actually using it ? I need
to know what I’ll do, before the AndroMDA-3.0-final release ...currently I am using it, but if it is stopping you
on other things I assume the change as good, and I don't mind changing it... Perhaps we could start a discussion or something
about what should be in bpm4struts and what not … I’m feeling very
strongly about refusing some of the feature requests but I prefer to run it by
you before actually changing any code. Some of these features are:
...I think that ordering actions and positioning
fields are part of the same... layout.... as I read before there are some
solutions to explore, so I think that we should go ahead and try them, since we
see that in this way we are not getting good layouts... |
