Talk:Xinerama

Page contents not supported in other languages.
From Wikipedia, the free encyclopedia

Skewed position[edit]

There are benefits/disadvantages of Xinerama vs RANDR. Xinerama supports multiple ASICs, RANDR supports a single ASIC. The article presents a primarly skewed position that the only redeeming quality of Xinerama is the ability to move windows.

XRandr is a client utility, not the technology[edit]

Usage should be migrated to RANDR Extension vs XRandr.

multiple wallpapers[edit]

The article had said that wallpapers would be stretched across multiple screens using Xinerama. This is dependent on the desktop environment, so I removed it. (If you're wondering, Enlightenment 17 lets you do all sorts of things with different backgrounds and Xinerama.) - Mohrr 23:36, 28 August 2007 (UTC)[reply]

I'm pretty sure the window managers that allow you to set different backgrounds for different displays under xinerama do so because they MERGE the background images you want into ONE bitmap that, when stretched, displays correctly to you the simple headed user... I could be wrong on this, but if I'm not it means you're ignorant and pushy. —Preceding unsigned comment added by 71.111.180.246 (talk) 22:36, 29 January 2008 (UTC)[reply]

Comparison with xrandr 1.2[edit]

What about xrandr 1.2 which allows to create multiple outputs on the same X11 screen? Is it the same thing as xinerama, but implemented differently? Is it better? —Preceding unsigned comment added by Eugen Dedu (talkcontribs) 16:42, 21 September 2007 (UTC)[reply]

Prounciation Tips[edit]

It would be helpful in this entry (and other tehcnology related entries which also use strange names) to provide pronunciation help. —Preceding unsigned comment added by 158.35.225.227 (talk) 15:11, 30 October 2007 (UTC)[reply]

Style[edit]

This article is written in conversational or "magazine" style. I have tagged it with {{tone}}, mainly as a reminder to myself to get back to it later. Eric Sandholm 08:36, 25 November 2007 (UTC)[reply]

It's not just the style: the whole thing is packed with personal opinion and original research. I'll come back later and delete most of it, I expect. Marnanel (talk) 20:41, 21 December 2007 (UTC)[reply]

Known Problems[edit]

Under "Known Problems", it says "Xinerama offers two overwhelming advantages over separate X screens (see next section)." There is no next section, unless it's talking about the "See Also" (but I don't think it is). Mcswell (talk) 03:01, 14 August 2008 (UTC)[reply]

Obsolete?[edit]

Going to page billed as the official website, http://sourceforge.net/projects/xinerama/, brings up a message saying that the project was discontinued in 2007. What is the replacement? Xrandr it is to be presumed, but where is that documented so that we can fix this article? Also, I notice that Xinerama is still available in the latest X.org server (1.11.4 RC 1) as of April 2012. Does it still have any redeeming uses, such as for old hardware that Xrandr doesn't support? — Preceding unsigned comment added by 67.171.24.155 (talk) 13:38, 30 April 2012 (UTC)[reply]

Unclear/contradiction in "Future" section[edit]

Keep in mind that this is an encyclopedia, and not a repository of X Windows information. People come here when they need information on a topic, but it's not right to assume that the readers here have a certain level of knowledge regarding software technologies. The following statement is either contradictory, or not fully explained:

  • "The RANDR extension exports its CRTC geometry in the Xinerama protocol, as well as through its own protocol. This conflicts with the reference X server's Xinerama implementation when multiple graphics processing units (GPUs) are used. Work is under way to correct this.[2] The 1.10 X server release removes the conflict between the Xinerama rendering multiplexer and Composite extensions.[3]"

Composite extensions are mentioned for the first time here in the middle of the article, and are not defined. Are they the RANDR extensions? If so, then this needs to be explicitly stated, and the previous statement needs to be updated from "conflicts" to "older versions conflicted", and "Work...under way" needs deleted. If the Composite extensions are different from the RANDR extensions, then there has to be some background that explains what they are. Also, "CRTC" needs to be written out the first time. Dementia13 (talk) 14:55, 22 July 2012 (UTC)[reply]

also as of now (xorg server 1.14) the most setups that use more than one gpu (or even from different manufactureres) do not support xinerama and composite together, making it virtually impossible to use stuff like compiz with xinerama setups. — Preceding unsigned comment added by 213.61.9.75 (talk) 14:16, 21 October 2013 (UTC)[reply]

External links modified[edit]

Hello fellow Wikipedians,

I have just modified one external link on Xinerama. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:

When you have finished reviewing my changes, please set the checked parameter below to true or failed to let others know (documentation at {{Sourcecheck}}).

This message was posted before February 2018. After February 2018, "External links modified" talk page sections are no longer generated or monitored by InternetArchiveBot. No special action is required regarding these talk page notices, other than regular verification using the archive tool instructions below. Editors have permission to delete these "External links modified" talk page sections if they want to de-clutter talk pages, but see the RfC before doing mass systematic removals. This message is updated dynamically through the template {{source check}} (last update: 18 January 2022).

  • If you have discovered URLs which were erroneously considered dead by the bot, you can report them with this tool.
  • If you found an error with any archives or the URLs themselves, you can fix them with this tool.

Cheers.—InternetArchiveBot (Report bug) 23:32, 20 July 2016 (UTC)[reply]