Java – how do I actually use the swing application framework?

I want to learn how to use swing application framework effectively Most of the examples I've found are blog entries that just explain how to extend singleframeapplication and override its startup method, but this is about it Sun's article is almost two years old. Like the project's own introduction, it has shown some evolution since then

Are there any up-to-date and thorough tutorials / howto available anywhere? Of course there is Javadoc, but it's hard to get a big picture from there Any pointers would be appreciated

Update: I realized that there was a mailing list archive on the project website Although a little clumsy (compared with stackoverflow), it seems quite active Unfortunately, there is no real tutorial anywhere Information is scattered here and there

Update 2: let me be clear – I'm not using swing itself, I'm talking about its application framework, which should simplify the application lifecycle (start, exit and anything that happens between them), action management, etc. - that's what most swing applications need Such a framework is the standard part of Java, which is very cool The only problem is learning how to use it

Update 3: interestingly, only the current status and future of JSR 296 were discussed in the project forum Soon: the current version 1.03 is considered quite available, but the API is unstable and the final version in Java 7 The package name will also change, so Java 7 will not destroy the current application on saf

Update 4: Karsten lentzsch said on the above Forum: "I doubt it can be included in Java 7, and I will vote against it." I would rather not question the sincerity of this great guru. Of course, it is wise not to let anything defective enter the core JDK, but frankly, this is a strange situation - he is the author of jgoodies swing suite, which is a part of business competitor JSR 296. He is sitting on the committee to decide whether this JSR is included in standard Java It is the same as JSR 295 beans binding written before

Given the current state of SAF, I think the best solution is to wrap the current implementation into the "home-made software" framework, so that the existing API can be changed

Solution

First of all, my personal suggestion is not to use the latest version of SAF. It is more like "refactoring in progress" (and this version has not evolved for 6 months)

I prefer version "1.03", which is not perfect, but more stable and usable (I mean applications in real life)

Indeed, saf has few resources I remember following this path:

>Read a @ L_ 404_ 6 @ about it; This gives a good picture of it > use it and read Javadoc when needed > sometimes look at the source code to alleviate the shortcomings of Javadoc

The mailing list is not active at present (but the real traffic has restarted a little since the beginning of this year, but I haven't seen sun representatives since August or September 2008!)

Last year, after about a year of SAF practice, I delivered a speech at jazoo in 2008. You can find the slides of on my blog The skills I collected when using the framework

Sometimes I have to add some points, because many problems are long-term (some are unimportant to me, others are blocked)

I remember seeing (not attending) another speech on saf practice at a meeting in Sweden. Sorry, I don't remember more details It's also interesting

It almost exists (as far as I know)