Home Download Buy Blog Forum Support

SublimeText Organization at GitHub!

Re: SublimeText Organization at GitHub!

Postby ajpalkovic on Wed Jun 15, 2011 6:07 pm

Personally, what I think what would be best is if we could define a plugin in a folder. I could do something like create a ClipboardHistory repo, and in the top level was a file called __init__.py or something like that. The advantage is that 1) I can use multiple files in the plugin, and 2) To install the plugin, I can just clone the entire repo into my packages folder (I don't just have to manually download one file). I personally think 2 would be a HUGE win.

So, instead of User/clipboardHistory.py, I would have User/ClipboardHistory/__init__.py
ajpalkovic
 
Posts: 142
Joined: Fri Jun 10, 2011 10:21 pm

Re: SublimeText Organization at GitHub!

Postby charlesroper on Thu Jun 16, 2011 10:53 am

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'.
charlesroper
 
Posts: 107
Joined: Thu Feb 18, 2010 7:30 am

Re: SublimeText Organization at GitHub!

Postby charlesroper on Thu Jun 16, 2011 11:11 am

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.



With strong editorial this seems to be a good compromise. By editorial I mean someone or the community should decide on what is generic and broad enough in appeal to go in the generic "Plugins/Text/Source" package, and what is esoteric enough to go in its own package.
charlesroper
 
Posts: 107
Joined: Thu Feb 18, 2010 7:30 am

Re: SublimeText Organization at GitHub!

Postby ajpalkovic on Fri Jun 17, 2011 12:55 am

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'.


I had tried to use folders in the User package, but not as a separate package. I've since moved all my plugins into a separate package (and github repo) (https://github.com/ajpalkovic/SublimePlugins). Thanks.
ajpalkovic
 
Posts: 142
Joined: Fri Jun 10, 2011 10:21 pm

Re: SublimeText Organization at GitHub!

Postby wbond on Thu Jul 21, 2011 5:08 pm

Quite a while ago I had tried creating a zip file with a filename .sublime-package and it didn't seem to work with ST2. I just saw your message @guillermooo, so I will try out your code.

I do think that having every little command in its own package is a good thing. What would be useful is some way through ST2 to discover and select packages to install/update. I'm relatively new to python programming, so I don't know what the current best practice is, but something like sublime_easy_install would be awesome.

I like the suggestions about the repo names for packages being CamelCase, however for discoverability I've added the work "sublime" to each repository/package name. This github organization should help some. I've also considered setting up a website for plugins. Perhaps it could pull metadata from the github organization and present it in a nice search-engine-friendly way.

To potentially further complicate the situation, I've also been spending a lot of time on a package I intend to sell for a small fee. Right now I think I'd like to have a little more friction between someone just downloading it on Github and not ever paying, but I would like to keep with the ST model and allow for an extended trial period. Perhaps this is something I'll just need to work out on my own.
wbond
 
Posts: 527
Joined: Mon Feb 28, 2011 5:33 am

Re: SublimeText Organization at GitHub!

Postby Marciano on Sun Sep 25, 2011 8:28 pm

HELPPP!!!!

As of yesterday, I can no longer push to the SublimeText/LaTeXTools repo! This is a problem, as there are a couple of urgent fixes I need to apply.

I noticed that yesterday I was added to the "developers" team, and that I have access to 5 repos... but NOT to LaTeXTools. Can someone (guillermoo) please fix this ASAP!

I like the idea of having a single org for SublimeText plugins, but if this becomes too much of a hassle, I will have to fork the plugin to a repo that I maintain directly.

M
Marciano
 
Posts: 146
Joined: Fri Sep 18, 2009 2:55 am

Re: SublimeText Organization at GitHub!

Postby guillermooo on Sun Sep 25, 2011 9:27 pm

Hi Marciano,

I have next to no idea how to use the org features at GitHub. I've tried my best, but I believe too many people have access to the repo now. You should try to talk to barneywilliams (Greg Williams). He did the initial setup and is more familiar with how it works. Let me know whether I can do anything else, though.
guillermooo
 
Posts: 728
Joined: Thu Jul 23, 2009 9:06 am

Re: SublimeText Organization at GitHub!

Postby Marciano on Mon Sep 26, 2011 2:06 am

Thanks---Greg already replied to an email I sent him via github. Hopefully he will straighten things out...
Marciano
 
Posts: 146
Joined: Fri Sep 18, 2009 2:55 am

Re: SublimeText Organization at GitHub!

Postby Marciano on Mon Sep 26, 2011 2:11 am

Actually, whatever you or Greg did worked---I am now able to push again.

I think this has to do with the creation of a "Developers" group. Up until this afternoon, I was a member of the Developers group, but LaTeXTools was *not* a repository "controlled" by Developers. It now is.

Again, I have access back, so whatever you/Greg did, Thanks!!!
Marciano
 
Posts: 146
Joined: Fri Sep 18, 2009 2:55 am

Re: SublimeText Organization at GitHub!

Postby chikamichi on Mon Oct 17, 2011 9:23 pm

Hi,

Just joined the party with https://github.com/SublimeText/TrailingSpaces
chikamichi
 
Posts: 14
Joined: Sun Oct 16, 2011 2:26 am

PreviousNext

Return to Plugin Development

Who is online

Users browsing this forum: Exabot [Bot] and 2 guests