Choice between GWT and ZK

My team has been using an in-house framework (Echo) built some years ago.

The idea is cool, design is nice, and implementation good. With good developers they achieve this.

The framework is created sometime ago, even before spring, struts, hibernate become popular. So at that time, the framework is designed to act as an one-stop solution for all, from UI, to service, to persistence. Till now, it’s slightly outdated. As the service part has been replaced with Spring, the persistence part has partially moved aside for using hibernate.

However, there is still one layer (UI) intensively using it. This should thanks to the great integration with ZK.

The framework (Echo) has created a lot of extension to ZK, form element, container element, eventhandler element etc. It has been in same ideology we have been using for the DB UI framework, creating bean to generate the HTML output corresponding each such XML element (forms, container, eventhandler, action etc).

Great ideas are similar. Smart are in similar ways.

That’s how I come to know ZK. The UI framework by some Chinese developers, based on their client-server fusion architecture. Basically, if I understand correctly, it’s translating ZHTML file, (their languge/context) into HTML, at the same time, put their javascripts, client layout engine. Server side, they have the couterparty to listen to their javascript’s ajax calls.

Not bad. Especially plugin with ZK studio.

Just drawback, debugging is really hard. At the same time, compared to GWT, Google is better in architecture, and design.

Simply, I vote for GWT.

refer to Zk vs GWt

ZK Architecture

GWT Overview

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s