For XTk toolkit information, see: XTkDoc.tioga

For user information, see: X11Doc.tioga

For implementor information, see: X11ImplDoc.tioga

For a list of messages, see: X11MessagesDoc.tioga

X Window System Protocol, Version 11

September 1987

Massachusetts Institute of Technology

X Window System Protocol Encoding, Version 11

September 1987

Massachusetts Institute of Technology

Sample application program

Goal: get this simple

An extensible set of widgets: Labels, Buttons, Fields, Rulers, Containers

More modules at this layer: X11BitmapWidgets

X people call this level Toolkit; there are multiple toolkits, each having the ambition to be the standard toolkit.

This is the layer which might replace Cedar viewers

Interface defining how widgets are supposed to interact and how widget classes should be implemented. Think ViewerClass.

More modules at this layer: XlAssoc

X people call this level Intrinsics, and it is very hard to use [I don't understand big parts it].

XTk is much simpler and somewhat less powerfull than the C aequivalent Xt.

XTk is aimed at vanilla clients; X11TkFriends is for widget implementors.

Cedar access to the "X Window System Protocol". Think window, connection.

More modules at this layer: X11Access, XlService, XlConventions

X people call this level XLib (for the C language), and it is of tremendous size.

Xl adds Cedarness, type safety, threads, garbage collection, more robustness and shared address space to its counterpoint in the C world

This is the layer which could be used as base of the viewers port

This is the reliable stream protocol of X as defined by MIT. This protocol speaks to the actual X display server, which is NOT subject of design here. This layer is well defined and of moderate size. [Much too big for my taste].

Normal X clients don't think in terms of this layer

Main definitions. This exports basically the XLib interface from C.

Semi internal interface, giving access to default server name and address translation.

Definitions usefull internally to X11.

Should not be used by normal clients.

Definitions usefull to split the implementation into separate modules; this interface is supposed to grow on a per need basis and is not really designed.

Should not be used by normal clients.

Chiseled some private features out of X11Private.

Should not be used by normal clients.

Client level features. Put into a special interface to avoid propagation of knowledge of hacks.

A package implementing bitmap backed windows. [Bitmap on the host side!]

Those X Window commands which might be usefull to window managers only. Separated out to reduce size of X11.

Types as used in the ICCCM convention.

Procedures usefull to implement ICCCM convention.

Usefull for widget implementors to carry per depth information.

Caching of connections towards same X server. Allows speed and memory savings.

Sort of tables which know how to deal with nesting windows and disappearing windows.

Procedures returning X cursors.

Temporary text window interface.

Temporary interface to deal with input.

Public toolkit interface. Sorry but also has some not so public types

Defines rules how widgets do interact.

Toolkit interface for widget classe implementors.

Nice set of widgets.

A good widget class implementing the Cedar Imager.

A very simple pou pu menu package.

Accessing databases with the format of X resource database. Generalized so it is useful in other contexts. A separate package.

Basic access to the "standard" resource database.

Access the "standard" resource database from widgets.

Definitions for the unix shared memory feature.

A poor mans memory manager geared towards shared memory segments.

The pixmap level access interface ofr the X shared memory extension.

The implementation contains stuff logically belonging on two levels:

Please don't judge efficiency of test program to be the efficiency of Xl. These test programs do not do things the most efficient way but test.