Ch02

Analyse ToDoZK

Look before you leap! -- The Analects

Let's review the customer's specification.

As customer's requirement, the main layout of ToDoZK is a standard Header-Siderbar-Content-Footer layout pattern. The Sidebar block is similar to menu list, end user can collapse some category to avoid screen too long. When end user select a static content page (under Document category), Content block will show the specify resource. Otherwise is TaskViewer, add Workspace, Milestone and Task, besides Content block will show the content generated by business logic, UserStatus block in Header block will change content too. UserStatus block can also effect the TaskViewer style which is card view or tree view.

Shake Spear : Sidebar and TaskViewer is a standard RIA, so there is no doubt to implement them by ZK. Although UserStatus block does not need be interactive, but after some CRUD operation it must update data, so ZK is good choice. Hence, the Content block is also implement by ZK, I won't worry about the interact between blocks, good job!

Well, at first glance it is perfectly reasonable and will work fine. But how can we explain the Mummy Pythian and Conqueror Clipper's complain?

Actually, Shake Spear use ZK in wrong way, he should not use ZK to build whole website.

So, when to do with ZK?

To System Architect

Use ZK to develop website is absolutely the right choice, but not for whole website. As you can use M$ Word to read system log, write a Java application to find file in hard disk, but you will not do it in general case, right?