[news.eclipse.newcomer] Re: GUI builder for new projects

[frecklefoot@xxxxxxxxx (Frecklefoot )]

<ns_dkerber@xxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

> What would be the appropriate project or package to use for building new
> data-collection java applications with very simple gui requirements (a
> couple of buttons, a small menu, and a scrolling textbox to display
> data).

If that's all the GUI you have, it might be easy enough to code it by 
hand.  It might be easier than trying to learn a new tool.  But if 
"rolling your own" isn't your cup of tea, a visual editor might be the way 
to go.

> In article <grvtv5$1em$1@xxxxxxxxxxxxxxxxx>, eclipse-news@xxxxxxxxxxxx 
> says...

> It does, but brings up one more question:  Swing or SWT, and why one 
> over the other?  

> From the Wikipedia article 
(http://en.wikipedia.org/wiki/Standard_Widget_Toolkit): "SWT and Swing are 
different tools that were built with different goals in mind. The purpose 
of SWT is to provide a common API for accessing native widgets across a 
spectrum of platforms. The primary design goals are high performance, 
native look and feel, and deep platform integration. Swing, on the other 
hand, is designed to allow for a highly customizable look and feel that is 
common across all platforms."

So, if you want "native look and feel," you should probably go with SWT.  
If you want the app to look the same no matter was O/S it runs on, use 
Swing.  From personal experience, Swing is pretty easy to use.  The 
Wikipedia article also claims that SWT doesn't have as much functionality 
as the Swing components, so that could also influence your decision.

Sorry this wasn't a "these components are better and this is why," but was 
"it depends", but this is the way as most things in life...

Regards,

Frecklefoot