Complying with CUA. (common user access)(Custom Micro Concepts Inc.'s CUAccess) (Software Review) (evaluation)

You've probably noticed that a number of commercial software packages greet you with a familiar-looking File Edit" menu when you first load them. Examples include Microsoft's "Quick" compilers, CompuServe Information Manager, and just about any Windows application. While this may seem like deja, vu, it's actually a result of CUA. CUA stands for "Common User Access," and is the "look and feel" part of the SAA standard, IBM and Microsoft's master plan for software compatibility and portability.

CUAccess, from Custom Micro Concepts, is a Clipper development tool kit for building SAA/CUA-compliant applications. CUAccess (pronounced "see you access") includes a Clipper function library and several utility programs. The function library helps you create Programs With the features of SAA/CUA applications: pull-down menus, dialog, list, and check boxes, and radio and push buttons. The resulting applications are mouse-aware, but a mouse isn't required. You can also create CUAccess programs with movable, resizable windows.

CUAccess applications are data driven, using a resource file, a concept also found in Windows applications. However, unlike Windows, CUAccess applications are aimed at text-based, 640K DOS environments. CUAccess's data-driven approach also means you can make changes to your screens without recompiling your Clipper programs.

The secret to many of CUAccess' features is dLesko's FUNCky library. It may be more of a secret than the developers intended-the user manual neglects to mention that YOu must also purchase the FUNCky library. I discovered this the hard way when I tried to link the sample applications. It would be helpful to have this prerequisite displayed prominently at the beginning of the manual, as it is in the promotional materials. In any case, be sure to buy FUNCky too.

The other prerequisites are MS-DOS 3.0 or later, 640K RAM, a hard disk, and Clipper Summer'87. A Clipper 5.0 version of CUAccess is not yet available. A dynamic overlay linker, such as Blinker, is strongly recommended.

The documentation is polished and concise. It begins with a primer on the background and objectives Of SAA/CUA, followed by an explanation of the elements of a SAA/CUA user interface. The next section discusses the CUAccess development environment, tools, and steps for building an application. The generously commented source code examples are invaluable for understanding this section. The "Function Detail Reference" describes the Purpose, syntax, and how to use each of the 27 functions. The appendices describe the contents and format of the resource, menu definition, help definition, and initialization files.

The package includes both 5.25 and 3.5-inch disks, and installing it is simple. Just follow the directions in the READ.ME file. There are instructions for compiling and linking two sample mailing list applications. Neither mailing list application is very extensive, but they will give you an idea of how the resulting user interface works. Although it isn't a demo program, the screen painter utility seemed to be a more substantial example of a CUAccess-developed application.