[Seaside] WAComponent>>#call:/#answer: usage question
cappadonza at hotmail.com
Tue Sep 11 13:24:45 UTC 2007
Lukas Renggli wrote:
>> 1.) If using a WATask, I must be able to simultaneously #call: twice.
>>>That doesn't really make sense, because #call: replaces an entire
>>>component with a new one.
>>>In case you really want to change two components at once you can use
>>>#show: that does not block (check out the comments of the methods
>>>#call: and #show:).
> couldnt we achive the same thing by composing the component with some
> child components. In what use cases would you use #show:
> still not sure how #show: works. i know #call: blocks out the calling
> component till an answer is recieved. when would you use #show:
>> 2.) The WATask must be able to render the Heading and Anchor.
>>>WATask does not render anything (check out the class comment). It just
>>>delegates the rendering to a sequenze of other components.
>> 3.) If I make a separate component for the heading and anchor, then
>> #render: those components, it must be able to #answer: for it's parent
>>>It looks like you need to compose your components, not to #call: them.
>>>#call: is only useful if you expect to get back a result (read the
>>>class comment of WAComponent).
> Lukas Renggli
> Seaside mailing list
> Seaside at lists.squeakfoundation.org
View this message in context: http://www.nabble.com/WAComponent%3E%3E-call%3A--answer%3A-usage-question-tf4304958.html#a12614551
Sent from the Squeak - Seaside mailing list archive at Nabble.com.
More information about the seaside