|
Re: Documentation for adding new Runtime [message #1587719 is a reply to message #1587377] |
Tue, 27 January 2015 14:20 |
|
Hi Adam,
I have been meaning to write some developer documentation (other than the videos) but unfortunately bug fixing has taken precedence. As a result, the code has changed but the documentation hasn't - sorry
The best I can suggest at this time is to look to the existing example plugins. It's probably best to use the jBPM runtime plugin as your template because I'm not even sure the other examples are working properly with all of the recent changes in the editor code, as I haven't tested those recently.
I really, really want to find the time to write some decent developer manual, but as I said bug fixing and release schedules always seem to get in the way.
If you have specific questions, I can point you in the right direction. For example, to limit the types of Activities available on the palette have a look at the <toolPalette> extension point section. Not sure what you mean by "configuration parameters" though - are you talking about User Preferences or BPMN2 element extension attributes/elements?
HTH,
Bob
|
|
|
|
Re: Documentation for adding new Runtime [message #1591518 is a reply to message #1590270] |
Thu, 29 January 2015 15:27 |
|
You're welcome
BTW, take a look at the Runtime Extension schema file org.eclipse.bpmn2.modeler.core/schema/org.eclipse.bpmn2.modeler.runtime.exsd (use the "Preview Reference Document" link on the top-right corner of the Eclipse Extension Point Schema Editor.) This contains some useful information about the extension points. One thing you may want to try right away, is to use a ".bpmn2config" file to test out your extensions. Essentially, you can just paste the XML snippets that would normally go into your extension's plugin.xml, into XML files in a folder called ".bpmn2config" in your runtime workbench. Once you get those working as you like, you can paste them back into your plugin.xml.
Note that some extensions may require a restart of the editor (not necessarily the workbench) to take effect. Also note that if you change the extension attributes & elements from one editor session to the next, you may not be able to open existing bpmn2 files created with the old extensions, since the parser won't recognize the old elements & attributes anymore.
Cheers,
Bob
|
|
|
Powered by
FUDForum. Page generated in 0.03638 seconds