On Tue, Jan 13, 2009 at 11:13 PM, Diego Moreno <[email protected]> wrote: > > I have just seen ruote-forms subproject. It looks very interesting. I wonder > how you will integrate it into workflow language, because as you know we are > doing something similar. Is there some documentation about it?
Hi Diego, ruote-forms is just a naive / rudimentary generic form handler. There is for now no documentation about it (it's quite straightforward as well). Ruote-forms is a plain javascript library you can glimpse at how it's used via http://github.com/jmettraux/ruote-forms/blob/master/public/index.html (RuoteForms.renderForm('div_name', json_data)). There is no integration at all for it in the workflow language. Currently the only way to influence 'forms' via the engine/participant is via the filters : http://openwferu.rubyforge.org/expressions.html#exp_filter http://openwferu.rubyforge.org/expressions.html#exp_filter_definition I'll probably adapt ruote-forms to make it follow the directives in the filters (passed in the workitem) (did some work about that today http://github.com/jmettraux/ruote/commit/fd48192a94649b0b35ee144b3c6687cb690a4248). As I write these lines, ruote-web2 form handling is limited to a text area for editing the JSON representation of the workitem payload. Ruote-forms intends to replace that textarea approach. But, in my opinion, the 'form' engine should be pluggable, determined by participant and/or workitem, like : <participant ref="toto" form="http://server.example.com/forms/customer_order.xform"; /> for example. The form selection could as well be hidden from the engine, left to the "worklist" part of the application (why not use a decision table / rule engine to select the form to use based on the participant, the workflow name/revision and the payload...) I'm trying to avoid having 'form' stuff in the process definition language itself (a bit like when we try avoid to have style directives within HTML documents). As hinted by the form attribute above, xforms (thanks to firefox) could be used (https://developer.mozilla.org/en/XForms) for forms smarter than the default ones proposed by ruote-forms. Ruby makes it easy for people to plugin the logic they need, they can do the last mile the way they want. What do you think ? By the way is the work of your team available / visible somewhere ? Kind regards, -- John Mettraux - http://jmettraux.wordpress.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruote (OpenWFEru) users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/openwferu-users?hl=en -~----------~----~----~----~------~----~------~--~---
