Hi Alain and Ilmari,
Op 31-12-2020 om 12:24 schreef LibreOfficiant:
As suggested by Ilmari, writing tutorials in the wiki looks like the
appropriate approach as Python newbies are your intended audience. I
understand you seek for guidance, here's my take on a potential "Macros and
more precisely for Python:
- Running Python example scripts
- using LibO UI
- checking for/ installing Python scripting framework (may be included in
installation pages) on *nix platforms
- Using the Python interactive console
- native Python examples
- e.g ScriptforgePythonHelper.py
- typing Python UNO example scripts
- import uno vs. XSCRIPTCONTEXT
- APSO benefits here...
- EDI benefits here..
I found it difficult to transfer what I had in mind via the mailing
list. Therefore I have put my ideas in a document: python_ideas.odt
It is available in
It is an attempt to cover the things you suggested above.
It is a document of about eight pages, do not know whether that is
suited for a wiki.
So now there is a concrete proposal to react on, it also reflects the
level of my skills.
Open for comments on the approach taken, and corrections on the content.
For the moment I will leave the other thread (on wiki.documentation) as
To unsubscribe e-mail to: firstname.lastname@example.org
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/documentation/
- Re: [libreoffice-documentation] Re: python documentation, a step up · Peter Heijink
Impressum (Legal Info)
: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (MPLv2
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our trademark policy