Talk:X Window System/March 2006

From Wikipedia, the free encyclopedia

Contents

[edit] Client vs Server

Someone switched client & server recently; this could be a problem with people unfamiliar with X terminology. Obviously there is a clash. In X, the server is the display, and the client is the machine running the program. This is the reverse of the more common nomenclature seen elsewhere. Should the paragraph point this out? Pagan 06:55, 31 Dec 2003 (UTC)

  • The article does exactly this in the ==Architecture== section. I wonder if that earlier mention of clients and servers is really needed. The concepts are covered well enough in the article anyway and if "network transparency" is really an important term to use, then it could be blended into the ==Architecture== section. Bevo 07:02, 31 Dec 2003 (UTC)
You have to summarize the most important information immediately, and in particular what X is and what it does, rather than burying it several paragraphs down in a subsection. Steven G. Johnson 20:44, 31 Dec 2003 (UTC)

My elaboration in the intro was quickly reverted. I'm leaving it as is for now, but don't think that my extra words were extravagent. Anyone new to X needs some direct explanation of how "server" and "client" are used. The usual impulse is to think that remote machines are the servers (not the clients), but it's reversed with respect to proving "display services" in the X model. Bevo 20:21, 1 Jan 2004 (UTC)

I've just done a chunk of rewriting. I hope the current intro makes the point clear in not too many words. It's a major point for anyone trying to get their head around X (I have seen it explode brains) and needs to be made clear in the intro. - David Gerard 17:39, Feb 12, 2004 (UTC)

When explaining why the X server is a server I've always found it useful to try to get the person to concentrate on the ephemerality of the programs involved: the X server is a single program which runs all the time (until the user logs out), while the individual client programs often run for much less time. Anyone think it might be useful to add this to the article? TheGoblin 22:20, 1 March 2006 (UTC)

[edit] Common non-Unix X servers

Does anyone use WeirdX other than its developers? I thought Exceed was obscure until I had to administer it, and even then ... - David Gerard 00:57, Feb 13, 2004 (UTC)

I've taken out the word 'commonly' in the list of X servers for Windows. The problem is that there is no X server that can be said to be "commonly" used - it's a very small market without a dominant player at all at present. I suppose we could list whatever current software we can think of ... - David Gerard 10:21, Feb 13, 2004 (UTC)

[edit] Recent history of XFree86

XFree86 is the most popular version. (MacOS X has more installations, but the X11 server is far from widely used.) Now, there's all the fun stuff with the recent history of XFree86 vs. Xouvert vs. Freedesktop.org/Keith Packard ... see [1] and particularly the summary called "Grokking the situation" posted by "Karl" (sorry, no link for the single comment). Can any of this be digested for the article? Or perhaps the XFree86 article. - David Gerard 23:21, Feb 25, 2004 (UTC)

[edit] "X Windows"

David Gerard wrote: "reread NPOV. descriptive, not prescriptive. think GNU/Linux."

That's not relevant because there actually are no entities that officially use "X Windows" (both because that's wrong and because it might actually tick off Microsoft's lawyers). The phrase may be common, but it's wrong to imply that it is somehow not incorrect, in an unofficial context -- in fact odds are that most people who use(d) it know that it's incorrect. And they generally switch to simply "X" after finding out... --Shallot 12:29, 7 Mar 2004 (UTC)
It's a common usage. It's been common since before MS Windows 3.0. That it's officially incorrect (I don't use it myself) doesn't change that.
No, but it also doesn't change the fact it's still incorrect, officially or unofficially. --Shallot
And I hardly think Microsoft's lawyers are about to swoop down upon Wikipedia for this entry - David Gerard 12:42, Mar 7, 2004 (UTC)
I didn't mean to imply that they would. --Shallot
How about "generally considered incorrect"? I really don't think it should be said in a prescriptive manner. Also, there's using it deliberately for a purpose knowing it's officially deprecated, as per the UNIX Haters' Handbook - it's not going away. - David Gerard 13:10, Mar 7, 2004 (UTC)
I've just done a new version of ==Nomenclature==. What do you think of this one? - David Gerard 13:14, Mar 7, 2004 (UTC)
That's better, I guess. Thanks. --Shallot

Should this be included with the other alternative names at the start of the article? Even though it is officially deprecated, it is, IMO, the commonest way to refer to the system in everyday speech as a first instance (before one has established what X one is talking about). --Joe Llywelyn Griffith Blakesley talk contrib 17:22, 14 February 2006 (UTC)

