Re: (MVC) Disappearing Source == Disappearing Source Control?
Re: (MVC) Disappearing Source == Disappearing Source Control?
- Subject: Re: (MVC) Disappearing Source == Disappearing Source Control?
- From: Vince DeMarco <email@hidden>
- Date: Tue, 1 Jul 2003 09:05:56 -0700
On Tuesday, July 1, 2003, at 8:30 AM, Roy Lovejoy wrote:
I'm a Mac dev from 'way back' (Lisa Pascal).
Did a tour of duty with NeXTStep in 90-93 (NeXTWorld Expo & Everything)
Attended WWDC, loved the MVC goodies, and the objectifying of the
Controller glue code,
but something was nagging in the back of my mind.
And now it's in the front of my mind- How do developers currently diff
nib files, in a source control
environment?
It's one thing for one developer to change 'controller' .c glue code,
check it in to whatever
source control system they are using, then another engineer can do a
diff & see what has been modified.
But with an uber-cool, yet quite graphical representation, how can
engineer #2 see what UI engineer #1
mucked with in their nib file, and now, the control representations in
their nib file?.
Snooping in a .nib, I see some ascii files, and some binary stream
files, so it's not a clear cut case of
diffing text.
(besides, it would give me the heebies to edit the individual files
contained in .nib packages)
just use FileMerge,
FileMerge runs the nib file though nibtool to generate and ascii
version. The Ascii version shows everything that is editable about the
object in IB, but doesn't show you all of the possible properties of an
object
nibtool -a /path/to/my/nibfile.nib
vince
_______________________________________________
cocoa-dev mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/cocoa-dev
Do not post admin requests to the list. They will be ignored.