That a morph will perform an action every miliseconds. Did you define the step method? or stepTime? Stef On Feb 7, 2010, at 10:22 AM, nullPointer wrote:
I think that there are always space to improve. This is just that we should look at what we are doing in a different way.
It seems that you're using the stepping mechanism, it is time consuming.
Yes stepping is not the way to go
What´s stepping? :)
also the layout managing and invalid areas redrawing.
do you redraw even the not visible cells?
I don´t know. I have a ScrollPane widget. In that scrollPane i have a container (simply a panel morph). That pane have TableLayout policy, from top to bottom. Each row is added at that panel. Te rows is configured with TableLayout policy too, from left to right list direction, and in each row exists a collection of cells.
I suppose than the ScrollPane dont redraw controls out of limits, but I don´t know.
With widgets from Squeak nothing is like we think they are :) With the new tree widget developed by alain you get a lazy Tree morph with can handle large collection.
Seeing the trace seems than the more problematic is when creating the cells ( the method #buildCellsStructureFrom ).
Is possible stop all UI events when Iis running the build of cells and rows? I did think in use threads, but the UI crushes when I try that way.
Regards
View this message in context: Re: Conseils for develop a grid Sent from the Pharo Smalltalk mailing list archive at Nabble.com. _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project