I don't think "X Windows" is even common anymore! My coworkers refer to it as "X" or "X11", for instance. The "X11" usage is probably being made more common by the largest Unix vendor referring to their X environment by that name. If someone said "X windows" people would think they were talking about individual windows on the screen. --FOo 17:45, 14 February 2006 (UTC)

[edit] Screen shots

What would be interesting is screenshots of various usual X Windows interfaces over the years. KDE and GNOME have screenshots. We need one for CDE (I'll get one from my Solaris 8 workstation tomorrow). But it would be really good to have the usual X interface as of 1987, 1991, etc. Earlier ones if such can be found. Any ideas where one would go looking? - David Gerard 23:46, Mar 15, 2004 (UTC)

Just added KDE, GNOME and CDE screenshots - the first two from their respective articles, the last taken by me today. They don't look perfect because the KDE and CDE shots are both 1280x1024 (5:4 aspect ratio) and the GNOME shot is 1600x1200 (4:3 aspect ratio). I don't want to change any of the screenshots for now, though, on the assumption we'll be able to get more. Must ask around some usual haunts ... - David Gerard 13:59, Mar 16, 2004 (UTC)

Some more screenshots, do with them what you will (all in the public domain):

  • DECwindows running on VMS V7.3-1 Alpha: [2] [3] Or not. Let's try a real screenshot of DECwindows: [4]. I know what the hell I'm doing...
  • A basic X session running twm etc: [5]
  • xterm-only X session: [6]

—Lady Lysiŋe Ikiŋsile | Talk 23:21, 2004 Jul 2 (UTC)

Thank you! Those DECwindows shots are spectacularly ugly. Is that the default? God help us ...
For a shot of 'basic X', I think I'll be emailing the X luminaries themselves fairly soon as I mentioned on irc to see if they have anything from the late 1980s - David Gerard 00:22, 3 Jul 2004 (UTC)
Yes, that is the default DECwindows/CDE desktop in all its fugly Motif glory :-) It's possible to change the colour scheme and fonts, but remote X-over-ssh-over-cablemodem is rather … painful, so I wasn't really inspired to spend too long making it look nice :-) I've heard noises from OpenVMS Engineering about porting KDE or GNOME, which would certainly be a nice improvement, but we'll see… —Lady Lysiŋe Ikiŋsile | Talk 00:41, 2004 Jul 3 (UTC)

[edit] Technical details

I've shifted the detailed technical architecture of X to be after the expository text. That's so people whose brains would fall out reading the technical stuff will still be able to get to the implementation and history sections first - David Gerard 19:33, May 22, 2004 (UTC)

[edit] More work needed towards Featured Article status

See WP:FAC. Specifically, the current objections are:

  • Object. The explanation, especially towards the bottom of the article, could use a lot more detail. For example, what's meant by the color packages? Also, I'd like to see more about its reception. What have critics of X said? How does it compare to MS Windows? Meelar (talk) 13:46, 24 Jun 2004 (UTC)
  • Object. No mention of Schiefler and Gettys. Nothing on X-extensions. Need to better describe the seperation of powers between components, and (just a one-liner) give the scope of the Xprotocol and Xlib. Need to at least touch on visuals, and server-side image storage. Needs a one-liner compare'n'contrast vs sunray/VNC/windows-visual-networkything. Needs a one-liner on window managers and ICCCM. Needs to cover some of X's real (past and present) and perceived problems: complexity and (supposed) expense of implementation, ageing image-model, neglected and/or costly (pre kde/gnome) widgetsets. History really should talk about the looong pause in innovation s (i.e. much the 1990s) where X's advantages were frittered away. Equally history should emphasise the latterday renaissance of X, and a one-liner for X on embedded systems (who am I to argue with Gettys). -- Finlay McWalter | Talk 02:47, 25 Jun 2004 (UTC)

I agree, it needs all that stuff.

I'm working on adding stuff at User:David Gerard/scratch - please feel free to add stuff to the article itself (preferable) or to my document if you don't feel that confident in what fragments you happen to know ;-) - David Gerard 13:10, 28 Jun 2004 (UTC)

[edit] Network transparency

