Bug 139767 - Model View for the UML editor example
Summary: Model View for the UML editor example
Status: NEW
Alias: None
Product: GMF-Tooling (ARCHIVED)
Classification: Modeling
Component: Samples-UML (show other bugs)
Version: unspecified   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Michael Golubev CLA
QA Contact:
URL:
Whiteboard:
Keywords: plan
Depends on: 112818
Blocks:
  Show dependency tree
 
Reported: 2006-05-02 13:30 EDT by Ferad Zyulkyarov CLA
Modified: 2013-05-12 14:04 EDT (History)
7 users (show)

See Also:


Attachments
navigator plugin (118.62 KB, application/x-zip-compressed)
2007-11-02 13:48 EDT, Dave Carlson CLA
no flags Details
plugin with shared editing domain (34.63 KB, application/x-zip-compressed)
2007-11-02 13:50 EDT, Dave Carlson CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ferad Zyulkyarov CLA 2006-05-02 13:30:12 EDT
It would be nice if the example UML editor plugin implements a model view. The model view will visualize the UML model as tree view. Users will be able to pick a classifier from that model and put it on the diagram editor. Also users should be able to change the underlying UML model directly from the UML Model View.
Comment 1 Alex Shatalin CLA 2006-05-02 13:33:42 EDT
This request could be implemented as a part of CommonNavigator implementation.
Comment 2 Artem Tikhomirov CLA 2006-05-16 12:31:28 EDT
Updated Version field to indicate next release.
Comment 3 Richard Gronback CLA 2006-11-09 22:30:28 EST
Updated target milestone
Comment 4 Alex Shatalin CLA 2007-03-20 17:18:57 EDT
Read-only part of this request supported by tooling from now see bug #112818
Comment 5 Dave Carlson CLA 2007-11-02 13:46:49 EDT
I have implemented a common navigator for UML Tools that is reasonably complete and very useful (for me and my users).  I attached the source for this navigator plugin to this bug.  I have not yet figured out how to add drag/drop from the navigator to a class diagram, but will work on that.

I propose that all navigators be removed from each diagram type, and are replaced by one navigator plugin.  There is no point having completely redudant navigator code in each diagram.

This code depends on a shared editing domain used by the navigator and all diagrams.  If you use my attachments by themselves, you will have a good navigator, but edits and command undo/redo will not be shared by the diagrams. See: https://bugs.eclipse.org/bugs/show_bug.cgi?id=189974

Functionality of my attachment includes:
* Extends SaveablesProvider to track modifications and prompt model saves
* Adds a few view filters (e.g. hide Association or Comment)
* virtual folder to group Associations
* toolbar and context menu support for delete/cut/copy/paste

I'm still learning how to implement some of these capabilities, so there is certainly room for improvement.  To see a more complete tool where this integrated with the class diagram editor (and other support for XSD generation), see: 
  http://www.xmlmodeling.com/download/hypermodel-3.1/


Comment 6 Dave Carlson CLA 2007-11-02 13:48:15 EDT
Created attachment 81986 [details]
navigator plugin
Comment 7 Dave Carlson CLA 2007-11-02 13:50:09 EDT
Created attachment 81987 [details]
plugin with shared editing domain

This plugin is also submitted to bug:
  https://bugs.eclipse.org/bugs/show_bug.cgi?id=189974
But is required to install the navigator.
Comment 8 Dave Carlson CLA 2007-11-02 14:16:24 EDT
I should add that you must open a model in the shared editing domain to enable use of the navigator view.  To use the navigator by itself without a diagram, select the "Open Model" context command on a .uml file.  There is also a "Close Model" command on opened Model objects.

If/when diagrams are modified to use the shared domain, then the navigator will be expanded for a model automatically when a diagram is opened.
Comment 9 Michael Golubev CLA 2013-05-12 14:04:26 EDT
Batch Update: UML2Tools is sample component for GMF-Tooling after restructuring