Wouldn't it be better design-wise to factor out this functionality
into some helper object? Then in the child you could bind to a getter
that relies upon this helper - and the parent does the same.
Just thinking loud
---markus---
On 18.01.2007, at 17:55, Robert Walker wrote:
Seabix,
Outsourcing would be a possibility. But I'll try with key value coding
first.
___
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list (Webobjects-dev@lists.apple.com)
Help/Unsubscribe/Update your
Seabix,
Wouldn't using performParentAction() from a subcomponent invoke an
action and subsequently create a new request-response loop? I don't
really think that's what you're after.
It seems to me that you really want an instance variable in the
parent that you would access from the
Is it possible to do the following? How?
ParentComponent - Parent.wo
ChildComponent - Child.wo
There is a WORepetiotion in Child.woa with a bunch of String values. So the
WORepetition is bound to the NSArray listValues and to the String value.
No i wan't to give the value of each iteration up
