Hi Oli,
> Hm, it may still be worth looking into this -- V is doing a shitload
> of "optimizations" using cliprects and other stuff now, and I'm not
> entirely sure that under certain circumstances, one of those may do
> more harm than good.
I have a good example on my homepage:
http://www.skyynet.de/gsmphones.html
is a big table and is coded very HTML compliant with the table size given
in its header. Thus it should produce the basic Table very fast and fill
it later on. Right now it takes about 25 seconds after clicking on the
link leading to that page until the new frame is even opened. I thought
the progressive display of pages would speed things up?
Of course you have problems assigning this page with JavaScript switched
on (with Voyager) as I used the totally clean code from the
German JavaScript Newsgroup's FAQ which Voyager can not cope with, yet
(hint, hint, hint!). Think it's due to it not passing a set variable as
there are no JS errors given and behaviour indicates this.
Otherwise Voyager is quite stable (for an Alpha it rocks!) here.
Ingo
--
---------------------------------------------------------------------------
Hasta la vista, baby E-MAIL : [EMAIL PROTECTED]
URL : www.skyynet.de
---------------------------------------------------------------------------
_____________________________________________________________________
Voyager Mailing List - http://v3.vapor.com/
Voyager FAQ....: http://faq.vapor.com/voyager/
Listserver Help: mailto:[EMAIL PROTECTED]?Subject=HELP
Unsubscribe....: mailto:[EMAIL PROTECTED]?Subject=UNSUBSCRIBE
