Revision as of 21:16, 25 June 2013 by Sdedic (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)


Term definitions

  • File Analyzer: analyzer which works with disk files. Possibly 3rd party library or executable
  • Live Analyzer: analyzer running on NetBeans platform, or with an agent, capable of reading editor contents
  • Passive inspection: inspection that does not provide a fix / refactoring. Typically a hint that originates from report of an external analyzer
  • Active inspection: inspection that provides a fix / refactoring (or more fixes).
  • Inspect will be used as a shortcut for Source | Inspect action and the appropriate UI
  • Options will represent the UI found at Tools | Options - Editor - Hints
  • Transform identifies the Refactor | Inspect & Transform action and the relevant UI

Identified issues

Inconsistencies and gaps

  • Cannot reuse custom inspection configuration -> Project. Only the Default configuration can be copied over to the project.
  • "new" inspection can be defined in Inspect & Transform, but not in Source | Inspect or Tools | Options
  • Source | Inspect and Inspect & Transform works on global configuration items, which are not visible in Tools | Options
  • Configuration 'Default' shared between Transform and Options, but not between Inspect and Options (possibly just defect)
  • Transform - Manage Configuration lists passive inspections, while Transform - Select single does not

Some more controversial inconsistencies

Different 'level' of fixed entries in Configuration selector

File analyzers, live analyzers, Configurations which mix File and live analyzers. Consider additional Live Analyzers will be added for individual languages: PHP, Javascript. The combo will not group items semantically, by language, or by live/file. In addition, user-defined items are last.

Cannot reuse custom inspection configuration -> Editor

The user must mirror the necessary changes to the Default configuration. From a high-level perspective, a Configuration represents a certain quality goal or metric which should be achieved, or at least be measured for the sources. While the goal check (Inspect) checks one Configuration, routine coding work (Editor hints) then is not guided towards that desired goal (the defined Configuration) but towards a different goal described by the builtin Configuration "Default".

Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo