Re: moving files into groups which match the filesystem
Re: moving files into groups which match the filesystem
- Subject: Re: moving files into groups which match the filesystem
- From: Michael Watson <email@hidden>
- Date: Sat, 18 Jun 2011 20:48:58 -0700
sending enhancement requests to the list is the wrong way to have your requests heard. you need to file radars for the things you want.
http://bugreport.apple.com
- m
On 18 Jun, 2011, at 05:27, Nikolaus Heger wrote:
> Sorry to bump this old thread but this keeps annoying me.
>
> Here is what I have done in the past, in response to your original question, and given a project that's a total mess:
>
> - Remove all classes and groups from project
> - Organize them into folders and sub folders either in the Finder or using your preferred tools
> - Sync with svn using the command line tool or your svn tool of choice (I sometimes resort to Eclipse just for that)
> - Once the folders and svn status are pristine....
> - Take the new "Classes" folder and drag it into the project, choose "create groups for any added folders". Copy can be selected or de-selected but shouldn't be necessary as you created the Classes folder in the right place on the file system so it won't copy.
>
> Then XCode creates the groups for folders.
>
> FEATURE REQUEST:
> Please make it an option to "Keep my Classes Organized" the same way iTunes does for music. Then those people who really want two sets of hierarchies can muddle along as they have done before, and we can have groups that simply represent folders on the disk. It should be possible to set this on a group level, so I can turn it on for "Classes" and "Resources" and keep it off for Frameworks, Products, etc.
>
> Having 100s of files and resources all in the root directory of the project seems to be the default setting in XCode, and it's rather lame.
>
> N.
>
> On Feb 27, 2010, at 11:06 , Roland King wrote:
>
>>
>> On 26-Feb-2010, at 5:39 AM, Keary Suska wrote:
>>
>>> 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.
>>>
>>
>> This does work. I managed to speed the process up a bit using the command line svn (svn mv <files> directory). Indeed if you have the files in the group to start with in XCode, they go red when you move them with svn mv, and just repointing the group to the correct directory finds them again. This is pretty quick.
>>
>> Thanks Keary
>>
>>
>>
>> _______________________________________________
>> 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
_______________________________________________
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