Yes. I have a couple of plugins that use some of the same color libs: ExportHtml, ScopeHunter, ColorHelper, and the mdpopups dependency. The idea is to create one dependency they use and make it available to anyone else as well. Though mdpopups will be harder move to a color lib dependency as it is a dependency itself, and Package Control can't specify dependencies for dependencies. Getting people who use mdpopups to migrate to using that color dependency will be more slow as I have to give people time realize the change is occurring and adapt.
Anyways, the idea is to clean up the code and provide a more sane API. I would just bundle the various color stuff as a dependency lib. That way my plugins will just use a shared dependency instead of all shipping the same/similar libraries as they do now.
I would change unnecessary things like
ColorSchemeMatcher.guess(view, pt, scope) to something like you suggested above
ColorSchemeMatcher.guess(scope, selected=True) (which I like), and it would provide you with the a style object with colors, emphasis, transparent colors converted to non-transparent colors (since the Sublime CSS engine doesn't really handle the color mixing stuff), etc. And you could then also request special colors like gutter, selection, foreground, and background directly like this:
ColorSchemeMatcher.get_special_color('selectionForeground', simulated_transparency=True). Not sure if I care about including access to stuff like
activeGuide etc. as I don't find that stuff useful, but maybe.
I think I would also throw in the library to adjust the colors, brightness, saturation, etc. I would throw in the colorbox library that can generate color boxes for sublimes HTML content. Maybe even provide access to a call to convert a scheme to CSS using standard TextMate scopes. Stuff like that. Then if I add more, everyone using the lib would get access to those things too.
I'm not sure yet how I feel about implementing a CSS parser though. I have no problem with providing access to the CSS though. People could put anything in there. And you still don't get what Sublime is providing under that layer. Luckily, in its currently implementation, you have to keep things simple. You can't really specify
.class1 .class2 (or you couldn't last I checked -- I don't know if things changed). All you can really do right now is
.class1.class2. But if any of that changes, things break and then get more complicated to parse.
I don't feel like it is practical to scan for everything in the CSS. The only time I really care about scanning for weird scopes in a scheme is when I am replicating a Sublime View in HTML, and I only need to that for creating code blocks from Sublime in HTML, and for something like ScopeHunter. I don't really need to replicate CSS in my sub CSS for popups and phantoms; I should already get that stuff for free as long as I don't override it. I don't want to scan for available classes either. I just want to know what standard classes are reasonably expected to be there. Whatever non-standard class you are looking for could be missing if you install another scheme. From a plugin standpoint, I would only be interested in what standard class names I can use, and maybe the
body element back-ground color for when I insert images. I would prefer that themes keep that stuff simple so I don't have to do elaborate analysis.
The reason why I wrote
mdpopups was to standardize everything for myself and the plugins I write to spare myself from analyzing scopes in every plugin for popups; it's all done for me. I just give it scopes and don't worry about. If I need something specific, I inject a little additional CSS using known scopes. I know I can only expect standard TextMate scopes and
.background. I know that
mdpopups will make the background and foreground color the same as the scheme background and the foreground. So it is a simple list I can reference. I now know that schemes are likely to include colors and font styling under the classes
.modified. I don't care if a theme inserts other classes as those will vary from theme to theme and can't be relied on. I am only interested in standard colors. I'd rather give up a little control to have things consistent.