Skip to main content

Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

Difference between revisions of "Modeling Ganymede M7 Review"

m (Installation)
(Startup)
 
(12 intermediate revisions by the same user not shown)
Line 10: Line 10:
 
* Standard Eclipse splash and welcome page (should be updated with Modeling project artwork?)
 
* Standard Eclipse splash and welcome page (should be updated with Modeling project artwork?)
 
* Initial perspective is Java (should be an [[AmalgamModelingPerspective]]?)
 
* Initial perspective is Java (should be an [[AmalgamModelingPerspective]]?)
 +
* CDO Weaver Notification pops up... apparently, enabled by default (best option?) [https://bugs.eclipse.org/bugs/show_bug.cgi?id=235415 235415]
 
* Many source features report invalid discovery sites <s>[https://bugs.eclipse.org/bugs/show_bug.cgi?id=228114 228114]</s> {{status|Fixed post-M7|green}}
 
* Many source features report invalid discovery sites <s>[https://bugs.eclipse.org/bugs/show_bug.cgi?id=228114 228114]</s> {{status|Fixed post-M7|green}}
* Installed Features list shows missing localization strings for *.m2m.qvt.oml source features {{status|Not in dialog in M7|red}}
+
* M2M QVT OML missing branding elements [https://bugs.eclipse.org/bugs/show_bug.cgi?id=231980 231908]
 
* About dialog: all are using proper modeling image, though some issues:
 
* About dialog: all are using proper modeling image, though some issues:
 
** GMF and UML2 Tools (documentation only) features missing buildId token replacement (shows @buildId@) [https://bugs.eclipse.org/bugs/show_bug.cgi?id=231420 231420] {{status|Fixed post-M7|green}}
 
** GMF and UML2 Tools (documentation only) features missing buildId token replacement (shows @buildId@) [https://bugs.eclipse.org/bugs/show_bug.cgi?id=231420 231420] {{status|Fixed post-M7|green}}
** All *.m2m.qvt.oml source plug-ins show provider as providerName and not Eclipse.org {{status|Not in dialog in M7|red}}
 
 
** UML2 Tools diagram plug-in naming scheme is inconsistent (Activity, Deployment, and Use Case should be prefixed with 'UML2' as are the rest)
 
** UML2 Tools diagram plug-in naming scheme is inconsistent (Activity, Deployment, and Use Case should be prefixed with 'UML2' as are the rest)
  
 
=== User Interface Contributions ===
 
=== User Interface Contributions ===
* Preferences
 
 
 
* Menus
 
* Menus
** Operational QVT Transformation & Library actions available on New menu within Package Explorer view of Java perspective (appropriate?)
+
** See M6 notes
** A Run -> Transformation... top-level menu item is available in all perspectives
+
 
* New Dialog
 
* New Dialog
** Eclipse Modeling Framework > EMF Model wizard would be more appropriately named 'EMF Generator Model'
+
** See M6 notes
** Eclipse Modeling Framework category contains no wizard to create a new Ecore model (found in Example EMF Model Creation Wizards category only)
+
** UML Model wizard found in Example EMF Model Creation Wizards category, with UML2 Tools diagrams found in UML 2.1 Diagrams category.  Why not have both in general 'UML 2.1 Modeling' category?
+
** Operational QVT example view, constraints, datatypes, rdb, and simpleuml models are available in EMF Model Creation Wizards category.  Move to Operational QVT category below Examples?
+
** Ecore Diagram is in the Other category.  With the Ecore Tools project available, and as this remains a GMF example, it should be moved to the Examples category?
+
** GMF-Xpand top-level category will eventually go away, but for now more appropriate under the existing Graphical Modeling Framework category?
+
** GMF wizard names could use some improvement.  How about:
+
*** New GMF Project -> GMF Project (strike the 'New' as it's redundant with dialog purpose and matches EMF counterpart upon which it's based)
+
*** Simple Graphical Definition Model -> Graphical Definition Model from Domain
+
*** Simple Tooling Definition Model -> Tooling Definition Model from Domain
+
*** Reconcile Graphical Definition Model -> Reconcile a Graphical Definition Model
+
*** Reconcile Tooling Definition Model -> Reconcile a Tooling Definition Model
+
*** Guide Mapping Model Creation -> Mapping Definition Model from Domain
+
*** Default subcategory -> Basic
+
*** GMFGen Model -> Generator Model
+
*** GMFGraph Model -> Graphical Definition Model
+
*** GMFMap Model -> Mapping Definition Model
+
*** GMFTool Model -> Tooling Definition Model
+
** Java Emitter Templates category has no wizard to create new JET Template?  (seems odd)
+
 
* Show View dialog
 
* Show View dialog
** GMF Dashboard is found in the General category.  Perhaps add a Graphical Modeling Framework category?  The dashboard is not very 'general'
+
** See M6 notes
** The Operational QVT category has a Metamodel Explorer view, which is fine.  As this view is not really QVT specific, but rather a general view for registered metamodels, perhaps it belongs in EMF itself?
+
  
 
=== UML Modeling===
 
=== UML Modeling===
Not looking for usability issues with the diagrams themselves, a few items stand out when creating and working with UML diagrams:
+
* See M6 notes
* The file extension for UML diagrams are rather long.  Perhaps an abbreviated form would be better, e.g. *.ucd instead of *umlclass_diagram?  Or, even just *.umlclass without _diagram would be better [https://bugs.eclipse.org/bugs/show_bug.cgi?id=230873 230873].
+
* Each of the right-click actions for creating a new UML diagram for a *.uml model file are also quite long.  Perhaps something like "Create UML Class Diagram" instead of "Initialize umlclass_diagram diagram file" would be better?  Also, why not have these off the '''New''' menu item?
+
* Under the *.uml model in the Project Explorer are 5 Package elements for a newly created Class diagram with no content was created, each showing the 4 default Element Imports [https://bugs.eclipse.org/bugs/show_bug.cgi?id=221223 221223].
+
* UML diagrams need a non-synchronized option, particularly the Class diagram [https://bugs.eclipse.org/bugs/show_bug.cgi?id=199731 199731].
+
* UML diagram creation wizards should allow you to select an existing *.uml model file and behave similarly to the "Initialize..." menu action, in this case.
+
 
+
=== GMF-based Diagrams===
+
* Perhaps opening the Properties view upon diagram creation is a sensible thing to do?  Having the Properties view open within a default Modeling perspective is another way to ensure it's open.  Otherwise, a user needs to right-click the diagram and select "Show Properties View"
+
* Add a File -> Save as Image... option to the main menu to augment the hard to find diagram right-click File -> Save as Image File... option.  Even an Export menu item would be more easily found.
+
  
 
== Additional Components ==
 
== Additional Components ==
 
Returning to the ganymede update site to install the remaining components in the Models and Model Development category, the following additional observations were made.
 
Returning to the ganymede update site to install the remaining components in the Models and Model Development category, the following additional observations were made.
=== Ecore Tools SDK ===
+
=== Installation ===
* Installed fine, features/plug-ins look fine (though not signed)
+
* In Review Licenses, most projects use the March 17, 2005 version of the license file, with the following exceptions:
* Contributes its own perspective (overkill?) with icon that needs transparent background
+
** Teneo, Net4J, and CDO use the January 28, 2004 version
** Modeling icon is used (too general?)
+
** EMF Compare and ATL use a non-standard file
** No default Show View menu contributions, or proper category in Open View dialog (both are in Other)
+
* Error on install using p2 [https://bugs.eclipse.org/bugs/show_bug.cgi?id=231172 231172]:
* Ecore Tools perspective is Resource perspective + Properties + EClass Hierarchy + EClass References
+
<pre>
** The last two are present and empty until explicitly synchronized with editor (should be default?)
+
An error occurred while collecting items to be installed
** Hierarchy doesn't display with menu item or key combination, as expected
+
  Problems downloading artifact: osgi.bundle,org.eclipse.jet,0.9.0.v20080504.
** Reference view doesn't work as expected (outgoing reference on selected class not displayed, though it does when incoming class selected)
+
    File has invalid content: /tmp/signatureFile25579.jar
** Menu items for Hierarchy/References available from EMF editor tree and Outline, but not diagram elements?
+
      Invalid content: org/eclipse/jet/internal/xpath/functions/extras/SortFunction$XPathComparator.class
* Contributes Ecore Tools project type wizard and nature
+
      The file "org/eclipse/jet/internal/xpath/functions/extras/SortFunction$XPathComparator.class" in the jar "/tmp/signatureFile25579.jar" has been tampered!
** Project wizard is not associated with perspective (no prompt to open on completion)
+
      Invalid content: org/eclipse/jet/internal/xpath/functions/extras/SortFunction$DescendingXPathComparator.class
** Can't create new model/diagram when creating project?
+
      The file "org/eclipse/jet/internal/xpath/functions/extras/SortFunction$DescendingXPathComparator.class" in the jar "/tmp/signatureFile25579.jar" has been tampered!
* Contributes Ecore Diagram wizard that creates *.ecore and corresponding *.ecorediag file
+
</pre>
* Form-based properties are available, though excessive vertical spacing between fields
+
* Install successful after deselecting JET features, but with the following warning logged on startup [https://bugs.eclipse.org/bugs/show_bug.cgi?id=231987 231987]:
** Setting EType requires dialog (title is 'Object selection' - perhaps 'Type Selection' is better?)
+
<pre>
* No separate tool for containment reference, as found in GMF Ecore diagram
+
eclipse.buildId=I20080502-0100
* Identical diagram preferences to GMF Ecore diagram example
+
...
* With Ecore Tools and GMF Ecore diagram installed, both contribute Ecore content to generic navigator (duplicates)
+
Warning
* Outline view has additional domain model tree, duplicating what's in Project Explorer but with different properties provider
+
Tue May 13 22:06:01 EDT 2008
** Additional Resources root provides nice action to invoke Load Resource... but doesn't use the latest dialog from EMF (no Registered models list available)
+
A conflict occurred for COMMAND+SHIFT+U:Binding(COMMAND+SHIFT+U,
* Filter and Validate contributions to main toolbar
+
ParameterizedCommand(Command(org.eclipse.jdt.ui.edit.text.java.search.occurrences.in.file.quickMenu,Show Occurrences in File Quick Menu,
** Error markers appear when validating empty/default diagram
+
Shows the Occurrences in File quick menu,
*** Error in Problems view states defaultname.ecorediagram is not well formed (the default is not well formed?)
+
Category(org.eclipse.search.ui.category.search,Search,Search command category,true),
** Filter menu is extension of runtime's filter contribution, but not co-located in Filter menu
+
,
** Filter toolbar button is present in GMF toolbar even when GMF Ecore diagram is open, though all items are disabled
+
,,true),null),
=== EMFT Mint SDK ===
+
org.eclipse.ui.defaultAcceleratorConfiguration,
* Installed fine, features/plug-ins look fine (though not signed)
+
org.eclipse.ui.contexts.window,,,system)
* Help content is empty, and title could be shorter to fit better in Contents
+
Binding(COMMAND+SHIFT+U,
* TODO: revisit functionality after generating code
+
ParameterizedCommand(Command(org.eclipse.uml2.search.common.ui.handlers.OpenFilteredUMLClassMetaElementSelectionDialogHandler,Open Filtered UML Classifier Meta-Elements Dialog,
=== EMFT Compare SDK ===
+
Open Filtered UML Classifier Meta-Elements Dialog,
* Only source feature shows up in About dialog, though p2 errors in log after install/restart
+
Category(org.eclipse.modeling.editors,Modeling Editors,Modeling Editors Commands,true),
* TODO: revisit this component
+
org.eclipse.uml2.search.common.ui.handlers.OpenFilteredUMLClassMetaElementSelectionDialogHandler,
=== EMFT Search SDK + UML2 + Ecore ===
+
,,true),null),
* Installed fine, though plug-ins not signed
+
org.eclipse.ui.defaultAcceleratorConfiguration,
** org.eclipse.uml2.search.ocl features is named 'Ecore OCL Model Search'
+
org.eclipse.ui.contexts.window,,,system)
* No Help contribution?
+
</pre>
* Ecore and GenModel need their own categories in Search dialog?
+
* When opening the Search dialog, several exceptions thrown [https://bugs.eclipse.org/bugs/show_bug.cgi?id=231988 231988]
* Show Model Result In ... Diagram doesn't open the diagram, though works if already open
+
* In View list, Ecore Tools views are found in Other, and not an Ecore category (or similar)
=== ATL SDK ===
+
* Mint examples have improper branding: providerName and pluginName in About, along with separate feature icon, although modeling32.png [https://bugs.eclipse.org/bugs/show_bug.cgi?id=232147 232147]
* Download and installation of features was fine
+
 
** About dialog shows additional Modeling icon, as org.eclipse.m2m.atl feature is by itself [https://bugs.eclipse.org/bugs/show_bug.cgi?id=220095 220095]
+
=== User Interface Contributions ===
** org.eclipse.m2m.atl feature and branding plug-in showing 'providerName' and 'pluginName' in About (doc and engine features are fine)
+
As a general comment on UI contributions, it seems most projects are fond of using their project/component name or abbreviation. This does not always work well, e.g. 'Ecore Tools Diagram' where a more general name would be better, e.g. 'Ecore Diagram' (OK, so bad example as this name is used by the GMF diagram example).
** Plug-ins are not signed
+
* Net4j (?) contributes a 'Buddies' root category to the Preferences dialog.
* Help contribution limited to javadoc
+
* Several EMF/Ecore-related preferences would be better located under a common 'EMF' (or even 'Modeling') category.  Specifically, 'Ecore Tools Diagram', 'EMF Compare', and 'Model Validation' all seem to be EMF-centric preferences.
* ATL has project type with nature/builder and associated perspective
+
** ATL perspective has no views? Is a perspective necessary?
+
** Perspective is Resource (using Navigator instead of Project Explorer) + Properties + Console + Error Log
+
* ATL Compatibility (2 word) top level menu contribution :(
+
* QVTO contributes a general 'Model to Model Transformation' wizard category, while ATL has its own (combine?)
+
  
=== Teneo SDK ===
+
=== Additional Modeling Installation ===
* Installed fine, though missing name strings in UI for Teneo features
+
* Attempt to install Xpand failed using update site [https://bugs.eclipse.org/bugs/show_bug.cgi?id=219248 219248]
** BuildId = {0} for teneo and teneo.doc features in About dialog (source is OK)
+
* Modeling Workflow Engine (MWE) installed fine, although all but doc feature have improper branding (About dialog)
** Plug-ins not signed
+
=== JET SDK ===
+
* Installed fine, plug-ins signed
+
* In New dialog, Java Emitter Templates category with conversion wizard, then JET Transformations with JET Project wizard
+
** Combine into one?  No JET template wizard or editor included?
+

Latest revision as of 13:48, 3 June 2008

This wiki page contains the result of the Ganymede M7 Modeling Package review.

Platform: Mac OS X

Installation

  • 257 MB (+104MB due to addition of SDKs) download extracts to 326MB (+143MB) on disk
  • Not all sources are packaged in the new method

Startup

  • Standard Eclipse splash and welcome page (should be updated with Modeling project artwork?)
  • Initial perspective is Java (should be an AmalgamModelingPerspective?)
  • CDO Weaver Notification pops up... apparently, enabled by default (best option?) 235415
  • Many source features report invalid discovery sites 228114 Fixed post-M7
  • M2M QVT OML missing branding elements 231908
  • About dialog: all are using proper modeling image, though some issues:
    • GMF and UML2 Tools (documentation only) features missing buildId token replacement (shows @buildId@) 231420 Fixed post-M7
    • UML2 Tools diagram plug-in naming scheme is inconsistent (Activity, Deployment, and Use Case should be prefixed with 'UML2' as are the rest)

User Interface Contributions

  • Menus
    • See M6 notes
  • New Dialog
    • See M6 notes
  • Show View dialog
    • See M6 notes

UML Modeling

  • See M6 notes

Additional Components

Returning to the ganymede update site to install the remaining components in the Models and Model Development category, the following additional observations were made.

Installation

  • In Review Licenses, most projects use the March 17, 2005 version of the license file, with the following exceptions:
    • Teneo, Net4J, and CDO use the January 28, 2004 version
    • EMF Compare and ATL use a non-standard file
  • Error on install using p2 231172:
An error occurred while collecting items to be installed
  Problems downloading artifact: osgi.bundle,org.eclipse.jet,0.9.0.v20080504.
    File has invalid content: /tmp/signatureFile25579.jar
      Invalid content: org/eclipse/jet/internal/xpath/functions/extras/SortFunction$XPathComparator.class
      The file "org/eclipse/jet/internal/xpath/functions/extras/SortFunction$XPathComparator.class" in the jar "/tmp/signatureFile25579.jar" has been tampered!
      Invalid content: org/eclipse/jet/internal/xpath/functions/extras/SortFunction$DescendingXPathComparator.class
      The file "org/eclipse/jet/internal/xpath/functions/extras/SortFunction$DescendingXPathComparator.class" in the jar "/tmp/signatureFile25579.jar" has been tampered!
  • Install successful after deselecting JET features, but with the following warning logged on startup 231987:
eclipse.buildId=I20080502-0100
...
Warning
Tue May 13 22:06:01 EDT 2008
A conflict occurred for COMMAND+SHIFT+U:Binding(COMMAND+SHIFT+U,
ParameterizedCommand(Command(org.eclipse.jdt.ui.edit.text.java.search.occurrences.in.file.quickMenu,Show Occurrences in File Quick Menu,
Shows the Occurrences in File quick menu,
Category(org.eclipse.search.ui.category.search,Search,Search command category,true),
,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.ui.contexts.window,,,system)
Binding(COMMAND+SHIFT+U,
ParameterizedCommand(Command(org.eclipse.uml2.search.common.ui.handlers.OpenFilteredUMLClassMetaElementSelectionDialogHandler,Open Filtered UML Classifier Meta-Elements Dialog,
Open Filtered UML Classifier Meta-Elements Dialog,
Category(org.eclipse.modeling.editors,Modeling Editors,Modeling Editors Commands,true),
org.eclipse.uml2.search.common.ui.handlers.OpenFilteredUMLClassMetaElementSelectionDialogHandler,
,,true),null),
org.eclipse.ui.defaultAcceleratorConfiguration,
org.eclipse.ui.contexts.window,,,system)
  • When opening the Search dialog, several exceptions thrown 231988
  • In View list, Ecore Tools views are found in Other, and not an Ecore category (or similar)
  • Mint examples have improper branding: providerName and pluginName in About, along with separate feature icon, although modeling32.png 232147

User Interface Contributions

As a general comment on UI contributions, it seems most projects are fond of using their project/component name or abbreviation. This does not always work well, e.g. 'Ecore Tools Diagram' where a more general name would be better, e.g. 'Ecore Diagram' (OK, so bad example as this name is used by the GMF diagram example).

  • Net4j (?) contributes a 'Buddies' root category to the Preferences dialog.
  • Several EMF/Ecore-related preferences would be better located under a common 'EMF' (or even 'Modeling') category. Specifically, 'Ecore Tools Diagram', 'EMF Compare', and 'Model Validation' all seem to be EMF-centric preferences.

Additional Modeling Installation

  • Attempt to install Xpand failed using update site 219248
  • Modeling Workflow Engine (MWE) installed fine, although all but doc feature have improper branding (About dialog)

Back to the top