On Feb 25, 2010, at 11:35 AM, Quincey Morris wrote:
On Feb 25, 2010, at 10:03, Keary Suska wrote:
Have you tried using the repository management interface in Xcode? I think it will do most of what you want. The only thing it won't do is associate your groups with a filesystem path, which AFAIK you have to do manually. But that only matters for files you want to add to those groups.
Speaking from experience, I'd say you *really* don't want to just move (repository) files around in the Repository window. My experience has been that the project itself is *not* kept in sync with such changes -- though of course I may have just been Doing It Wrong™ -- and figuring out how to get the project back into a working state is hours of hair-tearing frustration.
For my own edification, I tried my own recommendation out on a project that I could afford to screw up, and it works like a charm. The only drawback is that you can only move one file at a time, which can become fairly tedious fairly quickly. These are the steps I took:
0. Made sure that all of my changers were fully committed to the repository;
1. Closed the project
2. Used the repositories window of Xcode to create the new folder and move class files over.
3. Checked out the project, replacing my local copy.
4. Opened the project when prompted. Now, all of the files were in red because Xcode didn't know where they were, so I set the folder association for the group to the new location, and bam! all the files were automatically found.
5. Ran a build just to make sure everything was kosher--and it was.
This very well may work better in 3.2 than in previous versions, but it seems to me, at least with the current Xcode version, moving using the repository is very practical.