Basic integration does not involve extensive use of the desktop application program interface (API). Therefore, it does not provide other interaction with the desktop, such as drag and drop, session management, ToolTalk messaging, and programmatic access to the actions and data types database.
Your application will provide a desktop registration package, and your installation script will automatically register your application.
Registration creates an application group at the top level of Application Manager. The application group contains an icon the user double-clicks to start the application.
Your application will provide data types for its data files.
Data typing configures data files to use a unique icon in File Manager to help users identify them. The data files also have meaningful desktop behavior. Two examples are:
Your application will change interface fonts and background, foreground, and shadow colors dynamically.
The desktop defines general interface font and color resources that are used if no corresponding application-specific resources exist.
Upon installation, the application is automatically registered. The system administrator has little or no additional work to do.
All the desktop's configuration files are gathered in one location. Furthermore, the application can easily be unregistered if, for example, the system administrator wants to update it or to move it to a different application server.
The CDE Programmer's Guide contains a chapter on basic integration. Where appropriate, the chapter refers you to the information contained in the CDE Advanced User's and System Administrator's Guide . It also contains additional information specific to application programmers.
See the section on modifying font and color resources in the CDE Advanced User's and System Administrator's Guide .
See the CDE Programmer's Guide basic integration chapter for details.
Some types of printing integration require that you modify your application code. They are optional, and are discussed in the CDE Programmer's Guide basic integration chapter because they are closely related to basic integration tasks.
See this documentation:
See this documentation: