Am 08.11.2013 14:48 schrieb "Paul Elder" <pel...@ca.ibm.com>:
>
> Eric Moffatt  and I are planning a number of E4 model changes for next
week (M4). Our initial cut is below:
>
> * Change MCompositePart to extend MGenericTile<MPartSashContainerElement>
rather than MPartSashContainer. (This is so that MCompositePart will extend
only one concrete type, namely MPart. In implementing split editors/views,
Eric found that the MPart/MPartSashContainer ambiguity caused some
problems.)
> * Deprecate MInputPart and MInput.
>      * Question: Is there need for an 'inputSpec' attribute on MPart? (A
replacement for MInput's inputURI attribute.)

+1, this would help for simple editor input scenarios.

> * Create MWizard and MDialog classes (that extend MWindow), and add
corresponding collection attributes on MApplication
>      * Question
>           * Is there need for new attributes on these classes?
>           * Is there need for MWizardPage, too? (It seems to me that
MWizard's 'children' being mapped to the wizard's pages is sufficient.)
>

Would be nice to see a prototype how the new model elements would be use. I
assume we would have modelService.show(dialog, modular) or something like
that?
_______________________________________________
e4-dev mailing list
e4-dev@eclipse.org
https://dev.eclipse.org/mailman/listinfo/e4-dev

Reply via email to