appypod-rattail/pod/test
2011-09-15 15:55:00 +02:00
..
contexts Added missing encoding declaration. 2011-09-15 15:55:00 +02: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 appy.gen: in the default context of any pod field, added function '_' corresponding to obj.translate; appy.gen: xhtml2odt bugfix: when a <div> was contained in <ol><li> or <ul><li>, the whole function ouput was an empty string. 2011-07-07 09:43:16 +02:00
templates appy.pod: fixed bug https://bugs.launchpad.net/bugs/720270 (cell repetition). 2011-02-18 15:58:59 +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 appy.gen: added default validation for wrong dates; for Action fields, added value 'filetmp' for param 'result' for removing temp files that are returned as the result of an action; values entered by the user in the search screens are not stripped; wrapper method 'export' can now export an object in a CSV file; appy.pod: bullets for default list styles in any ODT file generated through pod are now smaller. 2011-02-12 17:09:11 +01:00
Tests.rtf appy.gen: in the default context of any pod field, added function '_' corresponding to obj.translate; appy.gen: xhtml2odt bugfix: when a <div> was contained in <ol><li> or <ul><li>, the whole function ouput was an empty string. 2011-07-07 09:43:16 +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 !