• 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: Enabling language-specific warnings in multi-language projects
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Enabling language-specific warnings in multi-language projects


  • Subject: Re: Enabling language-specific warnings in multi-language projects
  • From: Laurence Harris <email@hidden>
  • Date: Wed, 26 Jul 2006 14:26:15 -0400


On Jul 25, 2006, at 1:05 AM, Chris Espinosa wrote:

On Jul 24, 2006, at 7:46 PM, Sean McBride wrote:

It does, of course. My point was that in CW's case, almost all warnings
are controllable and _discoverable_ via the GUI, not so with Xcode. (A
couple of CW warnings are only controllable by pragmas, so it has a
similar problem to a lesser degree.)

One thing you might try is selecting "Warnings" from the "Collections" popup, and typing a few words into the search bubble at the top of the inspector. (Open up the Description window as well).


I suffered under the "too many obscure checkboxes crowded into a fixed panel in CodeWarrior" for many years myself.

Agreed. They needed to update and clean up that preferences window, but I guess they just didn't want to bother with that.


While I personally am not a big fan of checkboxes in a table,

I understand the benefits of using a big list for everything, but it's really not a good interface. This is typically the case when you try to get one widget to do too many things.


- If the Setting column is wide enough to avoid truncating any of the setting names, the entries in the Value column are often separated from their settings by too much space for me to see a setting and its value at the same time, as you can with a standard checkbox or popup button that has a title.

- Some textual settings are editable text and some set with popups, but the only indication that one uses a popup are two little triangles jammed against the right side of the list. If the window is very wide, the relationship is not obvious.

you have to admit that being able to search and sort the list of warnings or other flags you can enable

Sort how? Nothing sorts when I click on the headings. I can't sort the warnings so the ones that are on are at the top or bottom, and I can't sort by the Setting text.


, and to see a whole paragraph about each one (not just what fits into a checkbox label), adds to discoverability.

- The "Setting" column width is not persistent. Every time I open this window over a third of the warning names are truncated. That doesn't enhance to discoverability.


- There is no grouping. I'd much prefer to be able to view related warning options grouped in some way. For example, group the warnings specific to C++ together. Without grouping or sorting it's just a more or less random list of warnings.

Larry
_______________________________________________
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


  • Follow-Ups:
    • Re: Enabling language-specific warnings in multi-language projects
      • From: David Dunham <email@hidden>
References: 
 >Re: Enabling language-specific warnings in multi-language projects (From: Greg Guerin <email@hidden>)
 >Re: Enabling language-specific warnings in multi-language projects (From: "Sean McBride" <email@hidden>)
 >Re: Enabling language-specific warnings in multi-language projects (From: Shawn Erickson <email@hidden>)
 >Re: Enabling language-specific warnings in multi-language projects (From: "Sean McBride" <email@hidden>)
 >Re: Enabling language-specific warnings in multi-language projects (From: Chris Espinosa <email@hidden>)

  • Prev by Date: Re: Enabling language-specific warnings in multi-language projects
  • Next by Date: Re: Enabling language-specific warnings in multi-language projects
  • Previous by thread: Re: Enabling language-specific warnings in multi-language projects
  • Next by thread: Re: Enabling language-specific warnings in multi-language projects
  • Index(es):
    • Date
    • Thread