[Q] scrolling large collections
cottonsqueak at earthlink.net
Wed Apr 9 20:33:21 UTC 2003
By the way, although an ambitious changeset like Lex's Largelists may not be
able to gain favor from n squeakers (gaining such acceptance would seem to
be an O(N!) problem) we could do some minor things to help ScrollPane.
Specifically, on every scroll it iterates through all its morphs ( I think
i'm getting this right!) to find their bounds. This as far as I can tell can
be cached very reasonably to at least double the scrolling speed. Calculate
it lazily, and invalidate it upon a #layoutChanged. This isn't a total speed
fix but its simple and a considerable increment.
If anyone is interested in such changes I'll prepare them (its perhaps 2
one-liners), but I'm inclined to believe no one is. Of course if I'm
overlooking something fundamental please let me know.
----- Original Message -----
From: "Ned Konz" <ned at bike-nomad.com>
To: "The general-purpose Squeak developers list"
<squeak-dev at lists.squeakfoundation.org>
Sent: Wednesday, April 09, 2003 12:52 PM
Subject: Re: [Q] scrolling large collections
> On Wednesday 09 April 2003 08:56 am, Martin Drautzburg wrote:
> > If I want to display items from a list of say a million entries I
> > can do this with the available ListMorphs. But theses only display
> > text. What if my items have a graphical (Widget) representation
> > (for simplicity lets assume they all have the same height).
> > I certainly cannot draw them all and the clip to the visible parts.
> > I thought I could display a fixed set (say 8) of them and then
> > change the models of the visible representation when scolling is
> > done.
> > I just cannot figure out how the ScrollPane works. How do the
> > events from the scrollbar reach the TransformMorph that does the
> > actual scrolling ? Is there a place where I could plug in my own
> > way of scrolling.
> The slider in the ScrollBar sends #scrollBarValue: (or some other
> pluggable selector) to its model, which is often a PluggableListMorph
> (which is of course a ScrollPane). Then the PLM sends #offset: to its
> scroller (which is a MorphicTransform).
> The way that the ScrollPanes work, though, is that they tend to draw
> everything and count on clipping to do the work.
> You may want to look at Lex's "Large Lists" change set, which
> optimizes the display of very large lists.
> Ned Konz
> GPG key ID: BEEA7EFE
More information about the Squeak-dev