Of Course with python you can also read|write .odf in general inclusive .ods in detail without any soffice at hand.
this thirdparty-tool
You link provide no new informations, the HelloWorld-example is already included in ...libreoffice/share/Scripts/python/...
this is a good example and exemplifies my impression that the LibreOffice flavor of Python is fairly unPythonic dialect of Java. Would help to have a reference of what are the major objects/methods to invoke to get started, the equivalent in LO Basic of ThisComponent ThisDatabaseDocument and dbg_methods, etc.
Updating this old and maybe outdated but cross-referenced Q&A with a pointer to my (occasionally maintained) LibreOffice Scripting link collection.
1 Like
Check my profile in this forum for extra Python information
Alain: “Check my profile” isn’t the best way to advertise your great work you did on scripting documentation for LibreOffice, being one of the initiators of LibreOffice Macro Team. Better provide a good list of links to stuff like https://wiki.documentfoundation.org/Macros/Python_Design_Guide, or Python Scripts, or the talks you gave on our conferences you gave: in Almeria, online.
@flywire:
Some examples exactly for: NOT howto do
https://tutolibro.tech/2021/05/07/python-libreoffice-reverse-the-order-of-cells-content-from-a-cell-range/
data = (2,1,3)
output = tuple(entry for entry in reversed(data)) #no, no ,no!
# use simply:
output = tuple( reversed(data))
1 Like
@karolus Why don’t you post that comment on the blog where people will see it, and hopefully the author might fix it?
Edit: OK I understand from your comment below comments aren’t displayed until accepted.
@karolus Why don’t you post that comment on the blog where people will see it, and hopefully the author might fix it?
@flywire: thats already done!
1 Like
The AUTHOR doesnt fix, but he dont accept my comment, what an ignoramus!
Yes, my comments were ignored too. Blogs not being maintained is a common problem. LibreOffice needs basic tutorials like these in it’s own docs. At least the blogger made the source code freely available for the examples in the last half of those tutorials.
I’ve been working on docs suffering from perfection as the enemy of good. I should just make it available.
Good to see Blogger has processed comments now.
For someone who is familiar with Python, you can easily paste StarBasic code into your Python module and adjust the syntax line by line IF the code mainly consists of calls to the UNO-API. Apart from the language syntax you have to take care of:
- declaration of constants:
MyDT = com.sun.star.util.DateTimevs.from com.sun.star.util import DateTime AS MyDT -
ThisComponentvs.XSCRIPTCONTEXT.getDocument() - Several other convenient Basic definitions, mainly StarDesktop and createUnoService, need to be instanciated from uno.ComponentContext.ServiceManager. def createUnoStruct can be found in the uno module.
- Since you know Python, you will easily spot the routines where Basic code tries to manipulate strings and arrays. You can drop them alltogether and use some Python basics instead.
Macro code is stored globally or embedded in documents. In the macro organizer the global ones appear under “My Macros”, the embedded ones appear under the name of the loaded document.
A completely different thing is extension development. Extensions add new services to the office suite. Extensions do not appear in the macro organizer unless the extension distributes macros.
- The single most important extension you need for any kind of UNO programming is MRI:
[Tutorial] Introduction into object inspection with MRI This is also a great example for a powerfull extension which also adds a small macro library in StarBasic for convenience. - A convenient extension for Python macros is the "Alternative Script Organizer for Python (APSO). It allows to open macro code with your favourite editor. It can also embed code into a document without touching the document’s XML code.
Translate StarBasic as you go is about as good as the alternatives. When you look at https://pitonyak.org/OOME_3_0.pdf the offerings for the community to learn python macros are pretty pathetic. Kudos to those that have made the effort to offer what they can.
Python as an alternative macro language is an offering for those who are familiar with that language. What I tried to point out was that both macro languages are not that different in respect to UNO calls.
Whatever you prefer, a good overview on UNO concepts (frame->view->model, service, interface, types) together with MRI is vital.
StarBasic is not an option when it comes to extension development unless your extension is just a macro library.
I needed to write an excel macro and although I didn’t know VBA I didn’t need to know it to use the resources to learn it. It’s unreasonable to need to know python before you can use it to develop LO macros but that is the way it is presented to the community. That’s not the case with the StarBasic document I linked.
Agree all languages would use the same UNO calls and although the syntax varies an example from one language is useful in another, it’s just harder to understand when you have to translate it.
It depends. IIRC, XRay was a Basic extension; so is AltSearch, and I suppose that 90%+ in our extensions repo are Basic.
(A hint: I don’t know if you intended to write an answer, or just to continue comment thread, so just in case, because it’s often not convenient to find the button to post a comment: if you want to answer another’s comment, you may select some part of it, and get a “Quote” popup button, allowing you to start another comment.)
1 Like