Skip to main content

The alternative Swing frameworks

Posted by alexfromsun on November 16, 2009 at 6:34 AM PST

Hello Swing community

While the SAF project is on hold, the Swing team welcomes the active development of the alternative implementations of the Swing framework. I found a few promising projects and put the links to them at the SAF project main page:

and don't forget about the mature Netbeans Platform

I am happy to promote those projects. If there is anything I can help with,
please don't hesitate to contact with me, I'd be glad to get in touch with the development teams.

Let me know if there are more good projects to be added in this list.

Thanks and keep up the good work!

alexp

Related Topics >>

Comments

There's only one Swing framework...

... worth the effort of learning it, and it's called The NetBeans Platform. I've been there, seen that (during several years) and (with all respect) all I can say is that learning NetBeans RCP is the Best Thing I've done for building spiffy Swing applications. Cheers, Antonio

Netbeans is too heavyweight

Netbeans is too heavyweight for some apps. My main issue is what do want to incorporate in SAF? Docking (Jide, InfoNode, Netbeans, ...), saving properties, etc. I'd run a poll first on what people would like to see in a simple SAF. Regards

"Netbeans is too heavyweight for some apps."

"Netbeans is too heavyweight for some apps." That's a myth. It will continue to exist for as long as people continue saying it. The fact of the matter is that the NetBeans Platform is as heavyweight as you want it to be. That's because it is modular. You get to choose what you want/need. So, if it's "too heavyweight", you haven't grasped the central concept of modularity.

It's not a myth...

... but simply untrue. A NetBeans RCP application can be as small as 5Mb, featuring the major components of the Platform (yes, including all the Windowing System, Options Panel, etc). And, well, I don't think it's that difficult at all. Maybe I should blog a little bit on how to use the NB RCP for simple Swing applications, right? Cheers, Antonio

Netbeans Platform

Hello Antonio

I added a link to the Netbeans Platform, thanks for the pointer!

It will be really helpful if you write a blog about using it for a simple Swing application

Thanks

alexp

I will

Ok. I will then start a series of blog entries, probably during december. I'll let you all know when those are ready. Cheers, Antonio.

Netbeans Platform Tutorial

I find most of the tutorials..use the netbeans wizard which further hinders the understanding of the platform. Please try and make the tutorials IDE agnostic..so that we can use it on IDEA & Eclipse too.

Regards,
Pavan

A good way to have a project

A good way to have a project IDE-independent is to work with Maven. NetBeans 6.7/6.8 has got very good support for Maven, and IDEA seems to be the same (in contrast, I've got a lot of troubles in trying to open my Maven projects with Eclipse, but with a bit of work is for sure doable). I've posted the first of a series of tutorials that are focused about some projects of mine, but they use the Platform and at least half of that might be useful for people generically interested in the Platform. These tutorials are both textual and screencast - the first is linked from here: http://netbeans.dzone.com/videos/screencast-maven-and-netbeans.

Yeah, that would be really

Yeah, that would be really nice.

Rather than being "too

Rather than being "too heavyweight", the issue I have with the NBP is that I'm not smart enough to completely understand it. This may put me on the dimmer side, but perhaps it just means I like to _really_ understand the tools I work with if I'm going to build my entire app around them. I can't just swap the NBP out for another framework if issues arise - say, Oracle-related issues. If it has issues running on the latest borked Apple JVM, there's not much I can do about it unless I'm able to dedicate the time required to become a real NBP expert. This makes me nervous, especially as much of the code I write must be supported well after I've stopped looking after it and needs to run untouched for many years. With, say, Hibernate, while I don't fully understand the core of its workings I also know I can swap it out for something else via JPA 2.0, which is simple enough that I *can* get a good understanding of it. Joe Bloggs the 3rd year comp sci graduate has a chance of doing this when hired to work on the codebase to fix some painful bug five years after I've turned it over. The SAF is attractive to me because it's small and focused enough to be easily comprehensible. I see that as a big plus in a core app framework. It gets what I need done, but it's not the kitchen sink.