2.0.0 ideas

[nk-coding]

As mentioned in #488 , some ideas for the 2.0.0 release.
Just to be clear, all of these are just ideas, I'm totally fine with these being not implemented.
I would be willing to help contribute such features if desired.

• ESM build
• dependency updates
  • inversify 7.x.x (that's a breaking change, but I guess a new major version would be a good point in time to do this)
  • snabbdom 3.6.x (?, would likely require migration to pure ESM module, maybe not desired)
• maybe: make set-model a standalone feature to allow easier extension (there may be reasons why this is not the case currently)
• snapping when dragging elements (like PowerPoint, draw.io, countless others)
  • should likely be an optional feature
  • when I implemented it, I based my implementation on the Excalidraw implementation, but I could imagine this is not an option here
• touch support for more handlers (currently, basically only dragging the viewport is supported)
• Extract IMouseListener (Extract IMouseListener #478)
• adding pointer capture support for dragging (Pointer capture support #485, already tracked for 2.0.0 milestone)

[spoenemann]

👍 to (almost) all of these!

• I think we should migrate the codebase to ESM.
• Could you explain this one a bit more?

make set-model a standalone feature to allow easier extension

• There's already an interface for snapping and a simple grid implementation; it's applied in move.ts

[nk-coding]

• currently, the SetModelCommand is in base/features and directly declared in the defaultContainerModule, making replacement (and thus extension with custom features) more difficult as you cannot just omit a set-model module. I would propose adding a new module in features/set-model (or so), which then could more easily be replaced
• I thought more of snapping to other diagram elements, including some helper lines. This could then be an additional class implementing ISnapper. More or less what GLSP already has. But I can understand that this is maybe out of scope for this project, and if users need it, they could potentially use the GLSP feature. Also I don't know if this was maybe already discussed in the past

[spoenemann]

currently, the SetModelCommand is in base/features and directly declared in the defaultContainerModule, making replacement (and thus extension with custom features) more difficult as you cannot just omit a set-model module. I would propose adding a new module in features/set-model (or so), which then could more easily be replaced

It's already easy to replace the command implementation:

rebind(SetModelCommand).to(MyCustomSetModelCommand);

I thought more of snapping to other diagram elements, including some helper lines. This could then be an additional class implementing ISnapper. More or less what GLSP already has. But I can understand that this is maybe out of scope for this project, and if users need it, they could potentially use the GLSP feature. Also I don't know if this was maybe already discussed in the past

That would be a great feature to have in Sprotty, too! So yes, if possible this should be done as an ISnapper implementation.