Announcement

**gabrielcrowe** · 13-Sep-2007, 08:55 AM

preloading traditionally occurs in javascript, which for security reasons has no way to tell wht is inside a folder.

but this is basically pointless, becasue the entire contents of your site1 folder gets uploaded anyhow. bung all your files in there.

**lazyeye** · 13-Sep-2007, 10:00 AM

well, I know all that.

But preloading is not totally pointless and the issue cannot simply be waved off. Say a product is available in different colors and that when selecting any color choice the product image is swapped to show another image; in that case, preloading helps in having a more responsive effect, for you don't have to wait the few seconds needed in case the image was not preloaded.
In actiniccatalog.mdb there is an Additional Files table; my idea was to query it, filter out non image files and generate a javascript list.

**wjcampbe** · 13-Sep-2007, 10:33 AM

You do not want to preload all images, and would not normally preload any image until somebody opens the page where that image might be used.

Surely you don't want to force every visitor to download 23Mb of 'extra images' because they 'might' visit one page where they actually want to view an extra image?

Add a custom variable, list the image names in that varialble for each page and use the preloadimages routine in the <body ...> tag to load just the images needed when they are needed.

Now - to preload as the page opens, the images need to be available on your site. Getting them there is nothing to do with preloading.

So, is it the uploading of all the images to the site that is causing you problems - or the preloading of possibly required images when each page loads?

Announcement

additional files

additional files

Comment

Comment

Comment