Difference between revisions of "Documentation/DevGuide/AppendixA/OpenOffice.org API-Design-Guidelines"
From Apache OpenOffice Wiki
< Documentation | DevGuide
OOoWikiBot (Talk | contribs) m (Robot: Changing Category:Documentation/Developers Guide/Appendix) |
m |
||
Line 4: | Line 4: | ||
|NextPage=Documentation/DevGuide/AppendixA/General Design Rules | |NextPage=Documentation/DevGuide/AppendixA/General Design Rules | ||
}} | }} | ||
+ | [[zh:Zh/Documentation/DevGuide/AppendixA/OpenOffice.org API-Design-Guidelines]] | ||
{{DISPLAYTITLE:Appendix A: {{PRODUCTNAME}} API-Design-Guidelines}} | {{DISPLAYTITLE:Appendix A: {{PRODUCTNAME}} API-Design-Guidelines}} | ||
The following rules apply to all external programming interface specifications for OpenOffice. The API consists of the following stereotypes or design elements: | The following rules apply to all external programming interface specifications for OpenOffice. The API consists of the following stereotypes or design elements: |
Revision as of 02:56, 18 June 2008
- OpenOffice.org API-Design-Guidelines
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). |