An error occurred fetching the project authors.
  1. 03 Dec, 2009 3 commits
  2. 02 Dec, 2009 2 commits
  3. 26 Nov, 2009 1 commit
  4. 25 Nov, 2009 1 commit
  5. 20 Nov, 2009 1 commit
  6. 18 Nov, 2009 1 commit
  7. 05 Nov, 2009 1 commit
  8. 07 Oct, 2009 1 commit
  9. 06 Oct, 2009 1 commit
  10. 07 May, 2009 2 commits
  11. 30 Apr, 2009 1 commit
  12. 28 Apr, 2009 1 commit
  13. 27 Apr, 2009 1 commit
    • Tatuya Kamada's avatar
      * Fix · b32693fd
      Tatuya Kamada authored
       - LinesField via point-reference did not work,
         because it looked wrong node
       - LinesField insert order was wrong, it was reversed
      
      * Append
       replacing some control charactors such as 
       tabs and line-breaks
       
      
      
      git-svn-id: https://svn.erp5.org/repos/public/erp5/trunk@26637 20353a03-c40f-0410-a6d1-a30d3c3de9de
      b32693fd
  14. 24 Apr, 2009 3 commits
  15. 23 Apr, 2009 1 commit
  16. 22 Apr, 2009 1 commit
  17. 20 Apr, 2009 2 commits
  18. 15 Apr, 2009 1 commit
  19. 14 Apr, 2009 1 commit
  20. 13 Apr, 2009 1 commit
    • Tatuya Kamada's avatar
      * Fix · d2ddbb95
      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
      d2ddbb95
  21. 10 Apr, 2009 1 commit
  22. 09 Apr, 2009 3 commits
  23. 08 Apr, 2009 2 commits
  24. 07 Apr, 2009 4 commits
  25. 02 Apr, 2009 1 commit
    • Tatuya Kamada's avatar
      The Form Printout enables to create a ODF document, · 0ad69af5
      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
      0ad69af5