-
FEATURED COMPONENTS
First time here? Check out the FAQ!
Dear All,
I am asked to make a comparison between ZK and Kendo UI, though these tools have completely different architectures. I would like to impose ZK, can you please provide me some arguments to defend ZK againts Kendo UI?
Thanks
As per My understanding zk is a JavaScript Killer. No need to write JavaScript Code.It's a great feature in zk.
Hi, Which feature is a strength depending on your environment and requirement. Roughly speaking, Kendo UI is a JavaScript UI component framework which is very different from ZK, a Java UI framework.
Development in Kendo UI is obviously client-centric, but ZK is server client fusion which allows you to develop in Java and customize in JavaScript. ZK also handles those AJAX communication details for you, but you must do it by your own in Kendo UI.
ZK supports MVC / MVVM design pattern, easy to build prototype system, better integration with other Java framework (Spring, JPA), automated test support, lots of documents, and an active community.
Working with ZK is fun.
You can read this article ZK Web Framework Thoughts
In terms of functionality, what you can do with Kendo UI can also be done with ZK framework. It's because ZK framework allows you to do client-side programming. What ZK framework can do on the server-side can not be done with Kendo UI. You have to develop your own client-server communication and server-side data model for your Kendo view.
Another most important of ZK is, any developer has the background of Oops without any web development experience, they can easily adopt and start writing the code. For example, if you take me, i am from the client server Microsoft technology, it just took me to one month to start developing the web application using ZK.
ZK Hides lot of routine coding and makes the developer life easy.
Asked: 2013-01-18 12:20:43 +0800
Seen: 103 times
Last updated: Jan 23 '13