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


On 30/04/2020 03:34, Olivier Hallot wrote:
The way information is presented to the non-developer is sub-optimal.
Pre-Doxygen sdk was much easier to navigate and get information as the
ues cases below

What exactly do you mean with "pre-Doxygen sdk"? (IIRC, Doxygen has been introduced to replace OOo's autodoc first for generation of the C++ API documentation and then for generation of the UNOIDL API documentation.)

With installed sdk in his computer at
file:///opt/libreoffice6.4/sdk/index.html

What exactly is installed there? <https://download.documentfoundation.org/libreoffice/stable/6.4.3/deb/x86_64/LibreOffice_6.4.3_Linux_x86-64_deb_sdk.tar.gz> or <https://download.documentfoundation.org/libreoffice/stable/6.4.3/rpm/x86_64/LibreOffice_6.4.3_Linux_x86-64_rpm_sdk.tar.gz> as currently available at <https://www.libreoffice.org/download/download/>?

Let's suppose I am a candidate to macro programming and want to

Use case 1 : Search for ThisComponent -> no matches

Search how? I find no ability to search on <file:///opt/libreoffice6.4/sdk/index.html>. (Did you mean the search field at the top right of <file:///opt/libreoffice6.4/sdk/docs/idl/ref/index.html>, reached from <file:///opt/libreoffice6.4/sdk/index.html> via "IDL Reference"? But then, "ThisComponent" is not a term related to LO's UNOIDL API, so no matches is a plausible outcome there.)


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.