Comparison of Vaadin and ZK

Question

Does anyone know about comparing ZK and Vaadin ?

I am particularly interested in which one is better suited for a dynamic web application (i.e. where the layout and POJO are defined at runtime and can change at any time).

Most examples look good if you have a standard POJO (with a fixed set of fields). But how are tariff plans charged if the POJO is replaced with Map<String, Object> , and I need to create an interface depending on the contents of the Map ?

Answer 1

You will find Vaadin oriented comparison / discussion here: vaadin.com/forum/-/message_boards/view_message/134071 and another (more ZK oriented): jtechnoprojects.blogspot.com/2011/05/zk-vs-vaadin.html

In addition, with regard to your topic on the content of Maps, I think that with the Vaadin interface with the goods should be good. . For example, the “PropertiesItem” addon is essentially supported by a map ( java.util.Properties , to be precise) and is tied directly to Vaadin Forms .

Answer 2

Both frameworks handle a dynamic interface: s is just fine. When choosing a framework, you should compare things like components, quantity and quality of additional components, licensing, documentation, community, etc.

Answer 3

As a disclaimer, I work for ZK.

There are many features to help you do what you want to do. You can see the product page , which highlights many features. However, I highlighted two functions that may be especially useful.

Responsive Design - Change Layout

This approach was published in ZK 6.5 and allows developers to write applications that change with the layout. That would be very helpful for you. It also includes components that change their behavior depending on whether they are in a desktop browser, tablet or smartphone.

Information is available here .

data binding - layout and response to changes in POJO

Data binding is based on MVVM concepts and can respond to changes in your POJOs. You may have different templates that support different POJO states, etc. This is a good introductory tutorial for our data binding.