A new C++ editor is a good idea and often repeated, but it would need a dedicated person or several. In the past I've suggested to make a separate editor project, which would be good for keeping the responsibility separate, but may not be good for adoption. Having the editor come with the engine codebase would make it clear that it's "official". However what I really don't want to see happening is a one-time contribution and dump of a C++ editor into the main codebase, after which the contributor becomes inactive, and the workload for existing maintainers grows. This is a development antipattern which has repeated quite many times in Urho history, and why I'd like to keep my personal maintenance responsibility strictly in the "runtime" part of the engine.