Daniel, isn't this bug 5437 again? I know this is for jive, but it may be useful to have the effort spent as a combined task, rather than doing one and reimplementing for the other. At least with Jive it knows the controller info :)

If nothing else, worth linking them as depending on one another.  

I thought of these as different.  But I can see how they'd be linked and if engineering would end up working on them at the same time then certainly let's not have any redundancy.

My goal here is to have the information available in both areas: on Jive and in Slimserver.  Whatever process best fits that is the right process.

Dean, comments?

Let's make sure that we have all the requested information in the Settings -> <playername> Information and Controller Settings -> About screens.

this is an enhancement...

anything with Severity "enhancement" is getting a milestone tag as "Future"

Then I am altering this to not be an Enhancement.  We need access to this information quickly and easily.  Currently it's spread around under several menus.  Yes it's there.  But on the phone we need to direct the customer to look it up.  

Please re-assess this bug and assign to 7.0 or 7.1?

How 'bout I put it as a 7.0 P5 bug, which ranks it ahead of 7.1 in my priorities...

I actually think this will be pretty fun to implement, but I see it taking some time, of which I have precious little right now...

Ben, that is more than reasonable.  Thanks so much!  When you begin to look at this, let me know if there's any further info or feedback that would be helpful.

change 16144 adds a couple of missing player items and sets them all up to match the web UI's SC Status page.

Server and Library info are still missing.  Should this be something we have on the <player> information page, or on the about jive page??

A bit more complicated, and less in line with what service seems to be requesting there could be submenu items.  I'm not sure whether this is something easy to do from a textarea or not. First run might be best to have it all on the player info page and have library/server info on the lower part so we can scroll down.

This also needs to be refactored into something central.  Maybe hashes for each category of info that can be called up by player, jive and web ui by category where needed.  However, that's for later.

per discussion today, bug fixes are targetted for 7.0.1, new features for 7.1. This is the latter.

wiping priority field in 7.1 target bugs, as the priorities that were set as 7.0 target bugs are not relevant here.

Michael, adding you to the cc: on this one... I noticed that the webUI has a fairly detailed display of server and player statistics. How are you generating that data? 

My hope is that we can have a unified framework for SC to push system information out that the webUI or jive UI or whatever can pick up and display as needed.

On the SBC side, I'm thinking that it subscribes to a systemstatus subscription to each available SC. SC would then periodically pushes out information on server info, connected players, connected controllers, etc. in a similar manner to what playerstatus and serverstatus are currently used.

it's not common yet.  See Slim::Web::Settings::Server::Status and Slim::Buttons::Information.  They both compile similar information, however.  If we could all agree on common info, it shouldn't be too hard to have something like Slim::Utils::ServerStatus do the real work. I did create the web ui module with the idea that we could have something more or less structured.

versionString should be dismantled and rebuilt to fit the common structure as well.

"If we could all agree on common info" -- let's start there then. I'd rather spend a little extra time and do this right, eh?

Jive currently gets a bunch of server info from a 'serverstatus' subscription (Slim::Control::Queries::serverstatusQuery), but I think we are spec'ing out something broader here. Will it cause headaches to call it something other than ServerStatus? SystemSummary is what I was thinking...

new query would be better, even if it's redundant on some things.  We can build something structured, then walk through it from each ui to process it to fit.

EN/settings/server/status.html probably shows my idea of a structure as clearly as anything.  All I'd do further is to join each block into a single hash:
systemsummary => {
   library => {...},
   progress => {...},
   server => {...},
   clients => {...},
   controllers => {...},
   folders => {...},
   logs => {...},
}

and I'd add the versionString to the server section as individual items. See S::W::S::S::Status for the breakdown within each key.  I can maybe write it up more completely in the next couple of days, but I'm off to England again for two weeks as of Friday.  Time is a bit short.

Created attachment 3447 [details]
current list of web items

This is what the web covers (assuming Controllers eventually have the required info available)

The more that can be reduce to function calls (getLogs, progress(), etc) is probably better.  Is it possible to generate live xml/opml that can be browsed automatically by xmlbrowser/infobrowser??  That would be best overall I think as this is our built in browseable format.

wow, opml would be great. My only concern would be the flexibility of opml in terms of formatting for the screen on jive, but I bet we can work something out.

if Andy can use opml styling for the new trackinfo stuff I just saw, systemSummary should be exactly the same kind of thing Trackinfo => systemInfo

I'm afraid we're bumping up against a deadline for 7.1 checkins, and this bug needs more time. Target to 7.2, prioritizing to P1.

Marking as an enhancement.

punting to 7.3

Need to point out, when using bridged mode there's currently no way to see what IP is assigned to a SB Controller.

Another reason this Status page is needed.

*** Bug 9560 has been marked as a duplicate of this bug. ***

My much simpler request - IP address and Signal strength in about, has been dup'd to this.  I'm concerned that this complex enhancement will keep slipping out, when in fact what we need most is the simpler suggestion I made.

(Ignorance alert:  I of course don't know if the two facts I list are easily added to the about screen.  I'm just guessing/hoping).

I disagree with that statement-- what has happened is we end up supporting simple temporary solutions and pushing out what really needs to be done. Time to draw the line in the sand and fix this in its entirety. Michael and I will both be working on this for 7.3, and I have no intention of letting it slip.

Ben - I was considering adding this feature as another OPML menu (similar to the track info menu) to SC. I'll get back to you for the Controller specifics. Ok?

OPML sounds like a great approach since the foundation is already there.

We can cross this bridge when we come to it, but one thing I want to make sure is that the data are delivered in a way that lays out nicely on the controller-- whether it be a hierarchical set of menus or a long well layed out textarea, I don't really know the best route at this point. Regardless, we should be able to add the appropriate flags to XMLBrowse items to cause SBC to render the data appropriately.

I hoped to have something hierarchical like on the player's UI:

Server Information
  Server Name
  IP Address
  ...
Library
  Titles...
  Artists
  ...
Players
  Name
  IP
  Signal Strength
...

Hope to have some code by tomorrow.

There's now a uniform Settings/Information menu hierarchy available on player and controller, plus enhanced Settings/Status in web. We still need to add Controller information (bug 5437). Plugins can hook into these menus, see eg. the Health plugin.

Verified r 3403.  A new Jive Menu item; Settings > Advanced > Information exists.

This bug has been fixed in the 7.3.0 release version of SqueezeCenter!

Please download the new version from http://www.slimdevices.com/su_downloads.html if you haven't already.  

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.