Programming is like . . . ?
Of course, they both help. I almost switched my major to CS once. I was shocked to find all but one other student used a loop to compute the sum of a range of counting numbers. (I dropped most of my courses that semester, but sank too deep in depression without resigning. My university makes a big deal out of dropping every course, so that one sits on my record with an F or a D.)
As I've been building GnomeChat regularly from CVS, I've been exposed to a complex (read: common) build system of late. This has revealed other systemic cracks.
More than a year after Debian should have had an XML catalog, it still does not. Fortunately, I found a script by jamesh that solves the problem for me. It seems the Debian process provides all the bureaucracy of the U.S. Government without the service. I really hate it and I'm switching to something else as soon as I feel ready to archive $HOME and install another OS.
There are so many things that are more complex than they need to be that I don't feel like ranting about them; it would take too long.
GNOME Wishlist (cont.)
A panel applet is the wrong UI for some (most?) of the things the standard panel applets do. The inclusion of battfink is one half-step towards fixing this. (Removing the battery monitor applet is the other half.) Some other things:
- Use check menu items for the items on the panel which should appear only once.
- Be reasonable about what should appear how many times. Most of the applets should only have one instance per display or screen.
- Confine launchers to a special object on the panel. The ill-named "Quick Lounge" applet is along the correct lines.
When any problem could be fixed by fixing a lower-level problem, where does one begin? Not answering this, perhaps more than anything else, depresses me. Even when I decide to work on one problem, the deeper ones annoy me. When solving the chosen problem gets hard, the futility of doing so given the underlying problem weighs in. I'm thinking of problems like those in The UNIX-HATERS Handbook, and also a number of social problems.
Wanting to solve problems instead of wanting to get paid for solving problems is one of my problems. Though I've tutored a little in recent years, I haven't charged for it in more than 6 years.
Icons in the tray are supposed to be handled much like any other window. You set your hints, and then either you take what you're given or you go away. E.g.:
- You ask for a 1x1 space. You get a 16x16. Scale up.
- You ask for a 128x128 space. You get a 24x24. Scale down.
- You ask for a 1x128 space. You get a 32x32.
- Take a little bit of time to look at the platforms that has been using such a thing for a few years (Windows, MacOS) and see if you can get it to sink in that you should use something sqaure.
- Realize that if you don't use something square, your design is probably wrong.
Windows appearing outside of the tray have been reported. Since only the tray is supposed to map these window and only after they are embedded, someone is violating the spec. Is the tray mapping before embedding? Is an app attempting to map its tray icon? Dunno.