On Wed, 2011-12-07 at 15:04 +0100, Stephan Bergmann wrote:
toolpanel.py should use passive registration (i.e., an accompanying
.component file, which then is referenced in META-INF/manifest.xml).
desktop/test/deployment/passive builds an example .oxt containing
passively registered UNO components in C++, Java, and Python.
Right. That reminds me - don't even think about trying to register a
python 'module'; we have to refer to a .py by name, the module path in
pythonloader.py seems totally dysfunctional, to the point of
uselessness. Any python genius that can tell me how:
mod = __import__ ( "actual python-module-name" )
implHelper = mod.__dict__.get( "g_ImplementationHelper" , None )
is supposed to work, or indeed any half-way decent documentation on
what the object is that __import__ returns and by what I don't mean
floral vagueness but a concrete set of methods/properties and their
types that would let us find an internal variable definition ;-)
HTH,
Michael.
--
michael.meeks@suse.com <><, Pseudo Engineer, itinerant idiot
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: 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.