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


Hi :)  
Sorry no-one responded to this at the time.  Quite a few people were busy on
the 25th and also the message never reached the User's mailing-list.  Have
you been able to contact the devs list and try to get answers from them? 
THis question was waaaay beyond the scope of most of us here but it is
usually a good place to start with because we can usually signpost people to
the appropriate places.  

I'm not sure what you mean by scripting and i'm not familiar with the code
you wrote but i'm also not familiar with macros so perhaps it's the same
thing.  In which case there is a macro guide in the "Getting Started Guide"
and if you scroll further down the page to Andrew Pitonyak's 3rd party that
is usually hugely useful even though it costs a little money
https://wiki.documentfoundation.org/Documentation/Publications

Regards from 
Tom :)  



--
View this message in context: 
http://nabble.documentfoundation.org/Libreoffice-API-tp4026074p4029953.html
Sent from the Users mailing list archive at Nabble.com.

-- 
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.