Difference between revisions of "Add-on"
B michaelsen (Talk | contribs) |
|||
| Line 1: | Line 1: | ||
| − | {{ | + | {{Warn|This Chapter is under construction. Please be patient...}} |
=Introduction= | =Introduction= | ||
Add-on are tackled also in [[Documentation/DevGuide/WritingUNO/AddOns/Add-Ons|Developer's Guide]]. | Add-on are tackled also in [[Documentation/DevGuide/WritingUNO/AddOns/Add-Ons|Developer's Guide]]. | ||
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.
