|
|
Posted by Spartanicus on 07/06/06 11:04
"Chris Tomlinson" <anon@anon.com> wrote:
>>>Image1 starts loading first and the browser does not continue through the
>>>HTML until Image1 has loaded COMPLETELY. When Image1 is done, Image2
>>>BEGINS
>>>loading. When Image2 is 100% done, only then does Image 3 begin... and so
>>>on...
>>
>> That describes your perceived solution to a problem, tell us what you
>> are actually trying to do and we may be able to offer useful advice.
>
>We are trying to load a series of around 10 large JPGs (300K each), and want
>the first one to appear as quickly as possible. The speed of the remaining
>9 is not quite so important, but they should also appear in the order they
>are listed.
See if you have an application on your system that displays the
uncompressed size of images (most image viewers or editors will do
this). Add the values for all images displayed on that page up. Now
consider how a resource strapped device will handle that huge amount of
data. In this case a "resource strapped device" is likely to be anything
but the latest desktop computer with a huge amount of system and video
ram.
Then there is the load time, globally most internet users are still on
modem dial up. This includes many so called "developed" countries such
as for example here in Ireland. A single page with 3MB (disk size) of
images alone is going to be next to unusable for people who are not on
fast broadband connections, and slow and cumbersome for those on quite a
few home broadband packages.
So unless you have a very good reason why these images *must* be
viewable simultaneously (unlikely given the dimension alone), the
correct way to present such content is to present these images one by
one with a "Next 1 2 3 4 5 ... Previous" navigation.
--
Spartanicus
Navigation:
[Reply to this message]
|