Re: SCN in XCode 3.0 Leopard
Re: SCN in XCode 3.0 Leopard
- Subject: Re: SCN in XCode 3.0 Leopard
- From: "Timothy Reaves" <email@hidden>
- Date: Mon, 29 Oct 2007 16:26:33 -0400 (EDT)
- Importance: Normal
> On 27 Oct 2007, at 8:19 PM, Timothy Reaves wrote:
>
>> On Oct 27, 2007, at 10:58 AM, Keith Wilson wrote:
>>
>>> Has anyone got SVN working in XCode 3.0 and Leopard 10.0
>>>
>>> I need instructions (please) to set up SCM on a single machine as a
>>> sole developer on an iMac Intel.
>>>
>>> The XCode documentation seems to be out of date, (it mentions using
>>> using nicl which is not shipped with Leopard).
>>>
>>> OCVS is not shipped with Leopard and CVS does not support
>>> wrappers , so that leaves SVN.
>>>
>>> Thanks, Keith
>>>
>>
>> Skip it; source control integration into XCode is a (bad) joke.
>
> Well, _that's_ helpful. And, of course, your unsupported opinion is
> certainly good enough for me, but others may be curious...
>
> Are you speaking from experience of Xcode 3.0?
>
> How, EXACTLY, do you find Xcode's SCM support deficient? Which parts
> did you try? What did you expect? What did you get? Inconvenience?
> Data loss?
>
> Please share more.
>
> F
>
>
>
All you need to do is use something like Eclipse to understand how
horrible it is in XCode. Or Wing. Or IntellaJ. Or SlickEdit Or
even Microsoft's IDE's. The deficiencies are too many to innumerate,
and I shouldn't have to (to Apple, who should have researched it).
Yes, I've filed defects. No, Apple has said they won't act.
As to data loss, the integration itself hasn't caused it, but the way
it acts has. Unfortunately with Subversion, it can be easy to do
something unintentional that causes data loss (even in Eclipse, where
the integration is incredible).
The source control integration in XCode is kinda like the unit
testing, and even Python; in all cases, I've filed bugs against 3.0,
asking for more features or fixes to broken code (SenTestKit will not
work in XCode 3 if you use all of Objc2's features). If ALL cases,
Apple's response (I have it in writing) is that they consider the
issues closed and I should contact the open source community. But,
wait a minute: Apple was the one that announced the integration of
testing (which is why Sen:te dropped support), Python (why are they
telling me to ask the Python community for why the XCode templates
don't work?) and source control (but they've never actually compared
the support to other IDE's).
Is the support better than it was in 1.0? I should hope so. But that
doesn't mean it's good.
_______________________________________________
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