On May 14, 2008, at 4:10 PM, Hamish Allan wrote:
On Wed, May 14, 2008 at 11:25 PM, Mike Fischer
<[EMAIL PROTECTED]> wrote:
(I know this can be hacked, and that while verbose it's only xml.
But I'd
want my apps building in the next Xcode (sub-)release as well.)
Sure, well, you can't eat your cake and have it ;)
I'd have thought that you could maybe try to automate "Whenever any of
the parts of nib N1 and N2 change that are identical in both nibs I
have to remember to make the changes in both."
You can also use ibtool for verification
How so?
, so I don't buy that
"extremely dangerous" stuff
Just because a tool doesn't crash reading the file, and everything
appears to work normally doesn't mean that the file is correct and
valid.
As for the original question, you can modify an IB file, to some
extent, using ibtool --import and ibtool --export. For example, you
might consider placing all of your views and objects in the XIB/NIB,
and then using these options to control the isHidden property of
various views. That won't be easy though, as it isn't an intended
usage of ibtool. I think the best option here is to make the changes
in code, and to only use on IB file.
Good Luck -
Jon Hess
, and the bit about backwards compatibility
is irrelevant.
Hamish
_______________________________________________
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:
http://lists.apple.com/mailman/options/cocoa-dev/jhess%40apple.com
This email sent to [EMAIL PROTECTED]
_______________________________________________
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to [EMAIL PROTECTED]
