On 05/02/2013 12:47 PM, Alexander Thurgood wrote:
I seriously doubt that using LO Basic, you would be able to attain a
similar goal in any meaningful timeframe and with decent performance.
However, using another language via one of the UNO bindings might be a
more viable (if somewhat daunting) project.
If you use another language, then you have full access to everything
that it offers.
I usually check the online API docs (as shown above), inspecting the
objects, and I have even bothered to dive into the source code when I
was totally befuddled.
The documentation for LibreOffice Basic seems very space compared to MS
That's because it is. Documentation on UNO and Basic comes down to the
built-in help and anything you can find with regard to the
OpenOffice.org project, the current API documentation produced by the LO
project, and old Sun StarOffice documents (if they are still around).
VBA has a whole ecosystem and 20-odd years worth of product pushing
around it by people paid to push the platform forward. Although UNO has
been around since the days of StarOffice, it has never had that
Look at UNO, look at the language bindings, decide which is the most
appropriate for what you want to do :
My Macro Document: http://www.pitonyak.org/AndrewMacro.odt
For unsubscribe instructions e-mail to: email@example.com
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
Impressum (Legal Info)
: 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