As it is currently worded, the net-trans bit is far too complex, detailed and poorly worded. Making the intro stand-alone is fine, but that's not an excuse to just duplicate info. If network transparency belongs in the intro then it should be a simple mention of it, with more detail (including client/server and the apparent reversal of those roles) confined to later sections.Motor 16:50, 7 Jul 2004 (UTC)

Reverted - read the start of this very talk page. The talk page isn't write-only - David Gerard 13:15, 8 Jul 2004 (UTC)
I did read it -- and I've just read it again to ensure I haven't overlooked anything. I also read the entire article from the point of view of a casual user looking for information on X -- which you don't seem to have done. Your comments, besides being rude, are an inadequate brush off. It might be worth you taking a step back before continuing this... you needn't worry, I'm not about to revert again immediately.
Going into the details of client/server and their seeming reversal in X, in an INTRODUCTION section, is utterly pointless and confusing for anyone reading this article. If network transparency is mentioned in the introduction, then it should be at the level of "run a program on one machine, see the results on another" and how X was designed with this in mind... with no mention of client/server and especially no mention of how the roles seem to be reversed. The intro is supposed to be a short, simple overview setting out the basics. Or do you seriously think anyone coming to the article curious about X's use of the terms server and client will only read the intro and give up? This is quite apart from the fact that it is poorly worded and confusing. As it stands, the article is a bit of a mess this bit of the article is a mess despite having lots of useful info. Motor 15:55, 8 Jul 2004 (UTC)
No, it's important. I've known far too many people not to be able to get their heads around X's usage of "client" and "server" - that's why it went in the intro in the first place. Secondly, X's fully functional network transparency is pretty much its secret sauce at present - Windows and MacOS both work on better layer separation these days than hitherto, but the remote display functionality doesn't work nearly as well as it does with X, where pretty much any X client can display to any other X server with full functionality.
Anyone confused about the roles of client and server in X is not going to read the introduction and give up -- they are looking for specific information. On the other hand, someone casually looking up X is going to find themselves overloaded with irrelevant details right away. Network transparency is an important part of X... even to the extent of deserving a brief and simple mention of the capability in the introduction. I'm not arguing for the removal of such information from the article. What I am arguing for is the removal of client/server and the apparent reversal of those roles from the introduction. It serves only to confuse. Anyone interested in those kind of details can find them later in the article.Motor 17:42, 8 Jul 2004 (UTC)
This is an article in depth - to serve as a potential standalone, the intro does have to mention the odd usage and the network transparency.
Precisely, it is an in-depth article and needs a quick introduction for the more casual reader. I'm thinking of the people who are new to Linux/FreeBSD, or just someone who has heard X mentioned and wonders what it is. Technical details in the article are important, but there is simply no need to jump into discussions of client/server names/roles in an introduction. You don't get people up to speed on a subject by burdoning them with irrelevant details immediately. Motor 17:42, 8 Jul 2004 (UTC)
If you can write something shorter and snappier for the intro that does cover the subject and something clearer for the Architecture section, please do try - the current paragraph in the intro was a compromise that was accepted.
I'll have a go later.Motor 17:42, 8 Jul 2004 (UTC)
What do you think a casual reader wants? Who/what is the casual reader you are thinking of? - David Gerard 17:04, 8 Jul 2004 (UTC)
See above. Motor 17:42, 8 Jul 2004 (UTC)

[edit] History of X is the history of the politics - refs needed!

I'm still trying to get the 'History' section to a usable state without actually interviewing Jim Gettys personally. (Besides, that'd be original research.) Does anyone have good references to hand? The history of X is really the history of the industry politics and fuckups. I've dredged through a pile of news articles, personal page rants from the '90s, etc. Does anyone know of a decent writeup of the history? - David Gerard 09:58, 26 Jul 2004 (UTC)

[edit] Xaw = Project Athena?

