Extensions File Specification¶
RoboFont extensions are folders acting like files *.roboFontExt.
Info.plist is a XML property list. see A DTD is available.
|A list of menu descriptions that should be added to the extension menu, see Menu Item Description.|
|Name of the developer.|
|Site url of the developer.|
|Indicating it has a html folder. zero, 0 is False, one, 1 is True. index.html is required if set to True.|
|Indicating it should execute code during start up of RoboFont. zero, 0 is False, one, 1 os True.|
|*.py filename path (relative to the lib folder) executed during start up of RoboFont.|
|can be an empty string|
|The name of the extensions.|
|Version number of the extension.|
|The required major number of RoboFont. To help extension builders which aren’t supporting older versions of RoboFont.|
|The required minor number of RoboFont. To help extension builders which aren’t supporting older versions of RoboFont.|
The info.plist can have custom keys if necessary for the extension. It is advised to use reverse domain name as keys (com.example.myExtension).
A folder containing all the *.py script. If a developer prefers to send out only *.pyc files that should be possible but take note that the file should be made with python 2.7 (the build in python version)
This folder will be added to the sys.path so it can import all the other files and folders as modules.
An ‘html’ folder is not required. If such a folder is declared in the info.plist it should contain an ‘index.html’. These is plain html that is rendered in the help window with WebKit.
Any additional file necessary for your extension. Commonly used for bitmap, *.png to build tool bar icons, cursors. Or additional compiled command-line tools.