Slides

Meeting 36: Processing XML with ElementTree (Andrew Kuchling)

Presentation: ElementTree provides a simple library for processing XML that feels natural to Python programmers. This talk is a 45-minute tutorial showing how to perform basic tasks with ElementTree.

Meeting 37: Using XMLRPCLIB and Plone (Matt Kromer)

One of the lesser-known features of Zope is that it supports XMLRPC directly. In fact, XMLRPC can be used to talk to any object in the system.

Meeting 39-and-a-half: Plone Performance and Caching (Joel Burton)

Plone Performance and Caching

Meeting 42: Intermediate ArchGenXML: creating a facilities tracking website (David Griesen)

Intermediate ArchGenXML: creating a facilities tracking website. This presentation builds on Chris' June 6th meeting, introducing ArchGenXML's product and workflow code generation capabilities. The basics will be briefly reviewed, in case you missed Chris' presentation, and creating tools and widgets will be introduced. Then we'll dive right in to manually editing the ArchGenXML-generated code and creating page templates, without breaking the usefulness of our UML diagram

Meeting 44: Generating Python interfaces with SWIG (Josh Cherry)

Generating Python interfaces to a large set of C++ libraries using SWIG

Meeting 49: Plone 3 (Paul Everitt)

Plone 3 for Developers

Meeting 49: Grok (Philipp von Weitershausen)

Now even cavemen can use Zope

Meeting 50: Creating a Scope of Work for a Simple Plone Website (Patrick Shaw)

100 Hours or Less: Creating a Scope of Work for a Simple Plone Website

Meeting 54: ArchGenXML/Genesis Progress (Richard Amerman)

This session will discuss Rapid Application Development with the Plone Open Source CMS. We will talk about Archetypes, ArchGenXML, and the future with Genesis. ArchGenXML allows you to model your application in UML and then process the results to auto generate an installable Plone product. We will cover enough about Archetypes to have a basic understanding of the schema that ArchGenXML creates and how you can take things further on your own

Meeting 66: Continuous Integration With Buildbot (Dustin J. Mitchell)

The BuildBot is a system to automate the compile/test cycle required by most software projects to validate code changes. By automatically rebuilding and testing the tree each time something has changed, build problems are pinpointed quickly, before other developers are inconvenienced by the failure. The guilty developer can be identified and harassed without human intervention. By running the builds on a variety of platforms, developers who do not have the facilities to test their changes everywhere before checkin will at least know shortly afterwards whether they have broken the build or not. Warning counts, lint checks, image size, compile time, and other build parameters can be tracked over time, are more visible, and are therefore easier to improve. The overall goal is to reduce tree breakage and provide a platform to run tests or code-quality checks that are too annoying or pedantic for any human to waste their time with. Developers get immediate (and potentially public) feedback about their changes, encouraging them to be more careful about testing before checkin.