Hi Cyrille,
Ok, I think I see where the confusion comes from.
Every Morph is passed the actual Canvas in the drawOn: method. This is
part of the rendering loop.
What you want is to pass the AthensCanvas into that drawOn: method.
Does this help?
Doru
On 15 Jun 2010, at 13:50, Cyrille Delaunay wrote:
Ok.
But, first, I don't why MOCanvas is a subclass of Morph (and not a
subclass of Canvas) ?
MOCanvas doesn't define any 'drawRectangle:' or 'drawSomething'
methods, like usual canvas does.
By setting some halt in the 'shape-classes' (MORectangleShape,
MOEllipseShape), I saw that the method display:on: is called with a
'FormCanvas' as parameter.
So somewhere in the code, somoene is telling to MOCanvas: drawOn:
aFormCanvas. But it seems to not be in Mondrian
2010/6/15 Tudor Girba <tudor.girba(a)gmail.com>
Hi,
MOCanvas is the canvas, it is a subclass of Morph :).
Doru
On 15 Jun 2010, at 13:23, Cyrille Delaunay wrote:
When I look to MOCanvas, I don't find any initialization of the
concrete Canvas used .
There is only a Method MOCanvas >> drawOn:, that then let a MORoot
object call MORoot>>displayOn:, that then dispatch the work to each
'shape-class'.
But I still don't find where the 'concrete' canvas is used (maybe I
should wear glasses :))
2010/6/15 Tudor Girba <tudor.girba(a)gmail.com>
Hi,
now something important is that mondrian is barely usable for us:
DSM, package blueprint, torch are all slow.
I would really like to see some pragmatic solutions to be found.
Like not computing all the blocks all over the time.
This is what we are already discussing, but until now it is not
clear what exactly generates the slowness. I believe the problem
comes from the edges, but we have to take a more systematic look.
The other thing that has an impact is that right now Mondrian
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.
Doru
Stef
On Jun 15, 2010, at 12:43 PM, Tudor Girba wrote:
Hi Cyrille,
The canvas is defined in MOCanvas. This canvas is embedded in
MOBrowser and MOEasel, which in their turn create a StandardWindow
that holds the MOCanvas.
Just to inform the others, Cyrille is experimenting with adding the
Athens canvas (which provides an abstraction over Cairo, Balloon and
possibly others) behind Mondrian.
Cheers,
Doru
On 15 Jun 2010, at 11:42, Cyrille Delaunay wrote:
Hello,
I have been looking a bit for the place where we set the canvas to
use in Mondrian, but I didn't find.
I know that all shapes are drawn on a FormCanvas, but there is no
references to FormCanvas in mondrian classes.
I just saw that there is a 'defaultCanvasClass' method in the class
Form for example, so maybe such a method is use somewhere in the code.
Does somoene know the way to set a new Canvas to Mondrian ?
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
www.tudorgirba.com
"Presenting is storytelling."
_______________________________________________
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
--
www.tudorgirba.com
"There are no old things, there are only old ways of looking at 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
--
www.tudorgirba.com
"One cannot do more than one can do."
_______________________________________________
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