It's not a secret anymore!*
The moose likes Swing / AWT / SWT and the fly likes why (should I) Swing..? Big Moose Saloon
  Search | Java FAQ | Recent Topics | Flagged Topics | Hot Topics | Zero Replies
Register / Login


Win a copy of Soft Skills this week in the Jobs Discussion forum!
JavaRanch » Java Forums » Java » Swing / AWT / SWT
Bookmark "why (should I) Swing..?" Watch "why (should I) Swing..?" New topic
Author

why (should I) Swing..?

Rama Raghavan
Ranch Hand

Joined: Aug 22, 2001
Posts: 116
Agreed it has rich visual and keyboarding values..
BUT -
With application deployment over the web becomming so common(even for intranet apps) , why would one invest time (and money) to build Swing based client apps..?
Rama


Rama Raghavan<br />SCJP2<br />SCWCD
Vince Marco
Greenhorn

Joined: Oct 29, 2002
Posts: 1
With application deployment over the web becomming so common(even for intranet apps) , why would one invest time (and money) to build Swing based client apps..?

There are many reasons for developing rich client apps vs. web apps. While browsers are currently popular, they are are also very focused and restrictive. Web apps have had 3 distinct advantages over JFC apps: automatic distribution, consistent user interface (albeit dumbed down), and that simple web apps are much easier to build.
However, with JavaWebStart and InstallAnywhere the automatic distribution advantage is pretty much neutralized. JFC apps can produce apps with huge improvements in GUI over web apps. And most web applications which are not basic hyperlinked documents or simple forms, are pretty complex to develop and maintain.
So, when you cut through the myths the end result is that if your application is not basic hypertext documents or simple forms, a JavaWebStart JFC-based app is worth considering. This enables client applications to better distribute processing to client machines, produce truely interactive GUIs, and interact with the growing number of web services available on intranets and the internet.
As an example most of my developer tools (IDEA, JBuilder, Eclipse, NetBeans, DbVisualizer, PureTest, LdapBrowser, Oxygen, ThinkFree Office, etc) are all Java apps running on Windows, Linux, and OSX.
JFC is also being considered for use more and more in applets. My applet experience is that it grows exponentially more difficult to support AWT as more features are added into the applet. It is worth considering using JFC and requiring the user to install the JavaPlugin and latest JDK in many applet deployments, based on richness of applet interface and saved maintenance costs.
My 2 cents,
Vince
SCJP
J2EE Complete, co-author
eric moon
Ranch Hand

Joined: Nov 26, 2000
Posts: 133
For filling out forms of a few pages, HTML works. But try doing bug reporting on Oracle CRM system day in and day out. Thousands of man-hours wasted waiting for and scrolling through HTML pages. The fact is, if you are going to work with a tool on a daily basis, a web interface is not appropriate. And if you want to support drag and drop, or editable trees or tables or sliders, or have your GUI update in response to user data, forget it.
In fact, I can't even resize the window I'm typing on now!
Just one man's opinion, of course.


<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>"Those who cast the votes decide nothing. Those who count the<BR>votes decide<BR>everything." <BR> -Joseph Stalin<HR></BLOCKQUOTE>
 
I agree. Here's the link: http://aspose.com/file-tools
 
subject: why (should I) Swing..?