Summary: Allow Color schemes to be saved in both XML and JSON. Then auto-detect the file type and parse appropriately.

Whenever I open my color scheme to make a minor edit - it gives me a 'rhetorical headache' - it is so messy and hard and difficult to read and edit XML-Plist files for this kind of content!!!

I have found PlistJsonConverter plugin - which luckily makes things doable again but brings additional problems of losing comments, formatting, structure, etc. I don't see why this can't just be automated and implemented natively. Why should I have to keep converting back and forth between XML-Plist and JSON? Why can't Sublime Text just also support reading Color Schemes in JSON natively if they are found in that format? It would save a lot of headache.

 in order to view result directly without refresh the brouser and without ctrl+s the document, this will be a wonderfull feature

In TextMate in LaTeX bundle, you have 4 different types of calling snippets (I will put a very understandable example, $0 is the placement of the cursor):

• LaTeX symbol based on current word. i.e. If you write s and you use this command you get \sigma $0.
  
• Command Based on current word. i.e. if you write s and use this you get \sum_{$1}^{$2} $0.
  
• Environment based on current word. i.e. if you write s and use this you get \begin{s} $0 \end{s} (or what you have defined before).
  
• And, at last, Snippets (true snippets, as simple as in Sublime Text). i.e. if you write mat and press Tab button you get \begin{${1:pvbPVBsmall}matrix} $0 \end{matrix} (exactly, at least the same way as in Sublime Text).

I wish you could add this option to your program, I mean, one (configurable) key combination for each one of this four kinds of snippets. Anyway, I wait for your answer (saying yes or no, but please tell me you read that). In case of NO as answe, I would really appreciate to hear about your reason.

Ah, and a very very nice program. 

Currently, opening a file in the Finder will open the file in the last-used window (if "open_files_in_new_window" is disabled, which imo it should be by default). However, this is not very intuitive as I won't necessarily want the file to end up in that window.

It would be handy if we could designate a "default" window that new files are opened in (perhaps clicking a little icon on the window somewhere).

The way BBEdit does it that I find works quite well is that new files (that aren't already open elsewhere) open in a single non-project window. Typically I will have a bunch of project windows open and another catch-all window for misc files I'm working on that don't belong to an open project.