27 May
2011
27 May
'11
7:02 p.m.
I don't know yet. In principle I'm going to implement the drag & drop
behavior. In going to try to make an example using the Mondrian
representation for Monday.
2011/5/27 Johan Fabry <jfabry(a)dcc.uchile.cl>
I agree with Alex, but I have a question: how do you plan to handle
interactions, more specifically node replacement operations?
On 27 May 2011, at 12:22, Alexandre Bergel wrote:
--
Ing. Santiago A. Vidal
ISISTAN Research Institute
UNICEN University
Paraje Arroyo Seco
Campus Universitario
(B7001BBO) Tandil,
Bs. As. - Argentina
Phone: 54 2293 439840 Ext. 42
Fax: 54 2293 439681
Email: svidal(a)exa.unicen.edu.ar
http://www.exa.unicen.edu.ar/~svidal
I feel we should opt for 2).
We should export the visualization using Protovis, not recoding Mondrian
in
Protovis.
Alexandre
On 27 May 2011, at 12:19, Santiago Vidal wrote:
> Hi,
> I have been working in the visualization of the inner nodes. In general
I have
2 options to work with protovis:
> • Be independent of the data by means of
the use of Protovis
Layouts.
> • Copy the same visualization that is
used by Mondrian. That is
create a Protovis canvas of the same size that the canvas
of Mondrian and
place each shape in Protovis in the same location that in the canvas of
Mondrian.
> While the first option is more modifiable
than the second, it implies
the creation of new layouts when they are needed.
> The main advantage of the second option is
that the generated html file
could be interactive (such as the example that I send
before). However, it
doesn't improve the graphics generated by Mondrian.
> What do you think is the best option?
> Cheers
> Santiago
--
Johan Fabry
jfabry(a)dcc.uchile.cl - http://dcc.uchile.cl/~jfabry
PLEIAD Lab - Computer Science Department (DCC) - University of Chile
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev