Does someone know of a comparison between ZK and Vaadin?
I'm especially interested which of the two is better suited for a dyn开发者_高级运维amic 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?
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.
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.
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.
精彩评论