FROM : Uli Kusterer
DATE : Sun Nov 04 12:33:37 2007
Am 04.11.2007 um 02:18 schrieb Jon Hess:
> Interface Builder files have a long way to go with reguards to
> integrating with industry standard SCM systems. That said, you can
> get consistently good diff results with Filemerge. Filemerge runs
> Interface Builder documents through ibtool to provide a
> canonicalized human readable textual representation of a NIB before
> presenting you with a diff.
Well, I last tried this on Tiger, where nibtool is very selective as
to what information it will display to you. There's a lot missing,
like bindings. It did occasionally help to view NIBs, but it doesn't
let you merge NIB files, because it's a lossy export.
I've seen stuff in the Leopard release notes and docs that looks
like this is about to improve, but just yesterday Xcode 3 did
something with one of my NIBs that made one of my apps crash when
launched on Tiger, and I had quite a time tracking down and restoring
that. So, I'm reluctant to seriously go for Xcode 3 until I know stuff
like that has been fixed.
Cheers,
-- M. Uli Kusterer
http://www.zathras.de
DATE : Sun Nov 04 12:33:37 2007
Am 04.11.2007 um 02:18 schrieb Jon Hess:
> Interface Builder files have a long way to go with reguards to
> integrating with industry standard SCM systems. That said, you can
> get consistently good diff results with Filemerge. Filemerge runs
> Interface Builder documents through ibtool to provide a
> canonicalized human readable textual representation of a NIB before
> presenting you with a diff.
Well, I last tried this on Tiger, where nibtool is very selective as
to what information it will display to you. There's a lot missing,
like bindings. It did occasionally help to view NIBs, but it doesn't
let you merge NIB files, because it's a lossy export.
I've seen stuff in the Leopard release notes and docs that looks
like this is about to improve, but just yesterday Xcode 3 did
something with one of my NIBs that made one of my apps crash when
launched on Tiger, and I had quite a time tracking down and restoring
that. So, I'm reluctant to seriously go for Xcode 3 until I know stuff
like that has been fixed.
Cheers,
-- M. Uli Kusterer
http://www.zathras.de






Cocoa mail archive

