Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 353547

Summary:	[Property View] Add support for custom Label Provider in the property view header
Product:	[Modeling] Papyrus	Reporter:	Camille Letavernier <cletavernier>
Component:	Core	Assignee:	Camille Letavernier <cletavernier>
Status:	RESOLVED FIXED	QA Contact:
Severity:	enhancement
Priority:	P3
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	Windows XP
Whiteboard:

Description Camille Letavernier

2011-08-02 05:01:13 EDT

Currently, the user can customize the content of the property view. However, the property view header is specified in the Editor's extension point.

There should be a common Label Provider for all editors using the Customizable property view, which could be extended through an extension point, independently from the editor plug-in.

Comment 1 Camille Letavernier

2011-09-08 10:50:57 EDT

Partially done in r5409 (Branch 0.8.X)
Merged to the trunk in r5410

The extension point has been created.

The right label providers now need to be implemented and registered to this new extension point, with the right priorities.

Comment 2 Camille Letavernier

2011-09-19 05:48:47 EDT

Improved in r5499 (Branch 0.8.X)
Merged to the trunk in r5500

The registered label providers are still in conflict with the ones registered by the UML Diagrams. Moreover, some Label Providers are only compatible with certain types of editors ; we should avoid instantiating them systematically.

We should also check if the LabelProviders are disposed after usage, once the property view is disposed (Currently, the same instance of label provider is used everytime ; if a specific label provider implements the dispose() method, this may lead to an inconsistent state)

Comment 3 Camille Letavernier

2011-10-03 09:17:03 EDT

An old extension (from oep.tabbedproperties.core) is conflicting with the customizable label provider.

Extension removed in r5672 (Branch 0.8.X)
Merged to the trunk in r5673

TODO : The whole plug-in is probably deprecated. It only contributes two extensions and a Label Provider.
We should check the dependencies before moving it to the deprecated folder.

Comment 4 Camille Letavernier

2012-06-21 09:48:21 EDT

Fixed