Mostly I'm interested in a WYSYWIG page editor, like Visual Studio
.NET has for its web forms. It should be possible to read the .page files
and associated component definitions to generate object properties pages and
whatnot, thus allowing you do set your properties and bindings right there
on the editor in a fashion consistent with, say VB form design (or .NET form
design for that matter).
I'm less interested in graphical workflow editing because, in my
experience, there isn't really a way to "universally" decouple workflow
description from an underlying system implementation. Which means you either
get a tightly coupled workflow editor which works well only if your system
follows certain rules, or a loosely coupled workflow editor which looks sort
of spiffy by doesn't actually do anything.
--- Pat
> -----Original Message-----
> From: Christian [mailto:[EMAIL PROTECTED]
> Sent: Monday, May 23, 2005 1:11 PM
> To: Tapestry users
> Subject: Re: Would a Visual Tool be helpful to Tapestry?
>
> 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?
>
> 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]
