Hi,
I am coming back to the issue of zOrder.
Here is a little example:
view shape label text: #yourself.
view nodes: (1 to: 20).
view edges: (1 to: 20) from: [:x | x // 2] to: 1.
view edges: (1 to: 20) from: [:x | x // 3] to: 2.
view edges: (1 to: 20) from: [:x | x // 5] to: #yourself.
view edges: (1 to: 20) from: [:x | x // 7] to: #yourself.
view dominanceTreeLayout
Open this one is Mondrian and then in the Roassal Easel (see attached screenshots).
Then, try to select 1.
In Roassal, you cannot select 1 because of the edges that go on top of it. What is more, you also can barely see it. This situation will always appear in graphs with edges that cross the nodes.
Given that at least the MondrianViewBuilder should be about mapping domain models onto graphs, having a sensible zOrder, at least in the MondrianViewBuilder is important.
Doru
--
www.tudorgirba.com
"Sometimes the best solution is not the best solution."
Status: Started
Owner: damien.c...(a)gmail.com
CC: tudor.gi...(a)gmail.com, chisvasi...(a)gmail.com
Labels: Type-Defect Priority-Medium Platform-Pharo Component-Glamour
New issue 886 by damien.c...(a)gmail.com: GLMMorphicSpotterTest>>testCreation
is not automatic
http://code.google.com/p/moose-technology/issues/detail?id=886
This method opens a tool and requires user intervention. This blocks test
runners and continuous integration.
Status: New
Owner: ----
Labels: Type-Engineering Priority-Medium Milestone-4.7 Maintainability
New issue 887 by tu...(a)tudorgirba.com: <MSEProperty: ...> should replace
<property: ... > pragmas
http://code.google.com/p/moose-technology/issues/detail?id=887
Here is the list of violations:
#'Smalltalk::FAMIXClassGroup.abstractness()'
#'Smalltalk::FAMIXNamespace.bunchCohesion()'
#'Smalltalk::FAMIXPackage.martinCohesion()'
#'Smalltalk::FAMIXNamespace.martinCohesion()'
#'Smalltalk::FAMIXPackage.bunchCohesion()'
#'Smalltalk::FAMIXNamespace.efferentCoupling()'
#'Smalltalk::FAMIXNamespace.afferentCoupling()'
#'Smalltalk::FAMIXClassGroup.afferentCoupling()'
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 867 by kurs....(a)gmail.com: Start rule is missing in the
PPAllParsersBrowser
http://code.google.com/p/moose-technology/issues/detail?id=867
When you select e.g. PPArithmeticParser in PPAllParsersBrowser, you can
test 'start' rule by defining 'Sample' and pressing Parse button.
When you select some rule (e.g. number), you cannot test 'start' again. You
have to select another parser and re-select PPArithmeticParser.
Status: New
Owner: ----
CC: tudor.gi...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-PetitParser
New issue 882 by kurs....(a)gmail.com: PetitParser Inspector tab in
GTInspector does not work
http://code.google.com/p/moose-technology/issues/detail?id=882
When opening Petit Parser instance in GTInspector, Inspector tab is empty
Status: New
Owner: tu...(a)tudorgirba.com
Labels: Type-Defect Priority-Medium Component-Finder Milestone-4.7
New issue 885 by tu...(a)tudorgirba.com: Moose Finder does not provide the
navigation list in alphabetical order
http://code.google.com/p/moose-technology/issues/detail?id=885
For example, for a class, attributes appear somewhere in the middle of the
list. It should be on top.
Hi Alex and Vanessa,
At this point, Roassal has open branches. Is this wanted? I guess not, but if yes, which is the official branch?
Cheers,
Doru
--
www.tudorgirba.com
"Yesterday is a fact.
Tomorrow is a possibility.
Today is a challenge."
Status: New
Owner: ----
Labels: Type-Enhancement Priority-Medium Milestone-4.7
New issue 811 by anquetil...(a)gmail.com: Create more virtual association in
MooseChef
http://code.google.com/p/moose-technology/issues/detail?id=811
Famix recognizes 4 types of associations (reference, access, inheritance,
invocation) and Moosechef was built upon these dependencies
(queryAllOutgoingReferences, ...)
But this will miss a good deal of actual dependencies, because many of them
are not expressed by associations:
- exceptions caught, thrown
- parameter types in parameterized classes
- use of annotations
- other?