You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@openoffice.apache.org by bu...@apache.org on 2026/04/20 03:29:42 UTC
[Issue 60849] Python editing and embedding macros in documents
https://bz.apache.org/ooo/show_bug.cgi?id=60849
damjan@apache.org changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|UNCONFIRMED |CONFIRMED
CC| |damjan@apache.org
Ever confirmed|0 |1
Summary|Python Editor |Python editing and
| |embedding macros in
| |documents
--- Comment #5 from damjan@apache.org ---
In my package com.sun.star.script.framework.provider.python:
static ScriptProviderForPython.__getServiceFactory() creates the static inner
class ScriptProviderForPython_ScriptProviderForPython (which extends
ScriptProvider).
Apart from the constructor, ScriptProviderForPython_ScriptProviderForPython has
only 3 methods: getScript(), hasScriptEditor(), and getScriptEditor().
The getScript() method returns the ScriptImpl implemention of XScript, whose
invoke() method in my previous comment is the problem.
If we somehow bridged Java -> Python at the point of getScript(), returning the
XScript in Python, then invoke() on that script would be C++ -> Python,
bypassing Java.
This would be a good route to take, because we would reuse all the benefits
from the Java-based ScriptProvider like macro embedding in documents and user
interaction dialogs, while using Python only for the Python-specific
performance critical code. And both the Java code and the Python code would be
smaller and simpler.
--
You are receiving this mail because:
You are the assignee for the issue.
You are on the CC list for the issue.