Open NicolasRouquette opened 6 years ago
Filed Bugzilla issue for (A) here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=526841
Filed Bugzilla issue for (B) here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=526842
Filed Bugzilla issue for (C,D) here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=526843
Filed Bugzilla issue for (E) here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=526844
There are several usability problems with Xtext & Sirius in Eclipse Oxygen.1.
OML WB version 0.9.0.0-M14
Example
The screenshot below shows two editors/views:
Note that the synchronization icon is selected on both the
Model Explorer
andOutline
views on the left pane.This screenshot reflects the state of the Eclipse UI after these operations: 1) Select the
concept Product
on the OML XText editor (left).2) Select the
mission:SpecifiedElement
on the OML TerminologyBox Sirius view (right).3) In the Sirius interpreter view (bottom), the completion is invoked after
aql:self.
Usability problems
A) Lack of synchronized selection between XText editor & Sirius view
The screenshot reflects that the XText editor & Sirius view are not synchronized with each others' selection. If they were synchronized, then:
mission:Product
should have been selected on the view on the right.aspect SpecifiedElement
on line 11 should have been selected on the editor on the left.B) Missing "select in other editors/views" action
Assuming that an XText editor and a Sirius view would have a synchronization icon like the
Model Explorer
andOutline
views do, it would be useful when the editor or view are NOT synchronized to have a context menu action to update the selection in other editors/views based on the current selection.In this example, invoking such an action from the context menu on the
mission:SpecifiedElement
shown on the OML TerminologyBox view on the right would update the selection on the OML XText editor on the left such that the selection would change from line 13 to line 11.C) Interpreter completions need to be grouped and sorted
The completions shown in the
Sirius Interpreter
view are clearly not grouped nor sorted. Some methods come from the EMF API, some from a diagram-level API.These methods should be grouped according to which library they originate in. The library should be shown in one of several forms:
EMF API
org.eclipse.emf.ecore_2.13.0.v20170609-0707.jar
GAV
coordinates e.g.,org.eclipse.emf : org.eclipse.emf.ecore : 2.13.0.v20170609-0707
D) Interpreter completions should show # of completions and be filterable
The vertical scrollbar on the completion list suggests that there are lots of completion. The Eclipse
Problems
view shows a great example of a usable report because:GAV
coordinatesE) How to write Sirius services without building plugins / launching a runtime Eclipse?
It is unclear from the Sirius Writing Queries doc whether it is possible to do the following:
In an RCP environment like the OML Workbench -- that is, not launching a runtime eclipse
use existing viewpoints (e.g., the OML Viewpoints in the
OML Workbench
)allow a user to author new services to simplify writing queries