Vaadin 与 ZK 的比较
我特别感兴趣的是，这两者中哪一个更适合动态 Web 应用程序（即布局和 POJO 在运行时定义并可以随时更改）。
如果您有一个标准 POJO（具有一组固定的字段），大多数示例看起来都不错。但是，如果 POJO 替换为 MapMap 的内容构建 UI，那么框架的表现如何？
Does someone know of a comparison between ZK and Vaadin?
I'm especially interested which of the two is better suited for a dynamic web app (i.e. where the layout and POJOs are defined at runtime and can change at any time).
Most examples look pretty good if you have a standard POJO (with a fixed set of fields). But how do the frameworks fare if the POJO is replaced with a Map<String, Object> and I need to build the UI depending on the Map's content?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（3）
这两个框架都可以很好地处理动态 UI。选择框架时，您应该比较包含的组件、附加组件的数量和质量、许可、文档、社区等。
Both frameworks handle dynamic UI:s just fine. When choosing the framework, you should compare things like components included, number and quality of add-on components, licensing, documentation, community and so forth.
您可以在这里找到面向 Vaadin 的比较/讨论：vaadin.com/forum/-/message_boards/view_message/134071另一个（更多面向 ZK 的）在这里：jtechnoprojects.blogspot.com/2011/05/zk-vs-vaadin.html
此外，关于关于您关于地图内容的主题，我认为您应该对 Vaadin 的 项目接口。例如，"PropertiesItem"插件本质上是由地图支持的(java.util.Properties 准确地说），它直接绑定到 Vaadin 表单。
You find Vaadin oriented comparison/discussion here: vaadin.com/forum/-/message_boards/view_message/134071 and another one (more ZK oriented) here: jtechnoprojects.blogspot.com/2011/05/zk-vs-vaadin.html
Furthermore, regarding on your topic about Map content, I think you should be fine with Vaadin's Item interface. For example the "PropertiesItem" addon is essentially backed by a Map (java.util.Properties to be exact) and it binds directly to Vaadin Forms.
作为免责声明，我为 ZK 工作。
有很多功能可以帮助您做您想做的事情。您可以查看产品页面，其中突出显示了许多功能。不过，我强调了下面两个可能特别有用的功能。
响应式设计 - 更改布局
这种方法已在 ZK 6.5 中发布，使开发人员能够编写随布局变化的应用程序。这对你来说非常有用。它还包括根据是否在桌面浏览器、平板电脑或智能手机上改变其行为的组件。
信息可在此处获取。
数据绑定 - 布局和布局响应 POJO 中的更改
数据绑定基于 MVVM 概念，可以响应 POJO 中的更改。您可以拥有支持不同 POJO 状态等的不同模板。 这个是我们数据绑定的一个很好的入门教程。
As a disclaimer I work for ZK.
There are a lot of features that will help you do what you want to do. You can have a look at the the product page which highlights a lot of features. However, I have highlighted 2 features below which may be of particular use.
Responsive Design - Changing the layout
This approach was published in ZK 6.5 and enables developers to write applications which change with the layout. This would be very useful to you. It also includes components which change their behaviour depending on whether they are on a Desktop browser, tablet or smartphone.
Information is available here.
Databinding - Layout & Responding to changes in POJOs
The databinding is based upon MVVM concepts and can respond to changes in your POJOs. You can have different templates which support different POJO states and such like. A good introductory tutorial for our databinding is this one.