On 7/13/05, Phil Kulak <[EMAIL PROTECTED]> wrote: > Personally, I would use another browser if it listened to web pages > instead of me. Just because the web designer thinks I need to refresh > the content when using the back button, doesn't mean I want to sit > there and wait for the new version to load. I like the back button for > what it's meant to be, a quick way to look at a previous screen in the > state it was when you last looked at it. If I want to force a reload, > I'll hit reload or use a button on the page. > > -Phil
Phil, lets establish right at the beginning, that I do not suggest to chose one way over another. And I am not saying that reloading pages is the best thing ever. All I want is just to have an easy option to do that in Wicket, this is it. No, to the subject. The reload/show-from-cache is a long time religious argument. I for myself do not have a strict answer on that. Sometimes one is better, sometimes another. Also, users are different too. Some users are... er... not computer-proficient, they go back and cannot understand why their shopping cart is still there. Then they sumbit it again and cannot get why they see error message or even worse, why they pay twice. Reloading is good for these users, especially if they have good internet connection. Others know exactly what they do when they go back. Sometimes they can have bad connection too, so reloading is killing them. These users can leave with stale pages. You are one of these users, you are a power user :) you know what to expect and how to deal with stale pages. See this thread for insight: http://forums.mozillazine.org/viewtopic.php?t=99885&start=0 I understand that by posting this link I can swing the scales to "do not reload" decision, but again, I want to have an option for myself, I do not suggest to make all Wicket applications reloadable. Also, things are not black and white. Sometimes you want to reload, sometimes don't. If you read an article, and leave it and then return back, you probably do not want to reload it. Same with email, but this depends, see Google Mail, it reloads everything using Ajax. If you take a wizard, this is a clean example where you do not need to cache and need to reload. When you navigate from panel to panel to reload pages anyway, right? When you click Back on wizard, you just leave it, nothing is reloaded. When you click forward returning to wizard, you either reset it and show a new one, or display panel corresponding to current state, so you load it. You do not want to show stale page from a 30-minute old wizard, right? So, there should be choice and careful decision in each case. Every case is different, as some stuff need to be cached, while other stuff need to be reloaded. Anyway, just some thoughts ;) Michael. ------------------------------------------------------- This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual core and dual graphics technology at this free one hour event hosted by HP, AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
