Re: Xcode 3.0 and new SCM features
Re: Xcode 3.0 and new SCM features
- Subject: Re: Xcode 3.0 and new SCM features
- From: Jake Traynham <email@hidden>
- Date: Thu, 10 Jan 2008 11:44:58 -0600
Hi Andrew,
Thanks for responding.
Andrew Pontious wrote:
In Xcode 2.*, Xcode's SCM system would go through all the files in your
project, figure out their location, and figure out if those locations
were under some sort of SCM system that it could detect.
As you can imagine, this could take a lot of time and resources.
Sure, that may take a lot of time and resources for what you may
consider a "standard" or "normal" repository, but for people like me
(and I'm apparently not alone), having to set the "root" of the project
up higher means it takes a lot of time and resources to evaluate all
these other files that have no meaning/bearing on the current project.
I'm not saying the new way is wrong, I'm just saying maybe it could
somehow be a compromise between the old and new way. You said the old
way was file-specific - it looked at each file individually or whatever
and this new way is folder-specific - it only pays attention to the
"root" folder you've set up. That seems logical, but perhaps instead of
just the "root" folder, it should consider all folders defined in the
"Search Paths" section of the build settings. Seems to me if a project
needs files from some other path, that it would be safe to assume those
files may be under SCM control as well.
For Xcode 3.0, we switched to a system based on the new Xcode project
root. You specify one SCM system and location for your project, and that
is used to evaluate every file under your project root.
We realize that this shuts out the kind of functionality that you're
looking for, and I apologize for that. We are looking into potential
solutions for future versions of Xcode, I can't give you any further
information than that.
I'll say again that I'm not griping about the new way or that it's
wrong or anything, but I do think it could be made more useful. I could
probably work with the new system if there was at least one change. In
the "SCM" group in the "Groups & Files" pane, when you ... undisclose
(what do you call it when you reveal what's under a disclosure
triangle?) ... that group, if it mimicked the folder structure from the
"root" of the project, it would help pinpoint or drill down to the
information I'm really looking for. This would work the same way the
main project group works. If I selected the whole SCM group, it would
show me all the files that are changed, but if I selected a subfolder of
the SCM group, it would only show me those files. That would at least
help with the "out of sight" idea of ignoring all extraneous stuff that
shows up.
It's either that, or how about integrating the SCM stuff directly
into the main project group. Just give us the ability to add the SCM
column from the SCM group/pane to the main project group/pane. You
could color code the subfolder names or badge the subfolders themselves
(in the Groups & Files pane) to indicate when there's code there that
differs from the repository. If it did that, I wouldn't use the SCM
group at all, I would just see the indicators in the main project group
and select them to update/commit/whatever. This would also make it a
moot point for me having to set my project's "root" folder higher than I
used to because the main project group only shows me the files I've
included anyway. So, even if behind the scenes the SCM feature is
working harder than it needs to looking at files my project doesn't use,
I wouldn't see them.
Just some ideas. Thanks for listening.
Jake
--
Jake Traynham
Owner, CNS Plug-ins
http://www.cnsplug-ins.com/
_______________________________________________
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