[Seaside] why cant you call #renderOn: on a child component

[Boris Popov]

If you look at the implementation of #render: you'll notice it does a
few extra things to set things up. That should provide the best answers
for ya,

Cheers!

-Boris

-- 
+1.604.689.0322
DeepCove Labs Ltd.
4th floor 595 Howe Street
Vancouver, Canada V6C 2T5
http://tinyurl.com/r7uw4

boris at deepcovelabs.com

CONFIDENTIALITY NOTICE

This email is intended only for the persons named in the message
header. Unless otherwise indicated, it contains information that is
private and confidential. If you have received it in error, please
notify the sender and delete the entire message including any
attachments.

Thank you.

> -----Original Message-----
> From: seaside-bounces at lists.squeakfoundation.org [mailto:seaside-
> bounces at lists.squeakfoundation.org] On Behalf Of isaiah
> Sent: Tuesday, August 14, 2007 8:24 AM
> To: seaside at lists.squeakfoundation.org
> Subject: [Seaside] why cant you call #renderOn: on a child component
> 
> 
> hey i dont know if this has been answered before but i cant find the
> answer.
> why shouldnt you call #renderOn: on a child component, from the parent
> component's renderOn method. what is the reason ?
> why is is recommended to use html render: childComponent, to render a
> child
> component
> 
> --
> View this message in context:
http://www.nabble.com/why-cant-you-call--
> renderOn%3A-on-a-child-component-tf4267972.html#a12146589
> Sent from the Squeak - Seaside mailing list archive at Nabble.com.
> 
> _______________________________________________
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside