Re: Another Ajax back button question
If the ajax changes are reflected in the relevant model(s) then you will see them when you go back to the page. Scott On Thu, Dec 4, 2008 at 2:29 PM, Matt Welch [EMAIL PROTECTED] wrote: I'm sure this has been asked and answered but after searching the list, I'm still not sure if there is something I can do to fix my situation. The general gist is this: 1) I make some changes to a page with ajax calls (i.e. replace panel contents) 2) Click a link to take me away from that page 3) Use browser back button to return to previous page 4) Original page is in the state that it was BEFORE the changes made with the ajax calls. Maybe this is a, Well, duh.. of course it is. That's just the way it works moment, but I could have sworn I've seen this work differently in other wicket examples and apps I've worked on. Any tips? -Matt -- View this message in context: http://www.nabble.com/Another-Ajax-back-button-question-tp20843893p20843893.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Another Ajax back button question
If you want to manage all the back button events, i suggest you to use a simple bookmarking library.likeRSH We use the ajax calls to insert some tag that went added to the address after #. (target.prependjavcascript). After that, when going back to another tag, there was a script defined on the body onload method with RSH libraries. There, if the tag was one of the tags that should activate back button support, we simulated the click of an ajaxbutton to replace the current state of the page with the previous state.This was done with javascript and java code in wicket. In our project, we used RSH(http://code.google.com/p/reallysimplehistory/). 2008/12/4 Scott Swank [EMAIL PROTECTED] If the ajax changes are reflected in the relevant model(s) then you will see them when you go back to the page. Scott On Thu, Dec 4, 2008 at 2:29 PM, Matt Welch [EMAIL PROTECTED] wrote: I'm sure this has been asked and answered but after searching the list, I'm still not sure if there is something I can do to fix my situation. The general gist is this: 1) I make some changes to a page with ajax calls (i.e. replace panel contents) 2) Click a link to take me away from that page 3) Use browser back button to return to previous page 4) Original page is in the state that it was BEFORE the changes made with the ajax calls. Maybe this is a, Well, duh.. of course it is. That's just the way it works moment, but I could have sworn I've seen this work differently in other wicket examples and apps I've worked on. Any tips? -Matt -- View this message in context: http://www.nabble.com/Another-Ajax-back-button-question-tp20843893p20843893.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Another Ajax back button question
Scott Swank wrote: If the ajax changes are reflected in the relevant model(s) then you will see them when you go back to the page. Hmmm... perhaps I shouldn't have abstracted my issue and instead discussed exactly what is happening. Let me change some steps. 1) On a page with a form I enter information and submit the form 2) The page refreshes (normal submit; not ajax) and a panel that was previously invisible is displayed as the form submission is processed in the background. This processing is background task because it can take a very long time (anywhere between 5 seconds to half an hour). There is an AjaxSelfUpdatingTimerBehavior with a 5 seconds time attached to the now visible panel. 3) The AjaxSelfUpdatingTimerBehavior checks the background process in it's onPostProcessTarget() method and when the background processing is done, the panel is made invisible again and new panel is made visible with a link to report on the processing that just took place. 4) Clicking that link takes one to the report and then clicking that browser back button brings one back to the form page, however, it apparently brings one back to the form page in the state it was just after the original submit was clicked. The actual background processing doesn't get kicked off again, but the in progress panel is visible and remains visible until one cycle of the AjaxSelfUpdatingTimerBehavior goes by and then the page returns to the expected state. I'd like to figure out a way keep that in progress panel from showing up when the back button is pressed. -Matt -- View this message in context: http://www.nabble.com/Another-Ajax-back-button-question-tp20843893p20844322.html Sent from the Wicket - User mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
