Updates:
Cc: tudor.girba
Comment #1 on issue 396 by alexandre.bergel: Mondrian should provide teh
start and end nodes in the edge action
http://code.google.com/p/moose-technology/issues/detail?id=396
I started to work on this (testHandlerOnEdge). However, I am unsure for few
things.
view interaction on: MOMouseDown do: [ :v | ... ]
What v is supposed to be? The announcement or the value on which one has
clicked?
It has to be the value I believe. However, it may brake already existing
code. We could leave it like this, and introduce on:withValueDo:
What do you think?
Cheers,
Alexandre
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium
New issue 501 by alexandr...(a)gmail.com: Cache independence
http://code.google.com/p/moose-technology/issues/detail?id=501
The core of Mondrian is not independent of the cache implementation. The
logic of Mondrian rely on the cache to implement its semantics. This is
obviously wrong.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
bounds
"Answer the bounds of the receiver."
"the bounds is has an absolute origin"
"Note that the bounds computed above, may have (and it is likely to) a
different origin. The reason is that the layout is in charge to position
the nodes properly"
| basicBounds |
boundsCache ifNotNil: [ ^ boundsCache ].
"We check if the shape if present"
self shapeBoundsAt: self shape ifPresent: [ :b | ^ boundsCache := b ].
basicBounds := self shape computeBoundsFor: self.
self shapeBoundsAt: self shape put: basicBounds.
^ boundsCache := basicBounds
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
translateAbsoluteCacheBy: aPoint
absoluteBoundsCache ifNil: [ ^ self ].
absoluteBoundsCache := absoluteBoundsCache translateBy: aPoint
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Thanks to Santiago Vidal for pointing this out!
Status: New
Owner: ----
CC: vhane...(a)gmail.com
Labels: Type-Defect Priority-Medium Component-Spy
New issue 503 by alexandr...(a)gmail.com: Abstract classes and Hapao
http://code.google.com/p/moose-technology/issues/detail?id=503
Gaëtan le Brun suggested to remove abstract classes before running the test
in Hapao.
This makes sense
Status: New
Owner: ----
Labels: Type-Defect Priority-Medium Component-Hapao
New issue 601 by alexandr...(a)gmail.com: Covered methods and tests
http://code.google.com/p/moose-technology/issues/detail?id=601
It would be good to see what are the tests that _indirectly_ tests a
methods.
Thanks Laurent & Patrick
Status: New
Owner: andreho...(a)gmail.com
Labels: Type-Enhancement Priority-Medium Component-Famix
New issue 509 by andreho...(a)gmail.com: Modularization Quality Metric
http://code.google.com/p/moose-technology/issues/detail?id=509
We implemented the Bunch metrics of coupling and cohesion as quality
metrics for existing packages (FAMIXPackage) and namespaces
(FAMIXNamespace).
Now the idea is to implement the Modularization Quality Metric as a quality
metric for existing group of packages (FAMIXPackageGroup) and namespaces
(FAMIXNamespaceGroup).
Pointer to the papers that propose the metrics:
Using Automatic Clustering to Produce High-Level System Organizations of
Source Code (http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=693283)
Bunch: A Clustering Tool for the Recovery and Maintenance of Software
System Structures
(http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?arnumber=792498)
Status: New
Owner: ----
Labels: Type-Enhancement Priority-Medium Component-Glamour
New issue 582 by tudor.gi...(a)gmail.com: Watcher support in Glamour
http://code.google.com/p/moose-technology/issues/detail?id=582
Like we now have a statusbar, we should also have a detailed preview shown
in a floating Watcher window. The behavior would be similar to Quick Look
on Mac.