Difference between revisions of "Documentation/DevGuide/AppendixA/OpenOffice.org API-Design-Guidelines"
From Apache OpenOffice Wiki
< Documentation | DevGuide
Line 4: | Line 4: | ||
|NextPage=Documentation/DevGuide/AppendixA/General Design Rules | |NextPage=Documentation/DevGuide/AppendixA/General Design Rules | ||
}} | }} | ||
− | + | {{Documentation/DevGuideLanguages|Documentation/DevGuide/AppendixA/{{SUBPAGETITLE}}}} | |
{{DISPLAYTITLE:Appendix A: {{PRODUCTNAME}} API-Design-Guidelines}} | {{DISPLAYTITLE:Appendix A: {{PRODUCTNAME}} API-Design-Guidelines}} | ||
{{Download Collection|MediaWiki:Collections/Developer's Guide - OpenOffice.org API-Design Guidelines}} | {{Download Collection|MediaWiki:Collections/Developer's Guide - OpenOffice.org API-Design Guidelines}} |
Revision as of 08:55, 18 May 2009
- OpenOffice.org API-Design-Guidelines
[[en:Documentation/DevGuide/AppendixA/Template:SUBPAGETITLE]] [[zh:Zh/Documentation/DevGuide/AppendixA/Template:SUBPAGETITLE]]
Download as a PDF or ODT
The following rules apply to all external programming interface specifications for OpenOffice. The API consists of the following stereotypes or design elements:
Structures
- Structures are used to specify simple composed data elements.(Structures only consist of data, not methods.)
Exceptions
- Exceptions are used for error handling.(Exceptions can be thrown or transported using an any.)
Interfaces
- Interfaces are used to specify a single aspect in behavior.(Interfaces only consist of methods, not data.)
Services
- Services are used to specify abstract objects.(Services specify properties and the interaction of the supported interfaces.)
Typedefs
- Typedefs are used to define basic types for specific purposes.(This stereotype should be used carefully.)
Content on this page is licensed under the Public Documentation License (PDL). |