Bugzilla – Bug 7546
desktop skin: missing graphic assets and misc UI bugs
Last modified: 2009-09-08 09:14:28 UTC
This bug is a catch all for UI questions and issues seen in the first pass of making Squeezeplay for a larger interface. Questions: wallpaper background image Scott supplied in first deliverable is 1440x900. I converted to 800x600 to see how it looked (it looks good). But that raises the question, if Alberti is a Mac product, shouldn't we be doing a mac-like aspect ratio for the UI itself? That is, when I go fullscreen on my Mac, I have black bars on the left and right since 800x600 is 4:3. Are there going to be screensavers in Alberti? If so, should the NP screensaver be laid out any differently than the NP browse window? UI wireframes show Library->Albums list without artist names. My two cents: need both No progress bar on NowPlaying. My two cents: a NowPlaying window that gives no user feedback until a track changes is not a good idea. I'd vote for the progress bar to come back. How will textinput work in Alberti? Will we have keyboard support? IMO the wheel-style textinput input in a desktop env. is not a great one. ------------ Bugs and/or Assets needed (screenshot attachments coming): A - I haven't yet been able to get the menu/scrollbar to get any bottom padding B - Need larger mini-icons for all screens that use them C - The currently playing music note on the playlist window looks too big to me D - need bigger play/add icons for non-mouse mode (not to be confused with btn_selector_play/add which are for mouse mode) E - larger radio button assets (button, filled button) F - larger checkbox assets (box, filled box) G - bigger checkmark assets (selected, not selected) H - bigger connecting animation for fullscreen connecting popups (e.g., Connecting to SqueezeNetwork) I - textinput assets (this screen is a mess) J - different height elements in slider don't layout right, i.e., the big ball Scott supplied for the end of the volume slider). I'm guessing this will have to be fixed in the C code. K - showBriefly layout. I've failed thus far in getting any success in tweaking layout parameters for these. Is this hardcoded somewhere? -------------- Additional Assets needed: need animated connecting arrow need smaller animated connecting "spinny" for when playlist window is being updated. 125px, or whatever the final thumb size ends up being ---------------- Known issues (these will probably get there own bugs): there is a floating point exception crash when the current playlist window refreshes on track change I do not have center-screen popup yet (player status) skin doesn't handle variable height elements well (volume slider assets)
Created attachment 3102 [details] Home Menu screenshot (A&B)
Created attachment 3103 [details] current playlist window (A, B, C)
Created attachment 3104 [details] current playlist window (A, B, C) mark issues with letters
Created attachment 3105 [details] need larger play/add icons (D)
Created attachment 3106 [details] larger radio buttons (B,E)
Created attachment 3107 [details] larger checkboxes (B, F)
Created attachment 3108 [details] bigger checkmarks (G)
Created attachment 3109 [details] larger fullscreen connecting animation (H)
Created attachment 3110 [details] textinput window quite a mess (I, K)
Created attachment 3111 [details] volume popup (J) this lays out fine if I remove the slider_volume_thumb.png (the double-height knob at the end) from the slider elements
Created attachment 3112 [details] showBriefly layout (K) having a heck of a time getting anything to respond to my attempts at fixing the width/height of these showBriefly popups
Created attachment 3113 [details] NowPlaying window no real layout issues here (I think). Including to round out the set. FYI, Artwork size is currently set to 350px
Created attachment 3114 [details] These are the mini icons used in the SBC UI that need to be made larger (B)
CC'ing Noah, who will be helping out.
> wallpaper background image Scott supplied in first deliverable is 1440x900. I > converted to 800x600 to see how it looked (it looks good). But that raises the > question, if Alberti is a Mac product, shouldn't we be doing a mac-like aspect > ratio for the UI itself? That is, when I go fullscreen on my Mac, I have black > bars on the left and right since 800x600 is 4:3. I agree that we should design this for the 16:9 crowd and support 4:3, not the other way around. Especially since this is going to be aimed at the technorati crowd who will probably have somewhat new monitors or laptops, which would be widescreen. So what we can do if possible is design the backgrounds for 16:9, then flush the text to the left in 16:9. If we can allow more space on the right for text/characters horizontally that would be great too. Then for 4:3 we can only show part of the background and keep the character length the same as now. So that's basically a long "I agree" > Are there going to be screensavers in Alberti? If so, should the NP screensaver > be laid out any differently than the NP browse window? > UI wireframes show Library->Albums list without artist names. My two cents: need both > No progress bar on NowPlaying. My two cents: a NowPlaying window that gives no > user feedback until a track changes is not a good idea. I'd vote for the > progress bar to come back. I don't think that the NP screensaver should be different, but I see the issue with the progress bar. We discussed this during one of our meetings. Scott do you think it would be possible to mockup NP with the progress bar? > How will textinput work in Alberti? Will we have keyboard support? IMO the > wheel-style textinput input in a desktop env. is not a great one. Yeah we will have keyboard support and I'm not too worried about the input if you think about the use case. If you need to use text input for search or whatever, you would probably walk that "10 feet" and use your keyboard. I think its a good assumption that someone who has SP would have a keyboard. > Additional Assets needed: > need animated connecting arrow > need smaller animated connecting "spinny" for when playlist window is being > updated. 125px, or whatever the final thumb size ends up being I'm sure there are some freeware animated gifs out there that look similar to the visual design we already have...I'll take a look > Known issues (these will probably get there own bugs): > there is a floating point exception crash when the current playlist window > refreshes on track change That's an easy one, I already fixed that. Just kidding, good luck :)
The UI needs to work in both 16:9 and 4:3. We already can scale readily with the existing skin, this shouldn't be that big of a challenge. I suspect that designing for 4:3 and allowing stretching will be easier, but both need to work without black bars.
> The UI needs to work in both 16:9 and 4:3. We already can scale readily with > the existing skin, this shouldn't be that big of a challenge. The major thorn in that is artwork size, particularly large artwork in the NowPlaying page. Artwork size is hard-coded and does not change dynamically when the window size is changed, I think it's only going to look "just right" in one aspect ratio. > I suspect that designing for 4:3 and allowing stretching will be easier, but > both need to work without black bars. are you saying Squeezeplay needs to make a decision at runtime which aspect ratio to use?
er...future hardware? turning secure flags on just in case. feel free to correct if I'm wrong.
sorry kdf, just SqueezePlay on the desktop. nothing s3cr3t here :)
heh, ok. I think it was the phrase 'mac product' that got me wondering.
Ben/Tom, which of you should take this.
this bug is somewhat outdated as it was originally for the Alberti project, but a good part of it is still correct. I still need a bunch of graphics for the desktop UI to be acceptable.
this was for alberti, and will be a mess to continue to stay open against the new new new desktop squeezeplay
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.