Description: The use of Javascript for writing Macros and Extensions seems not to be documented on the wiki or anywhere else in libreoffice-space. Actual Results: I found the following: * https://wiki.documentfoundation.org/Extensions mentions the possibility to write Extensions in Javascript, but there seems to be no further info. * There are some examples for macros in JS at: http://opengrok.libreoffice.org/xref/core/scripting/examples/javascript/ but I did not find them linked anywhere Expected Results: Ideally, there would be: * An example for a Extension written in JS * Information on how to debug extensions which are written in JS. Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:51.0) Gecko/20100101 Firefox/51.0
Pretty please document the JavaScript macro functions! This lack of documentation is ridiculous. JavaScript is the most popular programming language (see https://developers.slashdot.org/story/17/08/24/1457245/javascript-is-eating-the-world for an update). People have been asking for to use JavaScript in macros since Sep 2016 - https://ask.libreoffice.org/en/question/77779/need-step-by-step-instructions-to-create-new-javascript-macro/ I've also asked for something as simple as a JavaScript currency conversion macro - https://ask.libreoffice.org/en/question/98257/javascript-macro-reference/ Yet, nothing?! Why does LO even support JavaScript then, if it's completely undocumented? The only slightly relevant stuff I've found on GitHub are three scantily documented samples at https://github.com/LibreOffice/core/tree/master/scripting/examples/javascript
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
This is still an issue. A web search for "LibreOffice JavaScript macro reference" produces non-results, i.e. my own questions[1], and an acknowledgment from Olivier Hallot that the wiki does need to cover this. [1]: https://ask.libreoffice.org/en/question/98257/javascript-macro-reference/ [2]: https://listarchives.libreoffice.org/global/documentation/msg11912.html https://help.libreoffice.org/Common/Scripting mentions JavaScript without any additional details.
Javascript is popular enough to be documented, take that into account. To cope with javascript-related assignments please visit https://assignmentcore.com/javascript-homework/
There's a very short documentation about Javascript in the Getting Started Guide, page 403. https://wiki.documentfoundation.org/images/b/b7/GS70-GettingStarted.pdf What can be done in the short term is create a help page describing how to create a Hello World in javascript based on the example available in the guide. Currently there has been a huge effort in improving Python documentation in LO, specially due the ScriptForge library, which allows Basic/Python interoperability. https://help.libreoffice.org/7.2/en-US/text/sbasic/shared/03/lib_ScriptForge.html?DbPAR=BASIC#bm_id491529070339774
Dear jan d, To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from https://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Just a note that the Rhino editor/debugger is removed with the Rhino 1.7.14 update: 58c4457a902c846229dc3383cc31bbc8f4b3aed9 (to be included in 24.8 release)