Laserfiche WebLink
somewhat on the selected fonts (e.g., small fonts must be used to fit a large amount of information on a <br />display). This issue should be revisited in Year 2. <br />The majority of the GUI design implementation has been according to the scope of work. However, <br />additional refinement is required in Year 2 to ensure full compatibility in the ?look and feel? of all <br />CRDSS interfaces. <br />DMI Design Guidelines <br />Task Memoranda 1.05-8 and 1.05-9 discuss DMI concepts and implementation guidelines. In general, <br />much of the low-level DMI work has been done at RTi, which has resulted in the DMI library (see the <br />Database chapter of the CRDSS Developers? Manual for information). Developers of DMI utilities (e.g., <br />vdb crdssgr <br />, ) have used this library to access the database. <br />The majority of the work in Year 1 has concentrated on time series retrieval because this information is <br />valuable to modelers, is for the most part readily available, and was populated in the database early in <br />Year 1. Additional low-level DMI routines were written at the end of Year 2 as other data (parametric <br />information, etc.) became available for water rights planning and consumptive use work and was <br />populated in the database. However, because of difficulties in getting some data, completion of some of <br />the DMI utility programs has been delayed until Year 2. There have been 10 DMI utilities developed for <br />accessing the database. Nine of the ten DMIs are specific to modeling activities, and one is a generic <br />utility that lends itself to a broader range of use. (Please refer to Task Memoranda 1.15-12 through 1.15- <br />16 and 1.14-10 through 1.14-13 for an explanation of the purpose and operation of each of these DMIs). <br />Error-handling and Debugging <br />Task Memorandum 1.05-3 discusses debugging procedures, and Task Memorandum 1.05-13 discusses <br />error handling procedures. In general, all new applications developed for the CRDSS suppor t error- <br />handling. Existing applications which have been implemented for the CRDSS may not support error <br />handling. The DMI library has a set of routines for printing error and debug messages <br />DMIPrintDebug DMIPrintWarning DMIPrintError DMIPrintStatus <br />( , , , ). See the man pages for <br />these routines for more information. A debug level for DMI utilities is generally made available via a <br />- <br /> command line option for the program. <br />d# <br />Advanced debugging tools such as the Purify software have not been available for the SGI workstations. <br />dbx xdbx lint <br />Consequently, standard tools such as , , and have been used. It is hoped that software such <br />as Purify will be available in Year 2. <br />GUI programs developed for the CRDSS each have a status bar in which status, error, and warning <br />messages are printed. <br />Error-handling in software developed for the CRDSS has been implemented by using return codes from <br />library routines and programs. Calling routines and programs can then check the return codes and take <br />appropriate actions (such as printing messages in interface status bars). <br />3 <br />A275 .01.09.95 1.05-32. Malers <br />