Re: Groups vs. Folder Refs
Re: Groups vs. Folder Refs
- Subject: Re: Groups vs. Folder Refs
- From: Aroon Pahwa <email@hidden>
- Date: Wed, 13 May 2009 15:00:34 -0700
- Acceptlanguage: en-US
- Thread-topic: Groups vs. Folder Refs
On 5/13/09 2:09 PM, "Chris Espinosa" <email@hidden> wrote:
>
> A folder reference (blue folder) is entirely different. It is a single entry
> that directly and irrevocably represents a directory in the file system, and
> its entire contents. You can view the contents of the folder and edit the
> files contained in it, but the folder reference¹s contents are not project
> members individually. Only the folder itself is.
>
> The advantage of this is that you can use the folder reference as a proxy for
> "copy the entire contents of this folder, regardless" in a Copy Files or Copy
> Bundle Resources build phase. Which means you can add art, documentation,
> etc. without thrashing your project file.
>
> The disadvantage is that the files in the folder are not under Xcode's SCM
> control; their contents and timestamps are not scanned by Xcode to force a
> re-copy or re-build if they're changed; you and a co-worker may have identical
> projects that build and behave differently because the contents of the folder
> reference happen to be different.
>
> Chris
Oh! Very helpful, thanks. I think we'll be sticking to Groups then. Having
the IDE take care of remembering what needs to be compiled is always nice.
Aroon
_______________________________________________
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