Each time I look at the task of constructing a business software application, I see tremendous repetition. Each application has many facets, most of them are generic. Yet each time we appear to rebuild each facet from scratch. For example, we construct new authentication screens. We build an object model for our domain.
I think these should make for a nice extension to the existing Java 5
From an Annotation, one should be able to navigate back to the programming element that it annotates.
For example, a method annotation clearly marked with a Target
of ElementType.METHOD cannot say getAnnotatedElement().getName(),
It seems to me that many issues that come up in Java stem from the
"I don't want to have to recompile my code" argument. All kinds of
design decisions stem from it too. We end up with systems that
are written in two or more languages. What I mean is that we
usually end up with a mix of Java code, properties files, xml files
and other stuff.
Approximately in June or July of 2005, I started
weaning myself off of my powerbook G4, and learning
the Gnome environment under Ubuntu (v5.04, now v5.10).
Overall, it's been a terrific experience, and it's looking
like I've come here to settle down.
Everyone stands behind their favorite web browsers.
Firefox definitely appears to be at the forefront.
But then you come across people who prefer Camino,
for example, which is a web browser that uses the
Gecko layout engine but taylors its user interface
to fit the MacOSX mold, so to speak. Camino
indeed is pretty cool and pretty fast.
Every so often I go and read the wisdom of elharo over at cafeaulait.org.
So today I came across this specific entry discussing "humane" interfaces:
Here is a snippet from elharo's blog entry:
It has taken me a while to get into java 5 annotations.
The reason partly was how late java 5 distributions
arrived to the macosx platform (and it's still not the
Xdoclet did a very good thing: not only did they use a doclet-like mechanism
to produce xml files and other artifacts to make j2ee and web development easier,
they gave us a better design than javadoc in that the code generation is
We all know that Java 5 represents one of the most significant evolutions of the Java language since its inception. And Java 5 is taking root and sprouting at different rates in different environments. The tool makers are the rapid adopters, of course. The IT houses are obviously going to proceed more slowly, more cautiously.
One area of Swing that does not appear to be getting much attention
these days (or that may have fallen out of favor with developers)
are the elements that make up the Multiple Document Interface: JDesktopPane
I believe that there's tremendous potential in further developing
the Swing features in this space.