On 12/16/06, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
On 12/16/06, Craig McClanahan <[EMAIL PROTECTED]> wrote:
> On 12/16/06, Rahul Akolkar <[EMAIL PROTECTED]> wrote:
<snip/>
> >
> > Indeed, I think a common paradigm will be: do stuff on entry / undo on
> > exit. In which case, the onExit() from the previous view state and the
> > onEntry() into the new view state (whose corresponding view user
> > navigated to using browser buttons) should minimally be fired. WDYT?
>
>
> That certainly seems reasonable. I don't know about calling onTransition()
> though ... it seems quite likely that the "transition" implemented by
> responding to the navigation-induced changes will identify an arc that does
> not actually exist in the state diagram.
>
<snap/>
I agree, no onTransition() makes sense to me.
<snip/>
The more I think, I'm not sure. In any case, will require us to have
good docs for onTransition() in context of browser nav buttons!
-Rahul
