roassal-based blueprint review
by Tudor Girba
Hi,
I looked over the Roassal blueprint implementation. We start to have a working solution. Good work.
However, there is still some work left :)
What is nice:
- Edges are properly drawn below the nodes
- The implementation layer shows a tree layout
- The morph menus work
- The layers do not capture the interaction
What is not so nice:
- Morph menus are shown even on left click. They should only appear on right click. I fixed this.
- The size of the root node grows too large and we get a little gap at the bottom (see the first attached picture). This has likely something to do with the latest fix from Alex related to padding.
- When dragging a method or attribute node outside of the bounds of the parent, the parent continues to grow (see the second picture). This is not good :). The problem is that the logic depends on setting the parent to have extensible size. Instead, in the case of the blueprint, it should be the responsibility of the layout to grow the parent as needed without actually making the parent to be extensible. This is why in Mondrian the layout could be set to stretch.
- Right now, the edges start and end in the center of the nodes. The convention in the blueprint is to have edges drawn starting from the right side and end on the left side of nodes.
In any case, I already added it to the MooseFinder (the blueprint tab).
Cheers,
Doru
--
www.tudorgirba.com
"There are no old things, there are only old ways of looking at them."
9 years, 10 months
Metaceller
by Diego Lont
Hi all,
Recently I have been working on some configurations, and I felt the need to have something better (more specific for configurations) to edit my configurations than the standard OB / Nautilus. On the PharoConf Doru told me about GTMetataceller, but this tool needed some work. So I did some work on it, and now I am looking for feedback how you like it. It is built in glamour, and you get it, when you download the latest Moose. Just type GTMetaceller open somewhere in the browser and you are ready to rock. If you know how Metacello works, the editor should be more or less self explaining. In case you run into trouble, there is a help button that explains the tool a bit.
I also did a screencast: http://youtu.be/LaJF_dfGsD8.
If you want to load this in your image, just do:
Gofer new
url: 'http://www.smalltalkhub.com/mc/Moose/GToolkit/main';
package: 'ConfigurationOfGToolkit';
load.
(Smalltalk at: #ConfigurationOfGToolkit) project development load.
(Smalltalk at: #GTMetaceller) open.
Note: I only tested this in Pharo 2.0, this loading does not work in Pharo 1.4. It should work in Pharo 1.4, since loading the GT-Metaceller package in Moose 4.7 works fine. I think I should create a stable version as well … that loads in Pharo 1.4 as well.
Cheers,
Diego
9 years, 10 months
roassal + athens
by Tudor Girba
Hi,
I would like to start adopting Athens behind Roassal. I believe there
already is a binding. The question is what keeps us from adding Athens as a
dependency to RoassalMorphic?
Cheers,
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
9 years, 10 months
