Although I'd be tempted at reevaluate my 1440x900 browser window. Do we really need to see 170 characters wide of a text file, especially when we have a convenient wordwrap feature at the click of a mouse? Conversely, a browser or a full blown integrated development environment may need that space. Consider your habit of firing up a text editor. It's a deeply ingrained habit that we overlook. It's a fact that screen real-estate is often misused without we ever realizing it. The type of applications being used may also make a significant difference in evaluating the usefulness of such a feature. One must wonder, could I make use of the added space more efficiently? Consider that not so long ago we were all comfortably using 1024x760 and that today we have gained ~400x200 pixels without that meaning much anything else other than more space for one application screen. In today's world where resolutions of 1440x900 and higher are quickly gaining ground as mainstream, there may start to be a practical reason to tile windows in such a way. The higher the resolution the more such a feature may make sense. The usability of a window tiling practice is tied essentially two two things: Take this with a grain of salt, I'm a very happy tiling wm newbie and I admit I may be partially biased. You could try a tiling wm in a virtual machine or in a window (by using a nested X server like Xnest / Xephyr) if you ever decide to try a tiling wm, this doesn't mean you should just get rid of your current wm/de, change and cringe in pain.switching virtual desktops and windows using keyboard only is indeed much faster and convenient as soon as you get used to it.windows in a tiling wm usually don't have border decorations, this saves some screen space.a tiling wm doesn't imply all your windows are on the same virtual desktop, tiling wms can have multiple virtual desktops just like non-tiling wms.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |