Java 中等效的复合应用程序框架
只是想知道 Java 中用于创建模块化 GUI 应用程序的相反框架是什么,例如事件聚合等。
我知道 Java 没有一个明确的 GUI 框架,到目前为止我已经看到了 Eclipse RCP 和 Netbeans然而,平台似乎并没有做这些事情。
我是一名 .Net 开发人员,希望过渡到 Java,如果问题没有完全有意义,请原谅我的无知。
Just wondering what the opposing framework in Java would be for creating modular GUI applications, with things like event aggregation, etc.
I know for Java there isn't a single definitive GUI framework, and so far I've seen the Eclipse RCP and Netbeans Platform, however these don't seem to do these kind of things.
I'm a .Net developer looking to transition across to Java, and please excuse my ignorance if the question doesn't make complete sense.
如果你对这篇内容有疑问,欢迎到本站社区发帖提问 参与讨论,获取更多帮助,或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱,如果其他用户或者作者回复了您的评论,将不能在第一时间通知您!
发布评论
评论(1)
您正在寻找应用程序框架或富客户端平台,因此 Eclipse RCP 如果方向正确。
Eclipse 构建在 OSGI 之上,这意味着任何模块(称为 Eclipse Plug-In 或 OSGi Bundle)都可以注册自己的服务或利用任何其他模块提供的任何其他服务。 Eclipse RCP 平台附带了许多方便的服务,尤其是。工作台级服务的含义,例如
ISelectionService
,您可以在其中挂钩以检索选择事件。这些选择事件已经处于更高的抽象级别,它们不包含鼠标 x/y 坐标,而仅包含被选择的对象,例如 Eclipse JDT 案例中的“Java 源文件”。有菜单管理器服务、选择服务、事件处理服务、管理服务、首选项服务、操作和命令处理程序服务等。如果我正确理解事件聚合,它会管理事件和订阅者列表,并管理将这些事件转发到订阅特定事件的人。
这看起来基本上是 Eclipse 已经涵盖的内容,例如 OSGi EventAdmin,但这是非常低级别的。
You are looking for application frameworks or rich client platforms, so Eclipse RCP if the right direction.
Eclipse builds on OSGI and that means that any module (called Eclipse Plug-In or OSGi Bundle) can either register its own services or makeuse of any other service provided by any other module. The Eclipse RCP platform comes with a lot of handy services, esp. in the meaning of Workbench-level services like
ISelectionService
where you can hook in to retrieve selection events. These selection events are already on a higher abstraction level, they don't contain mouse x/y coordinates but merely the Object(s) being selected such as a "Java Source File" in the Eclipse JDT case. There are menu manager services , selection services, event handling services, administration services, preferences services, action and command handler services etc.If i understand event aggregation correctly, it manages a list of events and subscribers, and manages the forwarding of these events to whoever has subscribed to a given event.
This seems basically what Eclipse already covers under the hood, e.g. with the OSGi EventAdmin, but this is very low level.