search

Colorsublime / Colorsublime-Plugin

Plugin for Color Sublime
MIT License
540 stars 58 forks source link

Split out "util" code? #10

Closed stephenfin closed 9 years ago

stephenfin commented 10 years ago

A lot of the code used in Colorsublime-Plugin is "utility" code that could be useful in other plugins. Example: status.py. Any chance you could split this out into a sub-repo that others could include in their own projects? You could then include this yourself using a subtree or submodule. I can do this myself, but I'd have to maintain a fork then :smile:

blopker commented 10 years ago

This is an issue with many ST plugins. There are many common pieces that everyone ends up rewriting. I agree, it would be great to have a standard way for plugins to share utility code.

That being said, I haven't used (and have been warned against using) subtree and submodules. I don't remember the exact reasonings, but it's possible the drawbacks can be mitigated for the ST plugin domain.

Since this won't help users of my Colorsublime directly, this kind of thing will be lower on the TODO list. However, if you fork Colorsublime and can demonstrate a usable subtree/submodule workflow I'll happily break off some parts into their own repos and maintain them there.

stephenfin commented 10 years ago

Sounds fair. I'll investigate. Stay tuned

blopker commented 9 years ago

Cleaning up issues today, if you make any progress on this feel free to reopen!