An error occurred fetching the project authors.
- 20 Apr, 2009 4 commits
-
-
Tatuya Kamada authored
- modify comments - append a ImageField mapping test skelton git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@26510 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
Tatuya Kamada authored
- fix the address in the GPL - append XML validation git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@26509 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
Tatuya Kamada authored
- append XML validation - append comments to report section test git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@26507 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
Tatuya Kamada authored
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
-
- 14 Apr, 2009 1 commit
-
-
Tatuya Kamada authored
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
-
- 13 Apr, 2009 1 commit
-
-
Tatuya Kamada authored
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
-
- 10 Apr, 2009 1 commit
-
-
Tatuya Kamada authored
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
-
- 09 Apr, 2009 3 commits
-
-
Tatuya Kamada authored
r26363 the way of RESPONSE header test was wrong, fix it git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@26364 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
Tatuya Kamada authored
- 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
-
Tatuya Kamada authored
- 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
-
- 08 Apr, 2009 2 commits
-
-
Tatuya Kamada authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@26345 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
Tatuya Kamada authored
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
-
- 07 Apr, 2009 1 commit
-
-
Tatuya Kamada authored
* 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
-
- 02 Apr, 2009 2 commits
-
-
Tatuya Kamada authored
git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@26253 20353a03-c40f-0410-a6d1-a30d3c3de9de
-
Tatuya Kamada authored
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
-