John, we are doing something very similar to this except we are using extjs to generate our form objects. We have a "form builder" which uses a drag and drop "tree" structure to build the form objects. Form data can persist in route or in the database. Forms post back into a workitems controller and it launches the process and persists the data. Its all still pretty primitive but it sounds similar to what you are doing. Its all very meta which creates some interesting problems around data persistence and testing. I am interested in how you approached the problem.
I am pulling down the project now. Thanks E On Oct 19, 4:16 am, John Mettraux <[email protected]> wrote: > Hello, > > I've started a sample rails3 + ruote (ruote-kit) + quaderno > (http://github.com/jmettraux/quaderno) application at : > > http://github.com/jmettraux/theboard > > It's very incomplete (especially CSS-wise) for now, but it should get better. > > It combines task management and form management. The auth/auth model is > minimal (meant to be replaced by whatever suits your needs). > > It should become a good ruote example. > > Stay tuned, > > -- > John Mettraux -http://jmettraux.wordpress.com > > P.S. InfoQ has an article about ruote :http://www.infoq.com/news/2010/10/ruote -- you received this message because you are subscribed to the "ruote users" group. to post : send email to [email protected] to unsubscribe : send email to [email protected] more options : http://groups.google.com/group/openwferu-users?hl=en
