[news.eclipse.platform.swt] Re: Using SWT/JFace to build Fat-Client App

[mwai@xxxxxxx (Mark)]

Thanks for David and Hans's answers.

> Swing has a much better, richer API and thus is easier to develop with. 
> However, performance wise, it sucks.

I heard that Swing 1.4 improves a lot in performance.  I also heard from
Java newsgroup saying that in most cases, Swing is fast enough.  I have
been hearing/reading conflicting comments.


>  So I would use Swing for 
> an application where minimizing development cost is imperative and the user 
> base is small (like an internal project).  But SWT/JFace is the way to go if 
> you expect your application to be widely used, mostly by external customers.

It sounds like your comments imply that for the same application,
development using Swing will be QUICKER than to use SWT/JFace.  I think
this will definitely be a concern because this means more development cost
for SWT/JFace solution.

Actually, before your reply, I would think that development Swing would be
a lot slower than SWT/JFace....