May be I am a little late, so I found the Mozilla Developer Center only today. Seems to be a veeery usefull resource. For web development I used SELFHTML the most until now. For JavaScript the Mozilla site could be even better.

Martin has posted a nice entry in his blog “programming kung fu” about eclipse hot keys.

I think the most important key is ctrl-shift-L which gives you a list of all shortcuts. A shortcut I often can not remember, when I am searching for a specific one. So it is also one used very rarley.

Beyond the common ctrl-C/X/V/S/W and the ones mentioned in the article or the comments, the shortcuts I use most are the following:

alt-up/down - For moving the actual line / all marked lines up / down one line.

alt-shift-up/down - Duplicate the actual line / all marked. This one is very cool in combination with the one above, when hacking configuration with many similar keys.

ctrl-D - For deleting the actual line. Very useful when you have used the two above too much.

Das muss ich doch nochmal kurz verkünden: Die Projektarbeit von Nils und Jörg ist fast fertig. Die Inhalte sind endlich alle zu Papier bzw. Tastatur gebracht und es müssen nur noch Korrekturen einfliessen. War ein hartes und ätzend langwieriges Stück Arbeit und des öfteren der Grund, warum hier so wenig steht.

Wenn das “160(+)-Seiten-Ungetüm” abgegeben ist, müssen wir nur noch einen Vortrag machen, mal eben ne Diplomarbeit aus dem Ärmel schütteln und fix das Kolloqium bestehen. Dann sind wir fertig.

Aber bestimmt nicht mehr vor meiner Hochzeit.

This mornig I had to think a little about how to configure a particular system. Some parts of the system use different implementations of specific modules defined by interfaces. If there should be used a special implementation among the standard one, it is configured in a properties file. The value is the full qualified name of the implementing class, which is loaded and instanciated via reflection. Because we use Java and Java is a statically typed language, we have to cast the instance from Object to the interface.

This is a common pattern, I think. It is used by log4j for example.

Because we use a property configuration, which is not typed and validated against anything, the implementations can be configured as needed.

The opposite may be an XML configuration, which is validated against a schema. If we would use this and wanted to use it continuous for all modules, we had to design an universal schema for all modules or one for every implementation, which is imported into the main configuration.

It is very clear which one is faster and improves development speed. I have seen this pattern with dynamic configurations (even with an xml like syntax) several times in different Java applications and frameworks, but I just remember one with a statically typed, xml based configuration. But even this one used a universal, not really typed schema for the dynamic modules. So I think it’s just the same.

Applications, developed in a statically typed language, but dynamically typed. As I think about it, a common error in those applications are wrong configurations, mostly these little typos you do not find very fast and drive you crazy. Much like in dynamic languages. But would a strong and statically typed configuration, validated against some genius schemas, be worth the effort?

Just a little a thought, that crossed my mind.

Die hier sind schneller als der Pony-Express:

Thanks for visiting RealVNC recently and downloading Free Edition VNC.

Die haben nur eine Woche Verspätung. Für ein EDV-System, garnicht mal schlecht ...