I noticed that "Xaw" is a link to a non-existing page. I considered making it merely a redirect to Project Athena (even though it's just a stub right now), but I'm not sure if that's the correct answer. Opinions? --Joe Sewell 17:30, 11 Aug 2004 (UTC)

Xaw is actually the Athena widget set. I'm not sure it should just be a redirect. I have the book on X11R6 here, I really should write it myself some time ... or other ... - David Gerard 23:10, 11 Sep 2004 (UTC)

[edit] Color Modes

This section seems silly. Names like "DirectColor" and "PseudoColor" have no meaning to somebody reading an encyclopedia article about X. (And if you know what they mean, you probably don't need to be reminded what their names are.) If we're going to list them, we should describe what they are; otherwise this might as well be "X has 6 different foozleblarg modes: sneej, leezle, briggo, foopy, ..." - 4.16.250.40

You are entirely correct. I looked up documentation on this and couldn't find any online! I'll keep looking, but in the meantime I've commented out the color section ... if anyone is upset by that, please restore it in a way that actually explains each mode! - David Gerard 16:53, 28 Dec 2004 (UTC)

There are, IIRC, three colour models, TrueColor, PseudoColor and DirectColor. TrueColor and PseudoColor are, basically, RGB values. PseudoColor is a palette (colormap) that you can or cannot change. One of TrueColor and DirectColor is changeable, but I can't, off-hand, remember the correct one. vatine 17:36 2005-04-01

[edit] X services and protocol interactions

The five listed items at X services and protocol interactions don't really describe everything X does I think. It leaves out things like inter-client communication, authentication, and the lowly XBell. --fvw* 19:25, 2004 Dec 28 (UTC)

{{sofixit}} ;-)
I have the book on X11R6 ... packed in a box under a couple of other boxes. When I find it, the early history will get filled out in great detail, and the technical section will probably get a good kick as well. - David Gerard 18:47, 29 Dec 2004 (UTC)

[edit] more than negligible vs "significant"

I agree that "None of these systems have had more than negligible uptake" sounds like less use than "None of these systems have had a significant uptake", but on the other hand I think "[not] ... more than negligable" constitutes a rather uncomfortable double negative. Anybody have a third option? --fvw* 21:26, 2004 Dec 28 (UTC)

"none have had significant" sounds like there might be a small core of users out there. "none have had more than negligible" IMO more clearly indicates that pretty much only the developers go near them, and often not even them (e.g. Berlin dying of apathy). Only Berlin/Fresco and Y have had even Slashdot attention as X replacements that I know of; I think the sentence would start "none of these systems have had x notice". - David Gerard 18:47, 29 Dec 2004 (UTC)

[edit] Unicode support

Request: could anybody write about the current state of Unicode support in X? — Monedula 14:13, 29 Dec 2004 (UTC)

Hummmm good question! Anyone? - David Gerard 18:47, 29 Dec 2004 (UTC)
I did a quick google on "x11 unicode". Markus Krohn did Unicode fonts in 1999 [7], put them into XFree86 as of XF86 4.1 and offered them to X.org saying "hopefully they will be in X11R6.7"[8] - I presume they were. Clients (e.g. xterm) supporting Unicode had been available for a while in XF86. That last page says "hardly any software released before ~2001" supports Unicode, and that the X Logical Font Descriptor included a tag for Unicode from X11R6.4. X's support still isn't perfect - "X11 was never designed for Arabic, Syriac, Indic, and special libraries such as Pango have to be used for these scripts." http://www.cl.cam.ac.uk/~mgk25/unicode.html#x11 indicates X11R6.6 had imperfect support for Unicode.
So basically, I'm not sure when you could put 'Unicode support' as a listed feature in the 'releases' chart. But if you want to beat the above into a para in a section or subsection (somewhere), feel free :-) - David Gerard 19:39, 29 Dec 2004 (UTC)

[edit] Client-server diagram

Ta bu shi da yu pointed out on IRC that the 'Architecture' section would benefit from a diagram illustrating 'client-server' with examples. Perhaps an xterm and a web browser on the local machine, with an app client running on a remote machine. Anyone with a nice drawing package want to come up with something for nitpicking?

(Also, we could then distribute the screenshots a bit better through the article. Also need examples of what X11R1 looked like) - David Gerard 19:39, 29 Dec 2004 (UTC)

First attempt. Could anyone who can work Inkscape better than I can come up with something nice based on this? I'd also like a more generic example of an app routinely run remotely than up2date - that sprang to mind because I was running it yesterday.
               user's workstation

     keyboard       mouse        display
    +--------+       /-\      +-----------+
    |mmmmmmmm|       | |      |           |
    +--------+       +-+      |           |
         |            |       +-----------+
         |            |             | 
         v            v             ^
         |            |             | 
+----------------------------------------------+
|        |            |             |          |
|        |            |             |          |
|        |            |             |          |
|    +-----------------------------------+     |
|    |                                   |     |
|    |               X server            |     |
|    |                                   |     |
|    +-----------------------------------+     |
|        |                  |           |      |
|        ^                  ^           |      |
|        |                  |           |      |
|        v                  v           |      |
|        |                  |           |      |
|    +-------------+  +-------------+   |      |
|    |             |  |             |   |      |
|    |   X client  |  |   X client  |   |      |
|    |(web browser)|  |   (xterm)   |   |      |
|    |             |  |             |   |      |
|    +-------------+  +-------------+   |      |
|                                       |      |
+---------------------------------------|------+
                                        |
                                        ^
                                        |
                                        v
                                        |
                               network  Z
                                        |
                                        |
      +---------------------------------|----+
      |                                 |    |
      |         +-------------------------+  |
      |         |                         |  |
      |         |      X client           |  |
      |         |      (up2date)          |  |
      |         |                         |  |
      |         +-------------------------+  |
      |                                      |
      +--------------------------------------+
                 remote server
"This X server takes input from a keyboard and mouse and displaying to a screen. Clients connecting to it include a web browser and an xterm on the local machine and a system updater running on a remote server. Note that the remote application runs just as it would locally."
If you've seen the X.org diagrams on how X works, a detailed version of the above (showing all the application layers, the video card/DRI, etc) based on one of those [9] would be really nice for the technical section as well. - David Gerard 15:29, 7 Jan 2005 (UTC)

No-one drew it or suggested another remote app, so I've done one myself. Anyone wants to play with it, I can email you the SVG (Commons isn't accepting SVG uploads) or suggest changes here - David Gerard 15:49, 22 Jan 2005 (UTC)

