Modeller vs Designer

[pankajtandon]

Hi,
I'm looking to extend the GUI components in the pallette that are available in the Eclipse plugin (Designer) and the KIS BPM Modeller so that my end users have a smaller set of widgets to work with.
But I'm seeing similar functionality in both tools and I am not sure which to extend.. the plugin or the modeller. I understand that the explorer is pretty much a Reference Impl, but it's pretty darn good and I suspect that it may be easier to extend.

Any pointers on which one I should focus on and how can I go about this task (docs for extending the components)?

Thanks!

[trademak]

Hi,

We provide a web based modeler and an Eclipse plugin because we think they but have their use cases.
So it's really up to yourself which one you would choose. We will continue development efforts on both tools.
For extending the palette for the Designer we already have a large section in the user guide.
For the Modeler this needs to be done still, but a community member (m2spring) will create a Wiki for it (see this post)

Best regards,

[m2spring]

Incrementally extending the Designer is pretty easy.
You can follow this example:
[img]https://github.com/jenkinsci/jenkow-plugin/tree/master/jenkow-designer-extension[/img]

Incrementally extended the Modeler is not possible at this point.
I'm working on adding a new task type ("Jenkins task") into the Modeler here:
https://github.com/m2spring/Activiti/tree/jenkow-0.3.0
Take a look here, too:
http://docs.codehaus.org/display/ACT/Extending+Modeler+with+new+task+type

The new task is working so far.
The missing functionality is the import of BPMN files.

-Max

[pankajtandon]

Hi m2spring,
Thanks a lot for the pointers.
Altho' I cannot get to the link that tells me how to extend the Designer (broken image)

Can you please repost that link?

Thanks!