guillermooo wrote:Creating a full new package for every plugin seems to be overkill. I think grouping small plugins in a "Plugins/Text/Source" package is the best way to go at the moment... Unfortunately, I don't think Mercurial or git (most plugins if not all are hosted either at Bitbucket or GitHub) let you clone single files from a repo. And I don't think anybody would like to blindly download all the plugins in the org.
So assuming this was the preferred way to deal with loose plugins, I see two compatible options:
1) We create a Plugins repo in the GitHub org off of which everyone can work
2) Plugin developers use the system that suits them best and provide a "Plugins.sublime-package" file for download. Sublime will copy the files to the Packages/Plugins folder on its own.
charlesroper wrote:Hi AJ,
I've probably misunderstood, but plugins can be stored in any folder under %APPDATA%\Packages can't they? They don't need to be stored in %APPDATA%\Packages\User. I've cloned wbond's Alignment plugin/package/command into %APPDATA%\Packages\Alignment. Nothing needs to go in User.
I have to admit I'm a bit confused as to the distinction between a 'plugin' vs a 'command' vs a 'package'.
Users browsing this forum: No registered users and 10 guests