Thursday, May 03, 2007


Try changing input focus policy on XP, Vista

On every window system I've ever used, except one, you can adjust the window behavior to suit your taste. I want the keyboard input to go into the window where the mouse pointer is, "focus follows mouse." Most other people seem to want the keyboard stuck to whatever window they clicked in last. That input focus policy is called "click to focus" and it wastes my time. When I move the input focus I want nothing else to happen. Most others seem to want the window they're typing in to jump on top of everything else. That annoying behavior, coupled with click-to-focus, is called "auto-raise." It wastes my time and my screen area.

I used to ask MS-Windows users how to switch the focus policy to focus-follows-mouse. They'd gawk at me as if I were speaking a foreign language. Then a Microsoft developer explained to me why you can't do it on MS-Windows, at least through XP. Believe it or not, the window behavior was hard wired into the MS-Windows operating system kernel! How stupid is that!

But it wasn't stupid at all. Microsoft wanted to prevent anyone else from writing a window manager for their operating system, or even porting one from somewhere else. "No more Quarterdecks!" One more MSFT design decision to serve the monopoly's needs, and against the users'. And it's why they didn't get virtual desktops until fifteen years after everybody else had them.

So, can I have focus-follows-mouse on Vista? It doesn't seem like a lot to ask for, from the software company with infinite development resources, that its fanboys tell me is the usability leader.


Fast install, just copy

Some MSFT fanboy was bragging that he can install MS-Vista in 35 minutes. Of course that's not including any MSFT applications. You have to do those one at a time, or you're "stealing."

I can reproduce an entire GNU+X+Linux installation in half that time. With the applications. That's because the Free Software Foundation's version of the UNIX "cp(1)" program can copy everything on a disk partition, faithfully, in one operation. Then all you need to do is "make the drive bootable" (install a boot loader) which takes another minute or two. It's way faster than installing from scratch, and you don't have to repeat your post-install customizations.

The (1) means it's in the first chapter of the online manual, and it's part of the program's name. GNU cp(1) is part of the GNU fileutils package, standard on any "Linux" distro you'll ever see.

The first GNU+Linux distribution I really liked was H.J. Liu's "GCC Release." Its installation program was, you guessed it, GNU cp(1).

MSFT users aren't allowed to copy their systems, even if it were possible.

Wednesday, May 02, 2007


Advice to a new user, most open-source projects' web sites suck

One of my users got stuck trying to add a calendar to his new Drupal site. He has no idea what to do next, and doesn't even know how to ask.

I got your mesaage, but I didn't know where you got stuck or what you wanted me to do, so I left it for later.

One of the things you will pick up about open source is how to ask questions. You have to say exactly what you are trying to do, what you did, what you expected would happen, and what happened instead. Nobody can do much for you without that information. If you are asking about a possible bug, the maintainers need enough information to reproduce it. If you are asking "what do I do next" we need to know exactly what you're trying to do, how far you got, and what you are missing before you can proceed.

The chronic problem with open source documentation, and software documentation in general, is it is written by the only people who do not need it, and they have no idea when they left something out. When I looked at the Drupal site, for example, I needed an introductory overview and a glossary of Drupal jargon. But they jump right in to details of how to do this or that, assuming you already know what is in their heads. Sourceforge "project pages" are especially bad that way. The Apache and PostgreSQL sites show that it doesn't have to be that way.

Many open source sites open with a front page blog of "news" where the developers are talking to each other about details of what they did yesterday, and you have to "drill" and search for any instructions or even a statement of what the product does. Sometimes the developers just have poor English composition skills and they are unable to write a sentence saying what the thing is. Slashcode and PHP are like that. What the hell is Slashcode? We don't know how to answer that question in plain English, but here's how to join the developers' mailing list. That's just how things are and you have to get used to it.

You said "modules that need database configuration and installed software from drupal." As far as I know, each Drupal site on the server only needs one
database. Ours is the "default" site, and its MySQL account has the privileges called for in the install instructions. Does the calendar require a second database? Does it need to be told where the existing database is? Are you using a different one than the one I pulled in? I could not find any other third-party modules. In fact I had to create the sites/default/modules directory to put calendar in it.

> let me know if there is anything I need to do

Please turn off the HTML in your messages from Hotmail. They're really hard to read.

This page is powered by Blogger. Isn't yours?