[jbpm-dev] form builder updates and requirements gathering

[Maciej Swiderski]

Don't know if it is already in scope or implemented but would be great 
to have wizard (multi form) based task forms

Cheers

On 17.05.2012 17:27, Mauricio Salatino wrote:
> Tiho,
> Thank you very much for answering this email.
> The main problem with doing manual changes is that we have two things 
> that you can change:
> 1) the form model (this is a meta model abstract to the rendering 
> layer), I think that this one is easily accessible, but here you can 
> change structure only, not look and feel
> 2) depending the technology used to render the form is how the form 
> will look like, and because the form builder uses GWT to preview the 
> form, there is no easy way to manually edit GWT and propagate that to 
> the model and then all the rendering options.
>
> I think that providing manual changes for the structure and for the 
> CSS that will be applied, no matter the (web) technology that we are 
> using can provide huge flexibility.
>
> I'm still learning about this project but I will keep that in mind to 
> see how we can provide more features around that requirement.
>
> Cheers
>
> On Thu, May 17, 2012 at 12:18 PM, Tihomir Surdilovic 
> <tsurdilo at redhat.com <mailto:tsurdilo at redhat.com>> wrote:
>
>     On 5/17/12 8:31 AM, Mauricio Salatino wrote:
>>     Hi guys,
>>     I was working with the form builder these last couple of days and
>>     I manage to provide support for file system storage. Making the
>>     form builder independent from Guvnor. You now can change the
>>     repository via a spring configuration file and deploy the form
>>     builder component without the need of any other component being
>>     deployed.
>>
>>     Now when I was trying to create a simple web application that
>>     will host the form that was created inside the form builder, I've
>>     started finding that some more work needs to be done in order to
>>     provide external applications the right set of dependencies which
>>     includes the model, the services and the renderers required to
>>     display the form.
>>     For this reason, I've started breaking up the projects
>>     jbpm-form-builder and jbpm-form-builder-api into a more granular
>>     structure. As soon as I get this refactoring ready I will write a
>>     blog post that shows how people can set up the form builder to
>>     start creating your forms and how they can publish and consume
>>     these forms from a different application.
>>
>>     Besides, from the update I would like to take advantage of this
>>     opportunity to ask for feedback on this component and also for
>>     new requirements. What do you think that will be the most
>>     important requirements that we need to fulfill to satisfy a
>>     business user? Should we target technical users first? What do
>>     you expect from a component that is called Form Builder? All the
>>     inputs are valuable and will help me to scope my deliverables and
>>     deadlines accordingly.
>     Being able to create and test forms in-line with the process
>     modelling efforts (do not have to switch tools/screens/whatever)
>     IMO would be great to have.
>     Ability to make manual changes to the source generated by the Form
>     Build is also IMO very important but afaik mariano said that was
>     not easily possible to do.
>
>     Thanks.
>>
>>     Cheers!
>>
>>     -- 
>>      - MyJourney @ http://salaboy.wordpress.com
>>      - Co-Founder @ http://www.jugargentina.org
>>      - Co-Founder @ http://www.jbug.com.ar
>>
>>      - Salatino "Salaboy" Mauricio -
>>
>>
>>
>>     _______________________________________________
>>     jbpm-dev mailing list
>>     jbpm-dev at lists.jboss.org  <mailto:jbpm-dev at lists.jboss.org>
>>     https://lists.jboss.org/mailman/listinfo/jbpm-dev
>
>
>
>
> -- 
>  - MyJourney @ http://salaboy.wordpress.com
>  - Co-Founder @ http://www.jugargentina.org
>  - Co-Founder @ http://www.jbug.com.ar
>
>  - Salatino "Salaboy" Mauricio -
>
>
>
> _______________________________________________
> jbpm-dev mailing list
> jbpm-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbpm-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/jbpm-dev/attachments/20120517/f4bb4b44/attachment.html