[Moose-dev] roassal-based blueprint review

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."