Howto:Hacking Inkscape to add Canvas support
|This article is a stub. You can help the wiki by|
Tom (Canvas) mentioned originally that for cockpit instruments using Inkscape with maybe a plugin will probably fit better.
Inkscape’s extension architecture can be easily used with Python. There is also some support for other scripting languages. communications between inkscape and its extensions is fairly limited and can be made to easily work for simple command-line (CLI) appliications.
Traditional Unix scripts can be used to extend Inkscape's functionality. Such programs read a stream of data on standard input, transform the data in some way, and then write the modified data to standard output. This is an easy way to expand Inkscape and provide custom functionality without learning the internals of Inkscape. Libraries for reading and writing SVG data exist for many programming languages, and most provide support for XML. This tutorial describes the "ins and outs" of writing one of these scripts and making it work with Inkscape's core functionality with a focus on creating MFDs for FlightGear.
Inkscape couuld also be used to directly establish a "connection" with FlightGear (think telnet/props, httpd etc)
Anatomy of an Inkscape Extension
- INX FILE
- Python code
The following extension types exist for Inkscape:
- input (read a file / data)
- output (write a file / data) (e.g. PropertyList/XML)
- effect (change contents in the document)
- print (output to an external device, this could be using fgfs itself)
Come up with a simple Inkscape extension that can serve as the foundation for creating Canvas based MFDs more easily. Ideally, in conjunction with Richard's MFD framework and the Emesary IPC system (eventually), maybe even taking Phi into account ?
- Canvas.Map (?)
Each MFD would be arranged using:
- an outer shell for the UI
- an inner region to display the Canvas serving as the screen
GUI (INX File)
For now, this section contains a few pointers on creating a custom INX file, which is the mechanism to register a new extension with Inkscape and provide a simple UI for it.
Extensions can be supplied with values obtained through easily definable parameters. Inkscape provides the basic GUI for user input. The following parameters are supported:
- int (for an integer number input field)
- string (for a text input field)
- float (for a float number input field)
- boolean (for a checkbox)
- enum (for a dropdown list)
- optiongroup (for a dropdown list or radio buttons)
- color (for a color selector, like the one in the Fill & Stroke dialog)
For the sake of the UI there are also the following two parameters that do not provide data to the extension but alter the user input GUI.
- description (for descriptions below parameters)
- notebook (for tabs)
| Work in progress|
This article or section will be worked on in the upcoming hours or days.
See for the latest developments.
To install a new extension, download and unpack the archive file. Copy the files into the directory listed at Edit > Preferences > System: User extensions. After a restart of Inkscape, the new extension will be available.
Installing is as simple as copying the script (unless it resides in your path) and its INX file to the inkscape/share/extensions ($HOME/.config/inkscape/extensions) directory. (If you install a script in your home directory be sure to copy the dependencies.)
There are two text files per extension: a Python program with file extension .py and a menu description with file extension .inx. The syntax of the latter file is that of XML while its semantics are specific to Inkscape. These files are located in different directories on different platforms:
- Linux: ~/.config/inkscape/extensions/
- Mac OS X: /Applications/Inkscape.app/Contents/Resources/extensions/
- Windows: C:\Program Files\Inkscape\share\extensions\
On Linux you willhave to make the python script executable first if you haven't done this yet. This is usually done by the usual command (or in your preferred file manager):
$ chmod a+x script.py
Now start Inkscape. A new menu item in the EXtensions menu should appear.
- come up with the boilerplate to add a custom extension to the inkscape menu
- come up with a simple wizard to create Canvas related MFD pages procedurally
- provide support for creating boilerplate for missing FG1000 pages using templates Not done
- set up a git repository and commit the proof-of-concept