Jump to: navigation, search

Difference between revisions of "Platform UI/Bug Triage Tips"

(Whose bug is it anyway?)
 
Line 9: Line 9:
  
 
== Whose bug is it anyway? ==
 
== Whose bug is it anyway? ==
* When the problem report involves some contribution that is not made my platform UI, PDE plug-in spy is your friend for figuring out where a particular UI contribution comes from.   
+
=== Plug-in Spy ===
** For selections, menus, dialogs, wizards, use Alt-Shift-F1 to launch the plug-in spy.  It will tell you who made the contribution.  
+
When the problem report involves some contribution that is not made my platform UI, PDE plug-in spy is your friend for figuring out where a particular UI contribution comes from.   
** For context menu items, select the item whose context menu you are interested in, use Alt-Shift-F2 to preload the plug-in spy (the cursor will change), then open the context menu and click the menu item.  This will show you who made the menu contribution.
+
* For selections, menus, dialogs, wizards, use Alt-Shift-F1 to launch the plug-in spy.  It will tell you who made the contribution.  
 +
* For context menu items, select the item whose context menu you are interested in, use Alt-Shift-F2 to preload the plug-in spy (the cursor will change), then open the context menu and click the menu item.  This will show you who made the menu contribution.

Latest revision as of 13:01, 29 July 2009

This is a list of tips that bug triagers use to figure out where a bug should go.

Bugs within Platform UI

  • Remember that the [JFace] component is for those JFace bugs that don't belong to the more specific JFace component areas ([Dialogs], [Preferences], [Viewers] and [Wizards]). Bug reporters will often mention "JFace" in the bug title, but read further to see if it can be categorized more specifically. No need to also mark it [JFace] if it belongs to the more specific area.
  • Preference pages associated with another platform UI component should go to that component, not [Preferences]. For example, the keys preference page problems should go to the [KeyBindings] component, not the [Preferences] component.

Platform-UI vs Platform-IDE

  • [Not sure what to say here. Do we have guiding principles for what belongs where, or should we always check both?]

Whose bug is it anyway?

Plug-in Spy

When the problem report involves some contribution that is not made my platform UI, PDE plug-in spy is your friend for figuring out where a particular UI contribution comes from.

  • For selections, menus, dialogs, wizards, use Alt-Shift-F1 to launch the plug-in spy. It will tell you who made the contribution.
  • For context menu items, select the item whose context menu you are interested in, use Alt-Shift-F2 to preload the plug-in spy (the cursor will change), then open the context menu and click the menu item. This will show you who made the menu contribution.