Labels: Type-Defect Priority-Medium
New issue 540 by vuqui...(a)vub.ac.be: Glamour: removing dependency in
configuration - core group
In the configuration of Glamour, the core group was loading only Glamour
packages, and the extras group: mondrian and magritte presentations. This
allowed to load those presentations if needed.
Currently, the core group is also depending on Mondrian. The method
MOViewRenderer>>openWithStatusbar is causing this dependency in the package
Can this dependency be removed from the group core?
The GLMUITheme changed:
- no more color fading, except for selected buttons and tabs
- more contrast between grays
- fixed the issue with lighter background color for inactive windows
This resulted in a simpler and slightly faster look.
"Being happy is a matter of choice."
Labels: -Priority-Medium Priority-High
Comment #4 on issue 446 by tudor.gi...(a)gmail.com: uml class shape aligned
A form of the problem is still around. This is an important issue that
prevents us from actually using the FormsBuilder.
Here is an example with a ChildrenShape inside. The green shape on top
should have a constant minimum size. Instead its height increases together
with the height of the children shape below:
| builder |
builder := MOFormsBuilder new.
builder column; fill.
builder row; fill; row; fill.
builder x: 1 y: 1 add:
(MORectangleShape new width: 30; fillColor: Color green).
builder x: 1 y: 2 add: (MORectangleShape new).
builder x: 1 y: 2 add: (MOChildrenShape new).
view shape: builder shape.
view nodes: (1 to: 5) forEach: [:each |
view nodes: (1 to: each).
view verticalLineLayout ]
Since some of you are working on remodularizing code, maybe the following may inspire you.
In Mondrian, the tests are badly structured. I actually wrote a large part of them as a way for me to understand the initial version of Mondrian, back in 2007-2008. Most of the tests are contained in the class MOViewRendererTest. They actually contain a lot of duplicated scenario (not really code): I open a canvas, put some nodes and edges, run the layout...
I would like to cut this class into smaller unit tests. Fixture will have to be found for each new unit tests. How to structure them? Along the class hierarchy? Along the features of Mondrian? Along the features commonly used in Mondrian scripts (which is how they are roughly structured)?
I can remodularize my tests and come up with a satisfactory design in a couple of hours. But maybe someone worked on a tool that would help me on this.
Alexandre Bergel http://www.bergel.eu
now that we have announcements it should be easy to have a code spy:
a window that when I browse any things in moose (being it a mondrian node, or
a whatever stuff announcement event) I could see in the spy window the code
of the entity.
This way I could move hyperfast my mouse on a nice mondrian view and get immediately
fats code overview wihtout having to click, spawn or wahtever action.
Do you like the idea?
Because I always got frustrtaed with visualaition because I could not get that behavior
in addition to the visualization.
Last year I ported some packages about 'Simulated Annealing' from
I am not sure what this is about and what does 'Simaulated Annealing' mean
exactly, But I recently remembered that I had it in my repository with all
tests green at least :)
So in case it can be usefull or it can interest somoene. I just put them in
a new repository: