Hack and / - Memories of the Way Windows Were
I'm a half-organized person. On one hand, if something of mine has a place, I can be pretty anal about making sure I put it back every time I use it. On the other hand, if something doesn't have a place, it inevitably ends up in a pile or a junk drawer. I've learned that if I want to be organized, I must give everything a home.
The same rule applies to my desktop environment. Back when I used to use Windows, I didn't have much of a choice—everything ended up stacking up on the same desktop, either maximized or at some arbitrary size. Once I started using Linux though, I discovered this interesting multiple desktop model. With Linux, I could assign windows into certain groups and then arrange each group on a particular desktop. The main downside to this much organization was that every time I opened a window, I usually needed to resize it and move it to a particular desktop. That's a lot of manual work on my part, and it wasn't long before I discovered that certain window managers supported window memory. With window memory, every window I use on a regular basis can be assigned a location, a size and a desktop.
My first exposure to window memory was with the Enlightenment window manager. Its window memory was quite easy to use and to set. All you had to do was right-click on a window, and you could check off attributes that Enlightenment would remember the next time you opened the window. In addition to having certain sets of terminals and Web browser windows open on certain desktops, I also was able to have windows always stay on top or stick across all desktops. Although it did require a little setup, by the time I was finished arranging my windows once, everything I used on a regular basis had its place on my desktops.
I stayed with Enlightenment for quite some time, even though I was eyeing this new window manager called Fluxbox as a potential replacement. It wasn't until Fluxbox added window memory, however, that I made the switch. Fluxbox's window memory worked a lot like Enlightenment's—right-click on a title bar and toggle the attributes you want to remember. As with Enlightenment, these attributes were assigned based on the window title, so if you had two windows with the same title (say, xterm, with no extra arguments), they both would take those same settings.
I used both Enlightenment and Fluxbox for years, but I kept eyeing the GNOME and KDE desktops all the cool kids were using. For me, window memory was the crucial requirement though, and it wasn't until I made the switch to using Ubuntu that I decided to give one of the “standard” desktop environments a fair shake. Out of the box, it didn't seem like Compiz had any window memory, and this was a major strike against it in my book. However, almost a year later, I still am using Compiz, and I have to credit the advanced window memory that I discovered buried in advanced Compiz settings for keeping me here.
By default, at least in Ubuntu, there are only so many settings you can tweak in Compiz. Compiz provides a tool, however, called CompizConfig Settings Manager (or ccsm) that gives you very detailed control over many different aspects of both Compiz eye-candy effects as well as a lot of the important settings for the window manager itself. The major downside to ccsm, however, is that there are almost too many options—if you don't know exactly what you are looking for, expect to spend some time digging through different categories. Even window memory settings are split between two different categories.
Ubuntu didn't install ccsm automatically for me, but I was able to install it with a quick trip to the package manager, and it should be packaged for other distributions that include Compiz. Once it is installed, you either can type ccsm in a terminal window or click System→Administration→Advanced Desktop Effects Settings. As I mentioned, the default window can be a little daunting (Figure 1) and is split into a narrow left pane that displays the categories and a larger right pane that shows all the particular settings you can configure for the category.
Everything you need to configure window memory in ccsm can be found in the Window Management category, and once you click on that category in the left pane, you drill down into a much more manageable set of options (Figure 2). For some reason, ccsm splits window memory into two different sets of options, Window Rules and Place Windows. The Window Rules options allow you to configure window attributes like stickiness and geometry, and the Place Windows options let you control the viewport and location where the window is placed.
Kyle Rankin is a systems architect; and the author of DevOps Troubleshooting, The Official Ubuntu Server Book, Knoppix Hacks, Knoppix Pocket Reference, Linux Multimedia Hacks, and Ubuntu Hacks.
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
| Dynamic DNS—an Object Lesson in Problem Solving | May 21, 2013 |
| Using Salt Stack and Vagrant for Drupal Development | May 20, 2013 |
| Making Linux and Android Get Along (It's Not as Hard as It Sounds) | May 16, 2013 |
| Drupal Is a Framework: Why Everyone Needs to Understand This | May 15, 2013 |
| Home, My Backup Data Center | May 13, 2013 |
| Non-Linux FOSS: Seashore | May 10, 2013 |
- RSS Feeds
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Using Salt Stack and Vagrant for Drupal Development
- New Products
- Validate an E-Mail Address with PHP, the Right Way
- Drupal Is a Framework: Why Everyone Needs to Understand This
- Download the Free Red Hat White Paper "Using an Open Source Framework to Catch the Bad Guy"
- A Topic for Discussion - Open Source Feature-Richness?
- Home, My Backup Data Center
- Tech Tip: Really Simple HTTP Server with Python
- Please correct the URL for Salt Stack's web site
1 hour 57 min ago - Android is Linux -- why no better inter-operation
4 hours 12 min ago - Connecting Android device to desktop Linux via USB
4 hours 41 min ago - Find new cell phone and tablet pc
5 hours 39 min ago - Epistle
7 hours 7 min ago - Automatically updating Guest Additions
8 hours 16 min ago - I like your topic on android
9 hours 3 min ago - This is the easiest tutorial
15 hours 38 min ago - Ahh, the Koolaid.
21 hours 17 min ago - git-annex assistant
1 day 3 hours ago
Enter to Win an Adafruit Pi Cobbler Breakout Kit for Raspberry Pi

It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Pi Cobbler Breakout Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- 5-21-13, Prototyping Pi Plate Kit: Philip Kirby
- Next winner announced on 5-27-13!
Free Webinar: Hadoop
How to Build an Optimal Hadoop Cluster to Store and Maintain Unlimited Amounts of Data Using Microservers
Realizing the promise of Apache® Hadoop® requires the effective deployment of compute, memory, storage and networking to achieve optimal results. With its flexibility and multitude of options, it is easy to over or under provision the server infrastructure, resulting in poor performance and high TCO. Join us for an in depth, technical discussion with industry experts from leading Hadoop and server companies who will provide insights into the key considerations for designing and deploying an optimal Hadoop cluster.
Some of key questions to be discussed are:
- What is the “typical” Hadoop cluster and what should be installed on the different machine types?
- Why should you consider the typical workload patterns when making your hardware decisions?
- Are all microservers created equal for Hadoop deployments?
- How do I plan for expansion if I require more compute, memory, storage or networking?






Comments
This really
could make setting up Kiosks easy if you set something to full screen and non closeable or able to change size
--
That which does not kill me only postpones the inevitable.