[Moose-dev] Re: next steps

Hi Santiago! Really cool! You succeeded in having class blueprint in a web browser, probably the most complicated visualization made with mondrian. I now have a question about packaging your work. All the compressed javascript code takes 188 Kb. Where should we put this necessary code? Within Mondrian directly I think. Like this one can simply export a visualization as html5 without having to install anything else on the side. Do you think you can store a zip file as a string (have a look at the ThemeIcons class side, they use Base64MimeConverter to have a binary code as a readable string)? And then unzip it when exporting a visualization as html5? Cheers, Alexandre On 9 Jun 2011, at 21:05, Santiago Vidal wrote: works with blueprint classes. One or more classes can be displayed (In the same way as Mondrian). There are some examples in the next file: www.santiagovidal.com.ar/MondrianProtovis/examples.zip out of it. it somewhere for us to download instead of sending them by mail directly. Use Dropbox for example: generation. It took some time because I had some performances issues whit dragging. Also, I had to use an external library to the tooltips because Protovis only supports basic tooltips in a single line. Owing to these problems some additional files are required to run the generated html (I'm attaching these files). rectangle nodes and edges. Specifically, inner nodes, DistributionMap, and system complexity. (I'm also attaching an example of each one) inner nodes. The new file is in the attachment. That is because the position of an inner node is determined by the position of its parent. However, I think that the implementation could be change properly. do drag together with the parent node, but I would also like to be able to interact with the inner nodes (e.g., drag or click). Is this a conceptual problem, or is it simple a missing implementation? example code: I do not see any edge. any edge. Am I the only one? I use Safari and OSX. whole Moose and generate the visualizations. complexity, inner nodes, and distribution map. I used for these examples the second option that we discuss previously. The examples are in the attachment. MondrianLayouts that will only work directly with Protovis. drag & drop behavior. In going to try to make an example using the Mondrian representation for Monday. to handle interactions, more specifically node replacement operations? recoding Mondrian in Protovis. nodes. In general I have 2 options to work with protovis: of Protovis Layouts. 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. second, it implies the creation of new layouts when they are needed. generated html file could be interactive (such as the example that I send before). However, it doesn't improve the graphics generated by Mondrian. University of Chile it cannot be done." <protovisMondrian.zip>_______________________________________________ <protovisMondrian.zip>_______________________________________________ <DistributionMap.html><DragWithChildRestriction.js><ex.css><jquery.tipsy.js><jquery-1.4.2.min.js><protovis-r3.2.js><tipsy.css><tipsyBehavior.js><innerNodes.html><SystemComplexity.html>_______________________________________________ -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: 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