Guru Sharma wrote:Hi
you can very well go ahead with Java Swing. Complete Stand alone solution for GUI Development.
You can also try GWT (Google Web Tool kit)
Ernest Friedman-Hill wrote:Swing is part of the core Java APIs; it's not going anywhere.
My suspicion was confirmed by Karsten Lentzsch a well-known Swing developer and one of the member of the expert group in a dicussion in the mailing list:
"I doubt that it can be included in Java 7; and I'll vote against it."
"There's no activity in the expert group, and no visible progress
in the public code base. Anyway I hope that Sun will revive this JSR.
At least, it would help if someone from Sun could comment what's going
Ernest Friedman-Hill wrote:None of that has anything to do with Swing; it's about a proposal for something completely separate called the "Swing Application Framework (SAF)," which looks like it's dying on the vine. That doesn't really mean anything.
Note that SWT was created as a part of Eclipse, an IDE and also an application platform. Sun's own "NetBeans" IDE, which is equivalent in many ways to Eclipse, is built with Swing. So to the extent that Eclipse is a "SWT Application Framework", Swing already has an application framework; SAF as described here is kind of redundant. perhaps that's why it lost steam and died.
Gregg Bolinger wrote:Although core Swing doesn't have any significant work currently going on to speak of, there is plenty of technologies built with Swing that are highy active. As Ernest said, Netbeans. IntelliJ's IDEA is also built with Swing. Griffon is a groovy based framework for creating Swing applications. There's actually lots going on if you just bothered to hit the interwebs a bit.
Long story short, Swing isn't going anywhere so its a safe bet. That doesn't necessarily mean SWT is the wrong choice though. Kind of depends on your ultimate goal (get a job, get a promotion, learn something new, create your own product, etc).
Freddy Wong wrote:I also don't think that Swing will die anytime soon. There are still a lot of number of applications written in Swing. I can't answer which one you should choose. It all depends on your needs. As far as I know, there are a lot of more books on Swing than SWT. You can probably learn Swing first, then learn SWT once you've become proficient with GUI framework. I believe learning SWT shouldn't be too difficult afterwards.
Freddy Wong wrote:It's definitely worth trying. But it's good to know some basic of Swing first before you delve into NetBeans Platform
Please do not shoot the fish in this barrel. But you can shoot at this tiny ad:
Building a Better World in your Backyard by Paul Wheaton and Shawn Klassen-Koophttps://coderanch.com/wiki/718759/books/Building-World-Backyard-Paul-Wheaton