[Seaside] Re: Help with understanding how #call: works

Boris Popov boris at deepcovelabs.com
Mon Feb 25 06:04:54 UTC 2008

No, outer components do not need to be aware of inner components possible call candidates, that would make the system unusably complicated.


-Boris (via BlackBerry)

----- Original Message -----
From: seaside-bounces at lists.squeakfoundation.org <seaside-bounces at lists.squeakfoundation.org>
To: Seaside - general discussion <seaside at lists.squeakfoundation.org>
Sent: Sun Feb 24 20:56:46 2008
Subject: Re: [Seaside] Re: Help with understanding how #call: works

Malte Zacharias wrote:

> I hope this clears it up a bit..

Not really.  What I'm looking for is this, if component A includes 
component B, but inside of B, it calls component C, what happens?

I assume C renders *in place* of B and the rest of A works as it did 
before?  Is this correct?

If so, does A have to include C in its children as well as B?

It is possible I totally don't understand this stuff.

Jeffrey Straszheim

seaside mailing list
seaside at lists.squeakfoundation.org
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20080224/19692b67/attachment.htm

More information about the seaside mailing list