2 Feb
2009
2 Feb
'09
9:22 p.m.
Hi,
As Lukas says, Morphs do not scale when you have thousands of them.
I really wonder
why (expect that morphic is doing far too much too) I
imgaine that this is the same as with VW
and when adrian implemented the visualiziation for chronia.
so do you draw on a canvas and map back the coordinates to the object
that should represent it?
Stef
Drag and drop did work at some point. It's just
that Jorge and me
started a larger refactoring that was supposed to improve the model
but stopped at midway because of some low level problems.
I will synchronize tomorrow with Alex and we will see what we can do.
Cheers,
Doru
On Feb 2, 2009, at 8:37 PM, Lukas Renggli wrote:
--
www.tudorgirba.com
"Be rather willing to give than demanding to get."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I was
wondering why you did not use morphs for mondrian since I
have the
impression that for drag and drop
alex is reinventing the morph event dispatch loop.
I don't know exactly the current situation, but when I last worked on
Mondrian for Squeak it had drag and drop. These were a couple of
lines
of code built on top of the basic mouse events. Essentially this is
the same as when you implement drag and drop in the HTML DOM tree.
Morphic is way too slow, way to wasteful with memory and too platform
dependent for something like Mondrian. One of the reasons why the
original Mondrian is not portable, is because it is tightly connected
with the graphic system of VisualWorks.
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev