Laserfiche WebLink
GUI development issues presented in this memorandum illustrate the complexity of developing <br />GUIs. Based on available budget and the requirements of the CRDSS, the following <br />recommendations are proposed: <br />Reusable modular code will be developed by prototyping shared GUI components (such as <br />? <br />a diversion structure detail form). The GUI component code will then be isolated and <br />placed in a library that can be accessed by all developers. This applies both to XVT and <br />Motif-based routines. <br />A consistent ?look and feel? will be enforced by relying on the native environment to set <br />? <br />defaults (such as colors) as much as possible, and by using resource files where special <br />settings are needed. GUI development will conform to the standards set by the Open <br />Software Foundation, the developer of Motif. <br />GUI code will be developed in a cost-effective manner by using a simple design for GUI <br />? <br />components and by limiting Year 1 efforts to the basic needs of model developers and for <br />displaying key information from the database. Task Memorandum 1.05-31 discusses the <br />GUI and DMI components for each model. Task Memorandum 1.05-16 lists the types of <br />data that will be displayable in the database browse tool. <br />New GUI code will be prototyped using the XVT GUI builder. New GUI code that is being <br />? <br />taken from existing Motif-based applications will be prototyped using the existing work as <br />a starting point. GUIs will be evaluated by interested users (such as GUI/GIS <br />subcommittee members) and by relevant project team members (such as relevant <br />modelers). <br />Cross-platform GUIs can be developed using a portable GUI builder. XVT will be used for <br />? <br />this purpose. GUI components can be maintained using general software maintenance like <br />make imake <br /> and . A GUI builder would allow maintenance of the GUI code created by the <br />GUI builder. <br />Public domain software will be used wherever possible to provide tested functionality <br />? <br />without requiring extensive budget for integration in the CRDSS. S ee Task Memoranda <br />1.05-16 and 1.05-18 for examples. <br />GUI code will be maintained in the long term as other code will, specifically by using <br />? <br />revision control and by adhering to industry standards in development. <br />GUI components will be designed to allow for future enhancements by providing ?empty <br />? <br />code? in areas where enhancements are expected. For example, provisions will be made for <br />allowing editing of scenario parameters; however, such editing features will not be <br />available in Year 1. <br />10 <br />A275 07.28.94 1.05-15 Malers <br />