View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0017544 | MMW 5 | Skinning framework | public | 2021-02-13 18:38 | 2022-09-14 14:39 |
Reporter | drakinite | Assigned To | |||
Priority | high | Severity | feature | Reproducibility | N/A |
Status | new | Resolution | open | ||
Product Version | 5.0 | ||||
Target Version | 5.2 | ||||
Summary | 0017544: Show thumbnail preview for skins in Tools>Options>Skins | ||||
Description | User suggested that the skins panel should show a preview of what a skin looks like, before they hit OK to change it. We can use the icon that's specified in info.json if it exists. This is a good idea because changing skins takes a lot longer in MM5 than MM4, so users should be able to see what they're gonna get before they switch. https://mediamonkey.com/forum/viewtopic.php?f=30&t=98422 Note: The current skins use a very low resolution thumbnail icon in the interest of space; We may wish to make them higher resolution and perhaps blur the artist/track names in the new screenshots. | ||||
Tags | No tags attached. | ||||
Fixed in build | |||||
|
Note that MM5 do not have Tools>Options>Skins Not sure if Skin change dialog or Tooltip can have LQ preview or we can make overlat layout on top of whole MM5 window as preview But this needs redesign in order to make such feature. There is an option to have tree node ith extensions taht can use Album Art field and behavior to sho preview image. EDIT: Assigned to Jiri for evaluation and best approach on implementation. |
|
Err, yes, it does? XD This is what I was imagining. Putting it in a fieldset would make the most sense to me, as that's how most options panels are designed. If the selected skin has no thumbnail and/or no description, it should be hidden. |
|
Sounds good to me (per the last screenshot above) and I would add also: 1) [Download more skins...] button or link (like used to be in MM4) 2) Probably also configurable font size (like used to be in MM4 and is requested by users) |
|
Sounds good. I'd also add: 3) Color(s) selection. As already discussed, changing the main skin color (or sometimes multiple colors) might be useful. Alternatively, it was also proposed to rather derive skins on existing skins and this way easily create multiple variants of the same skin. This way we could offer e.g. Material Design (Dark) skin with several sub-skins (tree structure would be useful to present the hierarchy?) where the default Orange color would be replaced by Green, Blue and other tuned variants. Deferring to 5.0.2, but probably rather to 5.1. |