|
Size: 5683
Comment:
|
Size: 2518
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 16: | Line 16: |
| 1. [wiki:self/Zope3Book/3-Zope3Components Zope 3 Components ] -- 0% | |
| Line 18: | Line 19: |
| 1. [wiki:self/Zope3Book/1-What-sZope What is Zope?] -- 0% === Zope 3 Components === Zope 3 will make use of many of the latest and hottest development patterns and technologies, and that with "a twist" as Jim Fulton likes to describe it. But Zope 3 also reuses some of the parts that were developed for previous versions. Users will be glad to find that Acquisition (but in a very di erent form) is available again as well as Zope Page Templates and the Document Template Markup Language - DTML (even though with less emphasis). Also, there is the consensus of a Zope Management Interface in Zope 3 again, but is completely developed from scratch in a modular fashion so that components cannot be only reused, but the entire GUI can be altered as desired. But not only DTML, ZPT and Aquidition received a new face in Zope 3; external data han- dling has been also totally reworked to make external data play better together with the inter- nal persistence framework, so that the system can take advantage of transactions, and event chan- nels. Furthermore, the various external data sources are now handled much more generically and are therefore more transparent to the developer. But which external data sources are supported? By default Zope 3 comes with a database adaptor for Gad y , but additional adapters for Post- GreSQL and other databases already exist and many others will follow. Data sources that support XML-RPC, like the very scalable XML database Tamino, could also be seamlessly inserted. How- ever, any other imaginable data source can be connected to Zope by developing a couple of Python modules, as described in various chapters. During the last five years (the age of Zope 2) not only Zope was developed and improved, but also many third party products were written by members of the very active Zope community for their everyday need. These products range from Hot Fixes, Database Adaptors and Zope objects to a wide range of end user software, such as e-commerce, content management and e-learning systems. However, some of these products turned out to be generically very useful to a wide variety of people; actually, they are so useful, that they were incorporated into the Zope 3 core. The prime examples are the two internationalization and localization tools Localizer (by Juan David Ibanez Palomar) and ZBabel (by me), whose existence shaped the implementation of the internationalization and localization support Zope 3 significantly. Another great product that made it into the Zope 3 core was originally written by Martijn Faassen and is called Formulator. Formulator allows the developer to define fields (representing some meta-data of a piece of content) that represent data on the one side and HTML fields on the other. One can then combine fields to a form and have it displayed on the Web. The second great feature Formulator came with was the Validator, which validated user-entered data on the server side. Formulator's concepts were modularized into schemas and forms/widgets and incorporated in Zope 3. Altogether, the framework is much cleaner now (and more pythonic) and features that failed to make it into the Zope 2 core were incorporated. |
Zope3Book -- 中文快速翻译项目
::-- ZoomQuiet [DateTime(2005-08-18T10:38:20Z)] TableOfContents
描述
为了学习，我们自个儿来翻译，仅仅作为学习笔记的一种方式吧
正文
- [wiki:self/Zope3Book/0-Preface 序] -- 0%
- [wiki:self/Zope3Book/1-What-sZope What is Zope?] -- 0%
[wiki:self/Zope3Book/2-PowerfulPython Powerful Python] -- 0%
[wiki:self/Zope3Book/3-Zope3Components Zope 3 Components ] -- 0%
- [wiki:self/Zope3Book/1-What-sZope What is Zope?] -- 0%
- [wiki:self/Zope3Book/1-What-sZope What is Zope?] -- 0%
Goals of this book
The main target audience for this book are developers that would like to develop on the Zope 3 framework itself; these are referred to as Zope developers in this book. But also Python program- mers will find many of the chapters interesting, since they introduce concepts that could be used in other Python applications as well. Python programmers could also use this book as an introduc- tion to Zope.
In general the chapters have been arranged in a way so that the Zope 3 structure itself could be easily understood. The book starts out by getting you setup, so that you can evaluate and develop with Zope 3. The second part of the book consists of chapters that are meant as introductions to various important concepts of Zope 3. If you are a hands-on developer like me, you might want to skip this part until you have done some development. The third and fourth part are the heart of the book, since a new content component with many features is developed over a course of 12 chapters.
Once you understand how to develop content components, part five has a set of chapters that introduce other components that might be important for your projects. The fifth part is intended for people that wish to use Zope technologies outside of Zope 3. The emphasis on testing is one of the most important philosophical transitions the Zope 3 development team has undergone. Thus the last chapter is dedicated to various ways to write tests.
Last but not least this book should encourage you to start helping us to develop Zope 3. This could be in the form of enhancing the Zope 3 core itself or by developing third party products, reaching from new content objects to entire applications, such as an e-commerce system. This book covers all the modules and packages required for you to start developing.