Bugzilla – Bug 13036
iPeng feature: Add "menuIcon" and "menuIconID" fields to SlimBrowse menus
Last modified: 2009-09-08 09:14:15 UTC
This is a proposal how iPeng 1.2 will handle menu icons for menus delivered using the SlimJSON protocol. In iPeng, this will work fow Home Menu items as well as for SlimBrowse items. Please comment if you want anything changed, there's about a window until mid August for that. Rationale: iPeng needs monochromatic icons for the main menu, the icons must make use of the alpha channel to provide contrast (as opposed to having a solid background). This doesn't work well with the icons delivered by SC by default. I will try to do a bit of processing to make them _somewhat_ work, but it will not be comparable to "real" b/w icons. So I want to give plugins a chance to provide icons for the iPeng main menu. Format: 40x30 pixels (up to, can be smaller). Alpha channel required, so PNG is probably a good idea. Should be b/w. iPeng will display others, too, but some results may be surprising, iPeng will use inverted and b/w'ed versions, too. Protocol change: iPeng will use thw following two fields in a menu item description: menuIcon => <URL> The URL of the image to be used menuIconID => <identifier string> This can be used to use iPeng's predefined standard icons for a menu. The ID of any menu item can be used and if iPeng knows an icon for that item, it will use it. Example: menuIconID => "myMusicArtists" Would use iPeng's icon for the "Artists" menu. Does this make sense?
I think it might be a good idea to adjust this so it's possible to deliver different icons for different skins. This way it would be possible to use the same mechanism for delivering icons to Controller, Squeezeplay Desktop and iPeng. With the suggested solution it assumes that all clients wants the same icon OR that the menuIcon/menuIconID attributes ONLY is used by iPeng while Squeezeplay Desktop and Controller use icon-id instead. It would be nice to have a common solution that works for all clients.
Any ideas?
The consensus in the bug meeting is just that there's lots of other important work at the moment.
I think that's a misunderstanding. Erland's generalization aside this isn't meant as something where anybody has to do anything, except maybe for myself. I would have assigned it to myself but I can't. It's a feature iPeng will provide on top of the existing SlimBrowser protocol. All I'm asking for is some feedback whether this fits into the existing namespace or whether I should change something. Plus it would be good to have it documented for plugin developers (which was the main intent of this bug), but I don't know where. The only documentation I am aware of is this outdated one: http://wiki.slimdevices.com/index.php/SqueezeCenterSqueezePlayInterface I could change that but would like to get a bit of feedback before that. If you could point me to documentation for plugin developers I would update that as well.