Hi,
Right now, every builder will build a view with a menu by default. This
does not work well when we want to embed the visualization into a larger
interface (e.g., a glamour browser).
The zooming menu should by an optional facility that should not be
hardcoded by default.
Is it Ok if I remove it?
Doru
--
www.tudorgirba.com
"Every thing has its own flow"
Hi,
I often have the problem that menu I want to show is different in each item shown (in case of lists or trees).
actions already support the #condition statement, but there is no vocabulary for doing it directly.
Of course I can doit anyway but is so common (at least in my workflows) that I wonder if it would be better to add the vocabularies instead needing to add the custom action?
(in fact, what I usually do is to add an extension method in my projects, but well… I’d prefer not to do it :) )
cheers,
Esteban
Hi,
using Roassal2 I would like to get a box with some nested element on it and
the box get a label above itself.
I tried this but it is not working
view := RTView new.
container := (RTVerticalCompositeShape new
shape1: RTLabel new;
shape2: (RTBox new color: (Color blue alpha: 0.5)))
elementOn: 'Container'.
els := RTEllipse new elementsOn: (1 to: 16).
view add: container; addAll: els.
RTNest new layout: RTGridLayout; on: container nest: els.
view @ RTDraggableView.
view open
As you can see the label is not move due to the resize of the box with the
nest.
I do not use TRConstraint because I will have several boxes and if I apply
a layout on them the label is not calculate in the size so I do not think
this is a solution but RTNest on RTVerticalCompositeShape is.
--
Cheers,
Leo Perard
University of Lille 1