Re: Which XCode files to version control? (Was: .mode1 files and version control)
Re: Which XCode files to version control? (Was: .mode1 files and version control)
- Subject: Re: Which XCode files to version control? (Was: .mode1 files and version control)
- From: Scott Tooker <email@hidden>
- Date: Wed, 11 Aug 2004 20:24:21 -0700
Currently we already separate project settings data into two parts:
project.pbxproj - per project data (file & group hierarchy, target
build settings, for example)
<username>.pbxuser - per user per project data (user bookmarks, custom
executables, UI layout)
In future releases we want to separate project data from UI layout data
(so the <username>.pbxuser file would split into two files). The .mode1
files are step in this direction.
We've also talked about separating out target-specific data from the
project.pbxproj file.
Scott
On Aug 10, 2004, at 10:45 PM, Heath Raftery wrote:
I've wondered this for a while now, but Christian's post motivated me
to put it in an email.
On 11/08/2004, at 2:47 PM, Christian Pekeler wrote:
I typically have .pbxuser files under version control, mainly to
archive launch parameters. I've noticed that as of Xcode 1.5 there are
now also .mode1 files for each user in the .pbproj directory. What's
their purpose? Would it make sense to have them under version control,
too?
I don't have any answers here, but was hoping to extend the query
somewhat. Using Borland RAD tools, version control is very difficult
because all the user settings (history lists, recent items, window
sizes) are in the same file as the project structure. You couldn't
update to someone else's project file because it would override all
your custom settings, usually breaking lots of things. In particular,
if a file was added to the project, you could update and get the new
file fine, but would have to add it and categorise it in the project
manually, because you couldn't update to the project settings file as
easily.
I always thought this was poor design - user settings should be
seperate to project metadata. The latter defines the project, the
former defines customisations which the project itself need not no
about. That is, if you were to remove all the user settings (revert
them to default say) all the information you needed to build the
project would be in the project settings.
Unfortunately, I'm seeing similar design with XCode! Inside the
project.xcode package are/were two files (as Christian mentions) but
after looking inside I can't be sure that there is a seperation
between say, saved window sizes, and project source groups.
Is it safe to commit one and not the other? Is there any official word
here? And was or is this seperation of project and user settings a
consideration in XCode's development?
Regards,
Heath
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives:
http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.
_______________________________________________
xcode-users mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/xcode-users
Do not post admin requests to the list. They will be ignored.