Community hub
Recent from talks
Knowledge base stats:
Talk channels stats:
Members stats:
IBM Common User Access
Common User Access (CUA) is a standard for user interfaces to operating systems and computer programs. It was developed by IBM and first published in 1987 as part of their Systems Application Architecture. Used originally in the MVS/ESA, VM/CMS, OS/400, OS/2 and Microsoft Windows operating systems, parts of the CUA standard are now implemented in programs for other operating systems, including variants of Unix. It is also used by Java AWT and Swing.
IBM wanted a standard way to interact with text-based user interface software, whether the screen was a dumb terminal connected to a mainframe or a PS/2 with VGA graphics. CUA was a detailed specification and set strict rules about how applications should look and function. Its aim was in part to bring about harmony among DOS applications, which until then had independently implemented different user interfaces.[citation needed]
For example, to open a file:
F1 was often the help key (such as Volkswriter (1982)), but in WordPerfect, help was on F3 instead. Some programs used Esc to cancel an action, while some used it to complete one; WordPerfect used it to repeat a character. Some programs used End to go to the end of a line, while some used it to complete filling in a form. Ins sometimes toggled between overtype and inserting characters, but some programs used it for "paste".
Thus every program had to be learned individually and its complete user interface memorised. It was a sign of expertise to have learned the UIs of dozens of applications, since a novice user facing a new program would find their existing knowledge of a similar application either of no use or actively a hindrance to understanding as learned behavior might need to be unlearned for the new application.
The detailed CUA specification, published in December 1987, is 328 pages long. It has similarities to Apple Computer's detailed human interface guidelines (139 pages). The Apple HIG is a detailed book specifying how software for the 1984 Apple Macintosh computer should look and function. When it was first written, the Mac was new, and graphical user interface (GUI) software was a novelty, so Apple took great pains to ensure that programs would conform to a single shared look and feel.[citation needed] CUA had a similar aim, but it faced the more difficult task of trying to impose this retroactively on an existing, thriving but chaotic industry, with the much more ambitious goal of unifying all UI, from personal computers to minicomputers to mainframes; and supporting both character and GUI modes, and both batch and interactive designs. By comparison, the Apple HIG only supported interactive GUI on a standalone personal computer. CUA also attempted to be a more measurable standard than the Apple HIG and had large sections formatted as checklists to measure compliance.
The CUA contains standards for the operation of elements such as dialog boxes, menus and keyboard shortcuts that have become so influential that they are implemented today by many programmers who have never read the CUA.
Some of these standards can be seen in the operation of Windows itself and DOS-based applications like the MS-DOS 5 full-screen text editor edit.com. CUA hallmarks include:
Hub AI
IBM Common User Access AI simulator
(@IBM Common User Access_simulator)
IBM Common User Access
Common User Access (CUA) is a standard for user interfaces to operating systems and computer programs. It was developed by IBM and first published in 1987 as part of their Systems Application Architecture. Used originally in the MVS/ESA, VM/CMS, OS/400, OS/2 and Microsoft Windows operating systems, parts of the CUA standard are now implemented in programs for other operating systems, including variants of Unix. It is also used by Java AWT and Swing.
IBM wanted a standard way to interact with text-based user interface software, whether the screen was a dumb terminal connected to a mainframe or a PS/2 with VGA graphics. CUA was a detailed specification and set strict rules about how applications should look and function. Its aim was in part to bring about harmony among DOS applications, which until then had independently implemented different user interfaces.[citation needed]
For example, to open a file:
F1 was often the help key (such as Volkswriter (1982)), but in WordPerfect, help was on F3 instead. Some programs used Esc to cancel an action, while some used it to complete one; WordPerfect used it to repeat a character. Some programs used End to go to the end of a line, while some used it to complete filling in a form. Ins sometimes toggled between overtype and inserting characters, but some programs used it for "paste".
Thus every program had to be learned individually and its complete user interface memorised. It was a sign of expertise to have learned the UIs of dozens of applications, since a novice user facing a new program would find their existing knowledge of a similar application either of no use or actively a hindrance to understanding as learned behavior might need to be unlearned for the new application.
The detailed CUA specification, published in December 1987, is 328 pages long. It has similarities to Apple Computer's detailed human interface guidelines (139 pages). The Apple HIG is a detailed book specifying how software for the 1984 Apple Macintosh computer should look and function. When it was first written, the Mac was new, and graphical user interface (GUI) software was a novelty, so Apple took great pains to ensure that programs would conform to a single shared look and feel.[citation needed] CUA had a similar aim, but it faced the more difficult task of trying to impose this retroactively on an existing, thriving but chaotic industry, with the much more ambitious goal of unifying all UI, from personal computers to minicomputers to mainframes; and supporting both character and GUI modes, and both batch and interactive designs. By comparison, the Apple HIG only supported interactive GUI on a standalone personal computer. CUA also attempted to be a more measurable standard than the Apple HIG and had large sections formatted as checklists to measure compliance.
The CUA contains standards for the operation of elements such as dialog boxes, menus and keyboard shortcuts that have become so influential that they are implemented today by many programmers who have never read the CUA.
Some of these standards can be seen in the operation of Windows itself and DOS-based applications like the MS-DOS 5 full-screen text editor edit.com. CUA hallmarks include: