🚀 go-pugleaf

Scott wrote:
> Has any worked with Eclipse's SWT (standard widget toolkit)?
> 
> How do you think it compares to Swing?

While reading this, keep in my that I haven't used SWT and I really like 
Swing.

My opinion is that SWT is probably fine but is overrated.  The two main 
problems it claims to solve are speed and true native look and feel 
compatibility.  Both of those were big problems 5 years ago, neither 
IMHO is a big problem today.  SWT might be better in both areas, but I 
don't think it's "WAY better, how can you use Swing, Swing sucks, you 
loser," which is what some of the zealots would have you believe.  I 
wouldn't choose SWT just on the strength of speed and native L&F arguments.

I also think it loses two of the main benefits of Java/Swing.  One is 
platform independence.  Sure, SWT is available on a wide variety of 
platforms, but I don't think it's as wide as Swing.  As you said, this 
is less of an issue with something internal where you have a pretty good 
handle on which platforms matter to you, but it still bothers me in 
principle.  In practice it may be a non-issue.

The second area is the MVC architecture.  This one is debatable.  I 
really like Swing's use of MVC and think it gives you a huge amount of 
flexibility.  SWT advocates look at Swing and see complexity and say 
that SWT eliminates some of that (which is true).  Which side of that 
fence you land on is a matter of personal preference.

So I probably haven't really answered any of your questions :-), but 
maybe this will help you solidify whatever conclusions you're coming to 
on your own.

-- 
Gillmer J. Derge [TeamB]