[Seaside] Component navigation
keropotter at gmail.com
Tue Aug 30 14:07:02 UTC 2011
Thank you all very much! You've been of great help!
I'll focus on James and Robert approaches, although I'm not sure what
Announcements are. I'll search some info on that =)
Thanks you again!!
On Tue, Aug 30, 2011 at 8:29 AM, Philippe Marschall <
philippe.marschall at gmail.com> wrote:
> 2011/8/29 keropotter <keropotter at gmail.com>:
> > Hi!!
> > I'm wondering what's the best option to navigate a series of components
> > GLASS. For instance, i'm developing a solution using anchors, and the
> > callbacks use the #call: message to render the next component.
> > But this makes me worry about the stack. Won't it grow indefintely and
> > eventually crash my application?
> No, the stacks are not joined together and only a limited set of
> continuations is kept.
> > I'm never giving an #answer, because I
> > don't know if the user will go back to the previous component. For
> > the user might be on one called component, and navigate via menu to
> > component that's not related to the previous one.
> If you're just changing the 'main' content component then see the
> answers of James and Robert.
> seaside mailing list
> seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the seaside