Task-Centered User Interface Design
A Practical Introduction
by Clayton Lewis and John Rieman
Copyright ©1993, 1994: Please see the "shareware notice" at the front of the book.
Contents | Foreword | ProcessUsers&Tasks | Design | Inspections | User-testing | Tools | Documentation |

6.1 Concepts
        6.1.1 Object-Oriented Programming
        6.1.2 Event-Driven Programs
        6.1.3 Resources
        6.1.4 Interapplication Communication
6.2 OSF/Motif in X-Windows -- Toolboxes in the Trenches
6.3 Rapid Prototyping in HyperCard
6.4 Windows, the Shared-Code Approach, and Visual Basic


6.1.3 Resources


Resources, for our purposes, are interface-specific information such as menu titles or button positions, which are stored so they can be easily changed without affecting the underlying program functionality. (A system may also treat the main program code as a resource.)


On some systems you might change the resources by editing values in a text file; on others you might need to use a special resource editor. But it typically won't require recompiling the application itself, and it won't require access to the source code. During prototyping, a few simple changes to resources might dramatically improve an interface, with no "real" programming. When the system is ready to ship, resources can be changed so the product can be used in countries with a different language.




Copyright © 1993,1994 Lewis & Rieman
Contents | Foreword | ProcessUsers&Tasks | Design | Inspections | User-testing | Tools | Documentation |