<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 TRANSITIONAL//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; CHARSET=UTF-8">
<META NAME="GENERATOR" CONTENT="GtkHTML/3.26.0">
</HEAD>
<BODY>
On Sun, 2010-12-05 at 20:39 -0800, Keith Packard wrote:<BR>
<BLOCKQUOTE TYPE=CITE>
<TT><FONT COLOR="#1a1a1a">@@ -29,14 +29,14 @@ protocol described here, as it has been overtaken by events.</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> </FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> These events include:</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> ► Modern toolkits (in this case, GTK+ 2.x) have progressed to the point</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">- of implementing migration between screens of arbitrary depths</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">+ of implementing migration between screens of arbitrary depths</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> ► The continued advance of Moore's law has made limited amounts of VRAM</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">- less of an issue, reducing the pressure to implement depth switching</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">+ less of an issue, reducing the pressure to implement depth switching</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> on laptops or desktop systems</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> ► The continued decline of legacy toolkits whose design would have</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">- required depth switching to support migration</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">+ required depth switching to support migration</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> ► The lack of depth switching implementation experience in the</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">- intervening time, due to events beyond our control</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">+ intervening time, due to events beyond our control</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> </FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> Additionally, the requirement to support depth switching might</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> complicate other re-engineering of the device independent part of the</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">@@ -138,7 +138,7 @@ Thomas Winischhofer for the hardware-accelerated SiS rotation implementation</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> Matthew Tippett and Kevin Martin for splitting outputs and CRTCs to more</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> fully expose what video hardware can do</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> </FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">- ❧❧❧❧❧❧❧❧❧❧❧</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">+ ❧❧❧❧❧❧❧❧❧❧❧</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> </FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> 2. Screen change model</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> </FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">@@ -182,7 +182,7 @@ pop-up menus and other pop up windows will position themselves correctly in</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> the face of screen configuration changes (the issue is ensuring that pop-ups</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> are visible on the reconfigured screen).</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> </FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">- ❧❧❧❧❧❧❧❧❧❧❧</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">+ ❧❧❧❧❧❧❧❧❧❧❧</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> </FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> 3. Data Types</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> </FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">@@ -190,7 +190,7 @@ The subpixel order is shared with the Render extension, and is documented</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> there. The only datatype defined is the screen size, defined in the normal</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> (0 degree) orientation.</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> </FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">- ❧❧❧❧❧❧❧❧❧❧❧</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">+ ❧❧❧❧❧❧❧❧❧❧❧</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> </FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> 4. Errors</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> </FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">@@ -203,7 +203,7 @@ CRTC</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> Mode</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> A value for a MODE argument does not name a defined MODE.</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> </FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">- ❧❧❧❧❧❧❧❧❧❧❧</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">+ ❧❧❧❧❧❧❧❧❧❧❧</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> </FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> 5. Protocol Types</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> </FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">@@ -266,11 +266,11 @@ CONNECTION { Connected, Disconnected, UnknownConnection }</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> connected to a monitor or other presentation device.</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> </FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> SUBPIXELORDER { SubPixelUnknown The subpixel order uses the Render</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">- SubPixelHorizontalRGB extensions definitions; they are here</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">- SubPixelHorizontalBGR only for convenience.</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">- SubPixelVerticalRGB</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">- SubPixelVerticalBGR</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">- SubPixelNone }</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">+ SubPixelHorizontalRGB extensions definitions; they are here</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">+ SubPixelHorizontalBGR only for convenience.</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">+ SubPixelVerticalRGB</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">+ SubPixelVerticalBGR</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">+ SubPixelNone }</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> </FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> SCREENSIZE { widthInPixels, heightInPixels: CARD16</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> widthInMillimeters, heightInMillimeters: CARD16 }</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">@@ -292,15 +292,15 @@ MODEFLAG { HSyncPositive</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> </FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> MODEINFO { id: MODE</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> name: STRING</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">- width, height: CARD16</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">- dotClock: CARD32</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">- hSyncStart, hSyncEnd, hTotal, hSkew: CARD16</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">- vSyncStart, vSyncEnd, vTotal: CARD16</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">- modeFlags: SETofMODEFLAG }</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">+ width, height: CARD16</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">+ dotClock: CARD32</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">+ hSyncStart, hSyncEnd, hTotal, hSkew: CARD16</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">+ vSyncStart, vSyncEnd, vTotal: CARD16</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">+ modeFlags: SETofMODEFLAG }</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> </FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> REFRESH { rates: LISTofCARD16 }</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> </FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">- ❧❧❧❧❧❧❧❧❧❧❧</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">+ ❧❧❧❧❧❧❧❧❧❧❧</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> </FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> 6. Extension Initialization</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> </FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">@@ -323,7 +323,7 @@ The name of this extension is "RANDR".</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> It is the clients responsibility to ensure that the server</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> supports a version which is compatible with its expectations.</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> </FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">- ❧❧❧❧❧❧❧❧❧❧❧</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">+ ❧❧❧❧❧❧❧❧❧❧❧</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> </FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> 7. Extension Requests</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> </FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">@@ -564,7 +564,7 @@ dynamic changes in the display environment.</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> name: STRING</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> connection: CONNECTION</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> subpixel-order: SUBPIXELORDER</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">- widthInMillimeters, heightInMillimeters: CARD32</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a">+ widthInMillimeters, heightInMillimeters: CARD32</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> crtcs: LISTofCRTC</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> clones: LISTofOUTPUT</FONT></TT><BR>
<TT><FONT COLOR="#1a1a1a"> modes: LISTofMODE</FONT></TT><BR>
<BR>
</BLOCKQUOTE>
Just to let you know that down to here, these changes are not related to space/tab combos.<BR>
These changes replace 'space chars' with a 'tab char'. I don't know if it is good or not,<BR>
or if it is intentional or not.<BR>
<BR>
git diff reports only a few space/tab combo issues:
<BLOCKQUOTE>
<PRE>
randrproto.txt:622: space before tab in indent.
+ output:OUTPUT
randrproto.txt:624: space before tab in indent.
+ atoms: LISTof ATOM
randrproto.txt:636: space before tab in indent.
+ pending: BOOL
randrproto.txt:666: space before tab in indent.
+ pending: BOOL
randrproto.txt:683: space before tab in indent.
+ output: OUTPUT
randrproto.txt:720: space before tab in indent.
+ output: OUTPUT
randrproto.txt:731: space before tab in indent.
+ output: OUTPUT
randrproto.txt:782: space before tab in indent.
+ window: WINDOW
randrproto.txt:785: space before tab in indent.
+ mode: MODE
randrproto.txt:798: space before tab in indent.
+ mode: MODE
randrproto.txt:976: space before tab in indent.
+ red: LISTofCARD16
</PRE>
</BLOCKQUOTE>
<BR>
<BR>
<BR>
<BR>
<BR>
</BODY>
</HTML>