Appendix A: API-Design-Guidelines

From Apache OpenOffice Wiki
< Documentation‎ | DevGuide
Revision as of 08:56, 18 May 2009 by Ccornell (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

PDF Icon.gif 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 are used to specify simple composed data elements.(Structures only consist of data, not methods.)


Exceptions are used for error handling.(Exceptions can be thrown or transported using an any.)


Interfaces are used to specify a single aspect in behavior.(Interfaces only consist of methods, not data.)


Services are used to specify abstract objects.(Services specify properties and the interaction of the supported interfaces.)


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).
Personal tools
In other languages