> maybe i'm missing the point: what's the point in a library that needs > another library > in order to be used? i don't really think it's a good idea. maybe it > would be better > to better implement the library in order for it to be used without > another sanitizing > library,
Its the same as with xcb or Xlib. Both aren't used a lot directly by application programmers, instead programmers use QT4/Gtk or Java2D as "sanitizing libraries" Xlib's task is to allow access to the X11 protocol from C, exatly what libXrender does for the RENDER extension. > that would cost more resources. libXRender only contains X11 protocol generation and a few definitions. If Cairo/QT4/... would have to generate the protocol themself, it would probably lead to a lot of duplicate code and bloat. > If the interfaces are documented, it's possible to change the library > implementations without breaking applications. Well, thats exactly what the protocol specification is about, it contains everything you need to know to implement a library. However, the protocol specification is not a programmer manual howto use RENDER or libXRender, and at least what I've heard, this is what most people are asking for (including myself about a year ago ;) ). - Clemens _______________________________________________ xorg mailing list xorg@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/xorg