A number of important discussions and explanations have transpired on the PEAK mailing list. Phillip Eby, the creator, architect, and primary developer of PEAK, often goes into great detail when responding to questions about PEAK, and also from time to time shares his thoughts on where PEAK is headed. This page collects a number of these posts to the mailing list in the hope that they will help others understand PEAK better in light of the current lack of documentation.
PWT: layout, macros, parameters, etc. pje 19-Oct-2004
Traversal, views, and templates = PWT, Reloaded pje 16-Oct-2004
peak.web in October pje 05-Oct-2004
followup pje 22-Oct-2004
Traversal, views, and templates = PWT, Reloaded pje 22-Aug-2004
Resources and traversal in peak.web pje 21-Aug-2004
More PWT Ideas (usage, not terminology!) pje 22-Jul-2003
PROPOSAL: New peak.web.template terminology/explanation pje 21-Jul-2003
Towards a GUI facility for PEAK pje 05-Dec-2004
And so it begins... (generic function migration) pje 11-Nov-2004
Towards a query theory, part 1: filters and correlation pje 10/12/03
TableDM proof of concept, request for comments John Landahl 10/9/03
followup pje 10/9/03
followup Ulrich Eck 10/9/03
ideas on object querying pje 10/9/03
further ideas on object querying pje 10/9/03
The new binding API names pje 9/4/03
Proposed peak.binding API change pje 9/2/03
followup pje 9/3/03
followup Ty Sarna 9/3/03
followup pje 9/3/03
followup Ty Sarna 9/3/03
followup pje 9/3/03
Multiple loggers pje 8/19/03
peak.running.logs pje 8/19/03
how to build a dynamic component container? Matthias Drochner 8/18/03
followup pje 8/18/03
followup pje 8/19/03
component path - property name dualism, does this make sense? Matthias Drochner 8/18/03
followup pje 8/18/03
followup pje 8/18/03
followup pje 8/19/03
followup pje 8/19/03
Pre-forking event-driven services pje 8/15/03
Use cases/design goals/scope for peak.web forms (part 1) pje 8/11/03
layout framework, and thoughts on DOMlet data specifiers pje 8/8/03
State of the Onion (updates to current release plans) pje 8/7/03
followup re: web forms Roch Compaan 8/8/03
followup pje 8/8/03
followup Roch Compaan 8/9/03
peak.web.forms (was re: State of the Onion) pje 8/9/03
followup Roch Compaan 8/9/03
followup pje 8/9/03
followup Roch Compaan 8/10/03
followup pje 8/10/03
Authentication services, specialists, and rules-checking pje 8/7/03
Error handling in peak.web pje 8/4/03
peak.web and forms Roch Compaan 8/4/03
Resource directories, file extensions, etc. pje 7/31/03
Binding templates and resources pje 7/29/03
Constraints on model attributes pje 7/26/03
Peer service discovery in PEAK pje 7/23/03
Template parsing and XML/HTML processing design pje 7/19/03
followup pje 7/20/03
followup Jean Jordaan 7/21/03
followup Roch Compaan 7/21/03
followup Jean Jordaan 7/21/03
followup pje 7/21/03
followup pje 7/21/03
followup pje 7/21/03
followup pje 7/21/03
followup Ty Sarna 7/21/03
Components + existing classes pje 7/18/03
Please don't advocate PEAK pje 7/16/03
Example of composing component hierarchies in Wiki Joel Boehland 7/15/03
The return of naming.Reference() pje 7/15/03
Some notes on peak.web templating, etc. pje 7/14/03
followup pje 7/18/03
followup pje 7/18/03
twistedpeak echoserver example Joel Boehland 7/11/03
runIni => ZConfig pje 7/11/03
Functionality Gaps pje 7/8/03
On the requirements for "Assembly Events" pje 4/28/03
Explicit is better than implicit pje 4/24/03
Building PEAK apps with Zope X3 pje 4/3/03
followup pje 4/4/03
followup pje 4/9/03
PEAK binding & naming howto pje 3/6/03
simple application skeleton? pje 3/4/03
PEAK Applications Code and Concepts pje 2/26/03
making progress - examples in cvs Ulrich Eck 2/21/03
followup pje 2/21/03
component config info pje 2/10/03
Use case outline - *very* raw first draft pje 12/12/02