No. It just looks like the smallest possible example. You may use one class and use the string argument to trigger(str) and call routines according to the passed argument.
You can also declare your own routines but then you have to compile some binary thingy using some tool in the development kit. I forgot all the details and will never do it again. Too cumbersome.
Menus and toolbars are defined in Addons.xcu in the extension.
<node oor:name="m01" oor:op="replace">
<prop oor:name="URL" oor:type="xs:string">
<value>service:name.JimK.LinguisticTools.PhonologySettings?execute</value>
</prop>
A caution about the Wavelet example: it’s nice and short, but there are declarations missing. Such old-style extensions often to fail to install and uninstall correctly. For a properly declared extension, see my struct.oxt example in the other post.
Thank you @jimk
As I said
[my extension is] quite well integrated in Libreoffice Menu, Toolbar, Configuration in Options…
So the question is much more about connecting many function through classes, which I haven’t done yet (lack of time).
You said:
For a properly declared extension, see my struct.oxt example in the other post.
I would appreciate so much if you could be more precise. Which other post? Your struct.oxt sounds very appeling to me!
The link to the post is in my answer above. Here is a link directly to the comment: Is it possible to transfer a struct from Python to StarBasic? - #10 by jimk
That is precisely what my answer and responding comment show.
Yes, so there was no need to ask again if you already knew how to add the menus.
It seems we are having some trouble communicating. Often when that happens, it is best to open a new, clearly worded question, as I also commented earlier. Or, you may already have all the information you need, and if so, now it is a matter of taking the time to get it working.
I did not know about this. From your warning, I think I’ll steer clear of it! The primary reason I prefer python rather than java is that there is no need for compiling and depending on the LO SDK when writing macros.
This is not about macros. It is about extensions adding real objects to this office suite.
Once upon a time I compiled some UNO blob from a declaration file like this:
module org { module openoffice { module sheet { module addin {
interface XPySudoku
{
sequence< sequence< any > > pysudoku( [in] sequence< sequence< any > > InputArray);
};
}; }; }; };
It declares an array function for Calc taking an array as argument (an unsolved 9x9 Sudoku) and returning an array (the solved 9x9 Sudoku).
The binaries are files with *.urd or *.rdb suffix.
https://extensions.libreoffice.org/en/extensions/show/1984
Oh, you’re talking about a Calc Add-In. My extension has one of those. I compiled the .rdb file a long time ago (don’t remember how) and it still works on my current version of LibreOffice.
<node oor:name="AddInFunctions">
<node oor:name="reverse" oor:op="replace">
<prop oor:name="DisplayName"><value xml:lang="en">reverse</value></prop>
<prop oor:name="Description">
<value xml:lang="en">Flips a string backwards. For example "apple" becomes "elppa".</value>
</prop>
<prop oor:name="Category"><value>Add-In</value></prop>
<!-- This won't help, because there is no reverse() in Excel. -->
<prop oor:name="CompatibilityName"><value xml:lang="en">reverse</value></prop>
<node oor:name="Parameters">
<node oor:name="s" oor:op="replace">
<prop oor:name="DisplayName"><value xml:lang="en">s</value></prop>
<prop oor:name="Description"><value xml:lang="en">The string to reverse.</value></prop>
</node>
</node>
</node>
</node>
This looks like Addon.xcu, the extension’s main configuration in XML syntax. The thing that is pushed into the compiler looks more like Java syntax. I think you have to compile interfaces with methods having their own in and out values, like a spreadsheet add-in or MRI with its inspect method. UNO IDL = interface definition language.
Okay, you have reminded me of how this all fits together. I will post another answer that is what the OP asked for, although it is probably way too cumbersome to be practical, as you mentioned.
My other answer assumes that an existing UNO interface is used. This is much easier. However there is a way to create methods of any interface, as @Villeroy commented.
An IDL file defines the interface that the method will use (name, arguments and so on). It needs to be compiled into an .rdb file with a tool in the LibreOffice SDK called idlc.
#include <com/sun/star/uno/XInterface.idl>
module name { module JimK { module LinguisticTools { module CalcFunctions {
interface XCalcFunctions
{
string reverse( [in] string s );
};
}; }; }; };
The compiled file is referenced in manifest.xml.
<!-- Compiled type library for the Calc addin -->
<manifest:file-entry
manifest:full-path="idl/XCalcFunctions.rdb"
manifest:media-type="application/vnd.sun.star.uno-typelibrary;type=RDB"/>
The implementation in python looks like this in my extension.
from name.JimK.LinguisticTools.CalcFunctions import XCalcFunctions
class StringReverserAddIn(unohelper.Base, XCalcFunctions):
def __init__(self, ctx):
self.ctx = ctx
@staticmethod
def factory(ctx):
return StringReverserAddIn(ctx)
def reverse(self, inString):
return inString[::-1]
g_ImplementationHelper.addImplementation(
StringReverserAddIn.factory,
"name.JimK.LinguisticTools.ReverseStringImpl",
("com.sun.star.sheet.AddIn",),)
If not creating an add-in, I think the interface name could be different, probably like this:
"name.JimK.LinguisticTools.ReverseStringImpl",
("name.JimK.LinguisticTools.ReverseStringImpl",),)
Anyway, this works in a Basic macro.
svc = CreateUnoService("name.JimK.LinguisticTools.ReverseStringImpl")
s = svc.reverse("hamster")
MsgBox(s)
Result:
retsmah
Note: MRI also uses an IDL file but it derives from the existing interface com/sun/star/beans/XIntrospection.idl, so that may be a different case.