Re: documenting bindings (was: Re: Dynamically loading a part of a Window in Cocoa)
Re: documenting bindings (was: Re: Dynamically loading a part of a Window in Cocoa)
- Subject: Re: documenting bindings (was: Re: Dynamically loading a part of a Window in Cocoa)
- From: Jonathan Hendry <email@hidden>
- Date: Fri, 03 Jul 2009 02:22:37 -0400
On Jul 3, 2009, at 00:25 AM, Jeff Johnson wrote:
This is why I tell people nibs are no good.
Also bindings. ;-)
Bindings are definitely the worst-case scenario for nibs. They tend to
proliferate, and they are burrowed deep in the IB UI making them hard
to miss if you don't check every widget on every tab view, etc.
Where I work, we implement experiments as loadable bundles. Since the
experiments tend to be very similar but specific to a student's
particular line of research, we have a tool that clones an existing
experiment project into a new project folder. It modifies class, ivar,
and constant identifier prefixes, removing a lot of drudge work, but
can't get into the nibs to change the bindings to refer to the new
keys. So we have to go through the nibs, track down all the bindings,
and make sure they're updated with keys that use the new project's
prefix string rather than the old one.
Some kind of bindings editing tool would be very much appreciated.
Maybe a table listing a nib's keys that are bound in the first column,
with additional info in additional columns, such as the associated UI
objects.
That at least would let you sort alphabetically, which would catch
stragglers, and would let you more easily check for missing keys.
_______________________________________________
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