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

proposed by jannik a while ago Yes, I will work on it. I have to identify where the slowness comes from, from Mondrian or package blueprint. Alexandre 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. 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" :). he did not want to help. blocks, you can easily get to quadratic algorithms. size]. 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 :) DSM, package blueprint, torch are all slow. 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. the Athens canvas (which provides an abstraction over Cairo, Balloon and possibly others) behind Mondrian. to use in Mondrian, but I didn't find. references to FormCanvas in mondrian classes. 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