[Seaside] calls within Children components
jfitzell at gmail.com
Wed Jul 29 16:23:11 UTC 2009
Nothing springs obviously to mind from what you've shown other than to
mention that lazy initialization is problematic with components, but
if you're sure the editor is being created in #initialize then that
should be fine. Mind you, if that's the case, why why not just put the
initialization directly within #initialize?
My advice is to create some new test components and find the smallest,
simplest possible example you can that demonstrates the problem. If
doing so doesn't allow you to find the problem yourself, you can post
a fileout or an .mcz of the example here for someone to try - that
will almost certainly allow someone to quickly figure out what's
holding you up.
On Wed, Jul 29, 2009 at 8:45 AM, Kevin Lacobie<kevin at agoric.com> wrote:
> I'm having a problem with call: not working for an anchor within a child
> component. The same call: does work for the parent component, so it is
> leaving me puzzled; perhaps I'm not doing something right with children?
> Here's the callback in question, inside renderContentOn: of the child
> html anchor callback: [self editArgument: myArgument]; with:
> myArgument title.
> and, the editArgument method:
> editArgument: anArgument
> self editor doc: anIBISDoc.
> self call: self editor
> ^myEditor ifNil: [myEditor := IBISDocumentEditor new]
> myEditor is added to the children OrderedCollection upon initialization.
> IBISDocumentEditor is a WAComponent. When the anchor above is clicked,
> I've confirmed that editor doc: is invoked, but it never makes it to self
> call: . More precisely, IBISDocumentEditor's renderContentOn: is never
> called. The same pattern of code works just fine when used in the parent
> component, so I'm puzzled. Ideas?
> seaside mailing list
> seaside at lists.squeakfoundation.org
More information about the seaside