[Seaside] Component navigation

[James Foster]

Hi,

The approach I use is to have a 'main' component that basically has a single child component and use the anchor callbacks to change the child component. See http://seaside.gemstone.com/tutorial/chapter10.pdf for an example in my tutorial.

James Foster

On Aug 29, 2011, at 2:12 PM, keropotter wrote:

> Hi!!
> 
> I'm wondering what's the best option to navigate a series of components in
> 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? I'm never giving an #answer, because I
> don't know if the user will go back to the previous component. For example,
> the user might be on one called component, and navigate via menu to another
> component that's not related to the previous one.
> 
> So, what's the best way to navigate components in seaside? Would using a
> Task be a good approach? Any suggestions on how to do this? I'm kinda stuck
> here...
> 
> Many thanks in advance!!!
> 
> --
> View this message in context: http://forum.world.st/Component-navigation-tp3777414p3777414.html
> Sent from the Seaside General mailing list archive at Nabble.com.
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
>