appypod-rattail/pod/test
2013-09-23 22:36:09 +02:00
..
contexts [gen] First draft of using POD ODS (Calc) templates. 2013-01-31 00:11:24 +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 [pod,px] Allow to reference an already defined variable instead of defining one in a var statement, via the '@' prefix. For example, in PX: var='@i = i + 1'. [pod] Repaired broken tests [gen] Bugfixes. 2013-09-23 22:36:09 +02:00
templates [gen] Wrapper.reindex: allow to specify attribute 'fields' containing the list of fields that must be reindexed. If not given, all object fields are reindexed. [pod] POD ODS templates: into POD results from ODS templates, Python expressions that produce ints, floats or dates (Zope DateTime only for the moment) produce cells with typed values. 2013-02-06 17:15:01 +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 Reworked AJAX framework with a lot of new sorting and filtering possibilities. 2010-04-30 12:05:29 +02:00
Tester.py Updated 'print' statements throughout Appy code, in order to be Python3x as well as Python2x-compliant. 2013-05-30 00:46:11 +02:00
Tests.rtf [pod,px] Allow to reference an already defined variable instead of defining one in a var statement, via the '@' prefix. For example, in PX: var='@i = i + 1'. [pod] Repaired broken tests [gen] Bugfixes. 2013-09-23 22:36:09 +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 run 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 !