Adam McDaniel wrote:

On Wed, Feb 05, 2003 at 08:53:53AM -0800, Taras wrote:

I second that opinion. It is very annoying if you have pages that are basicly long tables of contents and they get cut into 3-4 pages. Makes scrolling to find the right word very painful.

OK, think about the problem this way.

Let's say that you have an HTML document that's 200k long (I'm just
throwing around numbers here).. When you parse it it splits it up into
6 pages in the viewer (~32k each, etc etc). To view just one of those
pages there is a load time of 10 seconds until you can actually begin
to read and scrolldown on that one page.

Would you be willing to instead have a loadtime of 60 seconds just so
the viewer can properly re-build everything into one complete page,
just like the original?

I thought about that. However can't you do incremental loading?
So somewhere the length of the document would be stored and scrollbar would be sized accordingly. then as you get close enough to the unloaded segment it would load it.
Isn't that possible? I suspect that's how isilo gets around the problem

Taras

_______________________________________________
plucker-list mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-list

Reply via email to