So, i was doing the right thing essentially, and I only need a task to manage login in and stuff.<br>Thats good news ;)<br><br>yay, thank you!!<br><br><div class="gmail_quote">On Fri, Apr 25, 2008 at 3:15 PM, Roger Ostrander <<a href="mailto:atiaxi@gmail.com">atiaxi@gmail.com</a>> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Hello,<br>
<br>
The way I've approached this is similar to your idea: There's a<br>
"menu component" whose job it is to render the header, the footer,<br>
itself, and then whatever the active component is. I tend to store<br>
the active component in the menu component itself, but that has the<br>
problem that, unless you pass the menu component around, it's the only<br>
thing that can transition between pages (this hasn't been a problem<br>
for me).<br>
<br>
Tasks fill a different niche altogether. They're used when you want<br>
a sequential list of things to happen. So say before people see the<br>
menu component at all, they need to log in. Your task would look<br>
something like:<br>
<br>
do<br>
[self session loggedIn ] whileFalse: [ self call: self loginComponent ].<br>
self call: self menuComponent.<br>
<br>
Hope this helps!<br>
<div class="Ih2E3d"><br>
On Fri, Apr 25, 2008 at 4:45 PM, David Zmick <<a href="mailto:dz0004455@gmail.com">dz0004455@gmail.com</a>> wrote:<br>
> So, I have a website, and I would like it to have multiple pages, eg. an<br>
> about page, a members page, etc. I think you know what I mean. I have<br>
> currently accomplished this by creating a variable in my session class<br>
> called content and the root component renders different content depending on<br>
> what the content variable stores.<br>
> This approach appears to have these advantages:<br>
><br>
> I can have a header and footer that remains constant no matter what page the<br>
> user is on<br>
> It is very simple<br>
</div>> not much elseI do not entirely understand the idea of a root task but I have<br>
<div class="Ih2E3d">> a feeling that that is the way I should go about completing this.<br>
> What is the "proper" way to accomplish my goal, preferably, I would like to<br>
> be able to do the same things I can now, but do it "correctly" :)<br>
><br>
> --<br>
> David Zmick<br>
> /dz0004455\<br>
> <a href="http://dz0004455.googlepages.com" target="_blank">http://dz0004455.googlepages.com</a><br>
> <a href="http://dz0004455.blogspot.com" target="_blank">http://dz0004455.blogspot.com</a><br>
><br>
</div>> _______________________________________________<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>
><br>
><br>
<font color="#888888"><br>
<br>
<br>
--<br>
Roger<br>
_______________________________________________<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>
</font></blockquote></div><br><br clear="all"><br>-- <br>David Zmick<br>/dz0004455\<br><a href="http://dz0004455.googlepages.com">http://dz0004455.googlepages.com</a><br><a href="http://dz0004455.blogspot.com">http://dz0004455.blogspot.com</a>