Slashdot Mirror
XFree86 Fork Gets a Name, Website
Piethein Strengholt writes "Today the Xfree86 fork is a fact. A new project has started and is located at: xouvert.org. Xouvert has been started due to the corporate structure and the slow development of XFree86. They hope to reduce the risk to XFree86 of incorporating new drivers and features."
Note that this is not xwin.org... I browsed the xwin website a while ago (Keith Packards project) and people there have been complaining about how that project seems dead, while something should start happening. I applaud the effort of these guys.
Save your wrists today - switch to Dvorak
ZOO-VERT.
"ouvert" means "open" in French.
On the first line of the page, it says: Xouvert is an experimental branch of XFree86.
Looks like you got what you wanted.
Drop the network transparency, make it run framebuffer and XFree is obsolete on desktop.
Why do people not realize, that X-Windows is NOT sucking because of network transparancy! Any possible design of a clean API for a windowing system will more or less be automatically network transparent. The only this which is not network transparent are stupid ugly hacks. That said, we all know how X sucks, but it is has definitively nothing to do with network transparancy.
Cheers
KdenLive/PIAVE - non-linear video editing
See my previous comment on NX compression. I'm typing this on Galeon running at work, displaying on my home computer over a 56K modem, because it's faster web browsing like this than running the browser locally. NX has to be seen to be believed.
The interesting thing is, this level of compression is only possible because of the high-level nature of X's network transparency - Citrix / RDP / VNC doesn't run anywhere near as fast.
perl -e 'fork||print for split//,"hahahaha"'
Only the proxy is GPLed, the Xlib stuff is X11. The proxy is a separate program, so thats ok.
What is really needed is a driver for the XServer that will duplicate the current X command stream. This could then be sent to the NX proxy, and actually use it as a remote desktop. Also could use VNC, and it could also be useful for providing desktop pagers with full update capability.
Frankly, it may be worth jettisoning a lot of the XFree86 baggage and starting anew.
Y, an X Windows replacement, looks extremely well designed and this guy wrote a pretty complete implementation for his thesis.
Why not port the useful bits of X - like the hardware drivers - over to this already-established well-designed base instead of trying to hack XFree86 into something of similar quality?
(Well, the obvious answer, ``to keep the applications`` is fair enough. But a compatibility module wouldn't be too hard, and worth the benefit in the long run.)
So I just checked out the IRC channel, and they emphasized that Xouvert is an experimental branch of X, not a fork.
I could be mistaken but isn't that how /. came around? Hrm, and now that I check my sources the faq says:
:)
I wanted to make the URL silly, and unpronounceable.
So, I guess it has worked before
~Dan
http://www.pbase.com/efatapo
Ok, try to follow this:
They hope to reduce the risk to XFree86...
Looks like they want to make something less risky to XFree86. I wonder what it is?
Ah. They want to make the incorporation of new drivers and features seem less risky to the XFree86 project. As in, "See XF86? We put all these features and drivers into our project. It's not so bad!"
If you've ever managed a reasonably large open source project then you know that making everything public from the beginning won't necessarily be a good thing!
You can't just dump some stuff somewhere on the net and then expect people to contribute. You have to prepare a lot of things, so that people can easily contribute without getting lost in the mess!
And I don't know who moderated you up but those moderators certainly didn't read the website. I quote:
"Sat Aug 16 00:59:49 PDT 2003 - You can't download anything yet. We have this website, XWIN is providing Wiki space, and Savannah is providing mailing list and bug tracking services. We are importing the Xfree86 source code into an arch repository right now; the current job is making a script to tag the source files every time a CVS checkout is done. The IRC logging bot still needs to be set up, and code written to archive the logs daily."
The website has only been up since yesterday! Accusing them for "keeping it secret" and shoot down their image is just stupid, when they've just started recently.
What is a "GUI refresh rate?"
It's related to the lag between dragging the mouse pointer down a menu and having the items highlight. It's related to dragging the scroll bar and having the view move smoothly. It's related to dragging a window and having both it and what's under it react smoothly.
3) Your driver does not support hardware acceleration
This is one of the major problems. Hardware vendors tend to expose too many of their trade secrets at the register level, and then they use this as an excuse not to release information to driver developers in Free window system implementation projects.
Will I retire or break 10K?
This is the way every windowing system should be designed, even if you only want to display on one screen. It mimics reality -- there's a display over here, and there's a processor over there. Every "average" person uses a remote desktop. It shouldn't matter if the display is connected via a VGA cable or ethernet (through a network of other computers). It should still allow the same functionality with the same APIs.
If you were to try to strip network transparency and device independence from X, it would take a lot of work, and you wouldn't gain much.
Yes, X had design issues. Yes, it's hard to code programs for X (though if you use libs like SDL, KDE, or Gnome, things become very practical very quickly). But these problems are not necessarily caused by its feature set. I'm sure that if the original inventors had known this was going to become the major windowing system for many UNIX-like operating systems over the next few decades, they would have put a little more thought into the API design. But this is the same problem that haunts almost every software project.
...just my 2 gil.
Yes it's compatible. X11 is a protocol, not an implementation. XFree86 is an implementation. Xouvert will be another implementation of the same protocol.
let me be the first to give this project a usable name:
XO (pronounced: ex-oh).
ouvert is french for 'open'. ignore the prank the website is trying to play on you. i don't intend to add the french inflection 'zoovair' every fucking time i say it (much like i like my croissants to be crassandwiches). besides, the name XOPEN is already taken. so there you have it, folks. say it with: me XO is not Xfree86
Maybe you are looking for this-
http://xf4vnc.sourceforge.net/
:. Ultimate Control Dedicated/VM Servers
If you love that one how about the router debate?
Is the pronunciation a rooter or a rowter.
The computer device is a rooter.
The Woodworking tool is a rowter
Look it up
EA David Gardner -"... but the consumers have proven that actually what they want is fun."
Run along over to DirectFB, grab the framebuffer code and modules for your card, or just use their default VESA Framebuffer (works on everything), then try out the XDirectFB module for X Window System ontop of their Framebuffer. Already, DRI/accelerated openGL works by use of their DirectFBGL interface for Matrox G200/G400/G450/G550 and support for DRI/accelerated openGL will be around within a month (work in progress, almost released to public).
If you don't believe me, here are the direct links to what you need or should see:
DirectFB graphics support list (project page)
DirectFBGL (openGL Framebuffer abstraction layer for DRI project's openGL)
XDirectFB (alternative X Server! Works fast and verry compatible!)
Accelerated openGL screenshots (Quake3 works without X Window System, although hacked to abstract!)
Judging from the Fresco-changes list, progress continues to be made, albeit slowly. They really could use some support. If you know C++, check it out, it is an interesting project.
"They hope to reduce the risk to XFree86 of incorporating new drivers and features" ????
Idea dislexia? Are they really trying prevent new drivers and features?
Heh, if that were the case, I suppose they could stop at their name change and say they're done:)
The only one with dyslexia here is you.
"to reduce the risk"... let's put it in baby english for you... "to make it easier"...
Rewritten: "They hope to make it easier for XFree86 to incorporate new drivers and features"
You quote something reasonable and pretend it's something else. That's not even trolling, that's just plain stupid.
Free Gamer - Free games list and commentary
It's not an "obscure occult reference," it's French for "open." Let me guess: you're American. It's a perfectly acceptable name: the Internet is global, and there are other languages apart from English.
Click here.
There are some nice features going into Xouvert, one of them is the auto hardware recognition system which I feel is very cool and should be the way to go.
From Xouvert Wiki:
Ouverter is a new hardware auto-detection system build ontop of Xouvert kernel module. Ouverter
provides hooks to hardware detection and auto configuration. The system would generally auto
configure most common devices; such as mice, keyboards, gaming devices and DMS supported monitors.
Ouverter would also auto detect most modern video cards, using a database of card lookup, this
database would be updated regularly and new card signatures would be added and distributed outside
the usual Xouvert releases (to faciliate new hardware detection). A windows like display change
support would be built in as well.
This is cool and much appericated feature, I wish them luck and wait for their first release.
Linux is pronounced LIE-nucks.
On kernel.org you can find the correct pronunciation.
Do you care about the security of your wireless mouse?