My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
CRDSS_Task1_05-15_BuildingGUIComponents
CWCB
>
Decision Support Systems
>
DayForward
>
CRDSS_Task1_05-15_BuildingGUIComponents
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
9/25/2011 10:18:53 AM
Creation date
5/30/2008 2:42:08 PM
Metadata
Fields
Template:
Decision Support Systems
Title
CRDSS Task 1.05-15 - System Integration Issues GUI - Building GUI Components
Description
This memorandum addresses general issues related to building GUI components.
Decision Support - Doc Type
Task Memorandum
Date
7/28/1994
DSS Category
DMI Utilities
DSS
Colorado River
Basin
Colorado Mainstem
Contract/PO #
C153658, C153727, C153752
Grant Type
Non-Reimbursable
Bill Number
SB92-87, HB93-1273, SB94-029, HB95-1155, SB96-153, HB97-008
Prepared By
Riverside Technology inc.
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
10
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
Show annotations
View images
View plain text
this code may be somewhat repetitive and verbose (e.g., the creation of ten buttons may result in the <br />duplication of ten sets of code segments, without consideration of whether more compact code can <br />be written). <br />Macro language versions of the code consist of language such as the following: <br />attach push-button "quit-button" to button-manager "main- <br />buttons" <br />color: blue <br />width:100 <br />height:20 <br />border:2 <br />label:"Quit" <br />callback:quit_program <br />This type of representation for a GUI is used because the GUI builder must have some information to <br />recreate the GUI if it is being edited after the first time. It is much easier for the GUI builder to <br />recreate source code from the above macro language than to try to understand the source code itself <br />(especially if a developer has changed the source code for some reason). An important consideration <br />is that each GUI component part has an identifier and type. For example, in the macro code above, <br />the component has a name ?quit-button? and a type ?push-button.? <br />An additional file that is often associated with a graphics-based program is a resource file, which is a <br />file that contains parameter information for GUI components. For example: <br />quit-button.color:blue <br />quit-button.width:100 <br />quit-button.height:20 <br />quit-button.border:2 <br />quit-button.label:"Quit" <br />This type of resource file is used by the X Window System (see the file and the <br />.Xdefaults <br /> directory) and Microsoft Windows (see the files). Note <br />/usr/lib/X11/app-defaults .INI <br />that these files may also contain non-GUI information for specific applications. The purpose of such <br />a file is to allow the end-user to modify the attributes of GUI components without having to <br />recompile the application. The general precedence associated with setting GUI resources is as <br />follows: <br />(1)Use resources set on the command line for the application. <br />(2)Use resources set in user's resource file. <br />(3)Use resources set by system resource file (applies to all users on system). <br />(4)Use resources set within program. <br />The low-level GUI routines of the GUI builder library, on which all other routines are built, typically <br />include some type of database for GUI component resources. For example, each GUI component has <br />a color, size, and position. Default values are set within the program or are assumed to be set by the <br />system (such as by a window manager that controls the general look and feel of all applications). <br />The default values can be set by the user to satisfy that user. <br />3 <br />A275 07.28.94 1.05-15 Malers <br />
The URL can be used to link to this page
Your browser does not support the video tag.