Just Launched: You can now import projects and releases from Google Code onto SourceForge
We are excited to release new functionality to enable a 1-click import from Google Code onto the Allura platform on SourceForge. You can import tickets, wikis, source, releases, and more with a few simple steps. Read More
I finally got around to taking a look at these "Cocoa Bindings" that
everyone is so hyped about. I suppose they *are* pretty damn useful, at
that. There's a trade-off, of course; they drastically reduce the
amount of "glue" you need to write, but you have to be willing to make
your application Panther-only.
The first thing I needed was Key-Value Coding and KV Observing. No
problem, says I - Interface Builder uses KVC, so I'm already halfway
Wrong. IB doesn't use "real" KVC - that is, it doesn't call
setValue:forKey: to connect outlets found in NIBs, it uses a half-assed
KVC implementation found in NSNibOutletConnector instead. What I'd
already done was good enough for IB, but not good enough for "real"
Okay, well, I've intended to implement the real thing anyway, and it's
only two additional methods in CBPerlObject. Not too hard.
So, I'm re-building the currency converter tutorial in Perl. Almost
everything is working - the setter methods are called when I change the
values in the text boxes, and the getter method is called to initialize
the result field when the app first starts. The only thing missing is,
the result field is *not* getting updated when changes are made.
Maybe the docs have been updated? I'll look online. Have they *ever*
been updated! I find what's missing in about thirty seconds: A class
method needs to be added to the controller class, that defines the
dependencies between keys.
A class method? Oh. Well, those *are* on the "to do" list...
So close, and yet so far.