Slashdot Mirror


Window Managers for High Resolution Displays?

cfish asks: "Recently, I was told by a manager at a major monitor maker that CRTs are phasing out. I have a very weak eye and I read text at 1024x768 on a 21" monitor, sitting 2 feet away. Each alphabet is about 1/4" tall. What makes me panic is the fact that LCDs have fixed resolution and they are simply too small for me to read icons and widget text, like Microsoft's. This is a great chance for Linux to get a head start in a certain market: older folks and those who have eye strain problems. Generally speaking, not many people can read Microsoft's widget text on a 150dpi display, which may explain why no one buys them even that they are available. Imagine how frustrating it could be for medical display (x-rays), cad, image editing to have a high resolution realistic image but cannot read the menu and text. If someone can come up with a Window manager to beat MS on 200dpi displays, no doubt this will capture a strong following in image related applications. I have read about these debates 5 years ago. What has been done about it?"

3 of 382 comments (clear)

  1. Re:Windows by utexaspunk · · Score: 0, Troll

    you moron, you didn't understand the question at all. he was talking about the widgets. the font size gets bigger, but the all the widgets stay the same size, often screwing up the text, too. ever notice how if you use windows at ANYTHING other than the normal font sizes it looks EXTREMELY shitty? I just switched mine to large text @ 1600x1200- sure, the text is readable, but now all the widgets are off-baseline and still tiny. MacOS X has got everyone beat on this with Quartz

  2. Slashdot has turned into a comedy sight... by Beatlebum · · Score: 0, Troll

    The same guys that are debating privacy/encryption and other complicated issues can't even figure out how to change font size.

  3. Re:Workaround for you... by Webmonger · · Score: 0, Troll

    I dunno. I didn't compare Windows developers to Linux developers.

    The Windows GUI hands a lot of control to the developer. They can't be trusted with that power. They do stupid things like writing GUIs with system privileges.

    There are big differences between the output of a paid Windows development team and a volunteer open-source developer, but they're not a different species. They may even be the same person at work and at play.

    In any case, I'm saying a well-designed API is hard to use wrong and easy to use right.