[edit] x window on microsoft windows xp

is there a port for x window for microsoft windows xp? i found cygwin to have the ability to simulate x window - unfortunately it seems to be bound directly to the windows xp operating system i am running on my computer, rather then giving me the opportunity to connect to an x window client at some other place on the internet (i.e. my university mainframe).

thus, maybe someone can explain how the x window system on a given computer can communicate with an x window client far away?

thanks, --Abdull 00:23, 24 Jan 2005 (UTC)

The way it usually works is you go to the other computer (telnet or ssh to it or walk over to it or whatever) and get it to start a window on the server computer. The other computer is the client, so it has to ask to connect to your computer, the server; so you have to tell the remote computer to ask to connect to your computer's screen. Yes, this could do with a clearer explanation ... anyone? - David Gerard 18:16, 25 Jan 2005 (UTC)
I've added an explanation to "Architecture". Does this make sense? Does anything there need to be clearer? (I'm trying to avoid a detailed prescriptive "how-to") - David Gerard 18:36, 25 Jan 2005 (UTC)

[edit] Recent section changes

The page hit 30 kilobytes, but the technical section was still in need of great expansion (at least another 15KB), so I've spun it out as a separate article. Still in need of serious work.

I've added a section on the X user interface.

I also emailed the X.org and XFree86 mailing lists to ask for further input and missing bits. Jim Gettys is presently moving house, but when he's moved he should have some nice stuff for us :-D

Is there anything else the article needs before I take it to WP:FAC? - David Gerard 12:03, 26 Jan 2005 (UTC)

Nominated - David Gerard 01:22, 29 Jan 2005 (UTC)
Nominated - wk_muriithi Okay, that may not be the proper way of signing my name, but i hope the it does show my intention. And wonder whether there is any need to expand on X licensing history. See this for more information. [10]
If you want to support the nomination, go to WP:FAC :-) That looks like the typical Slashdot license flamewar - if there's something important to add about it, please do so - David Gerard 00:00, 31 Jan 2005 (UTC)

[edit] not necessary the right place, but

An interesting suggestion [11]

[edit] Way too much censorship by David Gerard on this topic

I have see the manner in which certain Wikipedia Administrators use their status to effectively censor the development and maturity of a topic and I see it happening here. I've reviewed the valuable contributions of a LOT of people to this topic and what happens again and again is that David Gerard removes their work and replaces it with his own work which he obviously prefers. The whole topic suffers and ends up being, in this case, a pathetic misrepresentation of the truth that should otherwise exist here. Unfortunately there's no remedy for it and Wikipedia ends up being, for purposes of this topic, a useless and, shamefully, even a misleading monologue. It isn't right and it isn't fair to the readership that something which is supposed to contain the collaborative efforts of a lot of people ends up being little more than a broken story that represents the viewpoint of someone who doesn't even do 'X' for a living. Those of us who DO do 'X' for a living, and who do very well with it BECAUSE we understand it, well, we think that our contributions deserve better than removal under a specious explanation called RV. There have been way too many removals of TRUTH about X by this person here and I regret that one person can weild so much power to have been single-handedly responsible for it. GeneMosher 22:46, 4 Apr 2005 (UTC)

