Hey everybody,
I’d personally like to gradually phase out the old UI, though I feel it might be too early to completely get rid of it with 4.0.0 - as there are still edge cases which are better supported in the old UI. So my suggestion would be:
- in 4.0.0, disable the old UI completely by default; and you need to switch on a setting in order to make it still reachable - something like: “enableDeprecatedOldUi” or s.th. like this.
- this way, package authors should be fine to only support the new UI from now on.
From my experience, when running in well-maintained new Neos projects, running the new UI is usually without any problems.
I’ve seen some problems when running the new UI just as a drop-in replacement for the old UI in some projects; the main issue usually being that we load JS in the new UI on every page load; but in the old UI it is only loaded initially. Because of this, the behavior with the new UI might be more sluggish compared to the old one, if your JS delays loading the page for a longer time f.e…
Regarding the event sourced CR: There, we’ll only support the new UI - but at Neos Con we’ll release a Technology Preview; so that means the event sourced CR will definitely not land in 4.0.0.
All the best,
Sebastian