• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: New to Xcode and need help
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: New to Xcode and need help


  • Subject: Re: New to Xcode and need help
  • From: Scott Tooker <email@hidden>
  • Date: Thu, 23 Jun 2005 14:00:54 -0700


On Jun 23, 2005, at 1:20 PM, Sean McBride wrote:

On 2005-06-23 12:56, Scott Tooker said:


Personally, I feel that *every* option like the above should be
available in the GUI as a checkbox or whatever is appropriate.
Having to to hunt down things like this is very wasteful of time
and resources.... IF you are even aware that something might be
able to be set like this to even begin searching for it.

Just my two cents. I know you guys are doing well, but I'd love to
hear someone say that you have a new team policy:  NO new compiler/
lnker/etc settings unless available as GUI options as well.


Taking the stand that all compiler/linker/tool settings HAVE to have associated UI is just not feasible, there are just too many flags and settings out there.


Hmmmm, CodeWarrior pretty much achieves what you call not feasible. In
all my years with CW, I never had to specify any parameters to any
command line anythings. (fancy pragmas were needed sometimes, yes.) So
I have to agree with Bryan. IMNSHO, the fact that XCode is built on top
of command line tools is the source of almost all its problems. If it
were not the case, the UI would have to be better thought out, because
Apple could never say to itself "we'll just let the user specify the
arguments to gcc here".

GCC has WAY more build settings than CodeWarrior has. Go read the gcc man page and look at the list of possible flags. For what it is worth, I think CodeWarrior does a good job of laying out the target settings available, but they have a significanly smaller set to show (though there is no way to search for a setting short of looking at all the panels). If CodeWarrior had as many options as GCC, I doubt their target settings UI would look like it does.


As far as custom UI goes, we've talked about having a subset of the possible GCC settings that are more commonly used get real custom UI (ala CodeWarrior) and then keep the currently existing UI as an "expert" view that shows all the GCC settings in a table view (including custom build settings). The tricky part would be providing customized UI layouts for groups of settings, but still making it easy to search for a given build setting.

Scott


-- ____________________________________________________________ Sean McBride, B. Eng email@hidden Rogue Research www.rogue-research.com Mac Software Developer Montréal, Québec, Canada




_______________________________________________ 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
References: 
 >New to Xcode and need help (From: RC <email@hidden>)
 >Re: New to Xcode and need help (From: Scott Tooker <email@hidden>)
 >Re: New to Xcode and need help (From: Bryan Pietrzak <email@hidden>)
 >Re: New to Xcode and need help (From: Scott Tooker <email@hidden>)
 >Re: New to Xcode and need help (From: "Sean McBride" <email@hidden>)

  • Prev by Date: Re: New to Xcode and need help
  • Next by Date: Re: New to Xcode and need help
  • Previous by thread: Re: New to Xcode and need help
  • Next by thread: Reference list of compiler messages?
  • Index(es):
    • Date
    • Thread