I assume you're 207.189.131.233. It looks like the above should have gone to my talk page and the below to the article talk page:
I strenuously object to the way you butchered my enhancements to the X Window System. You weren't kidding when you recently asked for help with the page and said that contributions would be edited mercilessly. Why on earth would you remove mention of X supporting touchscreens, for instance? You owe us all an explanation, starting there. Your edit amounted to vandalism.
And why would you remove any mention that application specific GUI's can be built with X primitives, virtually forcing people to infer that the only kind of GUI's that can be built with X are desktops and Widget systems? That is just plain WRONG. Are you really that ignorant? You should get used to the idea that learning is a better way to spend your time than teaching with regard to this topic since you don't know what you're talking about when it comes to the X Window System.
I make a very good living by developing X apps, selling X solutions worldwide and pushing the X Window System to its limits. I know damn well what it is and what it isn't, what it can do, and what it can't do. I resent your hatchet job on my work here in explaining what X is.
There are way too many people like you at Wikipedia who think that everything they don't understand or agree with is vandalism and that the only appropriate response that they need to exercise is to revert. Shame on you. GeneMosher 20:25, 4 Apr 2005 (UTC)
Touch screens: I really doubt that touch screens are so very relevant to X in particular that they must be mentioned in the intro itself. Statistically, almost no-one uses a touch screen. Surely they're just another input device; we don't enumerate that X also works with tablets, touch pads, trackpoints, etc. This is not special to X in any way whatsoever.
"Moreover, the remote "server" does not serve up files to any local storage system or application located at the user's local display." - this does not make sense in context of its paragraph: you're switching meanings of "server" mid-paragraph.
X terminals: I'm sure you could, though examples of it being at all current common practice to build what is commonly recognised by the term "X terminal" would be good.
Common criticisms: you cut out several with no comment. Is hardware support now just dandy, and does X no longer control the display directly? "This facility has been added to X." Do you mean serving up :0 via VNC, or another new thing?
"X's network transparency requires the client application host and the remote display servers to operate in a complementary fashion." Yes, but what does that mean? (I know what it means - see LBX - but it's just dropped in there without explanation. Also, it's mixing the answer to the criticism way too closely with the criticism itself, which verges on advocacy.)
Your wording is clumsy and jargon-filled. Read this talk page and the FAC nomination. We have rank beginners here.
Finallly, remember to assume good faith, as doing so helps avoid falling into making personal attacks. - David Gerard 12:23, 6 Apr 2005 (UTC)

I'm an acquaintance of Mr. Mosher's and thought I'd take a look at the article and discussion since he mentioned it in a conversation yesterday. I see you've added a defensive, personal attack of your own here, one which is irrelevant, of course. At least Mr. Mosher was focused on X while your attack is based solely on a specious claim that you understand Wiki style better than he does. I suspect that he would gladly concede that to you. But he's right about X as far as touchscreens go - touchscreens are everywhere, even if you've not noticed. Touchscreens in restaurants and retail establishments worldwide, they're running the touchscreen software paradigm that Mr. Mosher pioneered and helped to make popular. Touchscreens are on all the latest handheld devices, such as phones and PDAs, too. It's clear that he knows X and touchscreens, and that you don't, especially as X is used in remote GUIs.

If you don't actually build touchscreen X systems that span the globe, as Mr. Mosher does, then you couldn't possibly understand the deeper implications of X's versatility as a network transparent protocol and the value which it therefore has as an abstraction layer for virtually every kind of display and input device. X and touchscreens have something in common, actually. They are both widely misunderstood and misrepresented, even by people who benefit from them. The success of a technology is very much measured by the extent to which a user can benefit from it while being allowed to be totally ignorant of the technology. The way I see it, someone who is too busy making X and touchscreens do new and exciting things took a little time to make Wikipedia a more accurate source of information about X than it was. Then someone who describes himself as a Wikiholic infers from his perception of mastery of Wikipedia style elements a license to censor the work of others. At the very least, one shouldn't justify removal of a contribution by denigrating the contributor as a rank beginner. When you choose to swing a pendulum it surely will return.Bill Cannon 13:40, 6 Apr 2005 (UTC)

