There are two serious contenders for a GUI: Swing and SWT.
Swing is more mature (arguably), is part of the standard JDK (no deployment issues), very flexible and well-documented.
SWT makes it easier to behave like a native application across different OSes (but this also means significantly more portability issues). It also reportedly performs better in some scenarios (but this depends very much on what you do).
Some other considerations:
I'd seriouly consider creating a web app when making a new app nowadays. In that case, SWT scores an extra point, because it has Eclipse RAP which (more or less) lets you convert a desktop client into a web client by just recompiling against different libraries, because it uses the same API as SWT.
Also, you might consider building atop a client framework, instead of writing from scratch. In that case, if you use Eclipse as your framework, you'll have to use SWT. Or use Netbeans, which is based on Swing...
SWT has been good to me. It provides a native look-and-feel by using native controls when available.
You can optionally use it and JFace in the Eclipse Rich-Client Platform, which provides a framework for applications built atop a community of plug-ins. It has a high learning curve, but provides a mature, powerful framework that you don't have to build.
发布评论
评论（2）
查看您链接到的问题（ Which GUI Library is the best in Java ？
），那里的答案仍然相关。
简短版本：
GUI 有两个强有力的竞争者：Swing 和 SWT。
Swing 更成熟（可以说），是标准 JDK 的一部分（没有部署问题），非常灵活且文档齐全。
SWT 使得跨不同操作系统更容易像本机应用程序一样运行（但这也意味着更多的可移植性问题）。据报道，它在某些情况下也表现得更好（但这很大程度上取决于您所做的事情）。
其他一些考虑因素：
现在在制作新应用程序时，我会认真考虑创建一个网络应用程序。在这种情况下，SWT 会获得额外的分数，因为它具有 Eclipse RAP（或多或少） ）让您只需针对不同的库重新编译即可将桌面客户端转换为 Web 客户端，因为它使用与 SWT 相同的 API。
此外，您可能会考虑在客户端框架之上构建，而不是从头开始编写。在这种情况下，如果您使用 Eclipse 作为框架，则必须使用 SWT。或者使用基于 Swing 的 Netbeans...
Looking at the question you link to ( Which GUI Library is the best in Java?
), the answers there are still relevant.
Short version:
There are two serious contenders for a GUI: Swing and SWT.
Swing is more mature (arguably), is part of the standard JDK (no deployment issues), very flexible and well-documented.
SWT makes it easier to behave like a native application across different OSes (but this also means significantly more portability issues). It also reportedly performs better in some scenarios (but this depends very much on what you do).
Some other considerations:
I'd seriouly consider creating a web app when making a new app nowadays. In that case, SWT scores an extra point, because it has Eclipse RAP which (more or less) lets you convert a desktop client into a web client by just recompiling against different libraries, because it uses the same API as SWT.
Also, you might consider building atop a client framework, instead of writing from scratch. In that case, if you use Eclipse as your framework, you'll have to use SWT. Or use Netbeans, which is based on Swing...
SWT 对我来说很好。它通过使用可用的本机控件来提供本机外观和感觉。
您可以选择在 JFace .eclipse.org/index.php/Rich_Client_Platform" rel="nofollow">Eclipse Rich-Client Platform，它为构建在插件社区之上的应用程序提供了一个框架。它具有很高的学习曲线，但提供了一个成熟、强大的框架，您无需构建。
SWT has been good to me. It provides a native look-and-feel by using native controls when available.
You can optionally use it and JFace in the Eclipse Rich-Client Platform, which provides a framework for applications built atop a community of plug-ins. It has a high learning curve, but provides a mature, powerful framework that you don't have to build.