Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
Difference between revisions of "Platform UI/Multi-instance Properties View"
m (→Existing behaviour) |
(→Ideas/Use cases/Requirements for multi-instance Properties View (PV) {{bug|248103}}:) |
||
Line 10: | Line 10: | ||
* Back and forward buttons to navigate between the property view instances | * Back and forward buttons to navigate between the property view instances | ||
* Multiple PV instances are still restorable? | * Multiple PV instances are still restorable? | ||
+ | ** Only restore the master property view (the first one)? | ||
+ | ** Only restore property view instances which are pinned? | ||
+ | ** Restore all property views | ||
* Open the properties view from the context menu of the current selection (show in) (Object id might be used for secondary view id). | * Open the properties view from the context menu of the current selection (show in) (Object id might be used for secondary view id). | ||
* When a second view is opened from the original view, what should happen? Should the original stop following selection or should the second one? | * When a second view is opened from the original view, what should happen? Should the original stop following selection or should the second one? |
Revision as of 02:23, 24 September 2008
Contents
Ideas/Use cases/Requirements for multi-instance Properties View (PV) bug 248103:
- 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)
- Setting parents state/input requires additional API whereas freezing (pinning) the parent and opening a "fresh" PV wouldn't require any additional API
- The console view for example gets the parents content in org.eclipse.ui.internal.console.ConsoleView.consolesAdded(IConsole[])
- 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?
- Only restore the master property view (the first one)?
- Only restore property view instances which are pinned?
- Restore all property views
- Open the properties view from the context menu of the current selection (show in) (Object id might be used for secondary view id).
- When a second view is opened from the original view, what should happen? Should the original stop following selection or should the second one?
Existing behaviour
View | Open secondary instance by | Inherit parent's content | Inherit parent's settings | Same "input" opens new view | Name new instance |
---|---|---|---|---|---|
Search |
Pin parent and rerun search | no | no | ? | no |
History |
Pin and call Team > Show History on a different resource | no | yes | ? | no |
Memory |
"New" button View toolbar | ? | yes | ? | no |
Bookmarks |
"New ... View" from View menubar | yes¹ | no | n/a | yes |
Markers |
"New ... View" from View menubar | yes¹ | no | n/a | yes |
Problems |
"New ... View" from View menubar | yes¹ | no | n/a | yes |
Tasks |
"New ... View" from View menubar | yes¹ | no | n/a | yes |
Console |
Can be opened explicitly | yes | ? | ? | ? |
¹ Content comes from workspace