Hello. In my application I have an image library that I display, and some processing that gets done using one of the library images. The trouble is every time I do the processing bit (with a _POST), the page gets reloaded including the image library. This is a bit unncessary and the reloading of the images can be annoying.
What would be a good way of not reloading the images when I do the processing bit? For example, is it possible to use a frame that contains the images and doesn't get reloaded with every file update, but which retains the previous images. Or should I use a completely different approach?
Thanks in advance and sorry for asking such a noddy question.
Structuring a webpage, should I use frames
Moderator: General Moderators
-
bobthebuilder
- Forum Commoner
- Posts: 32
- Joined: Tue Mar 22, 2011 5:06 pm
Re: Structuring a webpage, should I use frames
You would have to be more specific about your processing, but generally, frames have lost favor in web development, largely because they are not SEO-friendly (that is, search engines won't find and index the content). You could avoid reloading the page by using Ajax techniques (Javascript and PHP) or, depending on what this "processing" consists of, perhaps just by performing the processing, but not sending anything back to the browser.
-
bobthebuilder
- Forum Commoner
- Posts: 32
- Joined: Tue Mar 22, 2011 5:06 pm
Re: Structuring a webpage, should I use frames
The processing I do is to take the image that has just bee clicked, adding it to a results image file, and displaying the new results image. I then need to redisplay the page so we can go through the cycle again. Whilst I need to redisplay the result image every time, I do not need to redisplay the image library each time. This page of my web-site would not have to be search engine friendly, and i do not want to use Javascript. Does it sound as though a frame is the way to go?
Re: Structuring a webpage, should I use frames
An Iframe should work, then, although if it were my site, I'd look closely at why Javascript shouldn't be used, because the smoothness of AJAX operations is something I value. The last time I checked, something over 95% of page requests are from browsers with scripts enabled. But if you are determined not to use JS, and you're not concerned about using a deprecated frame element, I think it should work.bobthebuilder wrote:The processing I do is to take the image that has just bee clicked, adding it to a results image file, and displaying the new results image. I then need to redisplay the page so we can go through the cycle again. Whilst I need to redisplay the result image every time, I do not need to redisplay the image library each time. This page of my web-site would not have to be search engine friendly, and i do not want to use Javascript. Does it sound as though a frame is the way to go?