Skip to main content
Jump to: navigation, search

Difference between revisions of "Platform UI/Multi-instance Properties View"

(New page: Ideas/Use cases/Requirements for multi-instance Properties View (PV): - Pin PV to current selection (stop following selection) - Inherit parents settings (For PV org.eclipse.ui.part.Work...)
 
Line 1: Line 1:
Ideas/Use cases/Requirements for multi-instance Properties View (PV):  
+
= Ideas/Use cases/Requirements for multi-instance Properties View (PV): =
  
- Pin PV to current selection (stop following selection)
+
* Pin PV to current selection (stop following selection)
- Inherit parents settings (For PV org.eclipse.ui.part.WorkbenchPart.getPartProperties() might be an option)
+
* Inherit parents settings (For PV org.eclipse.ui.part.WorkbenchPart.getPartProperties() might be an option)
- Inherit parents input (requires API to get the Input from the parent)
+
* Inherit parents input (requires API to get the Input from the parent)
- New one has focus?
+
* New one has focus?
 
+
* Open the new view either on the same stack or else where? (If the user wants to compare two objects, a stacked view doesn't fit)
 
+
* Back and forward buttons to navigate between the property view instances
- Open the new view either on the same stack or else where? (If the user wants to compare two objects, a stacked view doesn't fit)
+
* Multiple PV instances are still restorable?
- Back and forward buttons to navigate between the property view instances
+
* Open the properties view from the context menu of the current selection (show in) (Object id might be used for secondary view id).
- Multiple PV instances are still restorable?
+
- Open the properties view from the context menu of the current selection (show in) (Object id might be used for secondary view id).
+

Revision as of 02:47, 22 September 2008

Ideas/Use cases/Requirements for multi-instance Properties View (PV):

  • Pin PV to current selection (stop following selection)
  • Inherit parents settings (For PV org.eclipse.ui.part.WorkbenchPart.getPartProperties() might be an option)
  • Inherit parents input (requires API to get the Input from the parent)
  • New one has focus?
  • Open the new view either on the same stack or else where? (If the user wants to compare two objects, a stacked view doesn't fit)
  • Back and forward buttons to navigate between the property view instances
  • Multiple PV instances are still restorable?
  • Open the properties view from the context menu of the current selection (show in) (Object id might be used for secondary view id).

Back to the top