[Seaside] Help with understanding how #call: works

Diogenes Moreira diogenes.moreira at gmail.com
Fri Feb 22 15:25:21 UTC 2008


In Simple words..

When you use #call, you send the control to B object and  Object A waits for
B object answer.

I can guess  this problem happend  becouse  B Object don't receive any
canvas or context. renderON: method do this.

If you want render the B Object, the correct Form is:

#renderContentOn: html
      "child is a instance variable"
     self child:=B new.
     html render: self child.

And not forget children method.

       ^ self child.

Is very common use #call method in callbacks..


PD: sorry for my english.
On Fri, Feb 22, 2008 at 1:00 PM, Squeaker <squeakman at gmail.com> wrote:

> Greetings,
> I have two components A and B and I have the following code in A.
> renderContentOn: html
>        self call: B new.
> What I was expecting is that B would be rendered.
> (I suspect that there would be problems when B answers but for this
> experiment, this was not my concern yet.)
> My question is: Why doesn't B get rendered?  All I get is a blank screen.
> And, I know this a contrived example and is probably not something one
> would normally do.  I just want to understand why this does not work.
> Many Thanks,
> Frank
> _______________________________________________
> seaside mailing list
> seaside at lists.squeakfoundation.org
> http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.squeakfoundation.org/pipermail/seaside/attachments/20080222/300aa4f6/attachment.htm

More information about the seaside mailing list