Preliminary infrastructure for share rooms.
Hook share rooms into the menusheet.

Share Rooms collection fetch isn't working, because I'm unsure about the
rigth URL to use.
Include a preliminary version of .mySharesRootURL().  Not yet tested, at all.
Implement model-less view that consolidates a listing of share rooms
currently being visited by the app and the list of share rooms associated
with the account (when there is a logged in account).

This is not yet working, but further along.  Further along in the right
direction is the question; this checkin will enable some review.

The current, outstanding problem is putting the visited set of share rooms
in a collection still requires that the collection have a URL - but it's
just a local collection of share rooms, the ones being visited.

Rename ShareRoomsView.js to ShareRoomsViews.js, since it's, significantly,
more than one.  Adjust grunt concat accordingly.
Instantiate the ShareRoomsConsolidatedView and push it on the view stack.

Question: do we need to provide a case for the current view being the same
as the new one?
Whoops - add comment with question about providing for case where view
isn't changing...
Just a few tweaks from tommy
Devices were assuming all views had models… naughty.
ShareRoomModel.js: *not* ShareRoomsModel.js.
myShareRoomsCollection is for the list of share rooms associated with
accounts. It requires distinctive parsing, which is now implemented.  Also,
grunt.js tracks the name changes.
Templates for share room views:
- the root view
- subordinate share room item view
Not quite working, but further towards implementing a collection view of
the account ("my") and visited share rooms.

- Use the new templates
- Use myShareRoomsListView for the account share rooms subview.

I think the ShareRoomsListView should be useful identically for the account
and visited share room lists.  I'm not quite doing the collection view
right, though, not getting the right 'this' for the subviews.
Not quite working, but further towards implementing a collection view of
the account ("my") and visited share rooms.

- Use the new templates
- Use myShareRoomsListView for the account share rooms subview.

I think the ShareRoomsListView should be useful identically for the account
and visited share room lists.  I'm not quite doing the collection view
right, though, not getting the right 'this' for the subviews.
Preliminary infrastructure for share rooms.
Hook share rooms into the menusheet.

Share Rooms collection fetch isn't working, because I'm unsure about the
rigth URL to use.
Include a preliminary version of .mySharesRootURL().  Not yet tested, at all.
Implement model-less view that consolidates a listing of share rooms
currently being visited by the app and the list of share rooms associated
with the account (when there is a logged in account).

This is not yet working, but further along.  Further along in the right
direction is the question; this checkin will enable some review.

The current, outstanding problem is putting the visited set of share rooms
in a collection still requires that the collection have a URL - but it's
just a local collection of share rooms, the ones being visited.

Rename ShareRoomsView.js to ShareRoomsViews.js, since it's, significantly,
more than one.  Adjust grunt concat accordingly.
Instantiate the ShareRoomsConsolidatedView and push it on the view stack.

Question: do we need to provide a case for the current view being the same
as the new one?
Whoops - add comment with question about providing for case where view
isn't changing...
Just a few tweaks from tommy