Difference between revisions of "External script file execution"
From Freeplane - free mind mapping and knowledge management software
Irajawapys (talk | contribs) |
(Undo vandalism) |
||
Line 1: | Line 1: | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
== Setting the External Script Directories Search Path == | == Setting the External Script Directories Search Path == | ||
− | There is a mechanism to load and execute scripts from ''script directories'' matching a given name scheme (hardcoded: | + | There is a mechanism to load and execute scripts from ''script directories'' matching a given name scheme (hardcoded: <tt>".*\.groovy"</tt>). |
− | # The list of ''script directories'' is configurable by selecting | + | # The list of ''script directories'' is configurable by selecting <tt>tools->Scripting</tt> from the menu, and then in the resulting <tt>Preferences</tt> window, click the <tt>Scripting</tt> button. |
− | # In the | + | # In the <tt>Script search path (separate entries by ;;)</tt> text box, you can specify additional pathes where Freeplane can search for Groovy Scripts. |
=== Windows === | === Windows === | ||
− | Specify your path as you would normally in windows, just be sure to add a | + | Specify your path as you would normally in windows, just be sure to add a <tt>;;</tt> at the end of the path you add to the existing script path. |
==== Example ==== | ==== Example ==== | ||
− | If you wanted the default | + | If you wanted the default <tt>%USERPROFILE%\.freeplane\scripts</tt> directory, and also wanted to use <tt>C:\temp</tt> you would set : |
− | + | <tt>scripts;;C:\temp;;</tt> | |
=== Linux === | === Linux === | ||
Line 29: | Line 21: | ||
(todo) | (todo) | ||
− | (default: | + | (default: <tt>scripts</tt>, i.e. directory <tt>scripts</tt> in the freeplane user home). |
== Executing Scripts == | == Executing Scripts == | ||
− | *Matching scripts are listed in the menu | + | *Matching scripts are listed in the menu <tt>Extra->Scripts</tt>. |
== Hot Key Assignment to Execution of Scripts == | == Hot Key Assignment to Execution of Scripts == | ||
*Due to the flexible standard hotkey assignment it's possible to create hotkeys for these scripts. | *Due to the flexible standard hotkey assignment it's possible to create hotkeys for these scripts. | ||
For each script there is a submenu with three menu entries: | For each script there is a submenu with three menu entries: | ||
− | **''Execute for one selected node'': This will invoke the script for one selected node (arbitrarily choosen), i.e. if three nodes are selected, it will be executed once, with the | + | **''Execute for one selected node'': This will invoke the script for one selected node (arbitrarily choosen), i.e. if three nodes are selected, it will be executed once, with the <tt>node</tt> variable set to one of the selected nodes. Since setting of <tt>node</tt> is not really predictable this variable should not be used. |
**''Execute for all selected nodes'': This will invoke the script on every selected node, i.e. if three nodes are selected, it will be executed three times, once for each node with the ''node'' variable set to the respective node. | **''Execute for all selected nodes'': This will invoke the script on every selected node, i.e. if three nodes are selected, it will be executed three times, once for each node with the ''node'' variable set to the respective node. | ||
**''Execute for all selected nodes, recursively'': This will invoke the script on every selected node and recursively on all of its children. | **''Execute for all selected nodes, recursively'': This will invoke the script on every selected node and recursively on all of its children. | ||
Line 44: | Line 36: | ||
== Script Error Logging == | == Script Error Logging == | ||
− | *Errors while loading or while execution of scripts are handled by error message popups. (See resources | + | *Errors while loading or while execution of scripts are handled by error message popups. (See resources <tt>ExecuteScriptError.text</tt> and <tt>ReadScriptError.text</tt>.) |
[[Category:Scripting]] | [[Category:Scripting]] |
Revision as of 10:16, 24 November 2010
Contents
Setting the External Script Directories Search Path
There is a mechanism to load and execute scripts from script directories matching a given name scheme (hardcoded: ".*\.groovy").
- The list of script directories is configurable by selecting tools->Scripting from the menu, and then in the resulting Preferences window, click the Scripting button.
- In the Script search path (separate entries by ;;) text box, you can specify additional pathes where Freeplane can search for Groovy Scripts.
Windows
Specify your path as you would normally in windows, just be sure to add a ;; at the end of the path you add to the existing script path.
Example
If you wanted the default %USERPROFILE%\.freeplane\scripts directory, and also wanted to use C:\temp you would set :
scripts;;C:\temp;;
Linux
(todo)
Example
(todo)
MacOS X
(todo)
Example
(todo)
(default: scripts, i.e. directory scripts in the freeplane user home).
Executing Scripts
- Matching scripts are listed in the menu Extra->Scripts.
Hot Key Assignment to Execution of Scripts
- Due to the flexible standard hotkey assignment it's possible to create hotkeys for these scripts.
For each script there is a submenu with three menu entries:
- Execute for one selected node: This will invoke the script for one selected node (arbitrarily choosen), i.e. if three nodes are selected, it will be executed once, with the node variable set to one of the selected nodes. Since setting of node is not really predictable this variable should not be used.
- Execute for all selected nodes: This will invoke the script on every selected node, i.e. if three nodes are selected, it will be executed three times, once for each node with the node variable set to the respective node.
- Execute for all selected nodes, recursively: This will invoke the script on every selected node and recursively on all of its children.
- Note: If a node and a child node are both selected, then the script is invoked on the child node twice.
- To execute a script on all nodes in a map one has to select the root node and execute the script recursively.
Script Error Logging
- Errors while loading or while execution of scripts are handled by error message popups. (See resources ExecuteScriptError.text and ReadScriptError.text.)