Browser redesign

1
Browser redesign

• Goal -Allow search over a set of templates.
• Trade off search power vs simple UI.
• New requirements
• Multitemplate tracker, D3I, arbitray XML.
• Name and value search

2
Original browser

• Tracker and xml document centric.
• No way to search values.
• Directory -gt document -gt label-value
• Each list (file, name, value) has shadow
  information that is managed and searched
  separately.

3
Original D3I support

• 2 modes TRACKER_MODE, D3I_MODE
• XML mode handled under TRACKER_MODE
• Hack 10 places where mode mattered.
• Quick but a kludge

4
GUI Refactoring

• To allow for name and value tabs and appropriate
  behavior.
• Issues
• Layout containers, layout managers
• Behavior couples objects requires fields.

5
Code looks like layout

• More functional style
• createFrame
• createMenuBar
• createContentPane
• createNameTab
• makePanel
• createValueTab
• makePanel

6
Really we are searching

• Model relational view of data.
• Not document centric
• File x xpath x label x value x
• Display details and search localized.
• Mode template domain specific knowledge.
• Where field name, value, tooltip, comes from.
• D3Idb- handles all D3I database queries.

7
Status

• Mode selected at startup.
• Database and other details hard coded.
• Name tab has old objects with newer toolTips.
• Value tab built on new Model.
• Tabs are independent.

8
Issues

• How should tabs work together to make a query?
• Example use value tab to slect a value and thus
  a name. Should that name be selected in the Name
  Tab?
• What should reset do?
• Should search panel filter?

9
Filter state view