If there was a good solution for this it would be a real boon... I can think of a number of cases where this would be extremely useful.
----- Original Message ----- From: "Joel Halbert" <[EMAIL PROTECTED]> To: "Tapestry users" <users@tapestry.apache.org> Sent: Friday, 24 October, 2008 8:56:22 PM GMT +02:00 Athens, Beirut, Bucharest, Istanbul Subject: Re: Trapping the "user is on a new page event" and calling ComponentResources.discardPersistentFieldChanges() on new page? that's generally ok in my case. Wendell Ruotsi wrote: > Arriving at a new page doesn't always mean they've left the first page > - they could have done an "Open link in new tab/window". Or they could > have just opened a new window and typed in a different url on the same > site. In both cases, the first page is still open in their browser. > > -Wendell > > Joel Halbert wrote: >> I'm less interested in the back button event and more interested when >> when a new page is requested i.e. the user deliberately navigates >> away from the current page. Logically speaking T5 would just need to >> store he current page ref in memory, and notify the user when this >> changed. >> I'm guessing that it should be should be do-able, if it's not >> possible already? >> >> Jonathan Barker wrote: >>> Thiago, >>> >>> PageDetached fires when the instance of the page used to service the >>> request >>> gets returned to the page pool. It doesn't have anything to do with >>> the >>> user navigating away from a page. >>> >>> The problem is, with Forward and Back buttons, navigating away from >>> a page >>> is a browser-side event. Different frameworks have tried various >>> ways to >>> stop the back-button from breaking applications. It's one of the big >>> reasons that T5 moved to the redirect-after-post pattern. >>> >>> Jonathan >>> >>> >>>> -----Original Message----- >>>> From: Thiago H. de Paula Figueiredo [mailto:[EMAIL PROTECTED] >>>> Sent: Friday, October 24, 2008 14:29 >>>> To: Tapestry users >>>> Subject: Re: Trapping the "user is on a new page event" and calling >>>> ComponentResources.discardPersistentFieldChanges() on new page? >>>> >>>> Em Fri, 24 Oct 2008 14:21:05 -0300, Joel Halbert >>>> <[EMAIL PROTECTED]> >>>> escreveu: >>>> >>>> >>>>> Hi, >>>>> >>>>> Is there a hook you can leverage to trap an event when the user >>>>> navigates to a new page? >>>>> >>>> I didn't understand how different this situation would be from simply >>>> catching the end of the rendering of a page. This would be the >>>> @CleanupRender event or, maybe better, the @PageDetached event. All >>>> the >>>> component events are described here: >>>> http://tapestry.apache.org/tapestry5/guide/rendering.html and the page >>>> events here: >>>> http://tapestry.apache.org/tapestry5/guide/lifecycle.html. >>>> >>>> -- >>>> Thiago H. de Paula Figueiredo >>>> Independent Java consultant, developer, and instructor >>>> http://www.arsmachina.com.br/thiago >>>> >>>> --------------------------------------------------------------------- >>>> 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] >>> >>> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > -- SU3 Analytics Ltd 61b Oxford Gardens W10 5UJ London Tel: +44 20 8960 2634 Mob: +44 75 2501 0825 www.su3analytics.com SU3 Analytics Ltd is a company registered in England and Wales under company number 06639473 at registered address 61b Oxford Gardens, London W10 5UJ, United Kingdom. --------------------------------------------------------------------- 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]
