Trust me when I say that we didn't want to introduce a new
extension, but changes in Xcode 2.1 forced our hand :(
How about adding version information to the project file, so you
don't have to do that in the future - regardless of the changes you
make to the file format?
If you add a version "header" to the project file, you could just
post a "sorry, can't read this file" error panel when you encounter
a project file that is newer than the version reading the file.
Actually we have had a "projectObjectVersion" since the beginning of
Project Builder, that wasn't the issue. Co-development of Xcode 1.5
and Xcode 2.x projects was. To solve those sorts of problems we
needed changes to the project file format that were outside the scope
of Xcode 2.1.
As I stated earlier, we tried to avoid making another extension
change, but we couldn't avoid it in Xcode 2.1. Moving forward we want
to have a more robust project file format that won't require such
drastic changes.
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:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
