RiverWare 5.1: RiverWare Link to External RPL Documentation
Project Completion -- October 2008 -- Phil Weinstein -- Hit Refresh [12-5-2008].

Latest Materials

Major remaining tasks (ALL DONE):

  1. File Format Manager (or "File Association Manager")
    1. Data model (see notes below)
    2. GUI components
    3. Windows interface, registry info for file associations
    4. QSettings-based persistence
  2. Hooks from RPL Dialogs
    1. menus
    2. buttons
  3. Completion: Configure Rule External Documentation dialog
    1. Replication of the "View" section for "Edit", with option to use same data
    2. Anchor components
    3. Environment Variable substitution

File Format Manager -- Notes, 10-3-2008.

There will be a single base class, and generally trivial subclasses for the supported formats (HTML, Word, PDF). There will be two instances of each subclass, one for "Edit" and one for "View", maintained in an abstract collection (via base-class pointers) managed by a "File Association Manager" singleton (distinct from the associated dialog box).

I'm thinking about whether or not a seperate set of closely associated "device" classes is warranted to enapsulate the use of a particular program. The thing is, since a particular program (e.g. Word or Explorer) can be used for different formats (e.g. HTML or Word Doc), it may be a good to have a place to encapsulate the interface to such programs, distinct from format, e.g. to define how "anchors" are encoded (e.g. as part of the document path, or as command line parameters).

Original Documents (February-March 2008):

---