[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
Re: [e4-dev] Working with modeled UI and HEAD
|
Am 29.11.10 17:10, schrieb Paul Webster:
> On Sat, Nov 27, 2010 at 5:05 AM, Tom Schindl
> <tom.schindl@xxxxxxxxxxxxxxx <mailto:tom.schindl@xxxxxxxxxxxxxxx>> wrote:
>
> The Addon-Element is generally a problem in this sense. What about the
> following.
>
> a) The addons are contributed through a ModelProcessor
> b) The model processor checks if there is a tag for the addon in the
> MApplication-Element e.g.:
> addon:org.eclipse.e4.ui.workbench.addons.swt:DnDAddon
> addon:org.eclipse.e4.core.commands:CommandServiceAddon
> ...
> and only then contributes this addon.
>
> This way the one defines the Addon-Handler-Class is also the one who
> contributes the
> addon-element.<https://dev.eclipse.org/mailman/listinfo/e4-dev>
>
>
>
> The problem with extension points is they are read in an arbitrary
> order. Control of the ordering of this kind of thing has been a
> complaint on the RCP and/or Product side for a long time. If they go in
> the model, then document order controls them.
>
That's not completely true in the our ModelAssembler we do a sorting by
evaluating the dependencies between the contributing bundles.
So if e.g. keybindings has a dependency on commands e.g. then it is
guaranteed by this algorithm that the commands contributions are
processed before the keybindings ones!
I think Oleg or Brian wrote the algorithm.
Tom
--
B e s t S o l u t i o n . a t EDV Systemhaus GmbH
------------------------------------------------------------------------
tom schindl geschaeftsfuehrer/CEO
------------------------------------------------------------------------
eduard-bodem-gasse 5/1 A-6020 innsbruck phone ++43 512 935834