Miro Spönemann

Sounds feasible.

No idea 🤷‍♂️

It might make sense to move the hierarchy handling computation to LayoutAlgorithmResolver.

> I would even go further: it may be the only way to get people to contribute _at all_. I agree. > I felt working on and debugging an algorithm...

IDE-based tooling should probably stay in Eclipse Platform to avoid reimplementing stuff. But it would be great to add platform-independent (CLI-based) tooling that you can use anywhere. A big question...

Are you using the UI provided by ELK, e.g. the Layout toolbar button and the Layout view?

A possible way forward could be to extract everything Eclipse related into a separate repository built with Tycho, and to build the core repository with plain Maven or Gradle. But...

Yes, the code should stay at the Eclipse Foundation. You can request a new GitHub repository at the Help Desk: https://gitlab.eclipse.org/eclipsefdn/helpdesk I might be able to help with setting up...

Looks interesting! 👍

Proposal 1: ``` requires myOption in { MyEnum.VALUE1, MyEnum.Value2 } ``` Proposal 2: ``` requires myOption == MyEnum.VALUE1 or myOption == MyEnum.VALUE2 ``` Proposal 3: ``` requires myOption == MyEnum.VALUE1...