Well I'm actually getting close to the end of the first phase of my plugin development. Overall it's gone pretty well with the API being the least of my concerns and my actual application rules and logic being the primary focus. That's definitely welcome.
Out of curiosity, does anyone like to look at plugins and be willing to critique at an expert level at what might be good, bad, or indifferent? The stuff I've written so far seems to work okay, but I'm definitely new at this, both python and sublime. Having it work is the primary issue, but if there's ways to tighten up I'm all ears. I did bang my modules against the pylinter in Spyder editor with mixed results. Some really good suggestions, and others where I feel it's trying too hard to match the letter of the law (precise lexical rules) versus the spirit of the law (having something easily understandable and maintainable.)
For the next big phase (which I haven't really decided to commit to) I might try using the sidebar for something other than file selection. However I don't know if that's even possible! Does the sidebar have contexts for being used for one purpose or another? For instance, it may be somewhat useful to develop a language specific project explorer for the language mode I'm working on. The emacs mode has something for this but it's honestly a bit awkward to use as it spawn in its own frame and window. However what it does IS pretty neat, where it shows where objects are defined, where used, etc. Then activating those elements will put your cursor in that file on that location.
Is this even possible? The sidebar is a murky area. If it's reserved for file operations only, that'll be okay. But if it's malleable in content, then that opens up some interesting possibilities.