Scott,
Perhaps I don't understand what a custom executable is for...
For example, let's say I have a API project that needs to have an
additional application to run the API. This is a 'custom executable,'
right?
If that information is saved as part of the 'user' data, and I give my
project to another developer on the team, they will have to locate and add
their own 'custom executable' even though it's the same one I used???
In my opinion, this is an example where the custom executable should NOT
be considered a user setting; there is no way to debug the project without
this information...
A custom executable should be considered an integral part of the project
instead of 'fluff' that can be lost by passing the project around...
or by logging in a different user...
or switching to another machine (aka going home for the day)
Unless, of course, I've missed the point???
Scott Tooker <email@hidden> wrote on 08/24/2004 01:26:01 PM:
> Some of it was, but other information was never being stored prior to
> 1.5. Also, we wanted to break out the less critical per-user
> information into their own files to make it easier to just back up the
> per-user information that affects the actual project contents (like
> custom executables, breakpoints, and bookmarks).
>
> Scott
>
> On Aug 24, 2004, at 1:15 PM, Finlay Dobbie wrote:
>
> >
> > On 24 Aug 2004, at 01:38, Scott Tooker wrote:
> >
> >> That file contains information about your UI layout. It doesn't
> >> contain anything critical to the project, so it's up to you if you
> >> want to archive it in CVS.
> >
> > Wasn't this stored in <username>.pbxuser or something similar until
> > 1.5? Why the change?
> >
> > -- Finlay
_______________________________________________
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.
