Re: The inevitable 1.5 suggestion list
Re: The inevitable 1.5 suggestion list
- Subject: Re: The inevitable 1.5 suggestion list
- From: Scott Tooker <email@hidden>
- Date: Fri, 13 Aug 2004 15:08:38 -0700
Please file Radars for these so we can track the issues (and get back
to you if needed).
Scott
On Aug 11, 2004, at 10:08 PM, Brian Barnes wrote:
First off, as always, thanks to Apple for working hard on this free
tool. Also, my biggest bug has been fixed ... "-fast" finally works
while using ppc_intrinsics.h. I am so happy about this :)
A couple of suggestions, after a couple of days of work.
Bugs
1) Doesn't remember the state of ... what are those called? Drag
bars? A perfect example is the project window. The way I've found
to eliminate the detail view (IMHO I find useless) is to make the
window big, drag the bar to the right, then reduce the window as far
as it will go (this drags the detail view closed). Close the project,
then re-open. The detail pane is back. Same thing for lots of other
windows.
Suggestions
1) These additional options/preferences would go a long way to
appeasing some complaints
a) global option to turn off all embedded editors (except edit
windows, off course) -- remove "drag bars" as necessary
b) global option to remove project "detail", leave just the
tree (I've tried so hard to make this happen!)
2) some window widgets
a) widget to clear console on console window (debug menu is a
weird place for it)
3) target build changes
a) I always use "All settings" as it is now, it makes more sense
(IMHO) then the collections. I say go one step further and make
the build list a tree view, the same roots as it is in the
menu in the column headers (that's a weird UI :) ). Basically, you'd
have:
v General
v Build Locations
Development build product xyz
... etc ....
b) a way to do the opposite override from project -> target
settings. The way I work is to put everything in the target and
ignore the
project settings (including deployment, development.) I'd
rather have those as selectable targets. Strange, maybe. I get the
general idea why it's the way it is now, but it would be
neat to have a "ignore project settings" flag in the target, then I
could just
concern myself with the target setup and ignore everything
else. This allows me to have all settings for a project in one place
(yes, this makes more sense for single target projects).
c) way to copy target build settings, from one project to another
(not super important, but it could be used)
[>] Brian
_______________________________________________
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.
_______________________________________________
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.