cocoon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Christopher Oliver <res1c...@verizon.net>
Subject Re: SoC between flow and sitemap
Date Mon, 19 May 2003 18:53:14 GMT
Stefano Mazzocchi wrote:

>on 5/18/03 4:53 PM Sylvain Wallez wrote:
>
<snip>

>  
>
>>This is only one of the reasons why fetching the continuation ID cannot 
>>be hardcoded. Another example is the XMLForm integration with the flow 
>>(yep, one more nice thing by Christopher!), where a single page holds 2 
>>continuations ID : the current one associated to "next", and a previous 
>>one associated to "prev".
>>    
>>
>
>Yes. I remember discussing this IRL with Ugo a while back where he was
>exactly complaining about the fact that a "back" button associated with
>the previous continuation would simply make us fall back in the same
>screen we are, not in the previous one. And jumping back by two
>continuations will re-execute the logic between the two previous screens
>(which is not always desirable). Glad to see that fixed (I haven't tried
>it yet)
>  
>
The solution was to capture a continuation immediately before and 
immediately after cocoon.forwardTo(). Then to get to the "previous" page 
you go back _three_ continuations. Going back one causes the current 
page to be resent. Going back two returns you to the logic following the 
previous page. Going back three causes the previous page to be resent.


Mime
View raw message