when using selection_params with ReportSection,
 "listbox.get_value()" could not get selection_params from
 the SelectionTool.
 so removing whole 'render_prefix' to get selection_params.

 this bug is associated with r26403 refactoring

* Append
 - make Frames to enable "Hide and Show" according as
   FormBox 'enable' property
 - multi lines support such as Lines Field
 (TODO: unit testing)


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@26505 20353a03-c40f-0410-a6d1-a30d3c3de9de

  make ImageField-mapping-image-size-management better
  when image size is smaller than ODF frame size
  TODO: write a test


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@26419 20353a03-c40f-0410-a6d1-a30d3c3de9de

 range-reference and point-reference accepts unicode string
 as well as utf-8 string

* Modify:
 using restrictedTraverse when ImageField mapping for
 better security
  


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@26405 20353a03-c40f-0410-a6d1-a30d3c3de9de

  When ReportSection list are zero length,
  must remove the mapped frame in a ODF file.

  So that this specification, appending a limitation to
  the ReportSection mapping function. 
  The feature in the FormPrintout accepts only one form 
  in a ReportMethod. 
  You can not set two or more forms in the ReportMethod
  when using FormPrintout.

* Refactoring
  remove unused argument; render_prefix



git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@26403 20353a03-c40f-0410-a6d1-a30d3c3de9de

  if listbox has no data line, must not have table rows

* Append:
  ReportSection and ImageField mapping features
  TODO: write their unit test



git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@26389 20353a03-c40f-0410-a6d1-a30d3c3de9de

 - set 'View' permission to index_html method as well as r26362
 - when just call FormPrintout from Python script or python code,
   must not set RESPONSE headers



git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@26363 20353a03-c40f-0410-a6d1-a30d3c3de9de

Fix a misuse of the Zope Core Permissions.


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@26362 20353a03-c40f-0410-a6d1-a30d3c3de9de

 - point-reference to a paragraph mapping failed non-ascii value
 - the XML could not encoding 'utf-8', but displayes escaped 
   unicode charactor

* Append:
  range-reference to strings mapping


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@26361 20353a03-c40f-0410-a6d1-a30d3c3de9de

git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@26345 20353a03-c40f-0410-a6d1-a30d3c3de9de

  transform DateTime object into ODF acceptable format
  '2009/04/20' -> '2009-04-20'

* Append
  test cases which confirm fixing the bugs

* Refactoring
  - change method name into mixedCase, according to 
    the naming convention
  - using etree nsmap object instead of to define 
    the namespace-dictionary constant
  - the long test method devide into appropriate
    some methods



git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@26344 20353a03-c40f-0410-a6d1-a30d3c3de9de

  remove the DefaultValue feature because it did not consider localization


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@26318 20353a03-c40f-0410-a6d1-a30d3c3de9de

  - copy last-table-row-style when stat method or stat columns does not set
  - clean table-columns-value before listbox values setting
* Append
  the DefaultValue is the marker class indicate to use a ODF Template value



git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@26314 20353a03-c40f-0410-a6d1-a30d3c3de9de

  table last row could not set blank value


git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@26307 20353a03-c40f-0410-a6d1-a30d3c3de9de

* Append functions
  - styles.xml support
  - experimental FormBox support
  - experimental ReportSection support
* Fix 
  the table column attribute name was wrong



git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@26306 20353a03-c40f-0410-a6d1-a30d3c3de9de

using an ERP5 Form and an ODF template.

I and yo had long discussion, whether to invoke
an ODF template or an ERP5 form.
We selected an ERP5 Form to invoke, but because of 
some point of view, we changed the choice and decided
to create a new class to invoke to create a ODF document.

Why we decided to create a new class:

* Reusable of forms 
  If we invoke an ERP5 form to create an ODF document, we have to
  set a ODF template, and the view of the form fixes ODF.
  Thus the form can not use other cases such as html view.
  
* Consistency 
  Set a ODF template as well as page template, the forms has
  two ways two template. It has not consistency.

The Form Printout currently supports only ODT format document.
And the functions only supports paragraphs and tables.



git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@26251 20353a03-c40f-0410-a6d1-a30d3c3de9de