> On Dec 12, 2017, at 12:08 PM, Quincey Morris > <quinceymor...@rivergatesoftware.com> wrote: > > I don’t think bindings are fading away. They can’t, while they’re the only > way to connect UI elements without custom glue code. However, the design is > ancient (IIRC, bindings were introduced in macOS 10.3, and refined in 10.4, > and really nothing has changed since then).
It is the documentation of bindings that is fading away and if you are an iOS programmer then bindings are irrelevant. Malcolm Crawford had an excellent resource on the web for understanding bindings (Cocoa Bindings Examples and Hints) but it has disappeared. Malcolm Crawford made his last post to cocoa-dev in 2012 and so time marches on. > What has fallen away (because it never really got off the ground) was the use > of *custom* bindings, in part because no one could understand what to do, and > because they really needed the IB customization features introduced in Xcode > 3.0 (or was it earlier?) and killed off in Xcode 3.1 (or thereabouts). Custom programmatic bindings (not integrated with IB) work great but it is daunting to figure this out. So I agree. > In modern terms, bindings are a horrible hack, and that’s why (I assume) they > were never taken over to iOS. I always assumed the reason bindings never came over to iOS was they consumed too much cpu power and were too difficult to understand. It seems evident that 10 or 20 years from now Apple anticipates the bulk of it programmers coming out of school will use iPads with the new style documentation. Cocoa bindings do not fit very well into this picture. --Richard Charles _______________________________________________ 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: https://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com This email sent to arch...@mail-archive.com
