[Xcb-commit] History.mdwn index.mdwn tutorial.mdwn usingxcb.mdwn XcbApi.mdwn XcbNotes.mdwn XCBToDo.mdwn

Jamey Sharp jamey at freedesktop.org
Wed Oct 29 17:21:06 PDT 2008 

 History.mdwn  |    2 +-
 XCBToDo.mdwn  |    2 +-
 XcbApi.mdwn   |   12 ++++++------
 XcbNotes.mdwn |    3 +--
 index.mdwn    |   23 +++++++++++------------
 tutorial.mdwn |   14 +++++++-------
 usingxcb.mdwn |    2 +-
 7 files changed, 28 insertions(+), 30 deletions(-)

New commits:
commit ce7cfb958b8a4dd4d357cba82eecc0d603c2d8bb
Author: Jamey Sharp <jamey at minilop.net>
Date:   Wed Oct 29 17:19:58 2008 -0700

    Use ikiwiki-style links, not markdown links, for wiki pages.

diff --git a/History.mdwn b/History.mdwn
index 06064e1..a5da04b 100644
--- a/History.mdwn
+++ b/History.mdwn
@@ -1,6 +1,6 @@
 Described here are some of the decisions in XCB of historical interest.
 
-You can view [completed tasks](XCBCompletedTasks).
+You can view [[completed tasks|XCBCompletedTasks]].
 
 ### Life before git
 
diff --git a/XCBToDo.mdwn b/XCBToDo.mdwn
index 2b754de..361f2ba 100644
--- a/XCBToDo.mdwn
+++ b/XCBToDo.mdwn
@@ -75,7 +75,7 @@ This list might be roughly in order of importance.
 
 Encapsulate ICCCM, window reparenting and event capture, and anything else that seems appropriate, in one or more libraries. It should be able to cooperate with other libraries; Cairo comes to mind. Perhaps COMPOSITE extension helpers would be useful too, so it can support compositing managers as well.
 
-A prototype implementation is available in the xcb-util module; more discussion is on the [Using XCB](../usingxcb) page.
+A prototype implementation is available in the xcb-util module; more discussion is on the [[Using XCB|usingxcb]] page.
 
 ## Alternate targets
 
diff --git a/XcbApi.mdwn b/XcbApi.mdwn
index 5e4a9de..f40a1cd 100644
--- a/XcbApi.mdwn
+++ b/XcbApi.mdwn
@@ -2,11 +2,11 @@ _Refactoring this page...please be patient..._
 
 [[!toc levels="6"]]
 
-This is the API for [XCB](/). Each function and data structure documents the source file containing its declaration, in addition to the usual sorts of documentation.
+This is the API for [[XCB|index]]. Each function and data structure documents the source file containing its declaration, in addition to the usual sorts of documentation.
 
-See also [Using XCB](../usingxcb) for tips and tricks on how to properly use the API.
+See also [[Using XCB|usingxcb]] for tips and tricks on how to properly use the API.
 
-1. [Public API](../PublicApi)
-2. [Protocol Stub API](../ProtocolStubApi)
-3. [Protocol Extension API](../ProtocolExtensionApi)
-4. [Xlib XCB API](../XlibXcbApi)
+1. [[Public API|PublicApi]]
+2. [[Protocol Stub API|ProtocolStubApi]]
+3. [[Protocol Extension API|ProtocolExtensionApi]]
+4. [[Xlib XCB API|XlibXcbApi]]
diff --git a/XcbNotes.mdwn b/XcbNotes.mdwn
index 9532ff5..24e514e 100644
--- a/XcbNotes.mdwn
+++ b/XcbNotes.mdwn
@@ -20,7 +20,7 @@ Hope this helps. Comment welcome.
 
 ### Double Buffering
 
-Double buffering on X is kind of a mess. Here's documentation on the [Multi-Buffering](buffer.pdf) and [XDBE](dbe.pdf) extensions in case someone wants to write a protocol description for XCB. Note: Multibuffer is deprecated in favour of DBE. It also seems that DBE is deprecated. See [this](http://lists.freedesktop.org/archives/xcb/2006-August/001854.html) thread.
+Double buffering on X is kind of a mess. Here's documentation on the [[Multi-Buffering|buffer.pdf]] and [[XDBE|dbe.pdf]] extensions in case someone wants to write a protocol description for XCB. Note: Multibuffer is deprecated in favour of DBE. It also seems that DBE is deprecated. See [this](http://lists.freedesktop.org/archives/xcb/2006-August/001854.html) thread.
 
 A conversation with keithp indicates that his current thinking is that the right way to do double buffering is via an explicit copy from a separate pixmap. This is portable to absolutely everywhere, and requires no magic. Probably there will soon be a convention for the compositing manager to handle the double buffering on systems where one is running, since it needs to buffer anyhow. But this would be in the future.
 
@@ -39,4 +39,4 @@ The guiding principle of XCB naming is that one should be able to *infer* the na
 
 The basic C naming conventions are that macros are in all caps, other names are in all lower case, and underbar is used as a word separator.  All publicly-visible symbols are prefixed with "xcb"; extension symbols are then prefixed with the extension prefix (usually its name).  Following this prefix is the name of the symbol as given in the relevant protocol document, transliterated as exactly as possible.  Operations on a given protocol request, such as reply retrieval or iterator construction, are given by standard suffixes.  Typenames end with a suffix t.
 
