<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Oct 16, 2014 at 5:16 PM, Johan Brichau <span dir="ltr"><<a href="mailto:johan@inceptive.be" target="_blank" class="vt-p">johan@inceptive.be</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">As far as my knowledge goes about this part of the Seaside framework, #children is important in:<div>- a WATask [1]</div></div></blockquote><div><br></div><div>Ohhh that sounded a bell. It might have been that in my case. </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>- when you don’t override renderContentOn: (falling back to the default behavior of rendering the children)</div></div></blockquote><div><br></div><div><br></div><div>OK, I don't do this.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div>- in combination with #states when you want to support state backtracking with the back button</div><div><br></div></div></blockquote><div><br></div><div>mmmm I thought only #states was needed for the backtracking with continuations. So....do I need both then? </div><div>Esteban, I was about to answer you this....</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div></div><div>FWIW, I know and have many components that don’t declare their children and it works fine. Of course, I’m not using any of the above in those cases.</div></div></blockquote><div><br></div><div>Thank you both. </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><div><br></div><div>Johan</div><div><br><div>[1] <a href="http://book.seaside.st/book/components/tasks/sequencing-components" target="_blank" class="vt-p">http://book.seaside.st/book/components/tasks/sequencing-components</a><br><div><div><div class="h5"><div>On 16 Oct 2014, at 18:43, Mariano Martinez Peck <<a href="mailto:marianopeck@gmail.com" target="_blank" class="vt-p">marianopeck@gmail.com</a>> wrote:</div><br></div></div><blockquote type="cite"><div><div class="h5"><div dir="ltr">Hi guys,<div><br></div><div>From what I understand, if we have a component called X which, as part of the #renderConentOn: (or derivative), does:</div><div><br></div><div>ComponentX >> renderContentOn: html</div><div>html render: self componentY</div><div><br></div><div>Then we need to add componentY to the #chidlren:</div><div><br></div><div>ComponentX >> children<br></div><div>^ Array with: self componentY</div><div><br></div><div>So..not the question is...it seems in some places I forgot to add it to #chidlren and the component still render correctly. At the same time, I remember once I was fighting to find a bug and it was exactly because I forgot to add the component to #children. So... what exactly happens if I DON'T add the component as a #children? What does it get broken?</div><div><br></div><div>The second question is...is a bit of a pain the #children. Why? Because I must store the component somewhere...which I may not requiere that. For example, if I have this code:</div><div><br></div><div>html render: (MyWebMessageComponent new errorMessage: 'Problem with xxxx'; yourself)<br></div><div><br></div><div>then I must define an instVar for that component, assign to it before render, and then render...</div><div><br></div><div>so the second question is...for this type of component that I render only "once" (the component is instantiated as part of the rendering phase and dead after), do I also have to add it to #children?</div><div><br></div><div>Thanks in advance for any clarification. </div><div><br></div><div><div><br></div>-- <br>Mariano<br><a href="http://marianopeck.wordpress.com/" target="_blank" class="vt-p">http://marianopeck.wordpress.com</a><br>
</div></div></div></div><span class="">
_______________________________________________<br>seaside mailing list<br><a href="mailto:seaside@lists.squeakfoundation.org" target="_blank" class="vt-p">seaside@lists.squeakfoundation.org</a><br><a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank" class="vt-p">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br></span></blockquote></div><br></div></div></div><br>_______________________________________________<br>
seaside mailing list<br>
<a href="mailto:seaside@lists.squeakfoundation.org" class="vt-p">seaside@lists.squeakfoundation.org</a><br>
<a href="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside" target="_blank" class="vt-p">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</a><br>
<br></blockquote></div><br><br clear="all"><div><br></div>-- <br>Mariano<br><a href="http://marianopeck.wordpress.com" target="_blank" class="vt-p">http://marianopeck.wordpress.com</a><br>
</div></div>