Difference between revisions of "Documentation/DevGuide/Scripting/Storage of Scripts"
From Apache OpenOffice Wiki
< Documentation | DevGuide
OOoWikiBot (Talk | contribs) m (Robot: Changing Category:Documentation/Developers Guide/Scripting) |
m |
||
| (2 intermediate revisions by 2 users not shown) | |||
| Line 5: | Line 5: | ||
|NextPage=Documentation/DevGuide/Scripting/Implementation | |NextPage=Documentation/DevGuide/Scripting/Implementation | ||
}} | }} | ||
| − | {{DISPLAYTITLE:Storage of Scripts}} | + | {{Documentation/DevGuideLanguages|Documentation/DevGuide/Scripting/{{SUBPAGENAME}}}} |
| + | {{DISPLAYTITLE:Storage of Scripts}} | ||
A <code>LanguageScriptProvider</code> is responsible for knowing about how its own macros are stored: where, what format and what kind of directory structure is used. The Scripting Framework attempts to standardize how to store and discover macros by defining: | A <code>LanguageScriptProvider</code> is responsible for knowing about how its own macros are stored: where, what format and what kind of directory structure is used. The Scripting Framework attempts to standardize how to store and discover macros by defining: | ||
* A default directory structure. | * A default directory structure. | ||
| − | :Macros can only be stored under a directory with the language name ( as it appears in the script URI ) in lowercase under a directory called ''Scripts'', which is located in either the user or share directories of | + | :Macros can only be stored under a directory with the language name ( as it appears in the script URI ) in lowercase under a directory called ''Scripts'', which is located in either the user or share directories of an {{AOo}} installation or a {{AOo}} document. |
:Example for a <code>LanguageScriptProvider</code> for the “JavaScript” macro library. It is located in ''<OfficePath>/share/Scripts/JavaScript/Highlight'' | :Example for a <code>LanguageScriptProvider</code> for the “JavaScript” macro library. It is located in ''<OfficePath>/share/Scripts/JavaScript/Highlight'' | ||
| − | * A generic mechanism for enabling discovery of macros in macro libraries and associating meta-data with scripts located in | + | * A generic mechanism for enabling discovery of macros in macro libraries and associating meta-data with scripts located in these libraries. See ''parcel-descriptor.xml'' in [[Documentation/DevGuide/Scripting/Writing_Macros#Compiling_and_Deploying_Java_macros|Compiling and Deploying Java Macros]]. Example the parcel-descriptor for the JavaScript Highlight macro library is located in ''<OfficePath>/share/Scripts/JavaScript/Highlight/parcel-descriptor.xml'' |
{{PDL1}} | {{PDL1}} | ||
[[Category:Documentation/Developer's Guide/Scripting]] | [[Category:Documentation/Developer's Guide/Scripting]] | ||
Latest revision as of 15:07, 14 January 2024
A LanguageScriptProvider is responsible for knowing about how its own macros are stored: where, what format and what kind of directory structure is used. The Scripting Framework attempts to standardize how to store and discover macros by defining:
- A default directory structure.
- Macros can only be stored under a directory with the language name ( as it appears in the script URI ) in lowercase under a directory called Scripts, which is located in either the user or share directories of an Apache OpenOffice installation or a Apache OpenOffice document.
- Example for a
LanguageScriptProviderfor the “JavaScript” macro library. It is located in <OfficePath>/share/Scripts/JavaScript/Highlight
- A generic mechanism for enabling discovery of macros in macro libraries and associating meta-data with scripts located in these libraries. See parcel-descriptor.xml in Compiling and Deploying Java Macros. Example the parcel-descriptor for the JavaScript Highlight macro library is located in <OfficePath>/share/Scripts/JavaScript/Highlight/parcel-descriptor.xml
| Content on this page is licensed under the Public Documentation License (PDL). |
