User:MontyPan/Ch00

Introduction

When you search Java web development technique, ZK is always a good choice of high-productivity framework. After realize "How to use ZK', we usually have other questions like:

• Should we use ZK in this situation?
• Which ZK component can be used this time?

The goal of this book is attempt to answer these questions. You will be more comfortable in the planning, implementation web site after read this book.

Who should read this book?

What a dummy question is it? Everyone should read it again and again :P But we still locked the reader's identity in ZK programmers, system architects and web artists. In real world, layout issues can't be solved with programmer alone, it also need system architects' and web artists' support.

We believe everybody is a good ZK programmer, but if...

• Have no idea about ZK? Quick review "Learn ZK in 10 Minutes" or read "ZK Essentials" carefully.
• Is not familiar with ZK? Placed "ZK Developer's Reference" and "ZK Component Reference" in hand to be used to access at any time.
• If you ever use ZK MVVM, it's a good time to start! Please read this article: "Get ZK Up and Running with MVVM".

In other words, we suppose you are already familiar with ZK. We will ignore some implement details which is not related to layout issue directly. Please don't worry, the information we skip is not important (in this book :P) and will not hinder reading.

What content is covered in this book?

We will implement an online task management website: "ToDoZK", and answer these question:

• How to analyse your website?
• When and where to do with ZK?
• How to layout?
• Which ZK component should I use?

What content isn't covered in this book?

Due to space limitations in this book (totally wrong :P) and we also won't you to be distracted, these feature will be skipped:

• How to prettify your website?
  Aesthetic feeling is god giving, not human nature.
• Everything about business logic.
  No database, no persistence layer, no CRUD...
• Richlet、Macro、Composite.....
  In order to make this article simple and easy, we had to make some trade off. We use only ZUL and MVVM in example code, you can convert to other ZK techniques with your own needs.

Must recite all of this book?

Of course, we hope you can read this book step by step, chapter by chapter. However if your project is urgent and have enough time to read this book, we really know how miserable you are :'( . Therefore we tell you how to loaf on the job, don't let your boss know this section!

ZK Programmer

Poor programmer must read every chapter, but some sections are more important. You can read these chapter first with this order:

1. [Ch.4]
2. [Ch.3]

System Architect

If you are architect, you can ignore the implement detail and skill (The more you learn, the better you are :) ), so read these chapter:

1. [Ch.1]
2. [Ch.2]
3. [Ch.3]

And the "To System Architect" block should be read:

To System Architect

Learn ZK is a happy thing...

Web artist

If you are web artist, most ZK content and program skills are useless, but you should read these part:

1. [Ch.1]
2. [Ch.2]
3. [Ch.3]: You can start at "client side issue" section.

And the "To Web Artist" block should be read too:

To Web Artist

Learn ZK is a happy thing... /

OK! Let's GO!