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?"
Ya know, LCDs don't *have* to be run at their native resolution all the time. You are free to set an LCD to run at 640x480, 800x600, or whatever you like. The nice thing about a 200dpi LCD display is that you can run it lower than the native resolution and still get a great looking picture. Another thing...Windows can be set to a higher "dpi" than its traditional 96. This will increase the font size for EVERYTHING. Just go to Display Properties > Settings > Advanced, and select the "DPI" from the General tab that you wish to use. Beware, as some applications may not look right because they weren't designed to use that resolution. FP!
Homestarrunner.net -- It's Dot Com!
I might be missing the point completely here, but surely for accessibility purposes (i.e. if you have crap vision), the resolution doesn't matter. All you have to do is change the default font size in your window manager... it's hardly revolutionary :S
They make full-screen monitor magnifiers for people with vision problems. Take a look here for starters.
Karma: Food Fight (Mostly affected by Date Plate).
..and people are working on it. Seek KDE and I found this project on Sourceforge. I assume that you already turn on "large fonts" in Windows. Windows can theoretcally support font sizes that are larger, but the problem is that most applications aren't designed with varying font sizes in mind. Some applications already look messed up with the dpi setting that "large fonts" uses. It's a matter of poor UI design. People use fixed-size images in their programs and expect them to line up.
Here at the hospital we use a high-resolution radiograph system. The text IN the system itself is fine; however, the OS text from win2k is extremely small.
Luckily, all of these systems only have the imaging system and the OS installed... so the only program that ever runs is the radiograph system.
Isn't this just a setting, however? I figured the admins were just idiots and didn't bump up the text size.
Davak
Every OS makes use of TrueType fonts.
IIRC, essentially the entire UI is vector graphics (being done by OpenGL and all), so Apple might have this covered.
You do not recall correctly. The Aqua gui is entirely pixmap based, the widgets aren't even scalable (which has caused the safari team some grief).
I know local conputer shops that have already phased out CRTs because the shipping is so much cheaper that it balances out. They also save much needed floorspace in their inventories.
One of the things that ships with Windows is the magnifier accessibility applet - for people with poor vision. it turns the top of the screen into a magnified area of the screen under the mouse, so you can have the screen estate nicely laid out, and be still able to read any part of it you want to. (BTW I'm using XP, but I think its available on the other OS versions)
:-)
/. after all.
You can change its settings, make it follow text editing cursor, and keyboard focus, (its quite cool actually, I may bump my resolution down to 1600x1200 on my 17" monitor and use it
Not only that, when you first start it up, you get a dialog box offering to take you to see more poor-vision tools on the web.
10/10 for Microsoft on the accesibility features? na, this is
Once zooming is activated in the universal access control panel of Mac OS X, pressing apple-option-+ zooms in, while preserving clarity.
Also, the idea of senior citizens who have trouble seeing using linux is extremely laughable. I regularly help such people solve simple problems like ejecting a disk. I seriously doubt most would be able to do anything useful in linux at all.
Using XP, but it's almost the same on 2000 and NT:
And you're done. This functionality has been in Windows for, I don't know, a decade or more. Generally, commercial OSs, whether Windows or Solaris or MacOS, leave free ones standing when it comes to accessibility. The reason is that they want to sell to corporates, and corporates have to comply with legislation like ADA. Free software authors generally don't have that incentive.
You should check out Opera's browser. It has a magnifying feature that can magnify any webpage from 20% to 1000%. Anytime I can't see what's going on, I just bump it up and I can see again. It works pretty smooth too, on graphics, text, even flash.
It is true that LCDs actually have a fixed resolution, but you can actually adjust them. When this happens, the monitor makes two or more pixels represent one. However, this is a huge disadvantage, because of the fact that resolutions usually don't divide into each other evenly, there are some regions that are duped, some that are not, making a really wavy image that is readable, but still rather unclear.
XFree can handle screen DPI so that all other applications can use it productively. That's a pretty good base to build on. And no one yell "X sucks" now. Any framework that provides that measure would be suitable!
Now that gives you a way to make measurements unrelated to screen resolution. Handling fonts becomes ridiculously easy, and from my experience it's taken into account quite nicely. Just try fiddling with the physical screen measurements in your XF86Config.
Now, where KDE comes in is the part when we aren't talking about pure text anymore. KDE has at least the ability to handle icons created from SVG source which scale "lossless" and could also be tailored to use the resolution-independent measures.
Fight hunger. Filet a politician and send him to a 3rd world country of your choice.
Here's a tip : Use Opera for your web browser. Even in Windows, you get beautifully magnified text/graphics when you use the in-built zoom. -James.
Really, this is not a big problem.. I would be surprised if you can't quite easily overcome the problem of your high resolution display. I dare say, easier than you can in linux.
Yeah, Bill Windows Luser again tries to use his brain. Next time, check the facts...
XF86 detects display dpi automatically. (Though you can still override the dpi value if something goes wrong...)
_ALL_ GTK+ apps scale their fonts properly _by default_. This is a major design feature of the GTK+ toolkit. Not like in Windows, where every second app stays at a 8-pixel bitmap font and ignores user preferences happily. I imagine the situation is similar on the Qt side.
What they have is a fixed number of pixels. The entirely unsatisfactory solution to this dilemma is to merely drive it at an inferior resolution. It'll look like garbage, but it'll be bigger. A much better solution, however, is to drive it at an even divisor of the number of pixels, which will give you clean output. For example, a 1600x1200 LCD could be driven at 800x600; the letters will be nice and crisp, and will be four times larger.
Increase your window manger's font size, increase the font size of any toolkits. For example, I once made a .gtkrc with HUGE fonts that are readable from a few feet away. (This is because I was displaying things on a television.)
This is pretty much a no-brainer. You do not need a special window manager, and at any rate, it's the toolkits that handle application widgets, not the WM.
1.)Hold Ctrl down on the keyboard
2.)Roll the mouse wheel forward to zoom
3.)Sit back an read
I had the same problem - my wonderful Thinkpad A22p has a 1600x1200 LCD at 15" (that's 133 dpi) and the default fonts are almost unreadable. This is what's needed - and it will change fonts globally.
/etc/X11/Xresources to
1)In XF86Config-4, add the DisplaySize option like this:
Section "Monitor"
Identifier "Generic|Generic Laptop Display Panel 1600x1200"
VendorName "Generic"
ModelName "Unknown"
#Sort out tiny fonts - these are width, height in mm
DisplaySize 304 228
2)Change the line in
Xft.dpi: 133
where 133 is the value of xdpyinfo | grep resolution.
Then, restart X and the xfont server (xfs), and log back into KDE. The fonts should all look better (and larger). Hope that helps.
Richard
ViewSonic has a 200 DPI 22.2" display, 3840x2400.d _vp2290b.htm )
(http://www.viewsonic.com/products/lc
And Dell makes the Inspiron 8500 notebook with a 1920x1200 screen--that's 150 dpi, folks. That's the same number of pixels as the 23" Apple HD Cinema Display. The future is coming and it's going to be high-res flat panels. Might as well start planning now.
In other news (don't feel like starting a whole other post) LCDs look bad at their non-native resolution, and most divide into non-standard screens: 1280x1024/2 = 640x512--who supports that? Or 1024x768 goes to 512x384--that's the same res as a Mac Classic, not even VGA (640x480). We need to make out software smart enough to work in all these scenarios. I'd love to have one of those ViewSonics (they're $7500, btw) but a 640x480 pic on the Web will be the size of a business card. OTOH, I'd *pay* to spend some time working in Illustrator on one--assuming Adobe could grow the pallets to make them visible.
Dear Slashdot: next time you want to mess with the site, add a rich-text editor for comments.
Cliff, If you use Mozilla as your browser (as I do in Red Hat 8.0), you can simply type in Ctrl+ as many times to change the font size on the fly. Or type Ctrl- to reduce the font. I use this all the time and it suits me very well. Therefore, Linux already seems to be ahead of the curve here. Of course, this is not a generic fix, but a browser level fix, but thats where one tends to do most of one's reading (I guess). Hope this helps. cheers
...and I do it under Linux.
I have a classic, wonderful monitor: an SGI 1600sw, with 1600x1024 resolution. I only run it in its native resolution. My fonts are large and beautiful.
0) Use TrueType fonts.
Make sure your X11 setup is all correct for scaled fonts, especially TrueType fonts, and then get some good ones. Go everywhere and make sure you are using your good TrueType fonts. My GNOME preference fonts are all TrueType, plus my web browsers. The GNOME 2.x dialog for this is Applications / Desktop Preferences / Font. If you have an LCD flat panel display, be sure to check the box that says "Subpixel smoothing (LCDs)". For a CRT monitor, I suggest you check the "Best shapes" box.
1) Grow your fonts.
Go into XF86Config (or, in Debian, XF86Config-4 if you are using a recent version of XFree86). Find the part where it describes the monitor. There should be a DisplaySize line describing how big your monitor is, in millimeters. If the line is not there, search the web for specs on your monitor, or just measure it, and add the DisplaySize line. For the 1600sw:
DisplaySize 369.4 236.4
Now we want to lie to X11 about the size of our monitor, and say it's smaller than it really is. I want fonts 150% the usual size, so I multiply each number by 100/150 (i.e. 2/3 or 0.66666).
DisplaySize 246.3 157.6 # lie to get 150% font zoom (165 dpi)
# DisplaySize 369.4 236.4 # correct: 1600x1024 at 110dpi
Note that I like to leave comments about what the heck I'm doing here and why.
Now, X11 thinks my monitor is 165 DPI, instead of the real 110 DPI. When an application asks X11 to display 12 point text, X11 scales the TrueType font accordingly. I get automatic, across-the-board font zoom.
Peeve: there ought to be an X11 setting for this. You ought to be able to specify a zoom level, say 150%, and have X11 honor it without bastardizing the monitor size. If I can't have a zoom level setting, at least let us specify the DPI as a DPI number, instead of as the number of millimeters our monitors are!
2) Grow your web fonts too
Now your other big problem will be web sites that hard-code sizes. Even with 150% zoom, you really don't want 6-point fonts. The "minimum font size" setting in Mozilla hasn't worked well for me when I tried it in the past. You can specify a horrid large font size in the prefs, but then when you print a page, it prints huge too!
The solution is to use a cascading style sheet (.css) file. Go to your ~/.mozilla/default/<something>/chrome directory, and edit a file called userContent.css. (Be sure to check out the example files that Mozilla leaves there for you, while you are there!)
Add these lines to userContent.css and save:
@media screen {
* {
font-size: 28px !important;
line-height: 30px !important;
}
}
These lines mean: only for display on the screen (not while printing!), set the font size to 28 pixels height, and the line height to 30 pixels height. The "!important" part means you insist, even if the web page specifies a smaller size.
Now revel in the easier-to-read text.
You still have problems. Web designers who lay out pages with tiny fonts didn't expect their fonts to be forced huge, so the page won't look right; it might look downright ugly. And this fix does nothing to help when the webmaster specified a column width in pixels, so you may find a column that was intended to be over half your screen width is actually only three inches wide! (Thus you have big, easy-to-read text in a skinny very tall column, and you have to scroll the page a lot to read it.)
You also may find some text-entry forms that are 6 points tall, but the text you are typing into them is still huge, so you can't really read it. I ought to figure out what preference sets minimum text-entry box size.
Anyone with more useful tips, please share them!
P.S. Slashdot would not let me include the lines from my config files
lf(1): it's like ls(1) but sorts filenames by extension, tersely