java Vaadin 和 ZK 的比较
声明：本页面是StackOverFlow热门问题的中英对照翻译，遵循CC BY-SA 4.0协议，如果您需要使用它，必须同样遵循CC BY-SA许可，注明原文地址和作者信息，同时你必须将它归于原作者（不是我）：StackOverFlow
原文地址: http://stackoverflow.com/questions/7267408/
Warning: these are provided under cc-by-sa 4.0 license. You are free to use/share it, But you must attribute it to the original authors (not me):
StackOverFlow
Comparison between Vaadin and ZK
提问by Aaron Digulla
Does someone know of a comparison between ZKand 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).
我特别感兴趣的是这两者中的哪一个更适合动态 Web 应用程序（即布局和 POJO 在运行时定义并且可以随时更改）。
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?
如果您有一个标准的 POJO（具有一组固定的字段），那么大多数示例看起来都不错。但是，如果 POJO 被替换为 aMap<String, Object>并且我需要根据Map的内容构建 UI，那么框架会怎样呢？
回答by Joonas
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.
两个框架都可以处理动态 UI:s 就好了。在选择框架时，您应该比较包含的组件、附加组件的数量和质量、许可、文档、社区等内容。
回答by eeq
You find Vaadin oriented comparison/discussion here: vaadin.com/forum/-/message_boards/view_message/134071and another one (more ZK oriented) here: jtechnoprojects.blogspot.com/2011/05/zk-vs-vaadin.html
您可以在此处找到面向 Vaadin 的比较/讨论：vaadin.com/forum/-/ message_boards/ view_message/ 134071和另一个（更多面向 ZK 的）：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" addonis essentially backed by a Map (java.util.Propertiesto be exact) and it binds directly to Vaadin Forms.
此外，关于您关于地图内容的主题，我认为您应该对 Vaadin 的Item interface 没问题。例如，“PropertiesItem”插件本质上是由 Map（准确地说是java.util.Properties）支持的，它直接绑定到 Vaadin Forms。
回答by Tim
As a disclaimer I work for ZK.
作为免责声明，我为 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 pagewhich highlights a lot of features. However, I have highlighted 2 features below which may be of particular use.
有很多功能可以帮助您做您想做的事。您可以查看突出显示许多功能的产品页面。但是，我在下面强调了 2 个可能特别有用的功能。
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.
这种方法在 ZK 6.5 中发布，使开发人员能够编写随布局而变化的应用程序。这对你非常有用。它还包括根据它们是在桌面浏览器、平板电脑还是智能手机上改变其行为的组件。
Information is available here.
信息可在此处获得。
Databinding - Layout & Responding to changes in POJOs
数据绑定 - 布局和响应 POJO 中的更改
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.
数据绑定基于 MVVM 概念，可以响应 POJO 中的更改。您可以拥有支持不同 POJO 状态等的不同模板。我们的数据绑定的一个很好的介绍性教程是这个。
