On 16/08/2011 10:18, Tom Davies wrote:
________________________________
From: Onyeibo Oku <twohotis@gmail.com>
To: "Libre, Users" <users@global.libreoffice.org>
Sent: Tue, 16 August, 2011 7:46:53
Subject: [libreoffice-users] Extension Manager Runtime exception
I'm trying to package an extension for Calc. so far, the preamble seems okay.
But Extension manager chokes on the embedded python macro
Says 'XSCRIPTCONTEXT' is not defined. The scripts work when I put them in
user/.libreoffice/3/user/Scripts/python so I must be missing something in the
extension packaging.
I see from the error message that its trying to install the extension in the
user's libreoffice directory. What if I want that code installed in
Libreoffice's standard directory? Is that possible? How do I do it? Comments and
suggestions are welcome.
Regards
Onyeibo
---------------------------------------------
from twohot@device.mobile :)
Hi :)
I don't know if this is helpful but the Macro chapter in the Getting Started
Guide got updated a few days ago
http://wiki.documentfoundation.org/Documentation
There is an additional chapter in the Calc Guide but that is still on it's first
version.
Nothing useful here (as far as the subject matter is concerned, that is)
If you scroll down to the bottom of that page there 'should' be a link to the
book by Andrew Pitonyak (?speeling?) which is excellent and well worth getting
if you are really into Macros.
I have Andrew's book (though I might have to download it again. I
believe he recently uploaded an updated version). I'm not sure he
handled extension packaging ... (hmm, let me research that. Okay, yeah
... no useful hits on that here. So its not in the book).
Hopefully someone else on this list might be able to give specific help this
time but some of those guides might help you get a deeper understanding of it
all if that's what you are looking for.
Good luck and regards from
Tom :)
Thanks Tom, I've been reading the OOo extensions webpages for deeper
understanding
(http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/Extensions/Extensions).
I can't say I fully comprehend the entire plot. The study continues.
It might be useful to peek into an extension package having python
macros/code. That way, I can compare that with mine as see what I'm missing.
Okay, okay ... found something.
(http://wiki.services.openoffice.org/wiki/UNO_component_packaging)
Hmm, I need some explanations. Can someone explain what the
addImplementation method in the ImplementationHelper class is doing? I
need to understand what parameters types are expected. Yeah, I have
that in mine too but I just need to know why I'm using it.
This is what is throwing the Extension Manager errors:
doc = XSCRIPTCONTEXT.getDocument()
Says 'XSCRIPTCONTEXT' is not defined**. I read somewhere that the
python loader for python extensions cannot load libraries that are not
in its path and that any referenced lib should be included in python
libs folder. Is this it ... am I looking at that scenario? Any ideas
on how to go about fixing this situation? (which python lib folder???)
**Note: Same script works fine when placed in the folder:
user/.libreoffice/3/user/Scripts/python
regards
Onyeibo
--
For unsubscribe instructions e-mail to: users+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/users/
All messages sent to this list will be publicly archived and cannot be deleted
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.