appypod-rattail/pod/test
2010-02-09 15:59:03 +01:00
..
contexts Added the possibility to log OO errors in appy.gen method File.dump and changed some code for avoiding silly Plone warnings on every user click. 2010-02-09 15:59:03 +01:00
images Added the possibility to log OO errors in appy.gen method File.dump and changed some code for avoiding silly Plone warnings on every user click. 2010-02-09 15:59:03 +01:00
results Added the possibility to log OO errors in appy.gen method File.dump and changed some code for avoiding silly Plone warnings on every user click. 2010-02-09 15:59:03 +01:00
templates Added the possibility to log OO errors in appy.gen method File.dump and changed some code for avoiding silly Plone warnings on every user click. 2010-02-09 15:59:03 +01:00
__init__.py Added the possibility to log OO errors in appy.gen method File.dump and changed some code for avoiding silly Plone warnings on every user click. 2010-02-09 15:59:03 +01:00
Readme.txt Added the possibility to log OO errors in appy.gen method File.dump and changed some code for avoiding silly Plone warnings on every user click. 2010-02-09 15:59:03 +01:00
Tester.py Added the possibility to log OO errors in appy.gen method File.dump and changed some code for avoiding silly Plone warnings on every user click. 2010-02-09 15:59:03 +01:00
Tests.rtf Added the possibility to log OO errors in appy.gen method File.dump and changed some code for avoiding silly Plone warnings on every user click. 2010-02-09 15:59:03 +01:00

Here you will find some ODT documents that are POD templates.

A POD template is a standard ODT file, where:
 - notes are used to insert Python-based code for telling POD to render
   a portion of the document zero, one or more times ("if" and "for" statements);
 - text insertions in "track changes" mode are interpreted as Python expressions.

When you invoke the tester.py program with one of those ODT files as unique parameter
(ie "python tester.py ForCellOnlyOne.odt"), you get a result.odt file which is the
result of executing the template with a bunch of Python objects. The "tests" dictionary
defined in tester.py contains the objects that are given to each POD ODT template
contained in this folder.

Opening the templates with OpenOffice (2.0 or higher), running tester.py on it and
checking the result in result.odt is probably the quickest way to have a good idea
of what appy.pod can make for you !