But if we want to support that, then we cannot assume there is a way to access an application-global menu from a DeskBar or something similar.
In general what I’m trying to say: when you add more flexibility, you cannot push each working mode to the full potential. Because either users wanting a no-screenspace-wasted, keyboard driven system, will complain that they have no way to use an application-global menu. Or, we don’t have said menus, and users of the DeskBar will keep requesting that nice feature. Which we can’t use because of some other users with a different workflow.
I’m not saying we shouldn’t try to do something that works for everyone. I’m just trying to point out where the difficulties may arise. There can be ways to solve this that makes it usable in all cases, in a consistent way for everyone. What’s important is that the goal of Haiku is to provide a coherent user interface, this simplifies the lives of app developers because they can rely on some features being there, and they can design their UI on that common base. The more you make things configurable, the more this common base shrinks. And the smaller that common base gets, the more apps will tend to reinvent things that should be handled by the system, because they can’t be sure how the system will make it available to users and wether this is suitable for their needs.
This is why we have to be careful with making everything configurable. Again, it does not mean we should not allow configuring anything. It is something we have to keep in mind when considering making something configurable, to make sure we keep our consistency, which is a key selling point for Haiku (and yes, also for Gnome 3. They got this wrong by trying to cover too many use cases, namely desktops and tablets in their case. Which is why we focus only on desktop machines).