Difference between revisions of "Architecture"
From Apache OpenOffice Wiki
m |
m (Reworked.) |
||
| Line 1: | Line 1: | ||
| + | {| align=right style="margin-left: 15px; border:1px solid #aaaaaa; background-color:#f9f9f9; padding:5px; font-size: 95%;" class=box | ||
| + | |--- | ||
| + | | | ||
| + | '''''[[Architecture/To-Dos|To-Dos]]'''''<br> | ||
| + | '''''[[Modules]]''''' | ||
| + | <DPL>category=Module | ||
| + | count=2</DPL> | ||
| + | * [[Modules|...]] | ||
| + | '''''[[Architecture/Analysis|Analysis]]''''' | ||
| + | <DPL>category=Analysis | ||
| + | count=2</DPL> | ||
| + | * [[Architecture/Analysis|...]] | ||
| + | '''''[[Architecture/Efforts|Efforts]]''''' | ||
| + | <DPL>category=Effort | ||
| + | category=Architecture | ||
| + | count=2</DPL> | ||
| + | * [[Architecture/Efforts|...]] | ||
| + | '''''[[Architecture/Specifications|Specifications]]''''' | ||
| + | <DPL>category=spec | ||
| + | category=Architecture | ||
| + | count=2</DPL> | ||
| + | * [[Architecture/Specifications|...]] | ||
| + | '''''[[Architecture/Proposals|Proposals]]''''' | ||
| + | <DPL>category=Proposal | ||
| + | category=Architecture | ||
| + | count=2</DPL> | ||
| + | * [[Architecture/Proposals|...]] | ||
| + | '''''[[Architecture/Visions|Visions]]''''' | ||
| + | <DPL>category=Vision | ||
| + | category=Architecture | ||
| + | count=2</DPL> | ||
| + | * [[Architecture/Visions|...]] | ||
| + | |} | ||
| + | |||
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 OpenOffice.org|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:|Wikipedia]] gives a good understanding, of what a [[Wikipedia:Software architecture|Software Architecture]] can or should be. | 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 OpenOffice.org|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:|Wikipedia]] gives a good understanding, of what a [[Wikipedia:Software architecture|Software Architecture]] can or should be. | ||
==OpenOffice.org Software Architecture== | ==OpenOffice.org Software Architecture== | ||
[[Image:ArchOverview.jpg|center]] | [[Image:ArchOverview.jpg|center]] | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
[[Category: Software Architecture]] | [[Category: Software Architecture]] | ||
Revision as of 13:39, 30 May 2008
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.
OpenOffice.org Software Architecture
