So, thought I’d check in with folks on best practices on workflow here. So I have my language mode plugin that’s doing fairly well I think. I ran into an initial problem with naming however (path names for settings, snippets, python modules). Now that I’ve got this all committed and synced with GitHub and PackageControl, I’m running into trickier issues.
My original folder name was
vhdl_mode. When I committed to GitHub I called it
VHDL Mode. This is probably actually the most correct name, and this is how it displays on Package Control as well. Now when that package is downloaded it’s named
VHDL Mode.sublime-package. However I have been using GitKraken for local repository control. When it cloned the GitHub project, it named it
Presumably if I take the
sublime-package file and extract it to
%appdata%\Sublime Text 3\Packages as
VHDL Mode this is effectively identical to the zipped package file. That would give me a testbed to work on. I suppose I can keep my repository separate from the test zone, that way I’m not inflicting changes on myself while editing. The entire point is to create a testbench area that can be used, but then also have as close to the user environment as possible so that I know I’m testing what they will see.
Is there a way to make PackageControl download and unzip into a zone on a package by package basis? For the ones I’m not working on, I’m happy to have them in their compressed state, however for the one that I am the author for, it’d be nice if that one was extracted into an uncompressed working fashion.
Does anyone have another way of handling development, test, and delivery combining GitHub, and Package Control on their local setup?
EDIT: So yeah, the extraction of the
sublime-package and putting it into a directory of the same name under
Packages didn’t work out correctly. A ton of errors from
sublime_plugin.py about names. Now trying to come up with another solution.