Difference between revisions of "Build Environment Effort/ToDo"

From Apache OpenOffice Wiki
Jump to: navigation, search
Line 7: Line 7:
 
* build should not modify source tree
 
* build should not modify source tree
 
** configurable place for output directories
 
** configurable place for output directories
* split build, repositories and solver
 
** tools, URE, localization, help content, non-code parts, extensions (binfilter?)
 
 
* platform independent help content
 
* platform independent help content
* remove unnecessary dependencies (e.g. xmlhelp from svtools, linguistic from sfx2 etc.)
 
 
* evaluate integration of OOo SDK and OOo build environments
 
* evaluate integration of OOo SDK and OOo build environments
 
* find a way to move out localization completely (localize only strings, not resources)
 
* find a way to move out localization completely (localize only strings, not resources)
Line 16: Line 13:
 
** which of them do we localize  
 
** which of them do we localize  
 
** find replacements for all non-string types
 
** find replacements for all non-string types
** evaluate po files for OOo
+
** do we have the best file format for localizations?
* get rid of common output trees: They cause way too much hassle with bots etc. and arent worth the trouble
+
* make pre-build parts of the solver available on a module-by-module basis
+
  
 
[[Category:To-Do]]
 
[[Category:To-Do]]

Revision as of 13:55, 12 November 2009

Edit.png

Build Environment Effort

Quick Navigation

About this template


  • create runnable instance of OOo in solver
    • solver becomes incrementally filled office tree
    • libraries can be executed from solver
    • UNO services are registered from text files
    • configurable place for solver
  • build should not modify source tree
    • configurable place for output directories
  • platform independent help content
  • evaluate integration of OOo SDK and OOo build environments
  • find a way to move out localization completely (localize only strings, not resources)
    • which resource types can be localized
    • which of them do we localize
    • find replacements for all non-string types
    • do we have the best file format for localizations?
Personal tools