15 Jan
2010
15 Jan
'10
12:05 a.m.
Hi,
No to be negative, but I actually like the way I do it now, which is
as follows:
- I visualize famix elements (namespaces, classes, methods, ...)
- each of these implements a method that is responsible for adding its
representation to the view
- each of these has a status (a famix property) responsible for
keeping its visualisation state
I like this because
- I dont need to add vars to the classes
- the visualisation state is permanent: if I do a full refresh nothing
is lost
- closing-opeing an element returns the element to its previous state
although all the contained entities are redrawn
The only (minor) downside to this is that if I would have 2
visualisations on the same data they will show the same expansion
state. I see no problem with this.
Now the popupview is interesting as well. Are there any other use
cases ?
On 14 Jan 2010, at 16:24, Alexandre Bergel wrote:
Hi!
Now that some of you are building complex and interactive
visualizations, I feel the need to add some annotations on things
that are displayed. I am not talking about the model here, but
really annotation on the view. For example, assume that I want the
size of a node to increase (e.g., to see its method inside) when I
double click on it. Where do I store the information that the node
has been expanded ?
I started to have this need with popupView:. A node needs to know
whether its popupview is on or not. I added a variable popup in
MOGraphElement which solve this. But more complex interaction
requires a generalization of this.
I am about to introduce a variable annotation in MOGraphElement that
will lazily create a dictionary.
Any comment?
Cheers,
Alexandre
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
Johan Fabry
jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry
PLEIAD Lab - Computer Science Department (DCC) - University of Chile