Creating Python Scripts with ScriptForge /text/sbasic/shared/03/sf_intro.xhp Python scripts with ScriptForge

Creating Python Scripts with ScriptForge

Differences between Basic and Python

The ScriptForge library is available both for Basic and Python. Most services, methods and properties work identically in both programming languages. However, due to differences in how each language works, ScriptForge users must be aware of some characteristics of the library when using Python: Methods and Property names: In Python, all methods and properties can be used in lowercased, ProperCased or camelCased formats. Arguments: All keyword arguments passed on to methods are lowercased. Dates: All date objects are passed and returned as datetime.datetime native Python objects. Arrays: One-dimensional arrays are passed and returned as tuples (which is an immutable object). Two-dimensional arrays are passed and returned as tuples of tuples. None: Python's None keyword is equivalent to Basic's Null, Empty or Nothing. UNO objects: All UNO structures are exchanged between Basic and Python without any changes. Debugging: Whenever an error occurs in Python scripts that use ScriptForge, the error message provided by the Python execution stack displays the line of code that triggered the error. In Basic error messages do not display this information. Visit %PRODUCTNAME Python Scripts Help for more information on Python scripting using %PRODUCTNAME.

Editing Python scripts in IDEs

Python typing hints - relating to ScriptForge services public methods and properties - can be obtained from IDEs that support such facility. Visually, while editing a user script: hovering an object instance, a method or a property displays its detailed description. a "." after an object instance displays a drop-down box listing all available interfaces. brackets after a method-name start code-completion by displaying its arguments. Typing hints are displayed when editing methods and properties with propercase letters.

Running Python scripts on %PRODUCTNAME

Depending on what you intend to achieve, you may choose one of the following approaches to running Python scripts in %PRODUCTNAME: Run Scripts inside the current %PRODUCTNAME process: Python scripts are executed from within the %PRODUCTNAME process by using the Tools - Macros - Run Macro menu or the APSO extension to call user scripts stored in the Python scripts folder. You can also use the APSO Python shell to interactively run Python scripts. Run Scripts separately from the %PRODUCTNAME process: Python scripts are executed from an external process that connects to an ongoing %PRODUCTNAME process using a socket. If you plan to run scripts from inside the %PRODUCTNAME process, it is recommended to install the APSO (Alternative Script Organizer for Python) extension. However, to develop Python scripts from outside %PRODUCTNAME, you can choose your preferred Python IDE.

Running Scripts from inside the %PRODUCTNAME process

Using the APSO extension

The easiest way to get started with Python scripting in %PRODUCTNAME is by installing the APSO extension. After installing it, open any %PRODUCTNAME component and go to Tools - Macros - Organize Python Scripts. In APSO's main window go to Menu - Python Shell. Alternatively you can open APSO using the default shortcut Alt + Shift + F11. Now you can start typing Python commands and the shell will print the corresponding output after each line of code is executed. To start using the ScriptForge library, you need to import the CreateScriptService method, with which you will be able to access the services provided by the library. The example below uses the Basic service to display a message box. from scriptforge import CreateScriptService bas = CreateScriptService("Basic") bas.MsgBox("Hello!") To run the example above, enter each line in the Python shell, one by one, pressing the Enter key after you type each line of code. Now you can start executing Python commands using any of the ScriptForge services. For example, the code snippet below uses the UI service to create a blank Writer document. ui = CreateScriptService("UI") doc = ui.CreateDocument("Writer")

Creating Python script files

You can create your own Python files and edit them with your preferred text editor. Later you can call them from within any %PRODUCTNAME component. The first step is to locate where your user scripts are stored. For that, refer to Python Scripts Organization and Location help page. Now you can create a text file inside your Python user scripts folder, for instance sf_test.py, and start typing your scripts. Next is a simple example that gets the numeric value from a Calc cell and increments it by 1. Simply type the following code into the sf_test.py file. from scriptforge import CreateScriptService doc = CreateScriptService("Calc") def increment_cell(args=None): value = doc.GetValue("A1") value += 1 doc.SetValue("A1", value) g_exportedScripts = (increment_cell, ) This example creates the increment_cell function. Note that g_exportedScripts is a tuple that tells which functions will be displayed in %PRODUCTNAME as user scripts. To run this script from within a Calc document: Create or open a Calc file. Enter some numeric value into cell "A1" in the current sheet. Go to Tools - Macros - Run Macros . Choose My Macros - sf_test in the library selector. Then choose the increment_cell function under the Macro Name list. Click Run. Note that the value in cell "A1" was incremented by 1. You can also use APSO to run Python scripts in a similar manner: First open APSO by going to Tools - Macros - Organize Python Scripts. In the macro list, navigate to My Macros - sf_test - increment_cell. Click Execute.

