Posted by Chris Tomlinson on 06/23/06 11:07

"dorayme" <doraymeRidThis@optusnet.com.au> wrote in message
news:doraymeRidThis-318564.12420123062006@news-vip.optusnet.com.au...
> In article <8eaf9$449b45bc$40cba7b0$13310@NAXS.COM>,
> "Jonathan N. Little" <lws4art@centralva.net> wrote:
>> No, not 2.5MB That is way over the top of a webpage.
>
> I agree, it is far too big as a general page offered to the
> public. If you link to such a page with an explanation of what
> they are in for, fine. But then you need not preload or postload
> or anyload anything. They either go and wait as warned or don't
> wait because they are on a fast connection and they know it and
> are proud of it...

We take your points on board. It is a big dilemma, as once the page is
loaded the user experience is impressive. If we loaded the slices of the
image only when the user called them, it wouldn't provide for a seamless
scroll down the street.

What we are hoping to do based on your feedback is combine two effects:

1) Use the splash page which asks for their e-mail, to start preloading the
page (they need not know about this)

2) When they enter the big page, have some sort of 'floating flash progress
bar' which will tell them how close the page is to loading.

Are you guys able to point us in the right direction of a nice swf device
like this? It needs to sit near the bottom of the page over the
streetscape, so that it doesn't obscure the street introduction which they
can be reading whilst the page loads.
--
Thanks,
Me

[Back to original message]