Talk:X Window System
From Wikipedia, the free encyclopedia
 |
X Window System is a former featured article. Please see the links under Article milestones below for its original nomination page (for older articles, check the nomination archive) and why it was removed. | |||||||||||||||||||||||
 |
This article appeared on Wikipedia's Main Page as Today's featured article on September 3, 2005. | |||||||||||||||||||||||
|
||||||||||||||||||||||||
|
Click [show] for further details |
||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
 |
This page has been cited as a source by a media organization. The citation is in:
|
 |
This Engtech article has been selected for Version 0.5 and subsequent release versions of Wikipedia. It has been rated B-Class on the assessment scale (comments). |
 Archives |
| /March 2006 |
[edit] Quotes
Is there any reason for no quotes about X server in the article? Like Ken Thompson's
[edit] OpenVMS / DECwindows reference?
Should "Hewlett-Packard's OpenVMS operating system includes a version of X with CDE, known as DECwindows, as its standard desktop environment" be reworded? Since HP also ships HP-UX (which presumably also has X), perhaps both should be mentioned to avoid confusion, as OpenVMS and DECwindows are legacy DEC products. It just seems a little like saying "DaimlerChrysler's Plymouth Road Runner Super Bird," with the difference that HP is, in fact, maintaining and shipping legacy DEC stuff.
- Dunno. You can reword if you like, but OpenVMS is a current product. Just a very high-end one. And considerably less dead than HP-UX - David Gerard 12:16, 2 October 2006 (UTC)
[edit] Display PostScript did not become Aqua
As seen in the Wikipedia article on Display Postscript (http://en.wikipedia.org/wiki/Display_PostScript), it become Quartz. Aqua is the visual theme in OS X, not the display technology.
- Display Postscript was replaced by Quartz. Neither is a window manager. -Ahruman 15:46, 14 December 2006 (UTC)
[edit] Ununderstable introduction
Is it possible to begin this article with a sentence using the verb 'to be' so that it can answer the question that everybody wonders:
- "What is X Window System ?"
So, I think the article should begin this way:
- In computing, the X Window System (commonly X11 or X) is...
and it's up to you to continue... 16@r 22:35, 7 September 2006 (UTC)
- I tried just now and couldn't come up with anything. It is both a dessert wax and a floor topping, or a protocol for constructing such, or toolkits for such - David Gerard 12:15, 2 October 2006 (UTC)
[edit] criticisms section and factual inaccuracies/omissions
Many current implementations of X manipulate the video hardware directly. A misbehaving server can render the display unusable even if the underlying operating system continues to function, possibly requiring a reboot.
- So what? A misbehaving driver can lock up any graphical system on any OS. I don't see why this criticism is specific to X at all.
The X protocol provides no facilities for handling sound, leaving it to the operating system to provide support for audio hardware and sound playback.
- I thought MAS was part of the official standard now. Granted, nobody uses it...
The device-independence and the separation of client and server do incur an overhead.
- All decent graphics APIs are device independent, from Win32 GDI to Quartz to DirectX to OpenGL. That's kind of the point of the API. To provide device independence.
- Also, both Windows and Mac OS X operate on the same "separation of client and server" principle also. All modern GUIs do their actual output and GUI apps in separate processes. If every GUI app had direct access to the hardware (as this criticism seems to suggest) it would be a mess!
- Also, when you are running programs locally, X will use MIT-SHM and zero-copy sockets, which greatly reduces the affect of this separation.
I just think that many of these criticisms seem to have been put in by uninformed users. – Andyluciano 15:12, 17 September 2006 (UTC)
-
- Okay, I see that this last point has in fact been given treatment in the article. It needs to be clearer though. I have started editing the section, trying to be careful to do so in a neutral way. – Andyluciano 15:23, 17 September 2006 (UTC)
- The criticisms are actual problems that are or were commonly touted. I wrote that para most carefully. I suppose there could theoretically be cites for each ... The device independence one was actually unusual in the late '80s and is addressed about as well as it could be in that paragraph. MAS may be the 'standard', but there is no accepted sound transport standard that people actually use - David Gerard 10:19, 9 October 2006 (UTC)
- And I'm somewhat surprised you didn't look up the two sources of criticisms listed at the top of the section! A lot of the criticisms are old and outmoded, but still common - David Gerard 10:48, 9 October 2006 (UTC)
[edit] What is this article about?
A toolkit? A protocol? An implementation? A GUI?
- No, yes, a fair bit, not quite - David Gerard 12:08, 2 October 2006 (UTC)
- Intro rewritten as "[thing] is ..." - if that isn't clear, add wikilinks to taste - David Gerard 10:17, 9 October 2006 (UTC)
Well, I imagine over 90% of the world's computer-using population has never heard of the X Window System, so it's no wonder people are confused what this article is about. JIP | Talk 08:39, 16 October 2006 (UTC)
- To restore the honor of anonymous poster world-wide: I was not confused, but merely pointing out the inconsistency. —The preceding unsigned comment was added by 217.235.209.158 (talk) 21:47, 22 January 2007 (UTC).
[edit] Application Migration
The article asserts that applications cannot migrate. This is not in fact true. An early counter example is Gnu Emacs, which has been about to do so since the 1980's (along with replicated display). This was painful in the past due to colormaps (though if you thought ahead while building a toolkit, it wasn't difficult). It is now much easier, between client side fonts and true color displays being the norm.
A more recent example is that GTK+ applications can potentially migrate, at least if they do not use obsolete interfaces. See the "teleport" application of the GPE environment. What is still missing is both good integrated authentication and security (encryption) of the protocol to make migration "safe" to do. I'd like to see people pursue this: see my paper http://www.linuxsymposium.org/2005/view_abstract.php?content_key=102 And with the rewrite of the input section of the X Server, remoting input devices is also now becoming feasible. Oh, this paper should probably get added to the bibliography.
As I am Jim Gettys 23:57, 01-Jan-2007 (UTC), I leave it to others to verify this and edit the article.
- I tried to rephrase the Network section to reflect this, and used your paper as a source. Demian12358 22:41, 2 February 2007 (UTC)
[edit] On Portal:Free software, X Window System is currently the selected article
(2007-02-04) Just to let you know. The purpose of selecting an article is both to point readers to the article and to highlight it to potential contributors. It will remain on the portal for a week or so. The previous selected article was GIMP. Gronky 20:13, 4 February 2007 (UTC)
- The selected article box has been updated again, the new selectee is FOSDEM. Gronky 12:55, 12 February 2007 (UTC)
[edit] Broken reference link
One of your references had a broken link.
The means to an X for Linux: an interview with David Dawes from XFree86.org (Matthew Arnison, CAT TV, June 1999)
I used the latest archived page of it since I could not find the page anywhere else.
Psychless 01:38, 25 April 2007 (UTC)
[edit] What Happened to X ORG?
I got the following from a post to my local LUG (GWLUG):Both my ISP's and UT=128.83.185.40 's dns servers agree. X.org and www.x.org > > do not exist!
I got "Firefox can't find the server at www.x.org." after my attempt to connect to it at http://www.x.org/
Borgward 16:55, 4 August 2007 (UTC)
- Whois lists the domain as ok. None of the nameservers are responding so they are offline. Most likely they put all of their nameservers on the same subnet. No one should do this of course but it is quite common. Robert Brockway 17:06, 4 August 2007 (UTC)
[edit] Out of idle curiosity...
Will there ever be an X12? AnonMoos 21:44, 21 September 2007 (UTC)
[edit] Implementations
Yeahb, the picture takes a long time to load on AOL 9.0. It will be nice if we could fix that. PLEASE HELP —Preceding unsigned comment added by 209.244.187.252 (talk) 20:04, 30 December 2007 (UTC)
[edit] GAN failed
I've failed this good article nomination primarily because it lacks reliable sources woefully. Most of the sections are not referenced or referenced thoroughly, and when there are references, they are not complete. Other than that, I recommend sifting through the text and correct any grammatical, spelling, and other problems with the prose. Furthermore, some of this article may be too technical for a general audience wanting to know about X (example client-server). If this review was in error, please take this article to good article reassessment. 哦，是吗？(O-person) 03:50, 31 December 2007 (GMT)
[edit] Image X11 ssh tunnelling
The image pretends that one has only to log into another machine using ssh for having an ssh tunnel. But in the example just the call of xeyes is encrypted but not the data xeyes transferes. -- Raubsaurier (talk) 20:33, 19 January 2008 (UTC)
[edit] Fair use rationale for Image:Solaris8-cde.png
Image:Solaris8-cde.png is being used on this article. I notice the image page specifies that the image is being used under fair use but there is no explanation or rationale as to why its use in this Wikipedia article constitutes fair use. In addition to the boilerplate fair use template, you must also write out on the image description page a specific explanation or rationale for why using this image in each article is consistent with fair use.
Please go to the image description page and edit it to include a fair use rationale. Using one of the templates at Wikipedia:Fair use rationale guideline is an easy way to insure that your image is in compliance with Wikipedia policy, but remember that you must complete the template. Do not simply insert a blank template on an image page.
If there is other fair use media, consider checking that you have specified the fair use rationale on the other images used on this page. Note that any fair use images lacking such an explanation can be deleted one week after being tagged, as described on criteria for speedy deletion. If you have any questions please ask them at the Media copyright questions page. Thank you.
BetacommandBot (talk) 08:48, 21 January 2008 (UTC)
[edit] (GNOME, KDE etc.) vs. X Window System
What makes desktop environments such as GNOME and KDE different from the X Window System? --Abdull (talk) 19:58, 8 March 2008 (UTC)
- GNOME, KDE, etc., are particular applications that happen to run in X Tedickey (talk) 20:17, 8 March 2008 (UTC)
[edit] Requested fix at Talk:X_window_manager#Metacity.27s_compositor:_requested_fix
There's a factual inaccuracy in X window manager which has been noted at Talk:X_window_manager#Metacity.27s_compositor:_requested_fix for a while, which I can't fix because of WP:COI; can someone else step in, please? Marnanel (talk) 02:26, 28 April 2008 (UTC)
[edit] versioning system
Can someone explain the versioning system? There are multiple related but distinct version numbers, such as the protocol version (11), the release version (7.4), and the server version (1.4). This is so poorly defined that even Wikipedia can't get it right. For example, the KDrive article says, "As of X.Org Server version 7.1" even though the X.Org Server is currently only on version 1.4.0. It's not clear what to call the thing that the article is actually intending to refer to. (X? X Release? X System? X Window System? X11?) It's usually referred to using the notation "X11R#.#" because even if nobody knows what to call it, at least this notation lets people know what they're talking about. Is there a guide somewhere that sorts this out? Herorev (talk) 15:26, 19 May 2008 (UTC)