-I think looking through a few header files should clarify this, and working through a few examples should explain why we like it.  (It also makes it easy for us to generate the C from the XML protocol description, but that's just an added bonus, not the primary motivation.)
\ No newline at end of file
+I think looking through a few header files should clarify this, and working through a few examples should explain why we like it.  (It also makes it easy for us to generate the C from the XML protocol description, but that's just an added bonus, not the primary motivation.)
diff --git a/index.mdwn b/index.mdwn
index 4671f95..1a7dc98 100644
--- a/index.mdwn
+++ b/index.mdwn
@@ -1,29 +1,28 @@
-[![XCB](KittyLogo/neko.png)](KittyLogo)
+[[!img KittyLogo/neko.png link="KittyLogo"]]
 
 # Introduction
 
-The X protocol C-language Binding (XCB) is a replacement for Xlib [featuring](Features) a small footprint, latency hiding, direct access to the protocol, improved threading support, and extensibility.
+The X protocol C-language Binding (XCB) is a replacement for Xlib [[featuring|Features]] a small footprint, latency hiding, direct access to the protocol, improved threading support, and extensibility.
 
 # Download
 
 - You can obtain released versions of XCB from <http://xcb.freedesktop.org/dist>.
-- Follow the instructions from the [developer's guide](DevelopersGuide) to build, except that you can use released versions of the dependencies, and you don't need git, automake, autoconf, or libtool.
+- Follow the instructions from the [[developer's guide|DevelopersGuide]] to build, except that you can use released versions of the dependencies, and you don't need git, automake, autoconf, or libtool.
 
 # Development
 
-- If you wish to work on XCB, please read the [developer's guide](DevelopersGuide).
+- If you wish to work on XCB, please read the [[developer's guide|DevelopersGuide]].
 - **Mailing list**: Discussion of XCB and Xlib/XCB is through the [XCB mailing list](http://www.freedesktop.org/mailman/listinfo/xcb).
-- **IRC**: XCB developers also hang out on [IRC](IRC), and have occasional [meetings](meetings).
-- Of course, there's still a lot [to do](TODO) .
+- **IRC**: XCB developers also hang out on [[IRC]], and have occasional [[meetings]].
+- Of course, there's still a lot [[to do|TODO]] .
 
 # Documentation
 
-- The [XCB API](XcbApi) is documented. There is also a [tutorial](tutorial) and some random [notes](XcbNotes).
-- People wanting to implement higher level applications can use [xcb-util](XcbUtil).
-- XCB is built atop an XML description of the X core protocol and common extension protocols called [XML/XCB](XmlXcb). This protocol can be used in other interesting ways.
-- To aid in porting applications, you can configure Xlib to use XCB for the transport layer. We call this [Xlib/XCB](XlibXcb).
+- The [[XCB API|XcbApi]] is documented. There is also a [[tutorial]] and some random [[notes|XcbNotes]].
+- People wanting to implement higher level applications can use [[xcb-util|XcbUtil]].
+- XCB is built atop an XML description of the X core protocol and common extension protocols called [[XML/XCB|XmlXcb]]. This protocol can be used in other interesting ways.
+- To aid in porting applications, you can configure Xlib to use XCB for the transport layer. We call this [[Xlib/XCB|XlibXcb]].
 
 # Miscellaneous
 
-The XCB project has a long [history](History), during which it has produced many academic [publications](publications). XCB has, of yet, seen limited [adoption](adoption).
-R
+The XCB project has a long [[history]], during which it has produced many academic [[publications]]. XCB has, of yet, seen limited [[adoption]].
diff --git a/tutorial.mdwn b/tutorial.mdwn
index 6ec4cc7..9cc865b 100644
--- a/tutorial.mdwn
+++ b/tutorial.mdwn
@@ -2,13 +2,13 @@
 
 After reading this page, read these pages (in this order):
 
-* [Basic Windows and Drawing](basicwindowsanddrawing)
-* [Events](events)
-* [Text and Fonts](fonts)
-* [Window Context and Manipulation](../windowcontextandmanipulation)
-* [Colors and PixMaps](../colorsandpixmaps)
-* [Mouse Cursors](mousecursors)
-* [Xlib to XCB Translation Guide](../xlibtoxcbtranslationguide)
+* [[Basic Windows and Drawing|basicwindowsanddrawing]]
+* [[Events|events]]
+* [[Text and Fonts|fonts]]
+* [[Window Context and Manipulation|windowcontextandmanipulation]]
+* [[Colors and PixMaps|colorsandpixmaps]]
+* [[Mouse Cursors|mousecursors]]
+* [[Xlib to XCB Translation Guide|xlibtoxcbtranslationguide]]
 
 # Introduction
 
diff --git a/usingxcb.mdwn b/usingxcb.mdwn
index 78071cd..de08cc7 100644
--- a/usingxcb.mdwn
+++ b/usingxcb.mdwn
@@ -1,4 +1,4 @@
-(See also the [XCB To Do](../XCBToDo) list and the [XCB](/) project page.)
+(See also the [[XCB To Do|XCBToDo]] list and the [[XCB|index]] project page.)
 
 Now that we have this XCB library and it pretty much just works, what can we do with it? I'd like to make it easier to build new window managers. (For an example of a window manager, see fellow freedesktop.org project Waimea.) I've picked this goal partly because I want to see more experimentation in user-interface design through window managers, and partly because most of the needed pieces are more broadly applicable.

More information about the xcb-commit mailing list