Release status: experimental
|Implementation||User interface, Ajax|
|Description||In-browser vector graphics editing with SVG-edit|
|Author(s)||Brion Vibber (Brion VIBBERtalk)|
|License||GPL (extension), Apache (SVG-edit)|
Translate the SVGEdit extension if it is available at translatewiki.net
|Check usage and version matrix.|
Batteries not included: Neither SVG-edit 2.5.1 nor 2.6 is included at present.
Current versions of most major browsers should work. Internet Explorer 8 and earlier will require Chrome Frame plugin even with SVG-edit 2.6. IE 9 and later only need Chrome Frame with SVG 2.5.1 or earlier
- "Edit drawing" tab and button added on File: pages for SVG images
- "SVG drawing" button added to WikiEditor advanced toolbar "insert" section to create new files conveniently while working on a page
- file invocation is added to the text editor upon saving the file
- currently the filename will be autogenerated from the name of the page being worked on
- Download and place the file(s) in a directory called
- Add the following code at the bottom of your LocalSettings.php:
- Download SVGedit (see Configuration), and place it in .../extensions/SVGEdit/svg-edit
- Enable SVG support
- Done - Navigate to Special:Version on your wiki to verify that the extension is successfully installed.
There is only one configuration option, which allows using an externally hosted instance of the SVG-edit editor iframe:
$wgSVGEditEditor = 'URL to Svg Editor';
#Example: $wgSVGEditEditor = 'http://tools.wmflabs.org/svgedit/editor/svg-editor.html';
While the master code for this extension lives in Wikimedia's git repository, I also have a git repo where I may have some experimental branches:
Known bugs[edit source]
- Actual editor issues belong upstream: http://code.google.com/p/svg-edit/
- Editing in Internet Explorer 9 requires using a development build of svg-edit 2.6; see #Configuration for switching from the built-in 2.5.1 release copy.
- add an editor trigger on SVG images visible in regular page views (partially implemented, not yet ready)
- allow saving without closing the editor
- autosave & recover drafts
- build a Gadget/user-script shim, allowing end-users to add editing to SVG-supporting wikis themselves (needs a JSONP proxy to load files for Wikimedia usage, since ApiSVGProxy is not in favor and there's been no motion to change cross-origin headers)
- extend 'import SVG file' and 'image' tools to allow pulling other images from the wiki
While SVG-edit is pretty capable, it's still a bit experimental and may damage existing files. Always check to make sure things still look right after a save; remember you can always revert to the previous version.
The editor widget is loaded in an <iframe> within the current page context; after saving, the parent page is reloaded which should show the new version of the file.
Those using a separate domain to store files may need to enable ApiSVGProxy to load up existing SVG files. Cross-origin headers on the file server should also be able to resolve this, but this needs testing.
Saving is implemented by POSTing an upload request to the API from an XMLHTTPRequest; this does not require any extra tweaks other than making sure SVG files are allowed for upload.
Be aware that using an instance of SVG-edit hosted by a third-party can expose your actual SVG image data to client or server code on that domain. If using an external editor instance on a private MediaWiki, you should ensure that you trust the domain that you use.