| |||||||||||
X at OLSX at OLSPosted Jul 23, 2004 13:25 UTC (Fri) by elanthis (subscriber, #6227)In reply to: X at OLS by MathFox Parent article: X at OLS Why? After reading this write-up, it should be pretty clear even to someone not familiar with X11 at all that there is *NO* reason to break compatibility. Seriously, what would X12 have different from X11? All you'd do is have a slightly different set of default commands (extensions), and that's absolutely pointless, because you can just do that in X11. The low-level actual protocol of X11 is perfectly fine and doesn't need any changes in order to operate appropriately for modern needs.
(Log in to post comments)
X12 (was: X at OLS) Posted Jul 23, 2004 15:39 UTC (Fri) by MathFox (subscriber, #6104) [Link] Do we need suport for fixed size bitmapped fonts (only?) 256 colour palettes? The whole set of pixel or/and/not operations?With a modern graphics card you'ld want antialiassed scalable fonts, an RGBalpha colour model, colour blending, etc. Some of these are in current X11 expensions and should be moved to the X12 core. Some of the current X11 core stuff should be dropped and moved to a compatability library. Keith has some ideas that require deep modifications of the protocol.
X12 (was: X at OLS) Posted Jul 23, 2004 17:19 UTC (Fri) by bradfitz (subscriber, #4378) [Link] There's no advantage to having something "in the core". The reason X11 hasn't become X12 is because X11 adapts wonderfully to new extensions as they come and go. You make fun of the bitwise and/or/not operations now, but we'll be making fun of the current state of graphics in another decade.Why do we want today's cutting edge (tomorrow's crap) "in the core"?
X at OLS Posted Jul 23, 2004 20:31 UTC (Fri) by iabervon (subscriber, #722) [Link] I think the main change that should be made is really in Xlib rather than the protocol. A huge portion of the library is stuff that you shouldn't use these days. Another chunk deals with stuff you shouldn't have to worry about. It would greatly simplify X programming if the library insisted on a TrueColor visual and simulated 24bpp on other depths. Of course, cleaning all of this up would require changing header files, so the new version would have to be somewhere other than <X11/...>, suggesting that it would be X12.It might also be worth making the core X11 stuff an extension for uniformity, and to have a set of standard extensions that you'd be informed of simply by the server telling you what release it is. It might also be necessary to change the lowest-level protocol for some of the virtualization and security stuff.
|
|||||||||||