Moving forward, I plan on making it more robust. When just opened normal, I plan on asking if the user wants to open a theme file, or create a new one. I want to change the open file dialog to accept "tmTheme.JSON" files as well (it already supports them via the -j command line option; probably just change it to look at the extension instead of requiring the user to specify open mode). Maybe add a search option. Maybe add a way to "save as".
From a plugin standpoint, I plan on allowing you to open a theme via the open dialog (it will still be direct edit, which is why a "save as" option would be nice), and possibly create a new theme also from sublime.
...oh and try and get linux running .
Probably need an icon for the editor...
Haven't decided how to distribute it yet. I know the Mac binary is 30MB and the windows is only 10MB, not sure about linux yet. Because I may not want to require a user to update 40+MB every time the plugin updates, I may provide the plugin without binaries, and you install or download the editor somewhere and point the plugin at it. The plugin could check the version to tell if you need to update it (after initial development is done, I hope not to be updating it a bunch).
Chime in if you have any ideas.