Re: Xcode 2.0 upgrade glitch
Re: Xcode 2.0 upgrade glitch
- Subject: Re: Xcode 2.0 upgrade glitch
- From: Scott Tooker <email@hidden>
- Date: Sun, 8 May 2005 23:51:43 -0700
On May 8, 2005, at 11:39 PM, j o a r wrote:
On 9 maj 2005, at 01.20, Chris Espinosa wrote:
In most cases teams can share a project file between 1.5 and 2.0,
as long as the team working on 2.0 doesn't add build settings that
are 2.0 only.
If you have a lot of developers, most of who of course will not be
bothered to learn what version a particular feature of Xcode
appeared in, the only safe thing to do is to upgrade everyone at
the same time. There is no telling when someone will accidently use
some feature that will break compatibility, and how would you even
notice?
One way to support cross-version compatibility would be if you
added the ability to detect and optionally warn about version
specific project settings, in something like the way that Interface
Builder does it's compatibility checking. Another thing that
probably would be required is that Xcode needs to ensure / promise
to always preserve all keys found in the project file - even the
ones it doesn't understand / know about - as they could be keys
saved by a later version of Xcode.
We try to do this to the best of our ability, but sometimes a needed
change requires incompatible changes in the file format. We are well,
well, well aware that introducing a new version of the project file
format is not something our developers like and we try our best to
avoid it when we can.
Please file a bug about the IB-style warnings, that sounds like an
interesting future direction.
That said, I think it would probably be a better use of your time
to make it possible to run Xcode on more than just one version of
Mac OS X, rather than fiddling with file format compatibility.
I think it's unfortunate that you have to upgrade both the OS and
Xcode at the same time. If you just allowed Xcode to run not only
on the latest and greatest, but also the OS version before that, I
think that much of that pain would go away.
This is where we want to go in the long run, but it's something that
will take some work. Our work on SDK support is a first, small step
in that direction.
Scott
j o a r
_______________________________________________
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
_______________________________________________
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