Can somebody explain me why there is an MPart and a MPartDescriptor interface? What is the idea behind these two interfaces? What is the technical distinction?
The difference between those is similar to the one between Class and
Object in Java. MPartDescription is the blueprint for MPart instances
who are the instances you add to your UI-Structure (e.g. as children of
an MPartStack).
If you look at the ShowView-Menu you see all registered MPartDescriptors
and clicking on one of those the system creates an MPart-instance from
them and places them into the UI-Structure.
You can also compare them to ViewDescriptor/EditorDescriptor in 3.x and
their real UI counterparts ViewPart and EditorPart.
Tom
Am 11.08.10 08:37, schrieb Heiko:
> Can somebody explain me why there is an MPart and a MPartDescriptor
> interface? What is the idea behind these two interfaces? What is the
> technical distinction?
On a second thought maybe the Class-Object comparison is not a good one.
It is more of a Template => Instance relation.
MPartDescriptor is the template we use to create MPart-instance from, if
you look at the interfaces closely you'll notice that MPart-derives from
UIElement and MPartDescriptor only from ApplicationElement.
Tom
Am 11.08.10 08:52, schrieb Tom Schindl:
> Hi,
>
> The difference between those is similar to the one between Class and
> Object in Java. MPartDescription is the blueprint for MPart instances
> who are the instances you add to your UI-Structure (e.g. as children of
> an MPartStack).
>
> If you look at the ShowView-Menu you see all registered MPartDescriptors
> and clicking on one of those the system creates an MPart-instance from
> them and places them into the UI-Structure.
>
> You can also compare them to ViewDescriptor/EditorDescriptor in 3.x and
> their real UI counterparts ViewPart and EditorPart.
>
> Tom
>
> Am 11.08.10 08:37, schrieb Heiko:
>> Can somebody explain me why there is an MPart and a MPartDescriptor
>> interface? What is the idea behind these two interfaces? What is the
>> technical distinction?
>
On a second thought maybe the Class-Object comparison is not a good one.
It is more of a Template => Instance relation.
MPartDescriptor is the template we use to create MPart-instance from, if
you look at the interfaces closely you'll notice that MPart-derives from
UIElement and MPartDescriptor only from ApplicationElement.
Tom
Am 11.08.10 08:52, schrieb Tom Schindl:
> Hi,
>
> The difference between those is similar to the one between Class and
> Object in Java. MPartDescription is the blueprint for MPart instances
> who are the instances you add to your UI-Structure (e.g. as children of
> an MPartStack).
>
> If you look at the ShowView-Menu you see all registered MPartDescriptors
> and clicking on one of those the system creates an MPart-instance from
> them and places them into the UI-Structure.
>
> You can also compare them to ViewDescriptor/EditorDescriptor in 3.x and
> their real UI counterparts ViewPart and EditorPart.
>
> Tom
>
> Am 11.08.10 08:37, schrieb Heiko:
>> Can somebody explain me why there is an MPart and a MPartDescriptor
>> interface? What is the idea behind these two interfaces? What is the
>> technical distinction?
>