Unfortunately, you have no real control over how long a site takes to load. There are a huge number of factors that can affect that.
If it were me, I would try to cache these images on a server. ie. when one person has loaded site X, send the thumbnail to the server and put an entry into the database. Then on subsequent accesses, you can check if that site is already in the database and if it isn't, load up that site. I would probably add the date and time into the database so I could do a refresh every three months or so. --- In flexcoders@yahoogroups.com, "James" <garymoorcroft_...@...> wrote: > > Thank you very much Steve. That work's perfectly now. I never realised it > would be that easy. I'm quite inexperienced when it comes to coding. If it's > anything more than click="change something or other" then it's beyond me at > times ha. > > Just on another note. These images I'm trying to make in my final app will > act as links to the sites in question within 9 different categories each with > a few sites and the html window will be made non visible. I want to decrease > loading times of the html window and the app itself as much as possible. If I > use the same code for each categrory by using a html window for each > categrory each loading images the way this one does would that take up too > much loading time do you think especially on lower internet connections or > would it be okay? Also is there any way of making the html components load > faster in any way perhaps by making them load a low res version of some sort? > Basically I'm looking for ideas to make this aspect of the application as > quick in it's loading times as possible.