Running Scripts separately from the %PRODUCTNAME process

Determining the Installation Path

The first step to run scripts from a separate process is to find the folder where %PRODUCTNAME is installed. There are several ways to do that, but ScriptForge provides a quick way to identify your installation path. For that, open APSO's Python shell and type: from scriptforge import CreateScriptService fs = CreateScriptService("FileSystem") fs.FileNaming = "SYS" inst_dir = fs.InstallFolder print(inst_dir) The output from the code above is the base directory where %PRODUCTNAME is installed. Now you need to add the "program" subfolder to the resulting path. This is the base folder from which you will run Python scripts from a separate process. For example, suppose you get /usr/lib/libreoffice/ as the result from running the Python code above. Then you need to consider /usr/lib/libreoffice/program as the path to run your Python scripts.

Start %PRODUCTNAME with socket settings

To run Python scripts from a separate process, you need to start %PRODUCTNAME with a few additional options that specify the hostname and port through which the external process will communicate with the %PRODUCTNAME component process. Open the your operating system's command prompt, navigate to the program folder of your %PRODUCTNAME installation directory and type: ./soffice --accept='socket,host=localhost,port=2021;urp;' The command above will start %PRODUCTNAME with a communication channel open so that other processes can exchange messages with it. Note that the previous example opens %PRODUCTNAME start center. If you want to open a specific component, for instance Writer, you can add the --writer flag to the command, as follows. ./soffice --writer --accept='socket,host=localhost,port=2021;urp;' Take note of the host and port parameters, which in this example are localhost and 2021, respectively.

Running an External Python Shell

Start the Python shell from within the program folder inside your %PRODUCTNAME installation path. Follow the steps above to learn how to find your installation path. On Linux / Mac OS: $ cd /usr/lib/libreoffice/program $ python On Windows: $ cd C:\Program Files\LibreOffice\program\ $ python.exe This will open the Python shell and now you can start typing commands that will be executed by %PRODUCTNAME. But first you need to set up the socket connection. from scriptforge import ScriptForge, CreateScriptService ScriptForge(hostname='localhost', port=2021) Read the section Setting PYTHONPATH below in case of errors importing scriptforge.py or uno.py. The second line of code above defines the host and port settings so that the Python shell can communicate with an ongoing %PRODUCTNAME process opened with the same socket settings. Now you can run other Python commands and they will be able to communicate with the %PRODUCTNAME process. For example: ui = CreateScriptService("UI") bas = CreateScriptService("Basic") doc = ui.OpenDocument("~/Documents/myFile.ods") bas.MsgBox(doc.DocumentType) Python interpreter;PYTHONPATH

Setting PYTHONPATH

Depending on your operating system's configuration you will need to set the environment variable PYTHONPATH in order to import the scriptforge.py library, which in turn requires importing the uno.py library.
Use your operating system's file search tool to determine the directory where both these files are located. For instance, on a default Ubuntu installation both files may be located at: scriptforge.py: Located in /usr/lib/libreoffice/program uno.py: Located in /usr/lib/python3/dist-packages In this case, set the environment variable PYTHONPATH as follows before starting the Python interpreter: export PYTHONPATH=/usr/lib/libreoffice/program:/usr/lib/python3/dist-packages The location of these files will be different for each operating system and %PRODUCTNAME installation method.
eature/lfrb-vcl-opengl LibreOffice 核心代码仓库文档基金会
summaryrefslogtreecommitdiff
path: root/include/svx/EnhancedCustomShapeFunctionParser.hxx
AgeCommit message (Expand)Author
2020-12-11Adapt the remaining OUString functions to std string_viewStephan Bergmann
2020-03-23make more classes private in mergedlibs modeNoel Grandin
2020-02-02tdf#128302: Split SVXCORE_DLLPUBLIC from SVX_DLLPUBLICStephan Bergmann
2019-07-12Fix typosAndrea Gelmini
2019-05-16tdf#42949 Fix IWYU warnings in include/svx/[e-g]*Gabor Kelemen
2019-05-03The -fvisibility-ms-compat hack is no longer needed for UBSan on Linux...Stephan Bergmann
2018-01-15More loplugin:cstylecast: svxStephan Bergmann
2017-12-29loplugin:passstuffbyref improved return in svxNoel Grandin
2017-02-14Add operator<< to output values of type enum class ExpressionFunctTor Lillqvist
2016-08-30convert ExpressionFunct to scoped enumNoel Grandin
2016-06-08tdf#96099 Remove various smart pointer typedefsMark Page
2016-05-19loplugin:unusedmethods in svxNoel Grandin
2016-05-03C++11: disable ctors with delete in include/Jochen Nitschke