While investigating getting My Apps menu items to deliver context menus for adding themselves to the Home Menu (the remainder of bug 16334), it occurred to me that any menu item, not just those that fall into the jive.ui.HomeMenu space, should be customizable to the home menu.

That is, anything delivered via SlimBrowse menus, particularly those that can already be favorited, should also be able to be added to the Home Menu directly.

In this way, a user could potentially *fully* customize their home menu to what they access most often. Something like this:

Now Playing >
My Music >
[A Napster Playlist] >
[Some app] >
[A Pandora Radio Station] >
[A Local Album] >
[An Internet Radio Stream] >
[Andy's Picks] >
Settings >

The mechanism for making this happen isn't completely clear to me. While the code to add/hide SlimBrowse items from the home menu could be managed largely client-side, SlimBrowse menus expect the callback to be another server-side request, not a client-side action.

Perhaps it could be something like:

SlimBrowse context menus (*info menus) have an item next to "Save to Favorites" called "Add to Home Menu"
The callback to this item both saves it to favorites but also does the necessary steps to push the item on to the home menu via the menustatus subscription.
The favorites configured for going on the home menu would need to be stored server side so they are displayed if the server goes away and comes back later.
Hiding one of these favorites from the home menu on the client would need to send a command back to the server saying that favorite was no longer to be on the home menu.