[Moose-dev] Re: [Mondrian] Where can we set the canvas to draw elements?

Ok, so if I try to understand a bit the structure: => MOCanvas is just the 'global' Morph (and so not really a canvas ?) that will contains all the elements's morphs => This global morph know the MORoot element . => This MORoot element know each sub-MONodeElement. => Then the MOCanvas Morph can be set to any MorphWindow (to the MOBrowser or MOEasel for example). => It's only when we try to open such a window, that we concretely 'draw' each node (dispatching the work to the corresponding MOShapes). => So the morphic library says to the MOCanvas: drawOn:, wich dispatch the work to the MORoot, wich dispatch to each MONode, which dispatch tho the corresponding MOShapes. Like alex said, the concrete canvas to use is provided by Morphic, and if no one should manually instantiate it, Morphic should also be modified to use by default the RomeCanvas instead of the current ones (?).

What seems to be sure, is that we can't specify easily a specific canvas to be used in mondrian

2010/6/15 Alexandre Bergel <alexandre.bergel(a)inria.fr> difficult to find where problems are by looking at a very complex case. When the problems were raised, we did look into the issues, but it was just too difficult especially when we had multiple problems in the same time. multiple problems, there are some fixes, but there are still problems left. So, we have to dig deeper and we should do it more systematically by creating simpler cases that reproduce the problem. It's not an issue of "I told you so", it's an issue of "We need help to identify all problems" :). +1 Alexandre that he did not want to help. blocks, you can easily get to quadratic algorithms. each]) size]. again, so N^2. graphs. And those people that have a direct interest in getting Mondrian fast would be good to help in this direction, because it can get difficult to understand the particularities of each model :) us: DSM, package blueprint, torch are all slow. found. Like not computing all the blocks all over the time. clear what exactly generates the slowness. I believe the problem comes from the edges, but we have to take a more systematic look. computes everything lazily, so even if the visualization appears, scrolling might still be problematic the first time you go through the entire picture. So, testing should also take this into account. MOBrowser and MOEasel, which in their turn create a StandardWindow that holds the MOCanvas. adding the Athens canvas (which provides an abstraction over Cairo, Balloon and possibly others) behind Mondrian. canvas to use in Mondrian, but I didn't find. is no references to FormCanvas in mondrian classes. the class Form for example, so maybe such a method is use somewhere in the code. them." _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev _______________________________________________ Moose-dev mailing list Moose-dev(a)iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev