in the color scheme you can:
<key>popupCss</key>
<string><
body = """\n <style>\n body {\n background-color: #f1f1f1;\n}\n span {\n color: #aaaaaa;\n }\n </style>\n <span>ball</span> """
view.add_phantom("test", view.sel()[0], body, sublime.LAYOUT_INLINE)
They are not saved to disk anywhere, just stored in memory. They are not generated if the color scheme defines its own popupCss.
Small bug.
In symbol.py, this line:
symbol_begin_pt = view.text_point(l[2][0] - 1, l[2][1])
must be:
symbol_begin_pt = view.text_point(l[2][0] - 1, l[2][1] - 1)
In addition, this is a Gist with a modified symbol.py to propose active file items first and an other item than the current one by default.
Maybe this can be integrated in standard ST3 (only tested on Windows).
when i define the settings they always use the same default colors (white bg and blue links) so maybe u can save the generated colors to the scheme file ,this way it could be edited easily 
First off, thanks for the new build!
I’ve found https://github.com/lord/slate to be great for documentation, compare https://lord.github.io/slate for output of the gh-pages branch. Docs could be included and opened via default brower from Sublime Text when offline, as well as linked to from the website when hosted on github and opened from Sublime Text when online.
@alkuzad Dash and/or Zeal would require those to be installed, browsers come with the OS. Using Slate here would reduce third-party dependencies.
- Build errors are now shown inline at the location where they occurred. This is controlled with the show_errors_inline setting.
As much as I welcome this feature in general, I think the way it’s currently implemented looks terrible. Would be nice if error messages can by customized by themes, so they stand out visually, rather than looking like a line of text inserted in the editor – I find that very confusing.
Really excited about the new API’s. This opens many possibilities related to additional information about the code on screen. One thing I would like to see added is the ability to set an icon for a phantom region to be displayed only when there is no existing icon on the line (for inline display) or always display when displaying as a block region. I can see this being very effective for quickly identifying lines with build errors. To avoid the issue of trying to render multiple icons to the gutter I would say existing icons from normal regions that have been added to the code should take priority over phantom icons.
Thank you for the new build devs, keep up the amazing work!
I’ve been working on some enhancements to minihtml that will make it easier to tweak the various popups. I’m also planning on making some visual tweaks. Keep your eyes peeled for further improvements.
I was trying out your example ViewCalculator plugin and I noticed that if I open a new file tab that the is_applicable() class method gets called on every character I type into that view until the file is saved. Is that expected behavior?