Re: AI in Xcode
Re: AI in Xcode
- Subject: Re: AI in Xcode
- From: Ladd Van Tol <email@hidden>
- Date: Thu, 15 Sep 2005 20:40:46 -0700
On Sep 15, 2005, at 6:51 PM, Walt Horat wrote:
I could go on, and on, and probably should. Lets just say that I
now know
better, and whenever I check out and notice a project or nib file has
changed, I just delete it and pull it down from subversion again,
rather
than wait to see if the merge corrupted it. Because corrupted xcode
projects
and nibs usually wait until late in the game to behave strangely,
and let
you waste an inordinate amount of time before you finally delete your
corrupted copy and check out again. I can only presume that, hell,
I don't
know, a checksum would be "too hard"...
To Apple's credit, project merges work enormously better in Xcode 2.1
and above. Whereas bogus merges were commonplace with Xcode 2.0, once
we switched to 2.1 I have never had a bad merge or even a conflict.
YMMV.
With regard to nibs, you should not be doing merges on the
objects.nib file -- it's binary, and will not respond well. The other
two files (classes.nib and info.nib) appear to be fairly mergable,
although some caution may be in order.
Your other complaints are certainly valid -- I would recommend filing
bugs, then gently harassing the list until they get fixed. Apple has
been gradually working through my more pressing bugs, and I've been
pleased with the recent improvements, despite the occasional
frustrations.
- Ladd
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden
| References: | |
| | >AI in Xcode (From: Walt Horat <email@hidden>) |