[Zope3-checkins] CVS: Zope3/doc - CHANGES.txt:1.491 CREDITS.txt:1.19 DEBUG.txt:1.6 FTEST.txt:1.3 LOGGING.txt:1.14 ROADMAP.txt:1.7 TODO.txt:1.11 TODOLATER.txt:1.3 UNITTEST.txt:1.6
Anthony Baxter
anthony@interlink.com.au
Mon, 14 Jul 2003 09:31:57 -0400
Update of /cvs-repository/Zope3/doc
In directory cvs.zope.org:/tmp/cvs-serv7204/doc
Modified Files:
CHANGES.txt CREDITS.txt DEBUG.txt FTEST.txt LOGGING.txt
ROADMAP.txt TODO.txt TODOLATER.txt UNITTEST.txt
Log Message:
speling-geddon.
if you don't know how to spell a word, use the dictionary ;)
=== Zope3/doc/CHANGES.txt 1.490 => 1.491 ===
--- Zope3/doc/CHANGES.txt:1.490 Mon Jun 30 16:22:28 2003
+++ Zope3/doc/CHANGES.txt Mon Jul 14 09:31:16 2003
@@ -42,7 +42,7 @@
'c'.
Also defined and registered an adapter named 'zope', that
- provides a number of handy functions. For example, to gewt an
+ provides a number of handy functions. For example, to get an
object's name, use::
someobject/zope:name
@@ -87,7 +87,7 @@
The interface service will someday provide a tool for browsing
and modifying all of the configurations for a interface (type).
- The initial version demostrates browsing component configurations
+ The initial version demonstrates browsing component configurations
be showing you all views configured for an interface.
- WebDAV:
@@ -142,7 +142,7 @@
- FTP Support
- - PUT support (Allowing editing with Mozolla/Netscape Composer and
+ - PUT support (Allowing editing with Mozilla/Netscape Composer and
Amaya).
- Partial WebDAV support
@@ -165,7 +165,7 @@
- Views on exceptions.
- Much thanks to everone who contributed to this release:
+ Much thanks to everyone who contributed to this release:
Alan Runyan, Albertas Agejevas, Alexander Limi, Andreas Jung,
Anthony Baxter, Axel Bringenberg, Barry Warsaw, Bruce Eckel,
=== Zope3/doc/CREDITS.txt 1.18 => 1.19 ===
--- Zope3/doc/CREDITS.txt:1.18 Mon Jun 30 16:16:48 2003
+++ Zope3/doc/CREDITS.txt Mon Jul 14 09:31:16 2003
@@ -17,7 +17,7 @@
was instrumental in helping us figure out this format and
teaching me the XP process.
-- Chris Wither's and NIP hosted the first European sprint in
+- Chris Withers and NIP hosted the first European sprint in
London in February 2002.
- Alastair Burt hosted a workflow sprint in Saarbruecken, Germany,
@@ -69,7 +69,7 @@
- Steve Alexander
Providing much technical leadership and documentation in the TUV
- securiry certification effort.
+ security certification effort.
Provided major improvements to the implementation of context
wrappers, context descriptors, and worked out the decorator ideas.
@@ -86,7 +86,7 @@
are declared.
Created (with Marius) a framework, within the registration framework
- for dealing with the common case of objects registered soley by
+ for dealing with the common case of objects registered solely by
name.
Created (with Martijn Faassen) the schemagen system for generating
@@ -129,9 +129,9 @@
Did a lot of early implementation work for supporting FTP and
WebDAV.
- Ported (with folks from Coideworks) DTML to Zope 3.
+ Ported (with folks from Codeworks) DTML to Zope 3.
- Much work on the RDB-Connection and SQL-method frameworks and implementstion.
+ Much work on the RDB-Connection and SQL-method frameworks and implementation.
Worked with Shane on early server implementations.
@@ -154,7 +154,7 @@
on ideas from the Zope 2 caching framework.
Created (with Steve) a framework, within the registration framework
- for dealing with the common case of objects registered soley by
+ for dealing with the common case of objects registered solely by
name.
Helped Steve on much of the context-wrapper and decorator work.
@@ -173,7 +173,7 @@
zope3-checkins@zope.org and formats a summary of checkin messages as
a Mozilla sidebar or an RSS feed.
- Much work on the RDB-Connection and SQL-method frameworks and implementstion.
+ Much work on the RDB-Connection and SQL-method frameworks and implementation.
Numerous bug fixes and cleanups.
@@ -186,7 +186,7 @@
Implemented (with others from Codeworks) the Cache framework based
on ideas from the Zope 2 caching framework.
- Much work on the RDB-Connection and SQL-method frameworks and implementstion.
+ Much work on the RDB-Connection and SQL-method frameworks and implementation.
Added named-adapter support to the local adapter service.
@@ -198,7 +198,7 @@
Working (with others at Codeworks) on a new mail service.
- Much work on the RDB-Connection and SQL-method frameworks and implementstion.
+ Much work on the RDB-Connection and SQL-method frameworks and implementation.
Implemented (with others from Codeworks) the Cache framework based
on ideas from the Zope 2 caching framework.
@@ -230,7 +230,7 @@
Implemented security proxies (with Fred).
- Added initial bootstraping implementation to install standard
+ Added initial bootstrapping implementation to install standard
services in the root folder.
Integrated the Python logging module.
@@ -384,7 +384,7 @@
- Tres Seaver
- Built much of the earliest Zope 3 infrustructure.
+ Built much of the earliest Zope 3 infrastructure.
Created the NewsSite demonstration product.
@@ -418,7 +418,7 @@
Helped out on the NewsSite demo.
- Added support for tracking object creators as dublin-core meta data.
+ Added support for tracking object creators as Dublin-core meta data.
Added a type-conversion framework for use with database adapters.
@@ -434,7 +434,7 @@
- Alan Runyan
- Made RDB search result accessable in ZPT.
+ Made RDB search result accessible in ZPT.
A number of bug fixes and cleanups.
@@ -463,7 +463,7 @@
Implemented the initial principal-role management view.
- Contibuted to the translation service and implemented a translation
+ Contributed to the translation service and implemented a translation
service for Zope 2.
A number of bug fixes and cleanups.
@@ -510,7 +510,7 @@
- Deb Hazarika and S. Raju
- Filled out the initial file-system synchroniozation prototype.
+ Filled out the initial file-system synchronization prototype.
- Paul Winkler
@@ -670,7 +670,7 @@
o The folks at Codeworks, Albertas Agejevas, Marius Gedminas, and
Viktorija Zaksiene and contributed major parts of Zope, especially
- the relational database support and caching infrustructure. Much
+ the relational database support and caching infrastructure. Much
thanks to M Carling for making their time available.
o Much thanks to Alexander Limi, Alan Runyan, Godefroid Chapelle,
=== Zope3/doc/DEBUG.txt 1.5 => 1.6 ===
--- Zope3/doc/DEBUG.txt:1.5 Wed May 14 06:44:46 2003
+++ Zope3/doc/DEBUG.txt Mon Jul 14 09:31:16 2003
@@ -3,7 +3,7 @@
Introduction
Zope3 includes a mechanism to debug an object publishing request,
- similiar to the Zope2
+ similar to the Zope2
"debug mechanism":http://www.zope.org/Members/mcdonc/HowTos/UsingTheZopeDebugger
Setting up Environment
@@ -36,7 +36,7 @@
Run
The 'run' method executes a request with the publisher's normal
- error handling disabled and without outputing anything. This is
+ error handling disabled and without outputting anything. This is
useful for use with Python's post-mortem.
>> app.run(path='/folder/content_object')
@@ -47,7 +47,7 @@
Debug
The 'debug' method starts up the publisher in the python
- debugger, with an extra convience break point, setup just before
+ debugger, with an extra convenience break point, setup just before
the published object call::
>> app.debug(path='/folder/content_object')
@@ -61,7 +61,7 @@
- path - the url path to debug
- - basic - user:password used for http basic auth (it will be
+ - basic - user:password used for HTTP basic auth (it will be
base64 encoded by the debug method).
Accessing objects (without the debugger)
@@ -77,5 +77,5 @@
print list(root)
Also note that, after initializing the application, by creating
- the root object, you can access any global services setup diring
+ the root object, you can access any global services setup during
initialization.
=== Zope3/doc/FTEST.txt 1.2 => 1.3 ===
--- Zope3/doc/FTEST.txt:1.2 Thu May 22 12:33:28 2003
+++ Zope3/doc/FTEST.txt Mon Jul 14 09:31:16 2003
@@ -2,7 +2,7 @@
How to run Zope 3 functional tests
- In the toplevel directory, run "python test.py -f". If you've read
+ In the top-level directory, run "python test.py -f". If you've read
UNITTEST.txt you'll notice that the same script is used, but with an
additional argument '-f'. That's because in Zope 3 functional tests are
just a special case of unit tests. The rest of test.py options work as
@@ -41,7 +41,7 @@
- Functional test cases inherit from zope.functional.FunctionalTestCase
or zope.functional.BrowserTestCase instead of unittest.TestCase.
- - All global services, components etc. defined in assored configure.zcml
+ - All global services, components etc. defined in assorted configure.zcml
are available during test run time.
- A volatile in-memory storage with an empty root folder and all essential
=== Zope3/doc/LOGGING.txt 1.13 => 1.14 ===
--- Zope3/doc/LOGGING.txt:1.13 Thu Jun 26 10:10:28 2003
+++ Zope3/doc/LOGGING.txt Mon Jul 14 09:31:16 2003
@@ -139,7 +139,7 @@
we won't discuss further here.
Logger objects are lightweight and cached by the logging module;
- subseqent calls to logging.getLogger() with the same logger name
+ subsequent calls to logging.getLogger() with the same logger name
will return the same logger object. However, there is no way to
delete logger objects, so it's not a good idea to make up arbitrary
logger names dynamically.
=== Zope3/doc/ROADMAP.txt 1.6 => 1.7 ===
--- Zope3/doc/ROADMAP.txt:1.6 Thu Jun 26 10:53:16 2003
+++ Zope3/doc/ROADMAP.txt Mon Jul 14 09:31:16 2003
@@ -1,6 +1,6 @@
Zope Road Map
- This file lists fratures planned for future releases. It is roughly
+ This file lists features planned for future releases. It is roughly
the compliment of CHANGES.txt. Over time, entries from this file
will migrate to CHANGES.txt and then to HISTORY.txt.
@@ -35,7 +35,7 @@
- A flexible and pluggable authentication service.
- Interface service, for browsing and changing configuration
- by interface. This will include focussed browsing and
+ by interface. This will include focused browsing and
configuration of "content types".
- A file-system synchronization system. Initially, this will
=== Zope3/doc/TODO.txt 1.10 => 1.11 ===
--- Zope3/doc/TODO.txt:1.10 Fri Jun 27 10:36:56 2003
+++ Zope3/doc/TODO.txt Mon Jul 14 09:31:16 2003
@@ -15,7 +15,7 @@
- Implement a local permission service (using configurations)
- Rethink the organization of the security software to reflect the
- fact that people will likley plug in different grant and owndership
+ fact that people will likely plug in different grant and ownership
systems for different security policies.
* Document the relationship between the security policy and the
@@ -54,7 +54,7 @@
Maybe do something similar w annotations.
* Maybe do some more xmlpickle refinement with an eye toward
- impproving the usability of simple dictionary pickles.
+ improving the usability of simple dictionary pickles.
* export and import as a special case
@@ -108,7 +108,7 @@
* Undo everybody
- * Undo optionally takes place into acount.
+ * Undo optionally takes place into account.
* Should be an undo last.
@@ -150,9 +150,9 @@
- Finish "process control", specifically shutting down and restarting
via the web. The main issue here is plumbing. How to get the
signal from the UI to the server logic. The way to do this is via
- events. The UI should generate some sort of ShutwornRequest event
- and code in the server should be subscribed. Care needs to be taked
- to assure that only privaledged users can generate these events.
+ events. The UI should generate some sort of ShutdownRequest event
+ and code in the server should be subscribed. Care needs to be taken
+ to assure that only privileged users can generate these events.
- Help System?
@@ -171,7 +171,7 @@
See http://collector.zope.org/Zope3-dev/109
This requires a hook in the ZODB that Zope can override.
-- Python scipts
+- Python scripts
What form should these take? Should they be like Zope 2 Python
scripts? or should they by like Python modules.
@@ -202,7 +202,7 @@
- Mailing service
Mail sending service that integrates with Zope 3 transactions and
- only sends out email on successfull commits (and no multiple emails
+ only sends out email on successful commits (and no multiple emails
on ConflictErrors), is asynchronous (does not force the user to wait
until the mail is completely sent) and reliable (does not lose mail
on crashes, keeps a queue that can survive server restarts).
=== Zope3/doc/TODOLATER.txt 1.2 => 1.3 ===
--- Zope3/doc/TODOLATER.txt:1.2 Thu Jun 26 10:49:09 2003
+++ Zope3/doc/TODOLATER.txt Mon Jul 14 09:31:16 2003
@@ -5,7 +5,7 @@
too many other things to do. We *are* committed to adding this
eventually.
-- Support for permission catagories in the security model. No
+- Support for permission categories in the security model. No
one has been interested in working on this and, at this point,
there are too many other things to do. We *are* committed to
adding this eventually assuming that it becomes necessary due
@@ -19,7 +19,7 @@
It's sometimes hard to tell where the pieces that make up a
page come from. We'll investigate:
- - Leaving TAL and METAL markup in the ooutput, and
+ - Leaving TAL and METAL markup in the output, and
- Including special source attributes that record locations
of objects used in expressions.
=== Zope3/doc/UNITTEST.txt 1.5 => 1.6 ===
--- Zope3/doc/UNITTEST.txt:1.5 Tue Dec 31 16:49:21 2002
+++ Zope3/doc/UNITTEST.txt Mon Jul 14 09:31:16 2003
@@ -2,7 +2,7 @@
How to run Zope 3 unit tests
- In the toplevel directory, run "python test.py". This runs all unit
+ In the top level directory, run "python test.py". This runs all unit
tests silently (unless errors occur). It is possible to run the
tests more verbosely or to be more selective about which tests to
run. There are also other options. For information about all this,
@@ -66,7 +66,7 @@
written. A short, healthy cycle of "code/write test/run
test/repeat" can help a developer code more quickly by reducing
"backtracking" effort and by helping the developer focus on the
- actual problem at hand. Additonally, the unit tests generated at
+ actual problem at hand. Additionally, the unit tests generated at
initial development time can serve as later assurance that
maintenance and refactoring performed on code does not break any of
its intended functionality or behavior. The results of unit tests
@@ -82,7 +82,7 @@
Writing unit tests post-facto can be boring and also robs you of the
main benefits that unit testing can provide. Writing unit tests at
the same time you write the code helps you focus on the task at
- hand. Writing unit tests in conjuction with code can be fun and
+ hand. Writing unit tests in conjunction with code can be fun and
satisfying, and can help you improve the quality of your code while
its goals are fresh in your mind. Used properly, unit testing may
also help you write code faster, because you will need to
@@ -111,7 +111,7 @@
name of the unit test that failed.
"It is better to have tried to test and failed than to not have
- tried to test at all" aka "test the riskist things first." If the
+ tried to test at all" aka "test the riskiest things first." If the
prospect of writing a series of unit tests for an existing system
seems daunting, it's important to remember that no matter how many
unit tests you write, you cannot prove that your software does not
@@ -192,7 +192,7 @@
in some cases depends on state provided only in the context of a web
request, so calling Zope methods directly may not work as you
expect. If you're not intimately familiar with Zope, implementing
- unit tests can be fustrating. For example, for the common case,
+ unit tests can be frustrating. For example, for the common case,
before you are able to write code which tests a Zope SQL Method, you
must establish a test fixture which represents your entire Zope
site.
@@ -228,7 +228,7 @@
Beck).
Unit testing is a primary tenet of "Extreme Programming", a software
- development methodology designed to faciliate the rapid production
+ development methodology designed to facilitate the rapid production
of high quality code with a minimum of developmental ceremony. For
more information on unit tests as they relate to Extreme
Programming, see http://c2.com/cgi/wiki?UnitTestsDefined. Although