Scripting
FreeMind 0.9.0 has a scripting facility using Groovy.
Menu
- Tools > Evaluate: run all the scripts in a mind map
- Tools > Script Editor
Keyboard
- Alt + F8: run all the scripts in a mind map
Using
Each script is stored in a named attribute of a node, named for example as "script1" or "script2". One node can have several scripts attached. There is no way to store scripts in a script file for the whole application; scripts can only be stored in mind maps[verify].
To add a new script to a node, use the script editor, available from the menu Tools > Script Editor. Alternatively, you can plainly create an attribute whose name starts with "script" such as "script2"; such an attribute is understood by FreeMind to be a script.
To run all the scripts in a mind map, use the menu Tools > Evaluate or press Alt + F8.
To run a single script, use the script editor (Tools > Script Editor), and its menu item Actions > Run. The Run function of the script editor shows the results of the execution in the pane at the bottom, and it shows error messages there, if any.
For more detail, see the FreeMind documentation available from the menu Help > Documentation, the section "New features in version 0.9.0" and the subsection "Scripting support".
Examples
Some example scripts:
- Setting a new text of a node:
=12 * 14(A little trick: scripts starting with "=" replace the text of a node with their results.) - Changing the text of a node:
c.setNodeText(node, node.getText() + " - appended text") - Setting the text color of a node:
c.setNodeColor(node, java.awt.Color.RED) - Setting the background color of a node:
c.setNodeBackgroundColor(node, java.awt.Color.YELLOW)
See also Example scripts.
For another set of examples, see the FreeMind documentation available from the menu Help > Documentation, the section "New features in version 0.9.0" and the subsection "Scripting support".
Script editor
FreeMind has a very simplistic script editor, available from menu Tools > Script Editor. The editor has no color highlighting of code, and no specific support for writing Groovy scripts: it is basically a plain text editor like Notepad.
The editor has three panes: left one, right one, and bottom one. The left pane shows a list of scripts attached to a node. The right pane shows the script selected in the left pane. The bottom pane shows the results of the execution of a script.
The actions available in the menu Action of the script editor are New Script, Run, Sign Script, Dismiss Changes and Exit, and Save and Exit.
The action Action > New Script adds a new script to the left pane, named as "script1", "script2", etc. The newly created script can be edited in the right pane once the name of the script is selected in the left pane.
The action Action > Run runs the script selected in the left pane, and shows the result of running the script in the bottom pane, including any error messages.
The action Action > Sign Script makes it possible to sign a script. [To be documented].
API
The scripts can access FreeMind's scripting API--application programming interface. Above all, the scripts would typically make use of the methods of MindMapController. The mind map controller is available to scripts as 'c'.
Security
By default, FreeMind scripts are restricted in what they can do on the local computer. The restrictions include those of file operations, network operations and execution of applications. These restrictions can be lifted in user preferences, from the menu Tools > Preferences..., and the section "Scripting".
The available security options for scripting, in the section "Scripting" and subsection "Permissions":
- Permit File Operations
- Permit Network Operations
- Permit to Execute Other Applications
- Trust Signed Scripts
- Optional User Key Alias for Signing
Groovy
The scripting engine and language of FreeMind is Groovy. To find out about Groovy, you can check the following web resources:
- Groovy homepage
- Groovy, Java's New Scripting Language, 2004-09-29, onjava.com
- Your Thoughts on the Groovy Scripting Language?, 2006-04-17, Slashdot - a review and a discussion thread on pros and cons of Groovy
Implementation
Scripts are stored in an attribute whose name reads "script" followed with a numeral, meaning in the attribute of the attribute function, not in the attribute of XML.
The script attributes are probably distinguished from non-script attributes by their starting with "script".
An example of storage in XML:
<node TEXT="hello"> <attribute NAME="script1" VALUE="=node.getNodeLevel() + " " + node.getText()"/> </node>
Limitations
- Failure unless file operations permitted: Almost all scripts fail unless file operations are permitted for scripting; repeated execution of scripts succeeds, though[1]
- There is no way to store scripts in a script file for the whole application; scripts can only be stored in mind maps[verify].
