This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
The term "transformers" is pretty intuitive in Jackpot, I think: you transform one source form to another. But the term "operators" left me scratching my head. I would not have expected to find things like "Unused Variables" there. Perhaps the term has merit with reference to Jackpot internals, but from a user perspective it looks odd - '+' is an operator, but how is "Statistics" an operator? If anything, I would expect "operators" to mean what is currently called "transformers". "Searches" or "queries" might make more sense in the UI. (Just something to consider as the module moves from being an alpha tool for expert users to an integral IDE feature. Longer term, the use of "Jackpot" as a menu name is improper as that is a project code name rather than a user feature - would want to see these things tied smoothly into the "Edit" and "Refactor" menus.)
Operators are the search half of search-and-replace, in that they generate a report but don't modify the source in any way. The problem is that "Search" is well-defined for text searching. Any suggestions on a better term?
IMHO "search" could be used just as well for structural as for text searches.
Changed "Operators" to "Query" and "Transformers" to "Transform". Query is more accurate than search because queries (as I understand them) don't stop when a match is found but instead return all matches. There was also a minor problem coming up with a good mnemonic for "Search" with "Start" right above it.
Sounds fine. Re. stopping on first match: note that Edit -> Find (in selection, or in projects) opens a window Search Results, which shows all matches. So I don't think a user would be surprised by "search" showing multiple hits.