appypod-rattail/pod/test
2009-10-18 14:52:27 +02:00
..
contexts Fixed bug #394258 and added a new skin directly within Appy, such that every generated product does not need to include copies of Appy images and web pages. 2009-10-18 14:52:27 +02:00
images Initial import 2009-06-29 14:06:01 +02:00
results Fixed bug #394258 and added a new skin directly within Appy, such that every generated product does not need to include copies of Appy images and web pages. 2009-10-18 14:52:27 +02:00
templates Fixed bug #394258 and added a new skin directly within Appy, such that every generated product does not need to include copies of Appy images and web pages. 2009-10-18 14:52:27 +02:00
__init__.py Initial import 2009-06-29 14:06:01 +02:00
Readme.txt Initial import 2009-06-29 14:06:01 +02:00
Tester.py Initial import 2009-06-29 14:06:01 +02:00
Tests.rtf Fixed bug #394258 and added a new skin directly within Appy, such that every generated product does not need to include copies of Appy images and web pages. 2009-10-18 14:52:27 +02: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 !