| Re: [e4-dev] MDialog and MWizard |
Hi,
I've started looking once more into this topic and would propose the
following changes to the model:
a) Make MDialog a subclass of MElementContainer it makes no sense to
inherit the mainMenu stuff from MWindow, if you want something with
a menu create an MWindow
b) Add a mew marker class MDialogElement who extends
MApplicationElement which is implemented by MPart, MCompositePart,
MStack and MSashContainer
c) Make MWizard a subclass of MElementContainer - the reason not
inherting from MDialog is that I only want to allow very specific
elements
d) Add a new marker class MWizardElement who extends MUILabel and is
implemented by MPart and MCompositePart
This would give use:
interface MDialogElement {}
interface MWizardElement extends MUILabel {}
interface MDialog extends MElementContainer<MDialogElement> {}
interface MWizard extends MElementContainer<MWizardElement> {}
I'd still leave all those model elements marked as NONE API for Mars but
once we are confident they work as intended we should promote them as
API. Objections?
The bug for the development is
https://bugs.eclipse.org/bugs/show_bug.cgi?id=460826
Tom
--
Thomas Schindl, CTO
BestSolution.at EDV Systemhaus GmbH
Eduard-Bodem-Gasse 5-7, A-6020 Innsbruck
http://www.bestsolution.at/
Reg. Nr. FN 222302s am Firmenbuchgericht Innsbruck
_______________________________________________
e4-dev mailing list
e4-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/e4-dev