FROM : Georg Tuparev
DATE : Tue Nov 30 10:13:46 2004
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
DATE : Tue Nov 30 10:13:46 2004
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
| Related mails | Author | Date |
|---|---|---|
| Steven Palm | Nov 29, 03:12 | |
| mmalcolm crawford | Nov 29, 04:23 | |
| Steven Palm | Nov 29, 04:31 | |
| Larry Fransson | Nov 29, 07:05 | |
| Georg Tuparev | Nov 29, 12:55 | |
| Steven Palm | Nov 29, 16:18 | |
| Steven Palm | Nov 29, 16:33 | |
| Georg Tuparev | Nov 30, 10:13 |






Cocoa mail archive

