X.org and XFree86 Reform
albepetr writes "NewsForge is reporting about a press conference held today at LinuxWorld 2004 in New York, where some members of the X Consortium, XFree86, and freedesktop.org announced that X.org and XFree86 have merged. They claim that the reformed group will be working together to bring "not just more eye candy but new functionality" to the X Window Manager for Linux and Unix." Newsforge and Slashdot are both part of OSDN. Update: 01/23 18:06 GMT by M : XFree86.org denies the story. I think a more accurate description of the event might be something like, "XFree86 core developers leave XFree86, join X.org, remaining people of XFree86 are peeved".
Will we see a unified Windows environment for Linux now?
give credit to -- individual contributors rather than continue to view X development primarily as a corporate activity.
I like this alot. Functionality to the desktop is something that Unix and Linux both need to see loads of improvement on to help spread it to a larger market. I also like to see the OpenSource community coming together and joining into larger projects that can do more, rather than see hundreds of smaller projects all going in the same direction seperately. Bringing lots of brain power together gets stuff done.
Hopefully, they will work out a SINGLE standard for getting copy/cut and paste working correctly.
I can't tell you how infuriating it is when you go to copy a page of text from, say, openoffice.org, and paste it into a webform in Mozilla - only to find that perhaps the first half a paragraph out of 6 made it over.
Ron Gage - Westland, MI
Please, let's get off this dead horse.
Cut'n'paste works on X's level.
The problem is (or probably: was) not with X, but with Gnome and/or KDE.
Real life is overrated.
"It's just too big, slow, and full of features desktop users don't need. Directfb is more like what desktop users need, but not quite."
/., you would have known by this time, that X is neither big or slow, and the framebuffer approach is not what users really want (and that Windows' model is slowly transforming from the framebuffer to a more X-like approach)
If you really would have taken the time to read the previous X stories on
Real life is overrated.
...hands down.
The problem is (or probably: was) not with X, but with Gnome and/or KDE
Indeed.
X has the most elegant cut-and-paste scheme I've ever seen, certainly vastly superior to Mac OS X and Windows.
Select with the left button pressed, and click with the middle button in the target window to paste. No Apple-C or control-V crap, no need to press any key of any kind. Click-select, click, and you're done.
Once you get used to it, you won't be able to stand the way Mac OS X and Windows handle cut-and-paste.
Gnome and KDE made the extremely boneheaded decision to mimic Windows even when it really doesn't make sense; when the X way of doing things is vastly better. Click to focus as a default? Ugh! Windows-style cut-and-paste? An affront to humankind.
The Future of Human Evolution: Autonomy
Linux needs to fix cut and paste
Its been a while since xfree has done anything innovative at all, and with freedesktop making its rounds very quickly, this could lead to really great things for the linux desktop.
So, how do the new developments at freedesktop.org like XCB/XCL fit into this new picture? I'm hoping the exciting new code can be eventually rolled in more easily now?
"I object to doing things that computers can do." -- Olin Shivers, lispers.org
Because lord knows XFree86 has one of the dookiest logos ever!
Yes, there are many more important reasons why the merge is a positive thing, but when I first started using Linux as a teenager in 1994, I loved the X11 logo, and it definitely contributed to my perception of Linux and UNIX. Let's face it: the X Consortium's logo feels clean and elegant, but it looks hard and deadly.
CNN has a story today in which various people purport that Linux isn't ready for desktop prime time but has a window (rimshot) of opportunity to establish itself therein before the release of Longhorn in 2006.
Might this be a step in the right direction? Your fabled bluehaired grandmother doesn't want to choose between different window managers, etc. Hell, she doesn't know what a window manager is and doesn't want to know. Try to explain various incarnations of X to her and watch granny sizzle.
"If you want copy and paste, write a deamon to manage it"
...), preferably doing it the select and paste way as well as the keyboard way (which could add support for named buffers). U am not writing this, though, because it would merely add yet another standard, and besides, I don't care enough. It works for me as it is now.
I agree with that stance, though. The problem is not that there is no support, it's that there is too much support. KDE and GNOME do it differently. Some applications do it differently yet. If I select text in Mozilla and press Ctl+C, it goes to a different buffer than just selecting it. Etc...
My solution would be a module (lkm, library, daemon, I don't care) that handles it for all apps (be they console, GTK,
Please correct me if I got my facts wrong.
``One of the consequences is that if you select text and close that program then that data is gone!''
Sometimes I think the proponents of LISP-OS are right. Everything in one address space, no unnecessary copying of data or checking permissions.
If you select data, the clipboard obtains a reference to it. Close your app, the reference is still there and you can still paste the data. Replace the reference in the clipboard and your data gets garbage collected.
Please correct me if I got my facts wrong.
"If you want copy and paste, write a deamon to manage it"
I've been wondering for a long time why this hasn't happened already. How on earth can it be hard to come up with a daemon that can recieve, store and reguritate small blobs of text or binary data?!?
Best of all, it wouldn't depend on which gui you were using. It could work with all of them. It wouldn't depend on any gui being present all.
With a standard clipboard service/daemon, you could do stuff like cut in mozilla or a KDE app, and paste in commandline vi/emacs or reboot and paste into a gnome app.
My Karma: ran over your Dogma
StrawberryFrog
I was hoping somebody would come up with a thoughtful post rather than just slamming me (like the other poster did). I know that X is considered efficient, the point is that it doesn't show.
If I drag a window across the screen, my CPU load goes up to 100%. Resizing a window takes ages. uncovering prviously covered portions of a window on XFree86 sends expose events, causing redraws, which is somehow slow. Playing a movie (or any other pixel-based thing) doesn't give me a decent framerate. All this is better under other systems (BeOS, Windows) on the same hardware, using unaccelerated VESA drivers.
Thus, X is not efficient for local display. I am not saying that it is because it can display remotely. I don't know why, it's just slow.
As for remote display...it strikes me that I get a more responsive UI when using VNC than when using X. That doesn't speak in favor of X, either. I count myself lucky that there are so many good command-line apps and tools.
Please correct me if I got my facts wrong.
Cut-n-paste works under X, but I hate that Move-n-replace is ugly.
Windows:
1) Highlight new text
2) Ctl-x
3) Highlight text-to-be-replaced
4) Ctl-v
X:
1) Highlight text-to-be-replaced
2) Delete text-to-be-replaced
3) Highlight new text
4) Delete new text
5) Paste new text
I'd like to see X do something like this:
1) Highlight new text with left button
2) Keep holding left button and press right button to cut to clipboard
3) Highlight text-to-be-replaced with left button
4) Keep holding left button and press middle button to copy from clipboard
This wouldn't work for Left+Right=Middle, but Ctl-x|c|v would work for those people.
What do you think? I find move-n-replace to be very handy for text editing.
-l
Help cure AIDS, cancer, and more. Donate your unused computer time to worldcommunitygrid.org. Join Team Slashdot!
This is good news, I hope things will change to better over time.
I hope this will also be the end of the "XFree86" name/brand. Let's face it, it's not really that great name - Not couting "GNU Anything", I've always disliked names that push the "free software" or "openness" aspect, so names with "Free" in them always sound silly. The ideology should be in the heart, not the name.
Also, the whole name is a joke on something that hasn't been around for a while. I hear it's supposed to be a pun on "x-three-eight-six" - X386, which was what the project was called until 1992. I'm sure whoever came up with "XFree86" name had a good laugh with fellow developers, but now, over a decade later, this obscure fact has been completely buried in sands of time. No new users find it funny because they have no idea where it comes from - it has turned from silly and odd-looking to just plain odd-looking. Kind of like "DivX ;-)". Yawn.
"X11 Public Implementation" sounds nice and technical, however =)
If forking is one of the "bad things" that can happen to OSS, merging is one of the "good things." Multiple similar projects, each with their own advantages, merge together to make... damnit, what was that huge robot in the Power Rangers called...
I'd like to see X do something like this:
... but again, here a handy graphical app showing the stack could be handy for such ... expansive uses of the buffer).
1) Highlight new text with left button
2) Keep holding left button and press right button to cut to clipboard
3) Highlight text-to-be-replaced with left button
4) Keep holding left button and press middle button to copy from clipboard
What do you think? I find move-n-replace to be very handy for text editing.
That would be a handy enhancement.
I'd actually like to see something a little more general.
Cut-and-paste works as it is now, but make the buffer a stack (a little app could even display the buffer stack graphically)
Middle-click+number pulls that item from the stack.
Middle click pastes stack[0]
Your #4 (left and middle button) pastes stack[1] (your second cut has pushed it up and replaced stack[0]), as does middle-click+1.
middle-click+11 pastes stack[11],
middle-click+756 pastes stack[756] (if your stack is so large and you remember what you cut 756 steps ago
This returns keystrokes to more complex cut-and-paste operations, but 1) keeps basic cut-and-paste, copy-and-paste simple the way they are now, and allows for much more expandability in pasting older cuts and doing other complex c by only adding a couple of keystrokes.
The Future of Human Evolution: Autonomy
If we were stuck with a widget-based implementation, I'd have to upgrade my X server every time Xlib, GTK+, WxWindows, QT, Motif, Lesstif, etc, changed. That's stupid.
What's not stupid is using the existing protocol, which is fast (it ran well on 10 mhz SPARC machines 15 years ago!), efficient, and easy to compress for slower links.
--
Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
I have a feeling your post will be ignored, and the XFree86-heads will continue to call X's system of copy-paste "the most elegant they've ever seen," etc.
Yours is the most level-headed, rational criticism of X's copy-paste system I've ever seen, but as I've said before, X users have this bizarre fear of change and want things to stay the same for another 20 years.
XFree86 has not Merged with X.Org
[23 January 2004]
There are several news items claiming that X.Org and The XFree86 Project have merged. This is a blatant lie. The XFree86 Project remains an independent organisation, and will continue as operate as an independent organisation according to its mission statement. There has been no discussion with X.Org about any such merge, let alone any agreement to a merge.
X.Org is a vendor-sponsored organisation, formed by vendors to best suit the interests of those vendors; XFree86 is an independent volunteer organisation, with a focus on the individual. Therein lies the rub.
``No amount of speed is going to fix the resize problems. They are caused by two different processes drawing the window border and the window contents.''
It doesn't have to be that way. If the server keeps a copy of the contents and either knows how to draw the decorations or keeps a copy of them too, then it would be one process that does the drawing.
Also, I wonder if what you said relates to x86 in any way. I have heard someone say that context switches are comparitively slow on x86. Might the sluggishness come from that?
``And yes, I know this means the window borders can look different between programs, and that dreaded boogyman of "inconsistency" will be raised yet again.''
Not even necessarily. If applications call some library function to draw the borders, the library could ensure consistency.
``IMHO "sending widgets" is a mistake and will cause more communication: check out how many methods you need to create and control a Qt widget, and compare that to how many graphics calls you have to do to draw it.''
I can't imagine it costs more to send one message when a widget is created, one to attach a callback, and receive one message when the callback is triggered than it costs to send all the messages to draw the wizard, draw it differently when the mouse moves over it, yet different when it is clicked, etc. etc.
What I have in mind is something like HTML: you send the user interface once, and you only hear back from the user when they take certain actions. Now, web interfaces are a bit limited, because the server can't send events to the user, but I guess you get the idea.
Please correct me if I got my facts wrong.