albertinad/issue 12

Hi @njx  I forked your repo and create this branch to fix the issue #12 as the first implementation.
But in the process I fixed some other issues, below you can find more detail about this changes.

- issue #12

While bower registry is being fetched and downloading modules metadata, the status is displayed not only in the QuickSearch but also in the StatusBar, at the information section. I choose this section because is the one that is more visible for the user, even when he or she hides the Project SideBar and the component can log a little bit more of status information.
When an error occurs or the downloading was successful, the message is updated and then removes the entry from the StatusBar.

![002](https://cloud.githubusercontent.com/assets/2309921/4854983/dd825552-609d-11e4-9bf9-e3a5a4cd1490.png)

I fixed the position of the spinner in the QuickSearch, now looks like the following,

![001](https://cloud.githubusercontent.com/assets/2309921/4854979/b4d50d16-609d-11e4-9797-8845ef9e221d.png)

A new local module is added in order to organize the code and defines components with a single or fewer responsibility: StatusDisplay.
This module exposes an API to create StatusDisplay objects that can display information in the StatusBar, QuickSearch and Project SideBar. I reuse most of the existent code.

- I added some style properties for the text that is displayed when an installation of a bower component is taking place. This avoid the text to overflow when the message is too long without breaking the UI.

![003](https://cloud.githubusercontent.com/assets/2309921/4855031/b4a65966-609e-11e4-8d07-eaff88a90cab.png)

- issues #11 and #14
The key shortcut was updated, I suggest "Shift-Alt-B" combination.

- issue #16
QuickOpen.basicMatchSort updated to StringMatch.basicMatchSort

- The bower dependency was updated to the latest stable version.

In the following days I will be working on fixing the other issues in the backlog.  I also have some ideas that I will like to discuss with you and implement on branches. You can see my work on my fork.

Thanks!
Yes, you're right. I tried but Quick Open does not expose an API for that. It is possible, we know the id of the label so we can retrieve it from the DOM in a hacky way. The good thing of displaying the message in other place is that when the user close Quick Open, he still can known what is happening with bower, like a background task.
I took a look at Quick Open component and I think is not so hard to expose that API, to make Quick Open more powerful by allowing to display status dynamically.