Summit II

Date:March 14,15 2006 at Kitware Please make your own travel arrangements.

Agenda

Tuesday, March 14
Time	Item	Who
8:30-9:00	Coffee and knock-knock jokes	All
9:00-9:30	Overview and Awards	Rogers
9:30-11:30	Code walk-throughs and puppet show	Shead
11:30-1:00	Lunch	All
1:00-2:00	Prism over ParaQ discussion	McBride
2:00-4:00	UI design discussion	Matthew

Wednesday, March 15
Time	Item	Who
8:30-9:00	Coffee and knock-knock jokes	All
9:00-10:00	Lessons learned (GeoViz, Dobrano-viz)	Shead
10:00-11:30	Process Discussion	Geveci
11:30-1:00	Lunch	All
1:00-2:30	Wrap-up, planning for next month's development	All

Important Questions

• Is ParaQ a Pipeline or a Window based UI. How do we support a useful, understandable multi-view, multi-pipeline application?
• Do we support Multiview' or Dockable window management paradigms? Do we support both?
• What does a graph show, in a multi-view application? What is its update paradigm?
• How do we manage Views and Layouts - what you're looking at, and how it's laid out?
• What is our version number for the Sept. '06 release?
• What are our general multiview interaction mechanisms?
• What are our general Compound Filter interactions for editing and saving?

Notes

Code Walkthrough

Charting

• CSS-like attributes to control font, etc.
• Printing

UI design items

General

• Right mouse click in QVTKWidget - conflict with context menu in windows.
• Improvements in Auto-generated UI panels.
• Design method for adding code to hand-coded UI panels.
  • Should it always be a QT Designer-based thing?
  • Should we support a script-like way of changing UI in the field? Non-compiled?
• Compound filter creation/editing/loading.

Pipeline Browser

Major issues

• Simple fan-out
• Multiple sources
• Show things that aren't 'ON' (what's on; how is it shown?)
• Pipeline vx. Windows' interaction paradigm?
• Context menu (right mouse click)
• What are the basic operations we can do?
• How does this support Compound Filter operations (creation/editing/loading)

Current State

• Current variable (including range, etc.)
• Current timestep

Action Items

Who	Item
BG	Monitor interaction between pqPipelineData and server manager classes. In particular, the relationship between data in the server manager, and copies of that data saved in the UI for efficient UI interaction.
MR	Design and implement a 'graph' ancestor to pqPipelineData. Determine if there is a 'graph' package that we can create (with both models and views)
CS	Element Inspector: add capability to handly large data quickly
CS	Create wiki page explaining how to to create custom object inspectors.