Difference between revisions of "Documentation/DevGuide/ProUNO/Data Types"
OOoWikiBot (Talk | contribs) m (FINAL VERSION FOR L10N) |
m |
||
| Line 9: | Line 9: | ||
{{DISPLAYTITLE:Data Types}} | {{DISPLAYTITLE:Data Types}} | ||
<!--<idltopic>com.sun.star.uno.TypeClass</idltopic>--> | <!--<idltopic>com.sun.star.uno.TypeClass</idltopic>--> | ||
| − | The data types in the API reference are UNO types which have to be mapped to the types of any programming language that can be used with the {{ | + | The data types in the API reference are UNO types which have to be mapped to the types of any programming language that can be used with the {{AOo}} API. In [[Documentation/DevGuide/FirstSteps/First Steps|First Steps]] the most important UNO types were introduced. However, there is much more to be said about simple types, interfaces, properties and services in UNO. There are special flags, conditions and relationships between these entities which you will want to know if you are working with UNO on a professional level. |
| − | This section explains the types of the API reference from the perspective of a developer who wants to use the {{ | + | This section explains the types of the API reference from the perspective of a developer who wants to use the {{AOo}} API. If you are interested in writing your own components, and you must define new interfaces and types, please refer to the chapter [[Documentation/DevGuide/WritingUNO/Writing UNO Components|Writing UNO Components]], which describes how to write your own UNOIDL specifications and how to create UNO components. |
{{PDL1}} | {{PDL1}} | ||
[[Category:Documentation/Developer's Guide/Professional UNO]] | [[Category:Documentation/Developer's Guide/Professional UNO]] | ||
Latest revision as of 13:24, 9 December 2020
The data types in the API reference are UNO types which have to be mapped to the types of any programming language that can be used with the Apache OpenOffice API. In First Steps the most important UNO types were introduced. However, there is much more to be said about simple types, interfaces, properties and services in UNO. There are special flags, conditions and relationships between these entities which you will want to know if you are working with UNO on a professional level.
This section explains the types of the API reference from the perspective of a developer who wants to use the Apache OpenOffice API. If you are interested in writing your own components, and you must define new interfaces and types, please refer to the chapter Writing UNO Components, which describes how to write your own UNOIDL specifications and how to create UNO components.
| Content on this page is licensed under the Public Documentation License (PDL). |
