Keep in mind, the editor is designed to be a standalone app, and then I tap into it via a plugin.
My current plan is:
- make sure ESC is working properly in all platforms for closing dialogs.
- Probably adjust insert workflow, but again not critical on my list.
- Maybe add an "open theme" option in the menu to open a theme via the file picker
- Look into getting linux working
- Maybe add a menu in the sublime plugin to list available themes that can be picked to load in the editor
- If someone provides a list of common scopes, I will look into adding the ability to select them via a dropdown or something.
Maybe in the future:
- I may allow for the editor to be fed the path to a config file. In that config file, a user could specify folders to scan for theme files, and those theme files could appear in some kind of menu or dropdown list. This may happen sometime in the future, but not right now. I would have to add the ability for the editor to scan the folders, search sublime-plugin zip files, give logic to unpack from said zip files to a temp location. This isn't even including live edits that show in Sublime. To do that, I need to communicate back to the plugin to switch the theme for live updates (maybe to a settings file that is being watched, maybe sockets, maybe named pipes; I don't know). At this point, I view it as a nice to have. I want to avoid making the editor dependent on the sublime environment, but allow it to be an independent tool as it was designed to be.
The other thing to keep in mind is that right now I am ready to take a break from this tool, so more ambitious features are going to get stuffed in the wish list for the possible future.