在这种情况下使用 Netbeans Platform 或 Eclipse RCP 是否太过分了？
使用 Netbeans Platform 或 Eclipse RCP 等平台实际上会给您的应用程序增加多少膨胀？我正在尝试决定我是否真的有必要使用它。我只会使用框架实际提供的一小部分功能，所有这些功能都相对容易从头开始实现。
我基本上需要的是某种形式的插件管理，用户根据 API 编写他们的库，而我的程序可以找到他们的服务。这很容易通过几行代码从头开始实现。除此之外，我还需要做一些 2D 图形工作，其中可以拖放小部件等。这两个要求是否足以构成使用框架的充分理由？我实际上更倾向于自己做。
谢谢。
Exactly how much bloat does using a platform like the Netbeans Platform or Eclipse RCP actually add to your application? I am trying to decide if it is really neccessary for me to use it. I will only be using a very small amount of the functionality actually provided by the framework, all of which are relatively easy to implement from scratch.
All I basically need is some form of plugin management, where users code their libraries according to an API and my program can locate their services. This is easy enough to implement from scratch in a few lines of code. Further than that, I will need to do some 2D graphics work where widgets can be dragged and dropped etc. Does these two requirements make a strong enough case to use a framework? I am actually leaning more towards just doing it myself.
Thanks.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
如果您正在考虑编写自己的插件解决方案，我强烈建议您通过 RCP 使用 Eclipse 的 OSGi 实现。 OSGi 坚如磐石，可以处理同一库的替代版本和各种类路径问题等问题。这将有助于您的插件提供商，因为他们不必担心存在其他库。这比将一堆 jar 放入同一个类路径中要好得多。
If you are considering a writing your own plugin solution, I would highly recommend going with Eclipse's implementation of OSGi through the RCP. OSGi is rock solid, and handles things like alternate versions of the same library and all sorts of class-path issues. This will help your plugin providers, since they won't have to worry about what other libraries are present. This is much better than dropping a bunch of jars into the same classpath.