Servers browser, shares browser and apps browser

[cpg]

The app, at the highest level (once the user is logged in), consists a Server browser, and with a server selected, then a Share browser and and App browser.

Servers

A user may have one or more servers. If a user has three servers called "joe" "joe-2" "Welcome to Amahi", the user should be able to see them up top in the app.

The user must be able to get back "up" to this level to select any other browser.

Browsers may be active or inactive as given by the API, It should be clear to the user which one(s) are active and which ones are inactive. The user must be able to select an active server at any time.

If there is only ONE and exactly ONE server that is active at the moment, it should be automatically selected.

When a server is selected, the user should have the ability to select Shares or Apps.

Careful attention should be placed in proper error display so that the user sees graceful errors in case a server goes inactive (e.g. if the user loses WiFi -- simplest way to test this error).

Shares

When browsing shares, the user should see the shares of the selected server. Once selected, the user should then be able to browse all files and folders in the share and recursively navigate them. We will talk about opening them, thumbnails, handling internally or sending to other apps, sharing, etc., in a separate specification.

Apps

Separated to #45.

Misc Requirements

The app has to work on phones as well as larger tablets, both in portrait and landscape modes.

[cpg]

Closed by #35