dmx/doc/scaled.xml

1 <?xml version="1.0" encoding="ISO-8859-1"?>
2 <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.3//EN"
3  "http://www.oasis-open.org/docbook/xml/4.3/docbookx.dtd" [
9     <!-- Title information -->
30       <!-- Begin the document -->
36             a single multi-headed X server.  Combined with Xinerama,
37             these heads can appear as a single very high-resolution
46             provides high pixel-resolution may be difficult to see,
114               it does not provide any anti-aliasing other than that
115               provided by the underlying (Windows-only) system library.
121             The X Video Extension is a widely-available extension to the
134             Note, though, that the target output for this scaling is an
135             overlay plane -- so X Video provides functionality that is
146           implementation and the end-user programmer standpoint.
148         <sect2><title>VNC-like Scaling</title>
157               against <filename>vnc-3.3.7-unixsrc</filename> is available in the
177               VNC suite is being re-written in C++ and the forthcoming
203               A very early-stage proof-of-concept prototype was
205               <filename>vnc-3.3.7-unixsrc</filename> is available in the
219                   client-side image or a server-side off-screen pixmap,
226                     hardware scaling using an RGB format (e.g., ATI
234                     pixel-resolution for communicating updates on the
240                     Further, the well-known problem with YUV encoding
243                     1-pixel-wide vertical window border.  If the border
272                 The user-level API for X Video is fairly simple, but the
297                     Support for querying back-end X Video Extension
301                     Support for sending the image to the back-ends.
303                     may be a trade-off between bandwidth limitations and
308                     Possible support for a software fall-back.  For
309                     example, if all of the back-ends do not support the X
311                     such that the image is sent to the back-end with
321                 Extension, and assuming the target hardware supports an
332               hardware-assisted scaled blits, similar to the StretchBlt
347                   off-screen pixmap, and then calling XCopyAreaScaled
348                   between that off-screen pixmap and the target
353                   on-screen or off-screen memory, it has additional uses
368               between pixmaps (i.e., on-screen or off-screen areas of
371               XCopyAreaScaled would write into the non-overlay areas of
420               using OpenGL would transmit the non-scaled image to the X
422               non-transformed rect using that texture.  This also works
440         <sect2><title>Application-transparent Scaling for DMX
441           </title><sect3><title>Back-end Scaling Without Disconnect/Reconnect</title>
445               solution for DMX would require support in the back-end X
452               Screen Section, then pressing Ctrl-Alt-Plus and
453               Ctrl-Alt-Minus can be used to iterate through the listed
461               software control (via the XFree86-VidModeExtension), so
463               per-display basis, thereby scaling the information on part
469               1280x1024 displays.  If all of the back-end servers were
478           <sect3><title>Back-end Scaling With Disconnect/Reconnect</title>
483               XFree86-VidModeExtension Extension, would allow an
487                   Disconnect a specific back-end server (via the DMX
491                   reconfigure the XFree86 back-end server resolution,
495                   reconnect the back-end server to DMX -- at a new
507               one-fourth of the size of the DMX display.  This change
509               perhaps, for a DMX-aware window manager).  When work at
510               the increased resolution was completed, the back-end
516               DMX-aware X11 client assuming the DMX server support
523           <sect3><title>Server-side Scaling</title>
528               early VNC implementations).  The use of a server-side
531               issues and server-side memory issues (i.e., the frame
649                 implementation of a software fall-back in XFree86 and
654                 We suggest implementing the extension first on the ATI
668                 scaling method.  We suggest OpenGL as the first fall-back
673                 A project centered around OpenGL-based scaling would
675                 would include re-writing the <command>vncviewer</command>
683                 provide hardware-assisted performance in every
695                 ATI Radeon).
712           functionality.  Further, server-side scaling with a large
717           The back-end scaling, especially with disconnect/reconnect
725   <!-- Local Variables: -->
726   <!-- fill-column: 72  -->
727   <!-- End:             -->