Hi the Studio 3T team. First of all thank you for your great work & effort!!!
I'd like to have the ability to show/hide the top toolbar. It takes too many space. Most of the actions presented there can be done using the hotkeys or menu items.

It would be really useful to be able to write and edit Mongo queries in the IntelliShell using VIM key bindings

When creating complex queries in the visual query builder there is frequent scrolling required. most mouse pointer devices now have scroll wheels which are critical for big data exploration. Currently your record fields change if you are hovering (not selecting) over your fields in the visual query builder, which changes there values. This is extremely frustrating, and breaks the result. You should only be able to change this value of you have positively selected the object with a left mouse click.

The management of script files based in a source control project folder is missing.
Like an idea, it would be nice to open a folder and see the organised files in a tree like the connections.
Once you have a set of scripts, you don't need to find the collection anymore, you just want to open the file in the context of a connection and run it.

Why doesn't the explain tab on the aggergation reflect the actual explain() from Mongo? When I explain() an aggregation from the mongodb shell, the explanation is different than the one in the explain tab.

There is a greyed out box that says "Full explain is not available for aggregate queiries". Why is it not available?

it's really frustrating to have to copy the document and paste it into a text editor.

Why not have the same options one gets in a normal collection?
- view document
- show all / hide all embedded fields

Pretty straight forward either an export Schema Analysis as JSON or copy to paste board would be very useful.

Per the gridFS Spec https://github.com/mongodb/specifications/blob/master/source/gridfs/gridfs-spec.rst#design-rationale the contentType field is deprecated in favor of adding contentType as a value in metadata. I think this is a change that should be made to 3T when uploading files to a gridFS bucket.

Hi, when experimenting with aggregations in the Pipeline tab it would be useful or time saving if one could copy & paste stages or even duplicate them, i.e. right-click on a stage and have "Copy stage", "Paste stage" or "Duplicate stage" options in the context menu perhaps grouped in a "Stage" submenu to make clear that they are operations related to the selected stage and different from operations related to the whole of the pipeline.

In addition to the feature request for sorting connections by any available header (which looks like it may have been implemented?) I'd like to be able to save those sorting choices for the next time I load the connection window. Currently, the sorting order resets on each load of the connection window.

I'd like to be able to sort on connection name, most recent connection, etc., and have that sort selection persist between multiple connection window loads.

Columns have too much white space, you could see more on the screen if they autosized.

When returning to do something th econnection has been lost and it is not reconnecting like the other tabs

I usually run studio in fullscreen on a separate space. When I restart the app (like for an update etc.) it doesn't restore fullscreen view.

Please add colored background, bold text, or some other way to visually pick out the collection tabs easier. Right now, they are under the menu, and above the user\database\collection list. They blend in visually too easily, taking more effort to jump to the collection you want to edit or view.

it would be nice to search by a relative date.... ie last 60 minutes, 1 day, 1 month

http://cloud.jsherard.com/be4ca869403e

{modifiedDate:{$gte:new Date(new Date() - 60 * 1000)}}

When using mongorestore from a BSON file it's important to be able to map potentially different DB names. Supporting the --nsFrom/To flags would allow that. Currently this is possible with 3T if you're using the BSON folder but not with the file.

The JSON view (including all the options) does not provide a real JSON output which could be copy/pasted into an editor without the need for extensive editing. For example:

1. When there is > 1 document, results should be wrapped in an array.
2. Numbers should not be wrapped in NumberInt()
3. Documents should be comma separated