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

Re: [libreoffice-design] Agenda for the design/UX meeting 2019-Feb-06 (Wed)

Hi Olivier,

Olivier Hallot 於 2019/2/11 下午6:37 寫道:
> Hello Franklin
> We are filling these documentation gaps these days, thanks to
> LibreOfficiant and myself.
> https://help.libreoffice.org/6.3/en-US/text/sbasic/python/main0000.html
> https://gerrit.libreoffice.org/#/q/status:merged+project:help+owner:%22LibreO%25EF%25AC%2583ciant+%253CLibreOfficiant%2540sfr.fr%253E%22
> Also, the wiki has many pages on Python. Admittedly, Python macros are
> not as integrated as Basic macros, but it works.
> Kind regards
> Olivier

Thanks a lot for your efforts!

This Python scripts help is for LibreOfficeDev (6.3) ONLY, right?

Franklin Weng, Member, Board of Director & Certification Committee
The Document Foundation, Kurfürstendamm 188, 10707 Berlin, DE
Gemeinnützige rechtsfähige Stiftung des bürgerlichen Rechts
Legal details: https://www.documentfoundation.org/imprint

To unsubscribe e-mail to: design+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/design/
Privacy Policy: https://www.documentfoundation.org/privacy

Re: [libreoffice-design] Agenda for the design/UX meeting 2019-Feb-06 (Wed)Olivier Hallot <olivier.hallot@libreoffice.org>
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.