Re: Cocoa bindings and reluctance to use NSPopupButon
Re: Cocoa bindings and reluctance to use NSPopupButon
- Subject: Re: Cocoa bindings and reluctance to use NSPopupButon
- From: Brett Powley <email@hidden>
- Date: Mon, 19 May 2008 13:29:33 +1000
On 19/05/2008, at 12:38 PM, Andreas Mayer wrote:
Am 19.05.2008 um 04:03 Uhr schrieb mmalc crawford:
Which is exactly what the documentation takes pains to tell you.
I guess it's just not clear enough. There should be a big red
warning box:
"Don't try to use Core Data or Cocoa Bindings unless you are an
experienced Cocoa programmer and understand - and have used - all
the underlying technologies."
The problem is that we tend to be seduced by slick WWDC demos which
show us how to write the next Adobe Photoshop in 15 minutes with zero
lines of code, using Interface Builder, Core Data, and Cocoa
Bindings :-)
Of course I exaggerate, but my experience has been that there is quite
a lot of understanding that goes into knowing what to connect to what,
that isn't at all apparent until you try to do it yourself. You may
be able to do cool things with zero lines of code, but it often takes
a long time to write those zero lines.
I think one of the issues is that one of the normal sources of
inspiration - sample code - often isn't really tahat useful for things
done using Interface Builder. Seeing things already nicely connected
up doesn't tell you why they're done that way, and also doesn't tell
you about the other subtly-different-but-wrong ways of doing things.
Maybe the only way to do it is to work your way up to your own
personal "aha" moment by spending days getting a popup button to work
(I've been there too).
Brett
_______________________________________________
Cocoa-dev mailing list (email@hidden)
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:
This email sent to email@hidden