Re: Feature Requests
Re: Feature Requests
- Subject: Re: Feature Requests
- From: Chris Espinosa <email@hidden>
- Date: Wed, 3 Aug 2005 21:55:38 -0700
On Aug 3, 2005, at 9:34 PM, Michael Rice wrote:
I'm using Xcode 2.0 and do C/C++ development most of the time. The following are a few feature suggestions that I think would benefit many people; please forgive me if some of these are already in Xcode 2.1.
1. Make the "all-in-one" mode strictly all-in-one. For example, when I select the "View | Switch to Header/Source File" menu or press Shift-Cmd-UpArrow, open the counterpart file in the same window - do not open another window.
This is well-known but not yet fixed.
2. For Aggregate projects, allow access to the contained projects' contents from the Aggregate project's window. Basically what I'd like to be able to do is create an Aggregate project that contains all of my sub-projects. With Xcode in "All-in-One" mode, it should never require me to open another "top-level" project window to access the source files in a sub-project or edit the settings for a sub-project.
Also a common request.
3. Add data formatters for the debugger to display info for all of the C++ Standard Library types (e.g., std::string, list, vector, etc.)
string is in 2.1 and later. The other types are not as easy: templates are just that -- templates -- and are not backed by code until instantiated. The debugger is not a compiler and can't dynamically compile template access code. For vectors of well-known scalars we can provide help, but vector of <blah>, not.
4. Provide a way to store executable arguments and environment variables settings (from the Executable Info editor) in the user perspective file instead of or in addition to in the project file. Perhaps another column in the editor that specifies where each is/should be stored. This is very important, since arguments and environment variables can be very user and host dependent. When a single project is shared by multiple users or on different host systems, settings for one user/environment may not be at all appropriate for another.
Au contraire, we have a number of complaints that the executable settings are
only in the user file and
not in the project file. The suggestion that people should be able to pick the scope of persistence (per-project-per-user, per-project-pan-user, per-user-pan-project) is known, but will take a more elegant UI.
5. Currently, when editing a project that has SCM enabled, but the SCM system is unavailable (e.g., no network connection to SCM server), Xcode prompts if SCM should be disabled or left enabled. If the user elects to disable SCM for the project, that should be a transient setting, perhaps only while the project is open. This way, if/when the connection to the SCM server is restored, the user won't have to manually re-enable SCM for each project.
This behaves as you describe in 2.1.
6. Re-read the environment settings in ~/.MacOS/environment.plist when Xcode is started. I realize this is probably more of an OS X feature request, but having to logout/login just to change an environment variable is, to say the least, very inconvenient.
As you say, this is a loginwindow issue. You can always just execute the target app from a shell in which the env vars you want are defined.
Chris
_______________________________________________
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