I see from Eugene Mosher why Gene put a strong focus on touchscreen point of sale terminals in the X article. You're right, touch screens are everywhere. But why is this particular to X (and not to, say, the many touch screens run by Windows), so very special it belongs in the first four paragraphs of the article? Not to mention the other points.
Also, you talk at length about Gene's work and knowledge (which I've just been reading up on) - but it's hard to tell that from what appears to be an idiosyncratic edit from an apparently hit-and-run IP number, which in itself ("207.189.131.233", who is that at a glance?) carries no credibility.
If you could point out the bit that you think violates Wikipedia:No personal attacks, please do - David Gerard 16:05, 6 Apr 2005 (UTC)

SteveBaker believes that this article is about X - not about Windows. It's irrelevent whether Windows does or does not widely support touchscreens. If it's a significant fraction of X usage then it needs to be mentioned. I'd agree that it perhaps doesn't need to be in the introductory section - but it does need to be somewhere. Use X on an 'Agenda PDA' with handwriting recognition and a touch-screen and you'll appreciate that this is indeed an important facet of the X Windowing System.

I have to say that David's stance, and his response, seems a lot more reasonable to me than the complaints here. (What about touch screens is specific to X, for example, that it should go in the introduction? Maybe a subsection or sub-article on XInput, but... As for GUIs, isn't it obvious that with primitive drawing operations an application can present any interface it wants? In practice, most X apps seem to rely on one of a dozen or so GUI toolkits to do most of the work, though, and such toolkits therefore deserve the bulk of the emphasis.) Gene, it would be much easier to assess your criticisms if you confined yourself to calmly explaining what you think should go in the article that is contrary to David's edits; simply venting your frustrations about David is not persuasive. —Steven G. Johnson 06:25, September 3, 2005 (UTC)
Tell you what would be really helpful: a screen shot of X in a point of sale application. That would get the point across about the many uses of X nicely.
(And by the way, does anyone have a hardware X terminal they could take a GFDL photo of?) - David Gerard 19:36, 3 September 2005 (UTC)
We should also keep in mind, btw: when it comes to things to do with X, Gene Mosher >>> almost anyone here, particularly me, and his expertise is something Wikipedia can very much do with. I still think I'm a better copyeditor though ;-p - David Gerard 23:01, 5 September 2005 (UTC)

[edit] Synchronous/Asynchronous - Disambiguate?

At the moment, the Synchronous and Asynchronous links both take you to dismbiguation pages. I don't have enough knowledge to judge whether they should go to more relevant pages. Can someone else help here? --Finbarr Saunders 06:14, 3 September 2005 (UTC)

Those are not disambiguation pages. (A disambiguation page would be a list of links to more specific articles like Synchronous protocol etcetera.) They are simply (rather poor, from the look of them) articles on the terms, currently. —Steven G. Johnson 06:28, September 3, 2005 (UTC)

[edit] Poor paragraph in history section

I don't like this paragraph, but I don't know enough about the history to re-write it and retain accuracy. Here's the paragraph and my rewrite:

The project solved this by creating a protocol that could run local applications and was able to call on remote resources. In mid-1983 an initial port of W to Unix ran at one-fifth of its speed under V; in May 1984, Scheifler replaced the synchronous protocol of W with an asynchronous protocol and the display lists with immediate mode graphics to make X version 1. X was the first window system environment that was truly hardware and vendor independent.
The collaborators solved this by creating a protocol that could run local applications and was able to call on remote resources. They used the W code base as a starting point. By mid-1983 the initital port of W to Unix ran, but only at one-fifth of its speed under V. By May of 1984 Scheifler had replaced the synchronous protocol of W with an asynchronous protocol and the display lists with immediate mode graphics to make X version 1, the first window system environment that was truly hardware and vendor independent.

I'm making a number of assumptions, any or all of which may be wrong:

  • There was no formal project, just some collaborators, as there's no mention of one anywhere.
  • The collaborators began with a port of W to Unix, the same port they later modified into X.
  • Scheifler didn't do all the work mentioned in the one month of May ,'84.
  • X version 1 was hardware and vendor independent.

If I'm wrong about this perhaps more sentences are needed.

Regards,

--kop 19:21, 4 September 2005 (UTC)

