<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=utf-8">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.5.7651.59">
<TITLE>Re: [Seaside] Re: Help with understanding how #call: works</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/plain format -->
<P><FONT SIZE=2>No, outer components do not need to be aware of inner components possible call candidates, that would make the system unusably complicated.<BR>
<BR>
Cheers!<BR>
<BR>
-Boris (via BlackBerry)<BR>
<BR>
----- Original Message -----<BR>
From: seaside-bounces@lists.squeakfoundation.org <seaside-bounces@lists.squeakfoundation.org><BR>
To: Seaside - general discussion <seaside@lists.squeakfoundation.org><BR>
Sent: Sun Feb 24 20:56:46 2008<BR>
Subject: Re: [Seaside] Re: Help with understanding how #call: works<BR>
<BR>
Malte Zacharias wrote:<BR>
<BR>
<snipage><BR>
> I hope this clears it up a bit..<BR>
><BR>
<BR>
Not really. What I'm looking for is this, if component A includes<BR>
component B, but inside of B, it calls component C, what happens?<BR>
<BR>
I assume C renders *in place* of B and the rest of A works as it did<BR>
before? Is this correct?<BR>
<BR>
If so, does A have to include C in its children as well as B?<BR>
<BR>
It is possible I totally don't understand this stuff.<BR>
<BR>
--<BR>
Jeffrey Straszheim<BR>
<A HREF="http://straszheim.50megs.com">http://straszheim.50megs.com</A><BR>
<BR>
_______________________________________________<BR>
seaside mailing list<BR>
seaside@lists.squeakfoundation.org<BR>
<A HREF="http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside">http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside</A><BR>
</FONT>
</P>
</BODY>
</HTML>