https://bugs.documentfoundation.org/show_bug.cgi?id=148621
--- Comment #3 from Olivier Hallot <[email protected]> --- 1) Recent discussions in the ESC (Engineering Steering Commt'ee) lead to a phase-out of JavaBeans and JavaScript in the future. https://lists.freedesktop.org/archives/libreoffice/2022-January/088371.html Nevertheless, our documentation guides have some starting point for Javascript: https://books.libreoffice.org/en/GS73/GS7313-GettingStartedWithMacros.html#toc39 2) The poor layout is likely consequence of the update of prism.js and prism.css in master branch. Some tweak to set because the previous releases are not affected. https://gerrit.libreoffice.org/c/help/+/132570 3) It has been a looooong time like that and fixing it depends on volunteer effort or business investment on the issue. To give an example, we submitted (but were not picked for funding) a project on illustrating the API: https://wiki.documentfoundation.org/Documentation/GSoDOC/2022 And this project is an easy hack, actually. 4) These "Advanced" libraries are in the code since the birth of OpenOffice.org (StarOffice?) and were never documented. Excluding the current formatting issue, the Help page was an effort to give a minimum visibility of the macros. It worked since you got there (and your comments are appreciated) :-). 5) Exactly because reading the code is a time consuming task and the script signature has already a minimal useful information. The build of the Help page was done with a script and no human intervention. Feel free to propose a better, perhaps more professional description. Note a) the library is static from ages and is likely to stay like that unless you want to add contents and b) the script signatures are not translated. c) Have a look at the Scriptforge libraries under development at the moment. Documentation is coming along with the forge development. 6) Correct. These are 2 different entities. The Help targets the end user and the API targets developers and advanced script coders. Besides, the Help is translated into +70 languages while the API is not. Pushing for more contents to translation is something we consider with special care. The API website (which is an online version of the LibreOffice SDK) is generated by Doxygen. Of course, volunteers are welcome to improve the page layout and usability, as well as contents. Doxygen experts are welcome. Finally, the documentation is left historically to the community. We advise volunteers but we won't prevent them from using their pet tool for their own use. That said, some communities prefer wiki, others books, some Ask, other mailing list or Telegram groups, and so on... PS. we are aware of readthedocs and other tools in github. -- You are receiving this mail because: You are the assignee for the bug.
