SWT/JFace 还是 Eclipse RCP？
选择 Eclipse 富客户端平台作为我的应用程序基础而不是仅使用 SWT/JFace 的原因有哪些？
Which are the reasons to choose the Eclipse Rich Client Platform as the base of my application, instead of just using SWT/JFace?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（4）
Eclipse RCP 不仅仅是一个 GUI (SWT/JFace)，还是一个 OSGi< /a> 为基础的平台。
因此，您选择 RCP 框架的目的是：
如果您的应用程序只是一个整体 GUI 字体端，那么 RCP 可能有点大材小用。
Eclipse RCP is not just a GUI (SWT/JFace), but an OSGi-based platform.
So, you would choose the RCP framework in order to:
If your application is just one monolithic GUI font-end, RCP might be a bit overkill.
除了 VonC 指出的要点（OSGi 平台的优点：模块化、类加载器隔离、可扩展架构），Eclipse RCP 提供了许多应用程序级服务，可以简化最终产品的整体开发：
使用 Eclipse RCP，您将获得：
当然 - 后一部分并不一定意味着您必须使用 Eclipse RCP 平台这个庞然大物才能获得这些优势提供。
根据应用程序的范围，您最好只使用 Equinox 作为底层 OSGi 容器，并在此基础上构建您自己的 GUI 客户端。
还要记住，在 SWT/JFace 领域做出 GUI 框架决策时，Eclipse RCP 不再是唯一的选择。有一些强有力的竞争者可能会更好地满足您的需求：
编辑：
自从我最初的答案发布以来，Eclipse e4 项目已经不再是一个正在进行的工作，现在已经成为一个完全可用的富客户端应用程序框架/平台。它已经成熟到现在被用作最新 Eclipse 4.2 (Indigo) IDE 的底层平台。
In additions to points that VonC has pointed out (OSGi platform goodies: modularity, classloader isolation, extensible architecture), the Eclipse RCP provides many application level services that might ease the overall development of your final product:
With Eclipse RCP you'll get:
Of course - the latter part does not necessarily mean you have to use the behemoth that is Eclipse RCP platform to gain the advantages those offer.
Depending on the scope of your application, you might do well to just use Equinox as an underlying OSGi container and build your own GUI client on top of that.
Also keep in mind that Eclipse RCP is no more the only game in town when making a decision of GUI frameworks in SWT/JFace land. There are serious contenders that might suite your needs better:
Edit:
Eclipse e4 project has graduated from being just a work in progress since my original answer was posted and now has become a fully usable rich client application framework/platform of its own. It has matured to the point where it is now being used as an underlying platform for the latest Eclipse 4.2 (Indigo) IDE.
虽然只值我的 2 便士，但普通的 SWT/JFace 的学习曲线可能更简单。我喜欢它们只是简单的 GUI，您不需要学习“平台”（如 RCP 方式），只需掌握 SWT 组件并构建 GUI！总的来说，我认为它更简单（但我对 RCP 不太了解！）。
Just my 2 pennies worth, but vanilla SWT/JFace can be less of a learning curve. I like the fact they're just simple GUIs, you don't need to learn the "platform" (as in the RCP way), just get to grips with the SWT components and build you're GUI! Overall, I see it as simpler (but then I don't really know much about RCP!).
Eclipse 4的依赖注入机制是一笔巨大的财富，要选择Eclipse RCP，
现在有了E4，平台可以非常轻量级，
添加到这个e4工具中，加上它的模型编辑器，让你节省很多时间
Eclipse 4 dependency injection mechanism is a great asset, to choose Eclipse RCP,
and Now with E4, the platform can be very lightweight,
Add to this e4 tools with it model editor, let you save a lot of time