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

Bug 359794

Summary:	[UML - Tools] Content/Label providers
Product:	[Modeling] Papyrus	Reporter:	Camille Letavernier <cletavernier>
Component:	Core	Assignee:	Project Inbox <mdt-papyrus-inbox>
Status:	CLOSED FIXED	QA Contact:
Severity:	normal
Priority:	P3	CC:	vincent.lorenzo
Version:	unspecified
Target Milestone:	---
Hardware:	PC
OS:	All
Whiteboard:

Description Camille Letavernier

2011-10-04 03:43:06 EDT

Currently, we have a lot of different Label providers for UML, and a few Content Providers for specific tasks.

They are dispatched in different plug-ins (umlutils, diagram.common, properties.uml, ...)

Most of them handle a subset of UML, and they are either compatible with EMF Facet custom tree, or with standard EObject. The problem is that the EMF Facet Customizable Label Provider cannot handle pure EObjects, while the standard EMF Label Provider cannot handle EMF Facet objects.

It would be nice to have a single Label Provider for the whole UML Metamodel, compatible with both EMF Facet objects and standard EObjects ; and a standard ContentProvider (or two, for the properties typed by a Stereotype). They should also extend the standard EMF Providers (Which is not always the case currently).

Comment 1 Camille Letavernier

2012-01-12 11:40:28 EST

The new content provider tools have been committed in r6837.

The content providers are now divided in three main components :

- The semantic provider, which provides a complete tree (potentially infinite), and, for each value, indicates whether it is valid or not (IHierarchicContentProvider) for the edited EObject/Feature pair.
- The browse strategy, which is a filter for this tree, and implements an optimized search/reveal algorithm
- The graphical provider, which adds a text filter and an History (Related to the search-feature from the browse strategy), to handle user interactions

Implementations have been provided for UML and Profiles. They have been integrated in the Property view.

The EMF Implementation is not complete, and has not been integrated in the Property view.

The content provider has not yet been integrated to the ModelExplorer.

Comment 2 Vincent Lorenzo

2017-09-26 15:45:56 EDT

Many work has been done since 2012. I close this bug and we will reopen new one when required.