1. ORNL is managed by UT-Battelle for the US Department of Energy CSS: OPI Views Kay Kasemir, Jan. 2015

2. 2 Eclipse 4 1.RCP: Editors, Views, Perspectives, Help, Preference GUI 2.E4 Model: Windows, Part Stacks, Parts 3.SWT Renderer: Shells, Widgets

3. 3 RCP “Parts” in Eclipse 4 “View”“Editor” Can be placed anywhere We already link *.opi & macros to OPIView Has “Input”.. which can be “dirty”, supports “Save”, “Save As”  We don’t need that for *.opi Runtime Are saved/restored with the PerspectiveWe don’t have anything to save/restore “editors”... and RCP makes this really hard. By design, display is decoupled from the content. No API to “move” a view.

4. 4 Best Match “Editor” for *.opi editor “View” for *.opi runtime

5. 5 git checkout boy_runtime_view Replaced “*.opi” EditorPart with DisplayLauncher.. which opens in OPIView Adjusted “Open In Tab”, … to all use OPIView Fixed “BOY acting a little odd” #735 Updated OPIRuntime Perspective to allow this:

6. 6 OPI Runtime Perspective Basically works: Can open in “LEFT”, … LEFT RIGHT DEFAULT TOP BOTTOM

7. 7 Perspective “Save As”, Switch

8. 8 Problems Other tools’ perspective (Data Browser, Scan Editor, OPI Editor,..) –When activated, *.opi runtime views change –OK as long as they don’t self-activate? “Open OPI on LEFT” means “in part stack named ‘left’” –Even if user moved that to the “right” There is still a special Editor part stack

9. 9 OPI Runtime Perspective “Editor” Area, by default hidden in OPIRuntime

10. 10 org.eclipse.ui.editorss(!) “Editors” start in there View’s don’t, but can be moved to it Shared between Perspectives Not saved with the perspective

11. 11 org.eclipse.ui.editorss Conceptually, not bad: OPIViews placed there are shared amongst all perspectives. Won’t save/restore. In reality: Joe User won’t be able to tell, “Did I just move this into the ‘editor’ area?”

12. 12 Ideas Still use “View” for Runtime, with “Perspective” to persist. Hack into perspective code to save all “OPIView” instances?