It is generally a good idea to ask the user before closing an application without saving the data. If you deploy an applet, the situation is even worse: the user may get distracted, follow some link, forget what he was doing, and close the whole browser without realizing he closed the applet too. Fortunately, it's very simple to tell the browser to display a warning.
Since generics were out and I started using them, there were always a few cases in which I couldn't make them do what I wanted. I always thought it was my problem, and that I didn't understand what was going on... Turns out: it's not. There are at least two things that are implemented in a way that break what I thought were very safe expectations.
In this post I am going to sum up things I have learned while creating a fluent API (or internal DSL) in Java. I'll talk about the search API I created for my current position: it's not a toy problem, it's a real problem, which has a significant amount of complexity. Because of that complexity, you get to see techniques and ideas that you don't usually see in toy examples.
While much have been written on checked vs unchecked exceptions, I found very little practical, down to earth, advice on how and why to use them. Here are my thoughts after years of rumination.
The second generation plug-in really made me reconsider applet as a viable deployment method (though people who are not aware of the improvements think I am crazy). For the project I am working on (http://irmis.sourceforge.net/) we decided that the user interface would be a series of applets that communicate through a Java API to a REST Web Service.
A few months ago, we had to decide which technology to use for the front end
gui of our project. We ended up
choosing Swing/Applets due to the progress that they both have done in the past
couple of years.
This is an exercise that I did more or less an year ago to learn how to use annotations.
The idea is to use the then new Java 5.0 language features to create finite state
machines with no separate configuration files. By this time, probably there are
already a million implementation around, but the excercise did help me quite a bit
to understand how annotations can be used.
One area in which Java has an advantage over typical HPC languages
(C/C++/Fortran) is its ability to use information at runtime to fine tune the
I have just
made available a zip bundle on the Jabble site in response to
some users that got stuck in the installation process: new to Jabble,
new to NetBeans, new to Java... it's tough!.