|[platform-ui-dev] Defining the e4 default workbench model and contribution mechanism|
There was a brief discussion  of this topic earlier in the e4 mailing list, and I'd like to bring it up again.
The e4 workbench model gives us much greater flexibility in composing a workbench. Up to now, the focus has been on defining the model structure and ensuring adequate flexibility. RCP apps will have all kinds of flexibility. However, we still need to define what the default e4 workbench model/layout will be, and how bundles contribute to this model. Do we still have perspectives and a perspectiveExtensions contribution mechanism? Do we loosen up the structure of perspectives? How do bundles define their participation in a layout?
I've opened a bug to gather ideas and track the discussion. Please watch this bug and respond there with your thoughts.