Difference between revisions of "Add-on"
SergeMoutou (Talk | contribs) m (New page: =Introduction= Because we have already encountered components and [[|addin]] in a next chapter we give directly the schematic of the addon example in the SDK. [[Image:FirstAddon.png|c...) |
|||
| (16 intermediate revisions by 2 users not shown) | |||
| Line 1: | Line 1: | ||
| + | {{Warn|This Chapter is under construction. Please be patient...}} | ||
=Introduction= | =Introduction= | ||
| − | Because we have already encountered [[components]] and [[addin]] in a next chapter we give directly the schematic of the addon example in the SDK. | + | Add-on are tackled also in [[Documentation/DevGuide/WritingUNO/AddOns/Add-Ons|Developer's Guide]]. |
| + | |||
| + | The addon are like [[Constructing_Components|components]] but they don't add a particular interface. To put it differently they need no IDL file for their construction. Then, if you want to call an addon only menus are available. To describe such component we start with the SDK example in | ||
| + | |||
| + | <OOo_SDK>/Examples/developersGuide/Components/Addon/ProtocolHandlerAddon_cpp | ||
| + | |||
| + | Let's begin with a little comparison between the architectures of a component and the architecture of an addon. | ||
| + | |||
| + | =Addon's Architecture= | ||
| + | Because we have already encountered [[Constructing_Components|components]] (and [[CompleteAddIn|addin]] will be described in a next chapter) we give directly the schematic representation of the addon example in the SDK. | ||
[[Image:FirstAddon.png|center|thumb|600px|My first Addon (with Helper)]] | [[Image:FirstAddon.png|center|thumb|600px|My first Addon (with Helper)]] | ||
| − | This figure shows us what are the interfaces we have to implement. | + | This figure shows us what are the interfaces we have to implement. Four interfaces are showed : <idl>com.sun.star.frame.XDispatchProvider</idl>, <idl>com.sun.star.frame.XDispatch</idl>, <idl>com.sun.star.lang.XInitialization</idl> and <idl>com.sun.star.lang.XServiceInfo</idl>, and it's a good idea to have a look at them. |
| + | |||
| + | =Home Page= | ||
| + | {{Template:Home_Page}} | ||
| + | =See also= | ||
| + | * [[Documentation/DevGuide/WritingUNO/AddOns/Add-Ons|Developer's Guide]] | ||
| + | * [[OpenOffice_Add-On_Project_Type|OpenOffice Add-on Project Type]] | ||
| + | * [[Constructing_Components|Constructing components]] | ||
| + | * [[CompleteAddIn|Constructing addins]] | ||
| + | |||
| + | [[Category:Add-On]] | ||
| + | [[Category:Extensions]] | ||
| + | [[Category:Cpp]] | ||
| + | [[Category:Uno]] | ||
| + | [[Category:Tutorial]] | ||
Latest revision as of 22:05, 13 July 2018
 |
This Chapter is under construction. Please be patient... |
Introduction
Add-on are tackled also in Developer's Guide.
The addon are like components but they don't add a particular interface. To put it differently they need no IDL file for their construction. Then, if you want to call an addon only menus are available. To describe such component we start with the SDK example in
<OOo_SDK>/Examples/developersGuide/Components/Addon/ProtocolHandlerAddon_cpp
Let's begin with a little comparison between the architectures of a component and the architecture of an addon.
Addon's Architecture
Because we have already encountered components (and addin will be described in a next chapter) we give directly the schematic representation of the addon example in the SDK.
This figure shows us what are the interfaces we have to implement. Four interfaces are showed : com.sun.star.frame.XDispatchProvider, com.sun.star.frame.XDispatch, com.sun.star.lang.XInitialization and com.sun.star.lang.XServiceInfo, and it's a good idea to have a look at them.
