dmx/doc/dmx.xml

53 back-end X servers, which handle all of the visible rendering.  X
65 input (e.g., mouse and keyboard events) and output (e.g., rendering and
81 <para>Rendering requests will be accepted by the front-end server; however,
82 rendering to visible windows will be broken down as needed and sent to
84 rendering.  The basic framework will follow a Xnest-style approach.  GC
86 appropriate back-end server(s) as required.  Pixmap rendering will (at
133 rendering services and input device handling services.  However, before
137 devices (i.e., the keyboard and mouse).  The simple back-end rendering
145 configurations; the back-end rendering services will be transitioned to
348 <para>The output of the DMX system displays rendering and windowing
370 Converting rendering requests (e.g., XPutImage() or XGetImage()
390 <title>Handling rendering requests</title>
393 There are two possible implementations of how rendering and windowing
419     <para>Rendering requests are sent to each back-end server for
424     multiple back-end servers.  Rendering to the framebuffer is handled
432     completely clip the rendering primitive -- which wastes bandwidth
551 clients to break up complex rendering requests on their own and send
606 Rendering extension (Render) is being developed.  Render adds digital
607 image composition to the rendering model used by the X Window System.
647 and later.  Currently, the direct rendering infrastructure (DRI)
649 OpenGL support (i.e., software rendering) is provided for non-local
658 OpenGL rendering requests will be direct rendering to each back-end X
663 on the same physical machine can emulate accelerated indirect rendering.
675     used by repackaging rendering primitives and sending them to each
679     distributed rendering systems.
683     <para>Rendering to a pixmap in the front-end server using the
723 available bandwidth during font rendering for clients that use many
731 <title>Zero width rendering primitives</title>
733 <para>To allow pixmap and on-screen rendering to be pixel perfect, all
1651 	proxy server and rendering requests are repackaged and sent to
1967     <para>Calls to XSync() can slow down rendering since it requires a
1984 the rendering code and would have required sending potentially large
1988 rendering code that draws to windows can be used to draw to pixmaps on
2120 server and every rendering request was sent to every window regardless
2123 back-end server's screen and, in that case, it does not send rendering
2201 <title>Subdividing Rendering Primitives</title>
2221 <para>Other rendering primitives were analyzed, but the time required to
2223 required to send the entire rendering request to the back-end server, so
2224 this optimization was rejected for the other rendering primitives.
2994 back-end servers or handling them locally.  All rendering requests are
3003 <para>The X Rendering Extension (RENDER) provides support for digital image
3004 composition.  Geometric and text rendering are supported.  RENDER is
3013 <para>There is currently no test suite for the X Rendering Extension;
3189 over the entire set of visuals, additional rendering tests were run and
3191 supported by the fact that nearly all of the rendering errors reported
3196 <para>Further, when hardware rendering is disabled on the back-end displays,