Re: My bindings-enabled NIB ate itself... ?
Re: My bindings-enabled NIB ate itself... ?
- Subject: Re: My bindings-enabled NIB ate itself... ?
- From: Georg Tuparev <email@hidden>
- Date: Tue, 30 Nov 2004 10:13:46 +0100
On Nov 29, 2004, at 4:18 PM, Steven Palm wrote:
Malcolm is very serious :-(
IB does not like to remove bindings --- just to add them. With the
exception of very trivial cases like making a Preferences panel I
stopped using bindings in IB (but still use them programatically).
So basically, so much for "no glue code", because what you are really
saying is that you have to create outlets for every user interface
object and controller and them bind them together in code if you want
to have any semblance of control over what is happening? Egads...
Well, it is not so bad. What I am suggesting is following:
- do not use bindings in windows that need to be released after being
closed. Coping with the memory leaks is possible, but not worth the
effort.
- do not use bindings in multithreaded applications or with DO. NSProxy
& Co. will feel unhappy. Again, it is perfectly possible to subclass
few bindings related classes and use poseAs: to fix this, but again,
not worth the effort ... and not very trivial too.
- do not use bindings in a real project if you still do not understand
them well. Use toy apps to learn about them and to experiment with new
ideas. And KVC is always recommended ... with or without bindings.
In most other cases, bindings are great help...
Georg Tuparev
Tuparev Technologies
Klipper 13
1186 VR Amstelveen
The Netherlands
Mobile: +31-6-55798196
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Cocoa-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden