I'm very sorry that I'm good at widgets I would really like to help you. This is for such a reason that we should continue to clean morphic to arrive to the point where we do not have three different classes for doing the same and often not ahving the behavior we want.
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. > > 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 > [email protected] > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list [email protected] http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
