Return to Controls.rtf CVS log

Up to [NeXTSTEP 3.3 examples] / Examples / AppKit / BusyBox / English.lproj / HelpFiles

Annotation of Examples/AppKit/BusyBox/English.lproj/HelpFiles/Controls.rtf, revision 1.1.1.1

1.1       root        1: {\rtf0\ansi{\fonttbl\f2\fswiss Helvetica;\f1\fmodern Courier;}
                      2: \paperw11780
                      3: \paperh9540
                      4: \margl120
                      5: \margr120
                      6: \pard\tx960\tx1920\tx2880\tx3840\tx4800\tx5760\tx6720\tx7680\tx8640\tx9600\f2\b0\i0\ul0\fs36 Controls
                      7: \fs16 \
                      8: 
                      9: \fs24 \
                     10: Controls are graphical objects that users manipulate with the keyboard and mouse to give instructions to an application.  They're patterned after familiar control devices from everyday life-switches, knobs, forms, gauges, and the like-and perform analogous functions.  Like the dials and levers on a machine, graphical control objects let the user �operate� an application.\
                     11: \
                     12: Every control responds visually to direct manipulation by the user-a dial turns, a button pushes in or highlights, the knob of a slider slides.  Controls go beyond this direct response, however, to cause the application to do something.  They, in effect, translate the user's direct manipulation into an instruction for the application.  A button sets a state or initiates a program action, a slider sets a value, a menu item sends a command, and so on.\
                     13: \
                     14: The Application Kit defines five canonical controls:\
                     15: \
                     16: 
                     17: \pard\tx680\tx1920\tx2880\tx3840\tx4800\tx5760\tx6720\tx7680\tx8640\tx9600\fi420\li40 �        Sliders \
                     18: �      Buttons \
                     19: �      Menu commands \
                     20: �      Text fields \
                     21: �      Scrollers\
                     22: 
                     23: \pard\tx960\tx1920\tx2880\tx3840\tx4800\tx5760\tx6720\tx7680\tx8640\tx9600 \
                     24: You can also design your own controls-the Application Kit makes this relatively easy-but they should adhere to these basic design principles:\
                     25: \
                     26: 
                     27: \pard\tx220\tx1920\tx2880\tx3840\tx4800\tx5760\tx6720\tx7680\tx8640\tx9600\fi-220\li240 �      Every control must provide immediate feedback to let the user know that an action has �taken.�  Just as users can look at a dial on a stove to see whether it has been turned, a graphical control must alter its appearance in response to user actions.  It shouldn't depend on a reaction elsewhere in the application to give the user feedback.\
                     28: 
                     29: \pard\tx960\tx1920\tx2880\tx3840\tx4800\tx5760\tx6720\tx7680\tx8640\tx9600 \
                     30: 
                     31: \pard\tx220\tx1920\tx2880\tx3840\tx4800\tx5760\tx6720\tx7680\tx8640\tx9600\fi-220\li240 �      Every control should have a distinctive appearance and behavior.  Don't design controls that look so similar to the canonical controls that users will confuse one with the other.\
                     32: \
                     33: �      The behavior of a control should be apparent from its appearance.  After a bit of familiarity with the NeXT Computer, users should be able to easily recognize a control object and know almost instinctively how to operate it.
                     34: }

This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.