Hi all! For those, who don't know: Recently, we rewrote the X-target. It is in our latest CVS version. The main intention for this was to get rid of a design mistake, that was made. It forced us to write a complete GGI target for each different functionality (use of an different extension (xf86dga), use hw-acceleration of the X-server (Xlib), emulation of a virtual framebuffer (X)). Thus, the maintainance of it was not that simply. And there are still some users (with some more or less exotic system-configurations), who have problems with getting GGI on X working. The new X-target is likely a hybrid by merging X- and Xlib-targets together. It makes better use of hw-acceleration of the X-server and it is possible to make use of the X-extensions without writing a complete new target such as the xf86dga one. Further, it fixes some endianness bugs, the (old) Xlib target has. The price for this is, that the new X-target is less tolerant to bugs within the X-server. The Xlib-target is currently not removed, but disabled in CVS. The xf86dga-target will be removed as soon as the X-target can duplicate its functionality. We are heading to a libgii 0.8.2 and a libggi 2.0.2 bugfix releases. The X-target of libggi 2.0.1 works fine you? Then you surely expect, that it will work for you once you upgraded to libggi 2.0.2. The X-target of libggi 2.0.1 annoys you with getting problems? Then you surely hope, that they are solved with libggi 2.0.2. In order to avoid you to make bad experiences with libggi 2.0.2, we interced for giving it a try. Note, that you need the latest CVS version of libgii for the CVS version of libggi, too. CU, Christoph Egger E-Mail: [EMAIL PROTECTED]
