Linked by Thom Holwerda on Sun 15th Oct 2006 18:32 UTC, submitted by martini
OS/2 and eComStation The proposed design for Voyager, which aims to become an OS/2 replacement, is now available. "Voyager is the codename for the idea of having a replacement OS/2 on top of modern technology. This idea is the result of around 1.5 years of thinking a lot about what we can do in the future as current OS/2 and eComStation users. Note that it's absolutely impossible to convey what we plan to do in a few sentences. I made a speech on it at Warpstock Europe 2005 that, by itself, took 1.5 hours so you get the point." Read the Voyager FAQ to understand what it actually is and aims to become.
Thread beginning with comment 171939
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[3]: Well, what shall I say:
by rayiner on Sun 15th Oct 2006 21:49 UTC in reply to "RE[2]: Well, what shall I say:"
rayiner
Member since:
2005-07-06

XCB doesn't really need to be documented. It's just a t hin wrapper over the X protocol, which is itself quite well documented.

As for being outdated --- I don't see what's so outdated about the X protocol. It creates graphics contexts, windows, handles input, etc. There is just not a lot of new things to do in these areas. I mean, no matter how fancy your OpenGL-based windowing system is, you're still going to need to create windows, graphics contexts, handle mouse events, and is there a huge incentive to do these things in a fundementally different way?

There are legitimate reasons to avoid X, however. It's a big piece of code, and if you don't want to use the core X or RENDER to do drawing (you don't), then you're going to have to do some surgery, which won't be easy. Of course, using DRI independently of X will be a lot of work too, so you're probably not saving much.

Reply Parent Score: 2