Re: [e4-dev] E4 / 4.0 Architectural Review

[Paul Webster <pwebster@xxxxxxxxxxxxxxxxxxx>]

On Thu, Sep 16, 2010 at 3:30 PM, Eric Moffatt <emoffatt@xxxxxxxxxx> wrote:
>
> There's a new wiki page at
>
> http://wiki.eclipse.org/E4/40Review


Thanx Eric for putting together this page. Three areas that I'd like to address:

Menus/Toolbars: https://bugs.eclipse.org/bugs/show_bug.cgi?id=325392

Our new system has some interesting attributes, but also causes a lot
of discrepencies especially when applied to the compatibility layer.
We're going to look at having the MenuManager/ToolBarManager be the
rendering implementation for the menu/toolbar model.

----
Making data (variables) available at all the right levels:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=326182

One of the design guidelines that the hierarchical IEclipseContext was
to provide was "ask the context a question, and you will get back an
answer appropriate for where you've asked the question".   It turns
out that providing data in this system becomes quite complex, because
of the need to make even the simplest piece of data available at the
MApplication level so it can be consumed by the keybindings, or
application level scripting.  We should re-think this strategy and
provide new guidelines.

----
Making services available at the right levels:
https://bugs.eclipse.org/bugs/show_bug.cgi?id=326190

We need to refine our pattern for contributing services, especially
ones that need to be distributed across the various levels (MWindow
and MParts, mostly).  We don't take advantage some mechanisms (like
add-ons) and instead hard-code a lot of services at each level in
compatibility classes:initializeDefaultServices()

If you have thoughts on the above subjects, please read through the
bugs and comment thereon.

PW

-- 
Paul Webster
Hi floor.  Make me a sammich! - GIR