RiverWare 6.1: Unit Schemes
Edit: 8-10-2011, Phil Weinstein, CADSWES.

Recent Project Management Resources

• 8-10-2011: Two Initial Release Options
• 8-09-2011: Sources, Repositories and Uses of Unit Configuration Data in RiverWare -- An inventory of Unit Configuration Data
• 8-05-2011: Unit Scheme support for Data Objects -- Three Options

Development / See PROGRESS REPORT

• 8-11-2011: Analysis of Required Changes for Old-Style DMIs (with a provision used also for Database DMIs). [Task 6b].
• 8-05-2011: Screenshots: Database DMI Dataset Unit Maps / Unit Schemes
• 8-01-2011: (a) Slot Hierarchy Review Notes; (b) Column Map Instances / Three Screenshots; (c) System Schematic
• 7-31-2011: Slot Config Dialog "Unit Scheme" Notice proposal
• 7-28-2011: New Workspace "Units" Menu options.
• 7-25-2011: Status Report
• 7-19-2011 -- XML serialization: Notes / Example
• 7-15-2011 Design Review: Meeting Decisions ... Task List
• Unit Scheme Editor / Development Screenshots: 7-8-2011 .. 7-11-2011 .. 7-15-2011

Iteration 3: Design

• Design Review Meeting: 7-06-2011
• Requirements Changes / Additions / Decisions:
  1. No need to support non-display attributes from the riverwareDB file (for new object initialization)
     ... change of scope: now "Value Display Attribute Schemes", internally abbreviated "ValDisplayAttribScheme".
  2. More encapsulated Slot scheme caching architecture to protect against invalid access from within the Slot classes.
  3. There will be an "Initialization Scheme" with which the units of Slots on new objects are initialized. This scheme is editable but will always have "scheme rules" for all unit types. It should be possible to copy the contents of other schemes into the Initialization scheme (and in general, between schemes).
  4. There will be several preconfigured schemes for typical use from which new user-defined schemes can be created.
  5. Slot display properties not provided by the "active" scheme will default to the Local Scheme (rather than to the Initialization Scheme).
  6. Open Slot dialogs will provide an easy way to switch between the Local Scheme and the Active Scheme, possibly with some provisions within the Slot Configuration dialogs to effect that control (as well as within the Open Slot dialog itself).
      
• Ready for Review:
  • Value Display Attribute Schemes -- Slot Class Architecture
  • Mapped Scheme Architecture Diagram
     
• New Diagrams and Images:
  • Slot Class Architecture / Mapped Value Display Attribute Cache / Large / Photoshop
  • Value Display Attribute Schemes / Mapped Scheme Architecture / Large / Photoshop
  • Mockup Screenshots: Mapped Scheme Editor and Unit Type Selector.
     
• Coming Soon:
  • Mapped Scheme Editor GUI Design Document ... see mockup screenshots.
  • Scheme Internal Design (Manager and supporting Mapped Scheme classes) ... see diagram.
     
• Action Items:
  • Define and "name" one or two preconfigured Value Display Attribute Schemes (e.g. for common / major U.S. projects). These will probably have only Unit Type "scheme rules", and should cover all unit types.
  • Technical Decision: Can we change the "Display Format" encoding from a two-character QString (e.g. "%f") to a char? (e.g. 'f').
  • Discussion: Consider option for Schemes to be able to identify a "default" or "base" scheme, e.g. one of the preconfigured schemes. This would probably relieve most actual user scheme definitions from repeating the long list of unit type "scheme rules" already represented in one of the preconfigured schemes (see first bullet). There could be some provision for optionally showing "inherited" "scheme rules".

Iteration 2: Design Document:

• Slot Attribute Specifications Redesign in RiverWare 6.1 (PDF, 11-pages, 6-14-2011)
• Slot Name Selector Choices: GUS or dedicated Slot/Column Entity (Name) Selector

Iteration 1: Analysis Document:

• Unit Schemes in RiverWare 6.1 (PDF, 11-pages, 6-08-2011)
   
  • 6-08-2011: Reframing ... work will proceed in a new document: "Slot Attribute Specifications Redesign in RiverWare 6.1" which addresses the full scope of the slot and slot column parameters currently represented by the riverwareDB file. This external configuration file will be entirely replaced with a built-in GUI-supported capability.

• Reference Files
• Reference Screenshots
• Slot Name Chooser (alternaltive to GUS enhancement to support Slot Entities).

---