Christian wrote:
Hi Andreas
I personally think you're on the right track, but I didnt use tapestry
in large-scale applications
How do you position your tool vs. Spring Web Flow? Or, let me ask
differently: could you
imagine your tool beeing a frontend to Spring Web Flow?
Actually, I'm more interested in supoorting Tapestry, so I'd have to
wait and see if and how
Tapestry is going to be integrated with WebFlow or if it's going to use
another solution. There's
been some discussion on the dev list about how to best define page
transitions, e.t.c. but
I don't really know where we're heading...
I got the impression, that, one way or another, the workflow has to be
pulled out of (as you have
described it) .jwc, page, html. java code into a separte container.
Even in my own littul application,
I itches me to do something in that direction, but first things first...
Cheers
cs.
Andreas Andreou schrieb:
Hi.
I'd like to hear your opinions on whether a visual tool would
actually help during development.
What features should it have, what it should do and what it shouldn't.
Has anyone used such a tool (perhaps for struts or jsf) ?
Does it really help in large-scale apps?
I'm asking all these 'cause (more out of curiosity) I've put together
a (display-only)
version of such a tool for Tapestry. I've posted some screenshots at
http://andyhot.di.uoa.gr/blojsom/blog/default/java/2005/05/23/Diagrams_for_Tapestry.html
and I'm now thinking of further steps.
Andreas Andreou
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
