The scrolling certainly is not an easy task to complete. If one pops open
AvantGo, the reason why it scrolls correctly is that they are only rendering
either a line of text or a blank-line-the-height-of-a-text-line Therefore,
the last line of fully rendered text is always at the same pixel position
and it will always be the same number of pixels to slide up the correct
amount so the next lines correctly fit, with no text lines partially cut
off. This is the same idea that is used in many doc readers. However, drop
in an image into the AvantGo browser's page, or pump up the font size and it
will no longer work in this manner.
Since Plucker allows people to customize varying sizes of blank vspaces
between paragraphs/list elements/etc, allows custom font sizes, as well as
inline images, I certainly agree it really is a difficult task. Look forward
to what Michael can come up with though.
Best wishes,
Robert
> -----Original Message-----
> From: Michael Nordstr�m [mailto:[EMAIL PROTECTED]]
> Sent: Wednesday, July 11, 2001 7:06 AM
> To: Plucker Development List
> Subject: Scroll values (was: Don't like it)
>
>
> On Tue, Jul 10, 2001, Chris Hawks wrote:
> > I've been watching the 'scroll' discussions of late and while I
> agree that
> > we did leave a little too much of the old text on the screen when we
> > scrolled on page, simply scrolling the _entire_ page is BAD.
>
> Yep, and I'm glad to hear that I'm not the only one with that opinion.
>
> However, since it wasn't possible to convince some users about this I
> changed the scroll size to 145 in 1.1.7 (just to prove my point -- it
> was never added to CVS, only included in the binary). In 1.1.9 I used
> 140 and in the next version I will either use 135 or your suggestion
> (window height - height of largest font).
>
> I'll try to come up with a better solution (bug report #6), but it's
> not trivial (images add an extra level of complexity).
>
> /Mike
>
