[Xcb] Porting the rest of the X.Org apps to xcb

Daniel Stone daniel at fooishbar.org
Fri Jul 16 07:58:21 PDT 2010


On Fri, Jul 16, 2010 at 05:32:32PM +0300, Tiago Vignatti wrote:
> On Fri, Jul 16, 2010 at 04:24:04PM +0200, ext Vincent Torri wrote:
> > On Fri, 16 Jul 2010, Alan Coopersmith wrote:
> > > Given what I learned on the xwininfo port I took a quick pass across
> > > the rest of the X.Org app/* modules to see what it would take to port
> > > each to xcb.
> > >
> > > I am *not* volunteering to do these all, just offering some insight into
> > > which are going to be easier/harder/not possible and hoping that others
> > > will step up to do some of these.
> > >
> > > At least at a quick glance, I think these could be fairly straightforward
> > > to port to XCB, though whether it's worth the effort for all of them is
> > > debatable:
> > >
> > >    backlight, ico, xcmsdb, xcompmgr, xdriinfo, xhost, xinit, xkill,
> > >    xrandr, xrdb, xrefresh, xrestop, xsetroot, xshowdamage, xstdcmp,
> > >    xvinfo, xwd, xwud
> > 
> > Arnaud Fontaine wrote an XCB-based composite manager. Is it necessary to 
> > port xcompmgr ?
> 
> xcompmgr is a nice example of a tiny compositor manager. My quickly at
> Arnaud's tells that it isn't that much.

Mm, there's a lot in xcompmgr that makes it a great example of how not
to design a compositing manager.  Unless you don't care in the least
about efficiency or aesthetics (which is sort of the point of a compmgr).

Cheers,
Daniel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL: <http://lists.x.org/archives/xorg-devel/attachments/20100716/5584c166/attachment.pgp>


More information about the xorg-devel mailing list