to the palette data. (note the palette populating code has 3 data sections: level 1, level 2 and “debug”. Right now, all 3 end up getting dumped into a single palette. We expect someone
building a real BPMN editor out of this sample will put more work into a rational palette design than
But… to your questions… I think everything you want is there… here is a screenshot of the currently shipping sample with stuff just pulled out of the palette (with one exception… the timer
boundary event is added via a context-menu on the activity)
BPMN editors have a lot of User interface that isn’t part of the OSF spec. For example, many pop up little special link creating symbols when you select a node that make it possible to create a link to a new node without dragging from the palette. That’s all stuff you can do in GoJS (see our grafcet sample) but we have decided not to complicate the BPMN sample with that.
But… if we are missing something you need, please let us know. That’s part of how priorities get set around here.