Date: prev next · Thread: first prev next last
2015 Archives by date, by thread · List index

Am 25.02.2015 um 12:38 schrieb hw:

How do you build an installation package?

The code needs to live in your own name space (not library "Standard").
Tab [Libraries]

Non-Standard libraries can be imported from documents and templates. For
instance, you may distribute a document with documentation and examples
carrying the macros in a non-Standard library and use the Basic
organizer import/update that code.

LO is installed on a Windows terminal server for all users, yet each
user has their own settings.  To get macro distributed, I have to save
it to a text file which then can be copied and pasted from for each
user.  Or is there a better way?

BTW, is there a way to use an external editor to edit these macros?  I'd
rather use a decent editor like emacs than the poor thing built into LO.

You can use Python or JavaScript as macro language with your favourite
development tools. The Basic "IDE" is horrible, indeed.
Such macro code can be dumped as pure source code into the user profile.

To unsubscribe e-mail to:
Posting guidelines + more:
List archive:
All messages sent to this list will be publicly archived and cannot be deleted


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.