If you have been around SVG, XML, browsers, and computer graphics for a while, you may have noticed an upsetting dichotomy:
Other people’s reasons aside, think about yourself, your own brains, or your own money: Can you, do you want to, or can you afford to learn more than one programming language? For doing the same thing? For manipulating SVG? One programming language for coding in the editor, another programming language for coding in the browser? Write the same functions or methods twice?
Some years back, software developers often were a bit abrasive. Some opined I was on the soft side, trying to make software developers’ work easier. In fact though, I wanted to get a lot done. Result oriented.
For what I wanted to get done this time, one programming language for manipulating SVG was just the right number of programming languages. One. 1.
But, if using browsers as platform to manipulate SVG, browsers did not trivially let me write back to disk the result of manipulating SVG files.
Why would I want to write back to a file? I did not want to depend on a server. Some documents still are meant to be on the disk right in front of the person working with it. I am not alone: While some entities are pushing “storing everything on a server”, with the most modern and popular version control system, Git, what gets developers excited is the ability to work off the network (often described as “on an airplane”), which means disconnected from a server.
There are some simple example files, for showing off writing back to disk (must copy to your disk first), which don’t use Adj. Don’t get this wrong, I am for people using Adj. We’ve provided those simple example files solely to focus on the functionality of this add-on.
I would like to see and use a similar extension for Chrome. Written by somebody else but myself, for a change, please. Not to depend on a single browser for authoring. What if the next version of Firefox has broken features relating to SVG? For now, font metrics appears to be a little better in Chrome than in Firefox. That said, I do appreciate Mozilla’s independence maybe a little more than Google’s advertising revenue fueled interests. Multiple suppliers often are good for the user. But I digress.
Did I mention you could use the Save Back to File from DOM add-on for Firefox for various projects? Get a head start in making a browser-based SVG editor? Allowing you to focus on interactivity, for example, instead of worrying how to write back to disk.
And if you’re making a browser-based SVG editor, please build in support for Adj.