JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
Solaris X Window System Developer's Guide
search filter icon
search icon

Document Information


1.  Introduction to the Solaris X Server

2.  DPS Features and Enhancements

About DPS

How DPS Works

DPS Font Enhancements in the Solaris Server

DPS Libraries

Adobe NX Agent Support

DPS Security Issues

System File Access

Secure Context Creation

When DPS Encounters Internal Errors

How To Access Information From Adobe

DPS Compositing Operators

Operator Descriptions

Implementation Notes and Limitations

Partially Transparent Alpha

Indexed Color Visuals

Monochrome Displays

Interaction with X Drawing Operations

Destroying the Alpha Channel

Drawables with Unequal Depths

3.  Visuals on the Solaris X Server

4.  Font Support

5.  Server Overlay Windows

6.  Transparent Overlay Windows

7.  Security Issues

A.  Reference Display Devices



DPS Libraries

The following table lists the DPS libraries. The .so and .a files that comprise these libraries are located in the /usr/openwin/lib and /usr/openwin/lib/libp directories. For information on these libraries, see Programming the Display PostScript System with X and PostScript Language Reference Manual.

Table 2-1 DPS Libraries

DPS Client library
DPS Toolkit library
PostScript Language Resource Location library
DPS Motif Toolkit library

Adobe NX Agent Support

The context creation routines (XDPSCreateSimpleContext and XDPSCreateContext) in libdps attempt to contact the DPS NX agent if they are unable to connect to the DPS/X extension. The NX client must be started manually, usually during the boot or X startup process.

The Adobe DPS NX agent, which is available from Adobe Systems Inc., is a separate process from the X server and the DPS/X client. When connected to the DPS NX agent, the client's DPS calls are intercepted and converted into standard X Protocol requests. Thus, a DPS client can run on an X server that does not natively support the DPS extension.