Re: Feedback on Java Code Generator

"Shawn Hartsock" <[email protected]>
Newsgroups gmane.org.user-groups.trijug.juglist
Message-ID <[email protected]>
And just because I'm using it:
http://grails.codehaus.org/WebFlow

Grails WebFlow if anyone is interested...

On Jan 9, 2008 9:30 AM, Chris Bredesen <[email protected]> wrote:
> Tim Jowers wrote:
> > Chris, what I'm thinking about is the page-flow logic as a workflow
> > and the workflow as a set-population. The sets are the relations and
> > the overall set of sets for the workflow is all related tables
> > (relations). Thus the workflow could be generated by knowing the
> > relationships of the relations. The user would then only have to
> > decide the ordering of the screen ( e.g. start with the leaf nodes or
> > start with the tables having FK's). That's my thought process right now.
>
> This is certainly an interesting prospect and I don't know if anyone's
> doing it currently.  Seam uses jBPM to control page flow (optionally I
> believe) so it wouldn't be a stretch to imagine some simple declarative
> way to choose which entities comprise a page flow and allow the system
> to lay out what makes sense (and also understand how to handle
> exceptions).  Last time I looked at Rails it had some rudimentary
> association handling but I don't believe it created any flows (that was
> probably 1-2 years ago though).
>
> If you're interested in continuing this discussion, I'd urge you to stop
> by the Seam user forum [1] -- propose this idea and see what comes
> back.  The developers are very active there and you might get some good
> info.
>
> Best,
>
> Chris
>
>
> [1] http://www.jboss.com/index.html?module=bb&op=viewforum&f=231
>
>
>
> _______________________________________________
> Juglist mailing list
> [email protected]
> http://trijug.org/mailman/listinfo/juglist_trijug.org
>



-- 
/** Shawn.Hartsock http://hartsock.blogspot.com/  //*/
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.