[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [libreoffice-documentation] Re: Getting Started Guide for LO 6.4


Thank you for the reminder! I will be sure to do that. - Jean

On Wed, 22 Jan 2020 at 19:47 LibreOfficiant <pyoffice.romedenne@sfr.fr>
wrote:

> Hi,
>
> Would that be possible, when reviewing Chapter 13, to mention the fact that
> LibO macro programming isn't Basic-centric? Although it makes sense to
> highlight Basic.
>
> Other supported languages for macros, such as BeanShell, JavaScript or
> Python could be listed in the introduction, while the Library organization
> section may mention their existence/location.
>
> Cordially
> Alain
>
> e-refs:
> Python Script help
> <https://help.libreoffice.org/6.4/en-US/text/sbasic/python/main0000.html>
>
> Designing & Developing Python Applications Preamble
> <https://wiki.documentfoundation.org/Macros/Python_Design_Guide>
>
>
>

--
To unsubscribe e-mail to: documentation+unsubscribe@global.libreoffice.org
Problems? https://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: https://wiki.documentfoundation.org/Netiquette
List archive: https://listarchives.libreoffice.org/global/documentation/
Privacy Policy: https://www.documentfoundation.org/privacy

References:
[libreoffice-documentation] Getting Started Guide for LO 6.4Jean Weber <jeanweber@gmail.com>
[libreoffice-documentation] Re: Getting Started Guide for LO 6.4LibreOfficiant <pyoffice.romedenne@sfr.fr>
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.