[Seaside] Re: Navigating away from call:'s

[Sebastian Sastre]

There is not component call breaking. Just the flow of the user call after call.
You make your components to call others as much as they need and forget about
them. That’s the whole continuations magic.
You only worry about the answer when you need to.

Sebastian Sastre

 

> -----Mensaje original-----
> De: seaside-bounces at lists.squeakfoundation.org 
> [mailto:seaside-bounces at lists.squeakfoundation.org] En nombre 
> de Ronaldo Ferraz
> Enviado el: Viernes, 22 de Febrero de 2008 12:09
> Para: Seaside - general discussion
> Asunto: Re: [Seaside] Re: Navigating away from call:'s
> 
> Actually, here I'm thinking more about tradicional navigation. For
> example, a navigation bar at the top of the page any link of which the
> user can select at any time. Any selection will break the current
> component call and cause another to be displayed instead.
> 
> Ronaldo
> 
> On Fri, Feb 22, 2008 at 1:34 AM, Sebastian Sastre 
> <ssastre at seaswork.com> wrote:
> >  Cliks away is just too wide. You probably want to include 
> in that editor only
> >  anchors who has callbacks with sense for an edition 
> context. For example an
> >  explicit save or cancel. By saying 'clicks away' you are 
> suggesting just a
> >  different kind of post cancel action?
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside