Difference between revisions of "Extensions repository/Creative Commons/TODO"

From Apache OpenOffice Wiki
Jump to: navigation, search
 
 
(3 intermediate revisions by one other user not shown)
Line 1: Line 1:
 
 
== Code layout and tools ==
 
== Code layout and tools ==
* decide code/directories layout before commiting first code, because CVS does not allow moving files
+
* decide code/directories layout before commiting first code, because CVS does not allow moving files '''[DONE]'''
* decide Java package names (proposal: org.openoffice.extensions.creativecommons as base package name)
+
* decide Java package names (proposal: org.openoffice.extensions.creativecommons as base package name) '''[DONE]'''
* decide which tools to use (netbeans? eclipse? ant?)
+
* decide which tools to use (netbeans? eclipse? ant?) '''[DONE]'''
 +
** Ant
 +
** eclipse can use the Ant build file
  
 
== Creative Commons web api ==
 
== Creative Commons web api ==
 
* first implementation is working
 
* first implementation is working
 
* TODO: add caching if no network available
 
* TODO: add caching if no network available
 +
** save LicenseSet object as XML in home directory and reload it from saved
  
 
== License selection dialog ==
 
== License selection dialog ==
Line 18: Line 20:
 
== License information display ==
 
== License information display ==
 
* should we add a new "special field" (like date...) that can be added in the document and that contains licensing information
 
* should we add a new "special field" (like date...) that can be added in the document and that contains licensing information
 +
[[Category:Extensions]]

Latest revision as of 17:32, 8 March 2010

Code layout and tools

  • decide code/directories layout before commiting first code, because CVS does not allow moving files [DONE]
  • decide Java package names (proposal: org.openoffice.extensions.creativecommons as base package name) [DONE]
  • decide which tools to use (netbeans? eclipse? ant?) [DONE]
    • Ant
    • eclipse can use the Ant build file

Creative Commons web api

  • first implementation is working
  • TODO: add caching if no network available
    • save LicenseSet object as XML in home directory and reload it from saved

License selection dialog

  • to be implemented

License metadata integration

  • where to put license metadata in ODF?
  • license metadata export to other formats (.doc, .pdf)

License information display

  • should we add a new "special field" (like date...) that can be added in the document and that contains licensing information
Personal tools