I wrote the "early history" section using the history in the Scheifler/Gettys book listed in references as my source. I don't have it to hand any more (I gave it back to Vatine) - if someone can dig up a copy to check again, that'd be the thing to do first.
I think it was a team per se, and I'm not sure whether the 1983 port of W had anything to do with the changes that made X1. Asking on the X.org mailing list might be helpful, it would be good if someone from Wikipedia other than me emailed them ;-) - David Gerard 23:01, 5 September 2005 (UTC)

about "Competitors to X"

What is specific about Tarantella ? VNC also does provide Java applet. At list TightVNC.org package.

[edit] Links to year words on their own such as '1986'

In the edit history, David Gerard wrote:

  • restore dates (not overlinking - you're supposed to link all relevant dates

Here are my thoughts on the matter: one of the great things about Wikipedia is that it is hypertext. So a reader can easily go from one topic to another. So if the X Window article mentions network transparency, the reader can click on the link and read about 'network transparency'. That is a 'good thing'.

Since there are so many articles in wikipedia, we could go berserk and add a link to each word when such a strategy adds little value. Furthermore if we repeat a word, we could link the second instance of the word, the third instance of the word, the fourth instance of the word and so on. That may appear as a Reductio ad absurdum explanation but if we look at date links in Wikipedia we are not far off.

For example, in this article, we have four instances of the term 1986 in 4 consecutive lines. Each of those has been linked. Three lines later it is linked again. Later on in the article, it occurs again in three consecutive lines, each instance linked. It seems to me that:

  • of all the links in this article, terms such as '1986' probably come at the bottom of the list for further reading.
  • of all the reasons to repeat a link, a term being unlinked for 2 lines is probably not one of them.

I think one of the reasons why this issue comes up is because of something unrelated to hypertext. It relates to date formats and date preferences. For some reason, the mechanism for permitting date preferences to work has been implemented in the same manner as a link. So that is why many complete dates are linked. However, a year word by itself does not have the date format preference issue. You are not alone in thinking that all dates should be linked but I think that many people do not understand that this is only because of date formatting, not because of a particular Wikipedia philosophy that readers are unfulfilled in their ability to check up on date articles.

This issue comes up from time to time in various places. I have a clear opinion on it and you can, of course, take a different view to me. It is only a secondary interest of mine anyway.

You may wish to refer to the following:

Feel free to do whatever you think will improve the article. Keep up the good work. Regards. Bobblewik 15:31, 19 September 2005 (UTC)

[edit] Recent edits by 220.233.107.29

Are these recent edits really NPOV? --Joe Sewell 16:44, 28 September 2005 (UTC)

That recent edit and the attempted cleanup of it turned the 'criticisms' section into a dog's breakfast. OTOH it adds useful information. Is there a good writer in the house with time to rewrite it? - David Gerard 12:49, 3 October 2005 (UTC)
The Department of Redundant Redundancy Department went through it and removed most of it — much better now IMAO - David Gerard 13:36, 17 November 2005 (UTC)

[edit] Client Server "reversed"?

Saying that Client and server are reversed is an oversimplification that can confuse matters further. When I think of "Server" there are two elements I look at. First, my data files are frequently on another computer from the one I am at, but I access programs locally. Thus, in this sense, the "server" just holds data files. My second sense of server is similar to the sense when referring to X, but with one difference. My second sense of "server" provides the drivers for keyboard mouse and display, but also an API for allocating and accessing other system resources. This second part (other system resources) doesn't seem to be part of the X specification. Hackwrench 23:50, 21 December 2005 (UTC)

I would have just said that X running on the local computer is called the server because it waits for incomming connections from the remote programs that wish to display graphics. Ie the terms come from the underlying network model where it is the remote program that initiates the connection. Squashed sultana 10:06, 24 January 2006 (UTC)

[edit] Inward facing clients

This is my second and more pressing issue with X, which is how are clients made inward facing, which is to say not able to be connected to or connect to a server on another computer? The same question applies to the server too. Hackwrench 23:59, 21 December 2005 (UTC)

If I understand your question correctly: You can (try to) block network connections in a firewall. The server can decide to (try to) accept connections only from local peers, for example by not listening for TCP connections. SSH and other proxy software can of course fool these to some extent. --TuukkaH 23:04, 22 December 2005 (UTC)

[edit] Peer review of a related article

I submitted X Window core protocol for peer review, as I intend to candidate it for featured status. I would appreciate comments (Peer review page). - Liberatore(T) 17:56, 21 February 2006 (UTC)