Re: Re: Help with understanding how #call: works

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

Cheers!

-Boris (via BlackBerry)

----- Original Message -----
From: [hidden email] <[hidden email]>
To: Seaside - general discussion <[hidden email]>
Sent: Sun Feb 24 20:56:46 2008
Subject: Re: [Seaside] Re: Help with understanding how #call: works

Malte Zacharias wrote:

<snipage>
> 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
http://straszheim.50megs.com

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside