Difference between revisions of "Architecture"
From Apache OpenOffice Wiki
m (→Specifications: Fixed Specifications list.) |
m (Relativated lists to "Architecture" .) |
||
Line 10: | Line 10: | ||
==Analysis== | ==Analysis== | ||
<DPL>category=Analysis</DPL> | <DPL>category=Analysis</DPL> | ||
− | ==Architectural | + | ==Architectural To-Dos== |
− | <DPL>category=Architecture</DPL> | + | <DPL>category=To-Do |
+ | category=Architecture</DPL> | ||
==Efforts== | ==Efforts== | ||
− | <DPL>category=Effort</DPL> | + | <DPL>category=Effort |
+ | category=Architecture</DPL> | ||
==Specifications== | ==Specifications== | ||
<DPL>category=Spec | <DPL>category=Spec | ||
category=Architecture</DPL> | category=Architecture</DPL> | ||
− | |||
==Proposal== | ==Proposal== | ||
− | <DPL>category=Proposal</DPL> | + | <DPL>category=Proposal |
+ | category=Architecture</DPL> |
Revision as of 17:22, 29 January 2007
As most of you know, OOo is a complex and big software system. Many lines of code are implemented in various programming languages, including BASIC, C, C++, Java, and more (perl, make, ANT, ...), if one counts the build system or tests as being part of OOo. Obviously, it is necessary to follow some kinds of guidance, rules, principles or constraints, to make it work seemingly and to make it understandable. Wikipedia gives a good understanding, of what a Software Architecture can or should be.
Contents
OpenOffice.org Software Architecture
Implementation Modules
- Autodoc
- Automation
- Basic
- Boost
- External/Modules/freetype
- External/Modules/portaudio
- External/Modules/stlport
- User:Foral/VCL
- Framework/Modules/binfilter
- Category:Module:CPPU
- Category:Module:CPPUhelper
- Porting/Modules/SAL
- Sdext
- Uno/Binary/Modules/CPPU
- Uno/Binary/Modules/CPPUtools
- Uno/Binary/Modules/STOC
- Uno/Binary/Modules/URE
- Uno/Binary/Modules/bridges
- Uno/Binary/Modules/codemaker
- Uno/Binary/Modules/idlc
- Uno/Binary/Modules/rdbmaker
- Uno/Binary/Modules/registry
- Uno/Binary/Modules/remotebridges
- Uno/Binary/Modules/testtools
- Uno/Cpp/Modules/CPPUhelper
- Uno/Cpp/Modules/SALhelper
- Uno/Java/Modules/JURT
- Uno/Java/Modules/javaunohelper
- Uno/Java/Modules/ridljar
- Util/Modules/IO
- Util/Modules/JUT
- Util/Modules/sandbox
- VCL
Module Tests
- Porting/Modules/SAL/test
- Uno/Binary/Modules/STOC/test
- Uno/Binary/Modules/bridges/test
- Uno/Binary/Modules/codemaker/test
- Uno/Binary/Modules/idlc/test
- Uno/Binary/Modules/registry/test
- Uno/Binary/Modules/testtools/test
- Uno/Cpp/Modules/CPPUhelper/test
- Uno/Cpp/Modules/SALhelper/test
- Uno/Java/Modules/JURT/test
- Uno/Java/Modules/ridljar/test
Analysis
- Analysis/Multi-Threading
- Architecture/Libraries
- Architecture/Process Flow
- Architecture/Source Code Inventory
- Auto-completion
- Uno/Binary/Analysis/String Performance
Architectural To-Dos
Efforts
- Effort/Clean Up Anachronistic Threading Constructs
- Effort/Encapsulate the Win32 thread affinity
- Effort/Implement Basic Threading-Architecture
- Effort/Make Dialogs Asynchronous
- Effort/Make VCL Thread-Transparent
- Effort/Migrate DrawingLayer
- Effort/Migrate Rendering to XCanvas
- ODF Toolkit/Efforts/Packaging Modularization
- ODF Toolkit/Efforts/Three-Layer OOo