It should be possible to build the camunda modeler standalone product via tycho to achive as much automation as possible.

Hi Nikku,

This project is really amazing. The only missing piece I think is the xml editor.
Could you add a tab under the diagram called "source" so that we can switch to the xml source when needed.

It should be possible to open files

• via drop into the modeler
• via double click on a file (e.g. on Windows Open As -> ...)

Only one script invocation should be needed to generate windows installers based on the new build infrastructure created in #15.

I would like to have the possibility to generate a png aside my opened bpmn (original folder).

It should be the default behavior to create the internal workspace in user space, i.e. not in the PROGRAM_FILES directory in windows (or other OSs).

The user should be allowed to save a diagram to the file system (rather then the Eclipse project tree) via the "save as" menu item, as this is the expected action by a non-Eclipse user.

A native installer could take care of

• associating open files
• creating desktop shortcuts
• creating uninstaller
• creating Startmenu entries

The graphical user interface should be cleaned up and offer a preconfigured modeling friendly view.

Some ideas:

• Do not show project explorer per default
• Show property panel and problems tab per default
• Fix tool bar (remove spaces and perspective switcher)
• Cleanup menus

It should be possible to easily install the modeler on Ubuntu / Debian, including:

• Update (via file override?)
• Uninstall
• Register as application
• Link to .bpmn files

Add a simplified palette that contains only the following elements

• Start Event
• End Event
• Task
• Exclusive Gateway
• Parallel Gateway
• Sequence Flow
• Sub-Process
• Throwing Intermediate Event
• Boundary Event
• Text Annotation

Investigate branding / styling for the distribution.

• Splash screen
• Logo
• ...

Hi Nikku,

this is not really an issue, but a couple of questions I have. I am pretty new to Github, so if there is any other way to start a discussion, please let me know.
First of all, I'm glad that you started this project, thanks! I think I remember you from the Yaoqiang discussion. As Yaoqiang is dead (IMHO), we need another open-source standalone BPMN editor. Forking one of the existing Eclipse plugins seems to be a good way to go.
Though I am not a really good Java programmer, I would like to contribute as much as I can, but before I have some general questions:

• Organization: Will this be a "one man show" or is your intention to get a community? What are the measures to attract other contributors? Could there be support from the Camunda community.
• What is the technical connection between Camunda Modeler and this project? Is the purpose of this project just to strip down Camunda Modeler or will new features also be implemented? How are new features in Camunda Modeler are brought into this project, is much manual work neede.
• Why Camunda and not Activiti? (Non-judging question)

I guess your answers of these questions might be valuable to other potential contributors as well, an could be written on the front page.

Thanks

Marvin

It should be possible to build the standalone modeler for multiple platforms via the product configuration.

Search through all elements for unused context pad options and remove them.

It should be possible to create model files outside of a workspace.
This would round up the non-workspace story.

Remove camundaBPM / engine / execution specific extensions as these are too complicated for starters.

alternatively

Do not show properties panel.