On 2006-07-25 10:57, Matt Neuburg said:
>>My point was that in CW's case, almost all warnings
>>are controllable and _discoverable_ via the GUI, not so with Xcode.
>
>This sounds like a third-party opportunity. Why not write us all an
>application consisting of checkboxes for the "missing" settings? In other
>words, provide the interface you wish Xcode had. You can easily access the
>setting thru AppleScript, e.g.:
>
>tell application "Xcode"
> tell project 1
> tell target 1
> value of build setting "WARNING_CFLAGS" of build configuration "Debug"
> end tell
> end tell
>end tell
>
>This app could be like Accessorizer for warning flags, as it were. So
>something positive would come out of this, instead of complaints, and you'd
>have done us all a big favor by codifying your expertise about warnings into
>a nice interface. m.
I assume you're just poking fun at me, and yes, I'm laughing, believe me. :)
Anyway, I have tried to make something positive out of this experience,
by collecting what I've learned here:
<http://www.cocoadev.com/index.pl?XCodeTips>
I hope that's an ok place to stick it, and that others will benefit.
--
____________________________________________________________
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:
http://lists.apple.com/mailman/options/xcode-users/email@hidden
This email sent to email@hidden
