Announcement

**NormanRouxel** · 14-Nov-2005, 01:18 PM

That's basically correct but they're not put in a cookie. They're simply loaded by the browser so that they are available from then on in the browsers Cache.

The example above uses a bit of external JavaScript (from Dreamweaver I think) that you also need to include somewhere in your <HEAD> area.

However Actinic has a built-in PreloadImages routine available, so all you need to do is edit Act_Primary.html and look for the fragment

Code:

OnLoad="NETQUOTEVAR:ONLOAD"

and change it to

Code:

OnLoad="PreloadImages('myimage1.jpg','myimage2.jpg');NETQUOTEVAR:ONLOAD"

You can add in as many images as you like.

**Olly** · 14-Nov-2005, 02:09 PM

Thanks for your responce

Can this be used for other files aswell? i.e. Flash files (.swf)

Also if they are stored in the cache, are they updated often?
The files wouldn't be updated often, once a month at the most.

Olly

**NormanRouxel** · 14-Nov-2005, 04:42 PM

No, that's dangerous! Only valid image files can be preloaded this way.

The JavaScript is creating dummy images and setting their source property to the passed in arguments.

You might crash the browser by loading arbitary code into images!

As to caching; all images and HTML get automatically cached anyway. SO these images will be treated no differently from other content.

**Mike Hughes** · 14-Nov-2005, 05:07 PM

pre-loading is typically used for mouseover and other dynamic image swaps so there's no delay when the image is called for.

For images in normal use there's no benefit to doing it this way. It would probably slow down the page as the images are preloaded before the page is displayed.

Mike

Announcement

Frequently used images

Frequently used images

Comment

Comment

Comment

Comment