Bring the old dropdown back

[AndreasBackx]

Personally I don't use Vagrant Manager, but feel like I need to bring this to attention after showing Vagrant Manager to someone else that prefers not to use the Terminal. On the website, it shows a standard dropdown you would see everywhere on OSX. But the new one looks nasty imho and doesn't fit with OSX. Is it possible to at least have an option to go back to the 'old' one?

Tips:

• When a box is halted/inactive, make it gray in the dropdown instead of adding a colored circle. The circle doesn't look very nice and the grayed out text gives plenty of information on sight.
• Use SSH instead of 'vagrant ssh', same applies for up, halt, etc.
• Make it automatically refresh in the background when opening the dropdown, no need for a button/image.
• Center the icon pixelperfect.
• Move the check for updates option to the preferences pane, less clutter and that's where it's supposed to be.

[AndreasBackx]

Vagrant Bar has a beautiful looking UI/dropdown, but still not perfect.

[stopiccot]

+1. Hate new custom UI look so much. Just image that every program will have own custom UI.

[amitailanciano]

The custom UI in Vagrant Manager 2.0 was necessary due to some limitations to the native menu

In regard to your points:

1.) We chose the colored indicators because there are more states than up/halted; for example when a box is suspended, it shows an orange indicator.

2.) I think that's reasonable

3.) This would really slow down the app on computers without SSD's. Also, if you removed a box, or halted/upped one, the box order might change just as you are about to click one.. which would be pretty irritating

4.) Reasonable

5.) Arguable to me, we show an indicator on that menu item if there is an update available; plus, it is technically an action, so it doesn't really make sense in my mind for it to be in Preferences

I do agree that the new UI could look better, we'll look into possibly skinning it to look like the native OSX menu. Reverting back to the actual native menu is not an option due to aforementioned limitations.

Thanks for the input, we appreciate you taking the time to post your feedback

[stopiccot]

Just curious what limitations forced you to move to custom menu?

[amitailanciano]

We really wanted Vagrant Manager 2.0 to be a real step up from 1.x, so one of the main reasons we switched stemmed from the inability to manage multi-machine instances. Only with the new custom UI was it really feasible to allow the app to show sub-machines of a vagrant instance in a submenu of that menu item and allow you to manage those in the same way. Another reason was due to difficulties refreshing/rebuilding the menu while it was still open.

There were other more minor things such as the 'Refresh' button closing the menu when clicked not being something we wanted, however it felt just as strange to click it and NOT have it close the menu since it was a menu item like the rest of them. The new custom UI gives us more control over those kinds of idiosyncrasies. Vagrant Manager 2.0 was a complete overhaul of 1.x, and in order to provide desired functionality, we had to part with the native menu.

There are plenty of menu apps that use custom views such as Dropbox, Adobe's Creative Cloud, iStat, etc.. everyone has their own tastes and preferences. The new custom UI allows us to keep the app functional in the way we wanted it to be, but we'll try to make it look more appealing in coming releases.

[amitailanciano]

Due to popular demand we are currently re-implementing Vagrant Manager using the native OS X menu.

We'll put out a new release as soon as it's available, so keep an eye out

[ngocphamm]

That's a good news, @amitailanciano. Apparently, it's not only me who thinks the new menu is not appealing.

[chriswayoub]

The native menu has been re-implemented in release 2.1.0. You can download it from the Releases page.