||This article's use of external links may not follow Wikipedia's policies or guidelines. (July 2012)|
||This article appears to be written like an advertisement. (April 2013)|
|Stable release||6.5.2 / March 26, 2013|
|Operating system||Cross-platform (JVM)|
|Type||Ajax Web Framework|
|License||LGPL / ZOL / Commercial|
The core of ZK consists of an Ajax-based event-driven mechanism, over 123 XUL and 83 XHTML-based components, and a markup language for designing user interfaces. Programmers design their application pages in feature-rich XUL/XHTML components, and manipulate them upon events triggered by end user's activity. It is similar to the programming model found in desktop GUI-based applications.
ZK takes the so-called server-centric approach that the content synchronization of components and the event pipelining between clients and servers are automatically done by the engine and Ajax plumbing codes are completely transparent to web application developers. Therefore, the end users get the similar engaged interactivity and responsiveness as a desktop application, while programmers' development retains a similar simplicity to that of desktop applications.
Meanwhile, with the so-called server+client fusion, the optional client-side customization allows the developer to leverage the client-side resources, to custom the look and feel and to reduce the Ajax traffic.
In addition to component-based programming in a manner similar to Swing, ZK supports a markup language for rich user interface definition called ZUML.
- ZUML is designed for non-programmer developers to design user interfaces intuitively.
- ZUML allows developers to meld different markup languages, such as Mozilla XUL language and XHTML, seamlessly into the same page.
- ZUML allows developers to embed scripts in pure Java language (interpreted by BeanShell) and use EL expressions to manipulate the components and access data.
- Over 100 Ajax components offer UI designers a variety of feature rich components to meet the demands of enterprise Ajax applications.
- ZUML makes the design of rich user interfaces similar to authoring HTML pages. ZUML is a variant of XUL inheriting all features available to XML, and separates the UI definition from the run-time logic.
- Event-driven component-based model (similar to desktop programming models).
- Support for Model-View-Controller (MVC) decoupling View, Model and Controller for easy to develop and maintain.
- Support for Model-View-Presenter and Model-View-ViewModel (MVVM) design patterns that decouples the controller furthermore to minimize the code required and to maximize the maintainability.
- Databinding capability via in-ZUML-page annotations that transparently automates CRUD and state synchronization between UI view and the data and POJO.
- Application components, such as spreadsheet, pivot table, and calendar.
- Support for integrating with existing web frameworks via a JSP custom tag library, JSF support, Portlet, and a Servlet Filter. Has support for Spring and Hibernate.
- Extensible in that programmers can create new custom UI controls. Groups of controls can be re-used as a macro component.
Differences from XUL
- ZK is a server side framework which emits HTML and thus does not depend on client side presence of Gecko making it portable to any browser. ZK takes ZUML (xul and xhtml) serverside pages as input and outputs dhtml for the browser.
- ZK processes user interface logic on the server in Java. This increases choice in the scripting engines and application libraries that can be used to create logic. Presentation effects can be delegated to the browser using the Client-side Actions feature to reduce server load for dhtml effects. Running the application logic on the server in a single application container reduces the amount of cross browser and browser version testing when compared to extensively programming the DOM at the browser.
- While ZK and XUL have an overlapping subset of components, ZK has its own unique component sets. The component library can be extended with custom components. Macro components can be defined that are composites of components.
- ZK provides serverside databinding annotations to declaratively bind UI components to serverside data.
- Look and Feel differences.
Prerequisites of programming skills
- Basic knowledge of HTML and XUL
- Knowledge of a scripting language to write the glue logic (running on the server):
- Object Oriented Programming. You can choose to do AWT/Swing style programming against the ZK API. You can choose to program one or more custom UI controller classes in Java. This is entirely optional. Alternatively you can choose to use zscript script tags for user interface logic which is similar to dhtml programming.
- Servlet Programming. ZK is built on top of the Servlet API. You can choose to do regular Servlet programming and use ZUML as the page language.
- Ajax. ZK is built on top of Ajax but it automatically converts user input at the browser to Java events at the server so you do not have to either program or understand browser Ajax.
- Declarative Databindings. ZK has an optional syntax for binding user interface controls to your POJO Java Beans. ZK will automatically call your POJO setter/getter methods with zero programming in response to user input at the browser.
- Expression Language. ZK supports JSTL style EL.
ZUML (ZK User Interface Markup Language) is a markup language for rich user interfaces definition.
- ZUML is designed for non-programmers to design user interfaces efficiently with the ZUML markup
- ZUML allows developer to meld different markup languages, such as Mozilla XUL language and XHTML, seamlessly into the same page.
- ZUML allows developers to embed script in pure Java language (interpreted by BeanShell) and use EL expressions to manipulate the components and access data.
- ZUML is supported by ZK.
- Official Documentation : ZUML Reference
ZK is a server-centric framework. Technically you don't need to know about the implementation at the client side. It is how ZK Mobile running on Java Mobile VM is done.
Since ZK 5.0, the so-called Server+client Fusion architecture is introduced. Developers are allowed to access the client-side widgets directly if they want to. ZK Client Engine is based on jQuery. Technically you can use jQuery-compliant libraries and widgets.
- ZK 3 and older versions are licensed under GPL.
- Staeuble, Markus (2008). ZK Developer's Guide. Packt Publishing. p. 184. ISBN 978-1-84719-200-4.
- Van der Schyff, Andre (03-31-2009). "A look at MVC frameworks". ITWeb. "MVC frameworks provide limited functionality when compared to ZK, Echo and other Java Web frameworks."
- "ZK Explorer". Retrieved 08-25-2010.
- Clare, Timothy (02-09-2010). "Server+client Fusion: An Architectural Proposal". Dr. Dobb's. "A good framework architecture is flexible empowering developers and architects to implement their applications in a smart and elegant manner."
- Mahajan, Sachin (10-19-2010). "Enhance Ajax development with a fusion of jQuery, ZK, and Java code". IBM developerWorks. "The marriage between server-side Java code and jQuery can help you tackle the challenges in enterprise Ajax application development."
- Rich Internet applications using ZK at IBM developerWorks
- Implementing event-driven GUI patterns using the ZK Java AJAX framework at IBM developerWorks
- Next-Generation Applications Using Ajax and OpenAjax at OpenAjax Alliance
- Zero-code AJAX framework sought at InfoWorld.
- Designing rich AJAX Web interfaces with ZK at Linux.com
- ZK and Agile at TheServerSide
- The ZK Framework at Dr.Dobb's Portal
- Explore the CDI programming model in ZK at IBM developerWorks
- Ajax with the ZK Framework at developer.com
- Using Desktop MVC Patterns with ZK, Spring & JPA at JavaLobby
- Implementing Load-on-Demand using ZK and Grails at JavaLobby
|Wikibooks has a book on the topic of: ZK|
- ZK Home
- ZK Live Demo
- An Interview with ZK Creator Tom Yeh
- An Interview with Tom Yeh, ZK Creator (Un framework che guardi al futuro, Mokabyte)(Italian)
- Tutorial: ZK Rich Client Framework and Agile Development
- Tutorials for Informix applications with ZK I II III IV V VI VII
- Tutorials from IBM developerWorks I II IIIIV
- Small Talks