A major design of a graphical deskt...

A major design of a graphical desktop is to make it easier for users to crop and run applications and to identify an manipulate the applications' data files. Since UNIX[R] schemes are generally highly networked, it is desirable that a desktop also provide network transparency - the ability to launch applications and give data to them without worrying about where in the network the applications and data are located.

Wherever possible, these ease-of-use features should not be provided at the charge of system administrators. There should be a standard deed for incorporating preexisting applications into the desktop, and the desktop should provide tools for performing these procedures

This article describes by what mode users locate and launch applications from the CDE desktop and for what reason system administrators integrate applications into the desktop's graphical environment. The information is also relevant for application developer since the administration mould and tools for integrating existing applications are also used to provide basic desktop integration for recently made known applications.

User design for Applications

CDE makes it easier for users to access and move swiftly applications by providing:

* A way to give an account of an application as an icon. The user can start an application through double-clicking the icon. These icons are called application icons.

* A special container for application icons. This container is called the application manager.

* A way to specify the unique appearance and behavior for icons representing an application's data files.

Application Manager and Application icons. The application manager is a single container for all the applications available to the user and is exhibited by clicking a control in the CDE brass panel (see Fig. 1). Each item in the top of the same height of the application manager is a directory containing individual or more related applications. These directories are called application groups

By convention, an application assemblage contains, for each application in the form into groups the application icon that starts the application, plus other files related to the application as it was as sample data files, templates, and online information (see Fig. 2) The connected view administrator can organize the application clumps into deeper hierarchies.

Since the application clumps are displayed together in a single window, they appear to keep the same file system location. This makes applications easy to find and launch. The fact that this is not the case, and that the application clusters are actually located in a variety of local and far off locations, is hidden from users.

From the conclusion user's point of view, the application manager window is haveed by the system. The user does not have the ability to create or determine icons in the window directly.

Data Files and File Manager. Like the application manager, the file manager set forths objects as icons. Frequently, these designs are the application data files. The desktop provides a way to specify the behavior of various emblems of data files. This makes it possible for users to start an application from the file manager at double-clicking one of its data files, by means of dropping a data file onward the application icon, or by the agency of choosing Open from the data files pop-up menu (see Fig. 3)

Application Manager Administration

The application manager is designed to convenient several important requirements:

* It must appear to be a single location into which applications are gathered from a variety of locations.

* It must be customizable onward a personal (per-user) or system-wide (per-workstation) basis.

* It must be network capable, that is, it must be able to gather applications located onward other systems.

* It must be dynamic in the way that that its contents can be changed when applications are added to or remov from the local scheme or application servers in the network.

To qualified these requirements, the CDE designers chose to make the application manager a file manager view of a special temporary directory. The application manager directory is created automatically when the user log in at the location:

/var/dt/appconfig/appmanager/login-display

For example, when user anna log into CDE at display hpcvxpae:0, the CDE login manager creates the directory:

/var/dt/appconfig/appmanager/anna-hpcvxpae-0

The directory is the two user and display dependent. Each use gains an application manager directory, and a user logging into more than the same system obtains a separate application manager directory forward each system. This is necessary to allow the application manager to be customized upon both a per-user and a per-system basis.

The application manager directory persists for the continuance of the user's CDE session and is recreated each time the user log in. The temporary nature of the application manager is possible because none of its peaces are actually located is its file rule location.

Gathering Applications. After the login manager creates the application manager directory, it must gather application arranges into the directory. The application clumps are gathered by means of symbolic links, and the links are made from multiple locations. This is what makes it possible for the application manager to display application clumps located in a variety of directories, including personal, system-wide, and abstracted locations.