This is the second blog in a series on architecting
applications. In the first href="http://weblogs.java.net/blog/zixle/archive/2006/01/architecting_ap.html">blog I discussed the application
I'm going to develop, how it would be architected, and briefly
went over the model.
While in Russia (see Shannon's blog) I wrote a long blog on undo, actions and various other things. At the time I felt this a bit long for a blog and so it languishes in my unposted blog queue (with many others, but that's a different story).
blog I explained how to customize the visual feedback
provided by JPasswordField. Unfortunately the first option I detailed,
specifying a character that takes no space, had a bug in it. This blog
discusses the bug and how to fix it.
We've been gathering input from customers on various features they
would like to see us implement. At such a meeting one customer
requested a variation of JPasswordField. I figured it
would be interesting to blog on how you could modify JPasswordField to
vary the level of feedback it gives you.
In my last two blogs I've covered various aspects of Actions. I had
originally wanted to write about the changes to Actions in 1.6 but
felt the background would make interesting blogs. I promise this is
the last blog on Actions for a while;)
In 1.6 we've overhauled Actions adding new features and fixing a
handful of annoying bugs.
In my last blog I delved into why one might use
Actions. In this article I'm going to cover how Swing's components
support Actions. Eventually I'll wind up in why you should know about
Actions can be dynamically changed.
I originally intended to blog on the usefullness of WeakReferences for
client apps. This was to be motivated by the internals of Actions and
why Swing internally needs to use a WeakReference to support
Actions. In writing that blog I ended up spending more time describing
Actions that I've decided to split it into two blogs.
In my last blog I went over how we were able to make Ocean perform as well, and in some cases better than Steel.
One of the biggest features we did in 1.5 was revamping the java look and feel by providing a new theme (OceanTheme). Love it or hate it, Ocean requires a bit more graphics support than the line primitives of yore. In order to make Ocean the default we needed to make sure performance was in line with the old theme (Steel).
I was tempted to name this blog
Tricks and Subtleties of generics but I figured more people would be interested in providing feedback on mustang sorting. Anyway...
One of the bigger features we've added to Swing for the 1.6 release is sorting and filtering for JTable. The sorting and filtering API were designed in a way so that it is not tied specifically to JTable.