Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] Property View selection dialogs

Hello Tristan, hello all,

 

 

A lot of changes have occurred on the 0.9 version regarding the Content providers (We were going in the same direction, but only on the trunk). And we’re still planning to add a LabelProvider service.


Actually, the property view should not look *exactly* like the ModelExplorer, especially regarding the “read only” customization: it is grayed in the ModelExplorer (Because it cannot be edited), which is fine, but it should remain black in the Property view (Because it can still be selected). Having grayed primitive types in the property view can be really confusing.

 

So, most facets/custom should be shared, but not all of them. Thus, we need a finer customization grain than just use the same Label/Content provider between the two views.

 

The same goes for the ContentProviders: if you’re using the “Diagrams” view in the ModelExplorer (Only show diagrams, in a flat view), you cannot reuse the same content provider in the property view (Because you cannot browse the model from that view). Once again, we can have slightly different needs for different cases (With a lot of common things).

 

On the trunk, the LabelProvider service has not been implemented yet, and the CustomizationManagers are not correctly handled (We currently have only one customization manager, shared by all instances, while we should have at least one CM by context).

 

The following bug had been opened:

 

359794: [UML - Tools] Content/Label providers

https://bugs.eclipse.org/bugs/show_bug.cgi?id=359794

 

(It is tagged as UML, but the base implementation is generic enough to be used by all content providers)

 

 

I will have a look at your patch tomorrow and see what we can reuse on the trunk.

__________________________

Camille Letavernier

+33 (0)1 69 08 00 59 - camille.letavernier@xxxxxx

CEA LIST - Laboratoire d'Ingénierie dirigée par les modèles pour les Systèmes Embarqués (LISE)

 

De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de FAURE Tristan
Envoyé : jeudi 1 mars 2012 18:21
À : Papyrus Project list; FAUDOU Raphael; VELTEN Mathieu; DAUSSY Arthur; FAURE Tristan
Objet : [mdt-papyrus.dev] Property View selection dialogs

 

Hi,

We have currently implemented the bug #372993, the aim is having in the different dialogs of the property view (type selection for example) the same look and feel of the model explorer view.

 

If a facet in the model explorer view displays the elements in red we want to have the same behavior in the different tree dialogs.

We have commited this to the 0.8.X branch I just tried to commit it on the trunk but some of the classes of the property view are not present. (for example GraphicalModelExplorerBasedContentProvider)

 

Is it because these classes have been moved ? erased ? not yet migrated ?

 

Regards

 

Tristan FAURE

 

 


Ce message et les pièces jointes sont confidentiels et réservés à l'usage exclusif de ses destinataires. Il peut également être protégé par le secret professionnel. Si vous recevez ce message par erreur, merci d'en avertir immédiatement l'expéditeur et de le détruire. L'intégrité du message ne pouvant être assurée sur Internet, la responsabilité du groupe Atos ne pourra être engagée quant au contenu de ce message. Bien que les meilleurs efforts soient faits pour maintenir cette transmission exempte de tout virus, l'expéditeur ne donne aucune garantie à cet égard et sa responsabilité ne saurait être engagée pour tout dommage résultant d'un virus transmis.

This e-mail and the documents attached are confidential and intended solely for the addressee; it may also be privileged. If you receive this e-mail in error, please notify the sender immediately and destroy it. As its integrity cannot be secured on the Internet, the Atos group liability cannot be triggered for the message content. Although the sender endeavors to maintain a computer virus-free network, the sender does not warrant that this transmission is virus-free and will not be liable for any damages resulting from any virus transmitted.


Back to the top