Difference between revisions of "Add-ons (Develop)"
(→Steps towards your own add-on) |
m (→Steps towards your own add-on) |
||
| Line 7: | Line 7: | ||
==Steps towards your own add-on== | ==Steps towards your own add-on== | ||
| − | + | The goal of the add-on is to put: | |
| + | #a script <tt>myCoolScript.groovy</tt> in <tt><freeplaneuserdir>/script/myCoolScript.groovy</tt>; and | ||
| + | #an icon <tt>mycoolicon.png</tt> in <tt><freeplaneuserdir>/icons/mycoolicon.png</tt>. | ||
| + | |||
First download the [http://freeplane.sourceforge.net/wiki/index.php/Add-ons#Add-on_Insert_Inline_Image Developer Tools] from the [[Add-ons]] page. It provides scripts that relieves you from most of the tedious work. An easy way to do so: | First download the [http://freeplane.sourceforge.net/wiki/index.php/Add-ons#Add-on_Insert_Inline_Image Developer Tools] from the [[Add-ons]] page. It provides scripts that relieves you from most of the tedious work. An easy way to do so: | ||
| Line 18: | Line 21: | ||
#Restart Freeplane | #Restart Freeplane | ||
#The add-on functions are available in: ''Tools > Developer tools'' | #The add-on functions are available in: ''Tools > Developer tools'' | ||
| + | |||
Next define your add-on | Next define your add-on | ||
Revision as of 19:31, 19 November 2011
This page will provide detailed information about developing Freeplane add-ons.
Add-ons are installed in the Freeplane user directory (see Tools->Open user directory). They may contain any number of scripts and Zip archives which are unpacked on installation. Combinations of scripts and Zips especially interesting since this enables you to package scripts with required libraries/JARs/class files. For instance it's possible to bundle some Groovy scripts for creating diagrams with the JFreechart library - so there's no need to download and install the JFreechart libraries anymore.
Since plugins (such as the Scripting, LaTeX or Formula plugin you know) may also be installed into the Freeplane user directory, add-ons may even provide plugins.
Steps towards your own add-on
The goal of the add-on is to put:
- a script myCoolScript.groovy in <freeplaneuserdir>/script/myCoolScript.groovy; and
- an icon mycoolicon.png in <freeplaneuserdir>/icons/mycoolicon.png.
First download the Developer Tools from the Add-ons page. It provides scripts that relieves you from most of the tedious work. An easy way to do so:
- In Freeplane select Tools > Add-ons > Search add-ons > Visist add-on page
- Search your add-on; choose download
- Save the add-on on your computer, e.g. on the desktop
- Select Tools > Addons > Search and install
- Select directory icon ; find and select the file you just downloaded (e.g. on your desktop)
- Select Install
- Restart Freeplane
- The add-on functions are available in: Tools > Developer tools
Next define your add-on
- In Freeplane create a new empty map by Ctrl+n.
- Invoke Tools->Developer Tools->Build add-on. You will be asked for the name of your add-on. Answer My Cool Add-on
- Look through the messages in the info box that is shown if everything looks alright. The name attribute of the root node will be myCoolAddOn. This is the identifying technical name of the add-on while My Cool Add-on will be subject to translation.
- Set the version attribute of the root node to v0.1
- Create a new directory somewhere with the technical name of the add-on, myCoolAddOn.
- Save the new map to myCoolAddOn/myCoolAddOn.mm.
- Copy myCoolScript.groovy to myCoolAddOn/scripts/myCoolScript.groovy.
- In the map create a new subnode of the scripts node with name myCoolScript.groovy.
- Copy mycoolicon.png to zips/icons/mycoolicon.png.
- In the map create a new subnode of the zips node with name icons. Create a mycoolicon.png subnode under icons. The node hierarchy then is zips->icons->mycoolicon.png.
- Invoke Package add-on for publication. This will create the file myCoolAddOn-v0.1.mm which can be installed via Tools->Scripts->Install Add-on (or via Tools->Add-ons).
But before publishing your add-on read all notes in the add-on map. They are meant for developers, not for users since users are not expected to read an add-on package. The notes should guide you to add all missing information.
