First point, you should never call #renderContentOn. The framework is responsible for calling that. <div><br></div><div>Assume you have a Task that is the root of your application. In the Task's #go method, you will do something like this :-</div>
<div><br></div><div>go</div><div> self call: MyParentComponent new.</div><div><br></div><div>Seaside will then call the #renderContentOn method for that component. As your component has children, you then call #render: with the canvas passed into to parent's #renderContentOn, to render each child component.</div>
<div><br></div><div>If I'm not being clear, please ask more questions, and also checkout the new Seaside book at <a href="http://book.seaside.st">http://book.seaside.st</a> for more examples and explanations.<br><br><div class="gmail_quote">
On Fri, Nov 6, 2009 at 18:08, Tony Giaccone <span dir="ltr"><<a href="mailto:tgiaccone@gmail.com">tgiaccone@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
No. I don't think so. The relationship between the parent and child is just inheritance. <br><br><br> WAComponent subclass: MADetailDisplay<br><br><br>MAPersonDetail subclass: MADetailDisplay<br><br><br>If I write this in the subclass:<br>
<br>#renderContentOn: html<br><br> super renderContentOn: html<br> "Client renders here".<br><br>The super's method will be finished when the child's method starts. <br><font color="#888888"><br><br>
Tony</font><div><div></div><div class="h5"><br><br><br><div class="gmail_quote">
On Fri, Nov 6, 2009 at 5:43 PM, John Toohey <span dir="ltr"><<a href="mailto:johnptoohey@gmail.com" target="_blank">johnptoohey@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0pt 0pt 0pt 0.8ex;padding-left:1ex">
<div>If I understand you correctly, this is what you need to do :-</div><div><br></div>In the parent's #renderContentOn: html<div><br></div><div>html div id: #DetailDisplay; with:[</div><div> html render: child1.</div>
<div> html render: child2.</div><div>]<br><br></div><div>In the parents #children method</div><div><br></div><div>children</div><div> ^ Array with: child1 with child2</div><div><br><div class="gmail_quote"><div><div>
</div><div>On Fri, Nov 6, 2009 at 17:27, Tony Giaccone <span dir="ltr"><<a href="mailto:tgiaccone@gmail.com" target="_blank">tgiaccone@gmail.com</a>></span> wrote:<br>
</div></div><blockquote class="gmail_quote" style="border-left:1px solid rgb(204, 204, 204);margin:0pt 0pt 0pt 0.8ex;padding-left:1ex"><div><div></div><div><br>First I want to thank everyone for the comments on my last request about setting up a seaside/pharo server. Now on to my next question. <br>
<br>One more about implementation. <br><br>Suppose I have a page, and the page is broken up in to components. A menu, a header, a synopsis, and a detail record. Let's focus for a second on the detail record. <br>
<br>In MyApp, there are several different types of detail records, which could be displayed in that region of the page. They are all sub-classes of one parent class. For the purposes of discussion, let's assume that the parent class is MADetailDisplay, and the sub classes are MAPersonDisplay, MAFamilyDisplay, MAAddressDisplay (though in reality the exact classes aren't that important). <br>
<br>I want each of these to details to render inside the same div on the page.<br><br><div id="DetailDisplay"><br><br><!-- in this space the detail component renders --><br><br></div><br><br>
Now it would seem very reasonable to give the parent class the responsibility of rendering the tag that surrounds that detail component. In that way any sub class of MADetailDisplay is going to be in the right "location" on the page. <br>
<br>It's not quite clear to me how to do that in Seaside/Smalltalk. Nor is it clear to me if this is really the right way to even think about this problem. <br><br><br>Anyone care to comment?<br><font color="#888888"><br>
<br>Tony<br>
</font><br></div></div>_______________________________________________<br>
seaside mailing list<br>
<a href="mailto:seaside@lists.squeakfoundation.org" target="_blank">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></blockquote></div><br><br clear="all"><br>-- <br>-JT<br><br><br>
</div>
<br>_______________________________________________<br>
seaside mailing list<br>
<a href="mailto:seaside@lists.squeakfoundation.org" target="_blank">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></blockquote></div><br>
</div></div><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>
<br></blockquote></div><br><br clear="all"><br>-- <br>-JT<br><br><br>
</div>