Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] Tutorials on CNF
Title: Raphaël FAUDOU
It seems to make sense but I would like to have Kenn feedback.
Kenn, could you give us your feeling from your long experience now within Eclipse projects?
Thanks
raphaël

Jerome BENOIS a écrit : 
We are agreed.

Le mercredi 04 février 2009 à 14:40 +0100, GERARD Sebastien 166342 a
écrit :
  
Hi,

It is something interesting, but technologically, why we should use different technology/framework for both. TO my point, both are editors, they tree-based editor: the scope of the outline is then the content of the current diagram and the scope of the model explorer is then the model itself.
    
It seems the CNF (actual version without the https://bugs.eclipse.org/bugs/show_bug.cgi?id=235768 patch) isn't compliance with standard Outline view.
It seems that the CNF required the definition a new Eclipse View.
Indeed, I propose to write basic Outline with the standard eclipse ui framework, and an advanced Model Explorer with the CNF.

  
In addition, for the model explorer, I would like to have two kinds of model explorer: the physical model explorer that provides views of the file systems for the model (physical view of the model(s)) and the logical model explorer. This latter, as its name indicates it, provides a logical view of the model.
    
I also agree for physical (Resource Explorer) and logical explorer (Model Explorer).

Cheers,
Jérôme.

  
Cheers... Sébastien.




-----Message d'origine-----
De : mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de Jerome BENOIS
Envoyé : mercredi 4 février 2009 12:08
À : Papyrus Project list
Objet : Re: [mdt-papyrus.dev] Tutorials on CNF

Hi,

	Thanks Javier for tutorials links.

This morning, I study in depth Common Navigator Framework and I've a
crucial question for the Papyrus Team!

I think in the current implementation
(org.eclipse.papyrus.outline.emftree and org.eclipse.papyrus.outline) we
have confused the Outline and the Navigator Eclipse concepts. 

Indeed, I think we must have two distinct views in Papyrus perspective :
- The Outline view : containing a treeViewer with all semantics elements
of the current diagram open in the graphical editor and a thumbnail
birdview.
- The Model Explorer View (based of CNF) : provide a Navigator
containing the global treeViewer related to show the content of
DiResourceSet : 
	- the tree of all model elements,
	- with all diagrams
	- sorters capabilities (configured via CNF extension) : alphabetical
sorter ...
	- filters capabilities (configured via CNF extension) : Show Only
Diagrams, ...
	- actions capabilities (configured via CNF extension) : Create Diagram,
Rename, duplicate, delete ...
	- content provider capabilities (configured via CNF extension) : UML
Content Provider or dedicated content provider for an UML profile.

Thus, I propose to create a new plugin org.eclipse.papyrus.navigator to
add the Papyrus Model Explorer based on CNF.

What do you think about it ?

Jérôme. 

Le mercredi 04 février 2009 à 10:16 +0100, Francisco Javier Cano a
écrit :
    
  Hello,

  FYI, tutorials about the CNF I found quite helpful.

Building a Common Navigator based viewer, Part I: Defining the viewer
http://scribbledideas.blogspot.com/2006/05/building-common-navigator-based-viewer.html

Building a Common Navigator based viewer, Part II: Adding Content
http://scribbledideas.blogspot.com/2006/05/building-common-navigator-based-viewer_22.html

What does the Common Navigator Framework (CNF) help me do?
http://scribbledideas.blogspot.com/2006/06/what-does-common-navigator-framework.html

Building a Common Navigator based viewer, Part III: Configuring Menus
http://scribbledideas.blogspot.com/2006/06/building-common-navigator-based-viewer.html

Building a Common Navigator based viewer, Part IV: Object
Contributions
http://scribbledideas.blogspot.com/2006/06/building-common-navigator-based-viewer_18.html

Building a Common Navigator based viewer, Part V: Action Providers
http://scribbledideas.blogspot.com/2006/06/building-common-navigator-_115067357450703178.html

PDF versions now available!
http://scribbledideas.blogspot.com/2006/07/pdf-versions-now-available.html

Label Decorators in a Common Navigator Framework viewer
http://scribbledideas.blogspot.com/2006/07/label-decorators-in-common-navigator.html

  Regards,
  Javi

----
Francisco Javier Cano Muñoz
Programador senior
Prodevelop
www.prodevelop.es



_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
      
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev

    
_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev

--

Image Signature IOC Raphaël FAUDOU
 Responsable cellule Innovation / bureau méthodes
Head of Innovation & Method Definition
Atos Origin

Tel     : +33 (0)5 34 36 32 89
Tel     : +33 (0)6 10 53 50 44
Mail   : raphael.faudou@xxxxxxxxxxxxxx
Atos Origin
6, Impasse Alice Guy
BP 43045
31024 Toulouse Cedex 3

P Avant d'imprimer cet e-mail, pensez à l'environnement. 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 Origin ne pourra être recherché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 recherchée pour tout dommage résultant d'un virus transmis.
P Please consider your environmental responsibility before printing this e-mail. 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 Origin group liability cannot be triggered for the message content. Although the sender endeavours 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