Re: Nested component communication
Re: Nested component communication
- Subject: Re: Nested component communication
- From: Art Isbell <email@hidden>
- Date: Wed, 11 Aug 2004 09:49:34 -1000
On Aug 11, 2004, at 9:00 AM, Jean-Frangois Veillette wrote:
To minimize the risk of problems, do you component communication
explicit and restrict it to the minimum only.
I.e., override synchronizesVariablesWithBindings() to return false in
your subcomponent.
David Holt wrote on 8/10/04 6:52 PM:
From my reading, it seems that the component communication is
automatic from the parent components to child components so long as
the variables are named the same thing.
For a non-synchronizing subcomponent, the only sort of automatic
action I can think of is the use of the carat (^) syntax that will
automatically invoke valueForBinding()/setValueForBinding() without
your needing to implement these methods.
I don't implement subcomponents often enough to become totally
comfortable doing so. But I can always sort things out by rereading
the "Creating Reusable Components" chapter in the _WebObjects
Developer's Guide_
(http://developer.apple.com/documentation/LegacyTechnologies/
WebObjects/WebObjects_4.5/System/Documentation/Developer/WebObjects/
DevGuide/ReuseTOC.html).
Aloha,
Art
_______________________________________________
webobjects-dev mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/webobjects-dev
Do not post admin requests to the list. They will be ignored.