> ...then it must be > difficult. Actually, no. It is so much simpler and more elegant a solution than other frameworks that people have difficulty comprehending precisely because they keep trying to make it more complex than it is.
> Now if what they are trying to say is that I can bind a controller to > File's Owner and it will "see" all the properties of all the objects > in the class that File's Owner is set to, that would be cool. In that > case it is just serving as an instance of a class and can be used to > reach properties of objects of that class. Yes, exactly: "it will see all the properties of all the objects in the class that File's Owner is set to" is what "proxy" means. > What other objects outside the nib? That's up to you. Although the most general answer would be "your application", but that's a bit too vague. The point is, a nib file by itself isn't worth much, at some point, somehow, the application has to be able to connect to it to gather data, for whatever purpose the application is intended. I'm going to take a guess here, that if the sense of the documentation were inverted, so that it said "so that objects outside the nib can communicate with the nib objects", it might have made more sense to you. -- Scott Ribe [EMAIL PROTECTED] http://www.killerbytes.com/ (303) 722-0567 voice _______________________________________________ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the moderators at cocoa-dev-admins(at)lists.apple.com Help/Unsubscribe/Update your Subscription: http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to [EMAIL PROTECTED]
