Rhino <no.offline.contact.please@nospam.com> wrote:
> Forgive my ignorance but how does SWT differ from Swing/JFC? Does SWT offer
> desireable components not found in Swing/JFC?

The SWT differs from Swing in that is relies mainly on native widgets
(and therefore native code), but nevertheless keeps the JNI boundary low
so that most implementation can be done in Java with only a thin native
API wrapper. This is essentially a kind of compromise between the AWT
with its thick peers and lack of decent selectoin, and Swing with its
lightweight widgets.

The SWT is less fun to work with than Swing, and doesn't contain more
components than Swing. With JFace, at least a few of its components can
match the sensible behavior of Swing's model-based architecture. In
general, it's easier to screw up and you have to know more to do it
well. However, SWT is necessary for writing Eclipse plugins and RCP-
based applications, and that alone makes it worth learning. It's also
supposed to fix some performance issues of Swing.

> Doesn't Swing/JFC work in .NET/Visual Studio?

Who cares? Does anyone actually use Visual Studio to write "Java"?

--
www.designacourse.com
The Easiest Way To Train Anyone... Anywhere.

Chris Smith - Lead Software Developer/Technical Trainer
MindIQ Corporation