Thank you all very much! You've been of great help!<br><br>I'll focus on James and Robert approaches, although I'm not sure what Announcements are. I'll search some info on that =)<br><br>Thanks you again!!<br>
Alejandro<br><br><div class="gmail_quote">On Tue, Aug 30, 2011 at 8:29 AM, Philippe Marschall <span dir="ltr"><<a href="mailto:philippe.marschall@gmail.com">philippe.marschall@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
2011/8/29 keropotter <<a href="mailto:keropotter@gmail.com">keropotter@gmail.com</a>>:<br>
<div class="im">> Hi!!<br>
><br>
> I'm wondering what's the best option to navigate a series of components in<br>
> GLASS. For instance, i'm developing a solution using anchors, and the<br>
> callbacks use the #call: message to render the next component.<br>
><br>
> But this makes me worry about the stack. Won't it grow indefintely and<br>
> eventually crash my application?<br>
<br>
</div>No, the stacks are not joined together and only a limited set of<br>
continuations is kept.<br>
<div class="im"><br>
> I'm never giving an #answer, because I<br>
> don't know if the user will go back to the previous component. For example,<br>
> the user might be on one called component, and navigate via menu to another<br>
> component that's not related to the previous one.<br>
<br>
</div>If you're just changing the 'main' content component then see the<br>
answers of James and Robert.<br>
<br>
Cheers<br>
<font color="#888888">Philippe<br>
</font><div><div></div><div class="h5">_______________________________________________<br>
seaside mailing list<br>
<a href="mailto:seaside@lists.squeakfoundation.org">seaside@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
</div></div></blockquote></div><br>