One strong principle in Mondrian is to have graph elements independent of their representation. A graph element being just a wrapper of the domain object. This is what has been enforced in the VW and Pharo versions.
However, this has not been completely nice and clean. For example, MOGraphElement defines #bounds, #absoluteBounds. MONode defines #translatedBy:. Shall these methods be moved into the shape?
Currently, we have the following responsibilities:
a graph element:
- keeping a ref to its shape
- managing caches
- managing attributes
- managing nesting of nodes and edges
- supporting announcement
- keeping a location
- maintaining a zordered-list of elements to display
- dedicated caches (e.g., bitmap)
- rendering on a canvas
- target and source node
- rendering on a canvas
- selection box
- another event management
Clearly, some responsibilities are ill located. I will do soon some cleaning...
Alexandre Bergel http://www.bergel.eu
Labels: Type-Enhancement Priority-Medium Component-VerveineJ Milestone-4.4
New issue 550 by tudor.gi...(a)gmail.com: VerveineJ should export Annotations
The following entities should appear:
Labels: Type-Defect Priority-Medium Component-Finder Milestone-4.4
New issue 564 by tudor.gi...(a)gmail.com: Moose Wizard packages list scrolls
when importing from Smalltalk
How to reproduce:
- import from Smalltalk
- select a package
- the list scrolls automatically
This is confusing. The list should not scroll.
Labels: Type-Defect Priority-Medium Component-Glamour
New issue 559 by cy.delau...(a)gmail.com: magritte presentation does not fill
the cell's space
In glamour, When opening a magritte presentation in a tab widget, the
generated morph is too small and do not fill the whole space provided by
the glamour cell.
The Moose build uses 1.2.1 now:
On 3 Apr 2011, at 10:45, Stéphane Ducasse wrote:
> and yes we should continue
> On Apr 3, 2011, at 9:36 AM, Marcus Denker wrote:
>> On Apr 3, 2011, at 9:35 AM, Marcus Denker wrote:
>> .. the all green image of today from Hudson. Yes, this is not repeatable and tomorrow
>> the hudson one might be different. But we need to move on. 1.1 was build just once, too.
>> So we can continue to build the perfect fully automatic process for 1.3...
>> -> Make a one-click.
>> -> Make a cog one-click.
>> -> push all open reports in the tracker to 1.2.2
>> Marcus Denker -- http://www.marcusdenker.de
>> INRIA Lille -- Nord Europe. Team RMoD.
"Problem solving should be focused on describing
the problem in a way that makes the solution obvious."