I’ve tried several ways to keep track of my mouse pointer. It’s kind of hard from time to time. Adding more than one monitor does not help at all!
Recently a colleague gave me the tip to make the mouse pointer black… and larger. I tried this and found that the mouse pointer was much easier to spot. No surprise there, really. After all, white on white tends to become a bit hard to keep track of, tiny silhouette outline or not.
I was told how to do this in Windows (Control Panel > Mouse > Pointer, but that’s another story).
In Gnome (I’m running Ubuntu 8.10) you do it in the System > Preferences > Appearance dialog (see below). In my version of Window’s there’s no settings under Appearance > Mouse.
Next you click the “Customize” button:
In the new dialog select the “Pointer”-tab and select the color of pointer you want. In order to resize it, see the “size slider” below the list of pointers (there seems to be three distinct sizes to choose from).
Click “Close” once you’re done, and voila, you have a new and much easier to spot mouse pointer!
One of the more deadly things you can do is to act normally in an extreme situation.
This goes for extreme weather situations, being taken hostage, living on a planet that may be dying, etc. etc. Basically, I believe panic will make you react in a predefined way while keeping your cool will make you react according to the situation. A few times panic might save you (running from a violent person instead of trying to talk sense to them) while in most cases not panicking will probably get the best result.
Interesting thought: aren’t we presented with “extreme” situations now and then, and once we’ve managed through them, they’re not extreme anymore. Take for instance, first day at school, first love, first day as a parent, first day of retirement, or being a victim of a crime, being in a car accident, or other accident, being falsely accused, getting fired and being unemployed, etc. etc, there are a bus load of extreme situations out there.
So, the thing is to keep from getting pissed at your boss for firing you, and trying to get a good letter of recommendation out of it (after all, who say’s you’re getting kicked cause your boss dislikes you?) Or to stop being a kid yourself once your little ones are on their way, or to get out of that car wreck, and try to get everyone else in it along, before something worse than a roll and a spin happens.
So, it’s all about controlling panic then… or? Hmmm…
Humans are in fact not that different to other species. We make a little bit more complex sounds and our territorial behavior is a bit more involved, but to say we’re the crown of creation is rather self-involved. The most that can be said about mankind’s standing in the family of species is that we’re the black sheep, or the obnoxious kid sibling everybody has to put up with, or mom and pop will give them a hairy eyeball.
Microsoft Windows is the unique case that disproves Darwin’s theories of natural evolution and survival of the fittest while at the same time supplying no support for the main theory opposing Darwinism, the so called Intelligent Design Theory. It is obvious the existence of a system such as Microsoft Windows is the work of a deity. In this case an inherently chaotic and evil one; we usually refer to it as the Devil.
Mmm… wonder if I may be able to do a thesis on that, just wonder if it should be in the religion or computer science department… 😀
Looking around for an easy way to create applications with text GUIs for running over SSH terminals I came across CHARVA. CHARVA’s API copies Swings, it unfortunately is not built on top of Swing but is a copy of Swing. This forces implementers to import classes in the charva.awt and charvax.swing packages instead of traditional awt and swing classes. However, the result is rather nice, at least if you’re looking to run applications off a server on a simple Point-of-Sale or Point-of-Service (POS) terminal that may not even support graphics.
In my case I’m looking into making a simple app that I can use to keep track of passwords, both when I’m at home (regular swing) and when I’m away (at work or similar) and only able to access the application via SSH (CHARVA).
I’ve just had the rather unsettling experience of trying to deploy a new jar file (one I recompiled after some changes). This file were to be deployed on a rather old set up of Java 1.4.2. On first try everything broke with the classic “Unsupported major.minor version 50.0”.
So I went back to the drawing board. I installed java 1.4, and made sure my development Tomcat was running it. Then I did some research and found out how to make Eclipse compile 1.4 compliant code. I started and I got the same error still.
Once I figured out what was wrong I realized I was an idiot (Doh!). The error I’ve gotten wasn’t for any file part of the jar I was trying to deploy but for “index_jsp”. The thing is my Tomcat compiled my JSP:s into class files and never looked at them again until they were changed. I am sure there’s several ways to solve the problem, I just went and deleted the files in the “work”-directory (those pertaining to my Context).
Now over to how to make Eclipse code projects to a certain Java version.
There are two values you will want to keep track of. The source version and the target version. The source version tells what version your source code is written in. Whereas the target version tells what version of Java you want your class files in.
If for instance you have a project written in Java 1.4 source style, but you have to run it on a Java 5 you’d set the source version to 1.4 and the target to 1.5. You are now compiling Java 1.4 source into Java 5 class files. Unfortunately you’re not able to do the opposite, compile Java 5 source code into Java 1.4 class files. This is probably due to API incompatibilities, Java 5 has a larger API than Java 1.4.
Now, in Eclipse you have two settings in three places that controls the source and target versions of your compilations. Under Window->Preferences->Java->Compiler (Eclipse 3.4) you’re able to set the versions for the whole IDE.
When you create a new project you’re able to determine what version of Java (source and target you want) and right clicking on a project and choosing Properties->Java Compiler, you have the same dialog as before.
You set the target level in the select box “Compiler compliance level”, and optionally by unchecking the “Use default compliance settings” you’re able to change the target (“Generated .class files compatibility”) and source respectively.
If you experience other problems you may want to “clean” your project(s). Cleaning a project means all compiled files are removed and all source files are recompiled (something the IDE will do by itself when you change compilation versions, but if you want to be sure, you can do it manually). This is done by choosing Project->Clean. In the dialog you can chose to clean all projects or just those you select.