Announce: Material Skin

[slimhase]

I re-upgraded today to 0.2.1 to provide the requested information - and now I can not reproduce the error!
Very strange - yesterday it happened very consistent multiple times both on my phone as well as SLX on W10.
(I changed nothing from yesterday to today other than re-upgrading to current skin version)
Very, very odd.

Finally, the "left pane missing bug" reoccured - however, both on the iPhone as well as on Windows through SLX, I do not have browser developer tools.
(Or I don't know how to enable it in SLX) Sorry. :-(
I am now exercising the skin via Chrome & Edge; hopefully, I will see the bug there as well at some point.....

(BTW: On the iphone, clearing the cache is not enough to make it funtion again - I also need to recreate the Material Web-App.)

[cpd73]

Finally, the "left pane missing bug" reoccured - however, both on the iPhone as well as on Windows through SLX, I do not have browser developer tools.
(Or I don't know how to enable it in SLX) Sorry. :-(
I am now exercising the skin via Chrome & Edge; hopefully, I will see the bug there as well at some point.....

(BTW: On the iphone, clearing the cache is not enough to make it funtion again - I also need to recreate the Material Web-App.)

But, does it only happen if you have pinned apps? Please try removing all of these, and see if the error re-occurs.

[slartibartfast]

But, does it only happen if you have pinned apps? Please try removing all of these, and see if the error re-occurs.

I can reproduce the issue on my phone by simply pinning an app, closing the webapp and reopening it. With no pinned apps it doesn't seem to occur.

Sent from my SM-G900F using Tapatalk

[slimhase]

I can reproduce the issue on my phone by simply pinning an app, closing the webapp and reopening it. With no pinned apps it doesn't seem to occur.

Sent from my SM-G900F using Tapatalk

Yes - that is the way to reproduce it!
Also on i.e. Chrome:
- pinning an app,
- closing the browser
- and reopening the browser

Then I get these errors in the console:

 HTML1300: Navigation wurde ausgeführt. mobile (1,1)
- ReferenceError: 'i' is not defined
- TypeError: Unable to get property 'addEventListener' of undefined or null reference
- ReferenceError: 'i' is not defined

And this is contents of "lms-material:inned":

key,value
lms-material::pinned,"[{""id":"apps.podcasts","title":"Podcasts","image":"/plugins/Podcast/html/images/icon_50x50_o.png","command":["podcasts","items"],"params":["menu:podcasts"]},{"id":"apps.radioparadise","title":"Radio Paradise","image":"/plugins/RadioParadise/html/icon_50x50_o.png","command":["radioparadise","items"],"params":["menu:radioparadise"]},{"id":"apps.spotty","title":"Spotty","image":"/plugins/Spotty/html/images/93aac68fb06348598c1e67734dfaceee_50x50_o.png","command":["spotty","items"],"params":["menu:spotty"]}]"

[ElFishi]

When the error occurs again, please

1. Open your browser's developer tools.
2. Open the console tab - errors causing the view not to be drawn should be logged here
3. Open the storage tab and expand local storage on the left.
4. Click the LMS url that appears.
5. On the right should now be listed materials settings that are stored
6. Paste the contents of "lms-material:inned" here. This is the setting that contains the details of pinned apps.

The above is for firefox - don't currently have chrome installed here, but you should be able to locate 'locate storage' in a similar vein.

I can only assume that a pinned app is causing the storage to be corrupt. But as it does not happen here, kinda hard to determine the issue. Perhaps an encoding issue? However, there were no changes between 0.2.0 and 0.2.1 that should have affected this.

clearing the cache in chrome or edge does not bring back the left pane for me.
I presume the equivalent info to the one asked above is for chrome:

[{"id":"apps.spotty","title":"Spotty","image":"/plugins/Spotty/html/images/93aac68fb06348598c1e67734dfaceee_50x50_o.png","command":["spotty","items"],"params":["menu:spotty"]}]

and for edge

[{"id":"apps.spotty","title":"Spotty","image":"/plugins/Spotty/html/images/93aac68fb06348598c1e67734dfaceee_50x50_o.png","command":["spotty","items"],"params":["menu:spotty"]}]

[cpd73]

Thanks all, I've found the error - stupid copy'n'paste error. I wasn't seeing it as the error is no longer in git! Will be fixed in next release - which I'll try and make later.

[cpd73]

0.2.2 Release

Main changes:

1. Fix cover display when re-ordering favourites.
2. Use current cover as queue background, and album/artist as browse background
3. Re-add option to sort favourites, disables drag'n'drop ordering.
4. Add button to save default UI settings, and pinned items, on server.
5. Re-add swipe to change view.
6. Fix pinned apps breaking browse view.

[grimmace92]

Main changes:

1. Fix cover display when re-ordering favourites.
2. Use current cover as queue background, and album/artist as browse background
3. Re-add option to sort favourites, disables drag'n'drop ordering.
4. Add button to save default UI settings, and pinned items, on server.
5. Re-add swipe to change view.
6. Fix pinned apps breaking browse view.

Use current cover as queue background, and album/artist as browse background

This looks great! Do you plan on adding this to the now playng screen in the mobile version? Would look awesome there too. Also is it possible to have a toggle in desktop version to show the mobile now playing screen instead of the menus? Thanks for the work you have done. It looks awesome.

[bernt]

Main changes:

1. Fix cover display when re-ordering favourites.
2. Use current cover as queue background, and album/artist as browse background
3. Re-add option to sort favourites, disables drag'n'drop ordering.
4. Add button to save default UI settings, and pinned items, on server.
5. Re-add swipe to change view.
6. Fix pinned apps breaking browse view.

Thank you! And a very merry christmas to you and all that make this great system even greater.

[slimhase]

Main changes:

1. Fix cover display when re-ordering favourites.
2. Use current cover as queue background, and album/artist as browse background
3. Re-add option to sort favourites, disables drag'n'drop ordering.
4. Add button to save default UI settings, and pinned items, on server.
5. Re-add swipe to change view.
6. Fix pinned apps breaking browse view.

Thank you again - it works great!

P.S. Would it be possible down the road to have the ability to also move items from the main menue to the top of the menue (or pin them to the top)?
I.e. I often use 'Favourites' and 'Radio' - which are at the very bottom and need to be scrolled down to in the mobile smartphone view.

[Franck@]

Main changes:

1. Fix cover display when re-ordering favourites.
2. Use current cover as queue background, and album/artist as browse background
3. Re-add option to sort favourites, disables drag'n'drop ordering.
4. Add button to save default UI settings, and pinned items, on server.
5. Re-add swipe to change view.
6. Fix pinned apps breaking browse view.

Thank you for the latest developments of the skin.

I just observe two small problems:

• With both Chrome for Android and Firefox for Android, icons for adding alarm clock or changing alarm clock have no effect. (No input interface is displayed when you click on these icons.)
• With Chrome for Android, the interface is in French. With Firefox for Android, the interface is in English. (My two browsers are configured in French.) It seems to me that the problem appeared with one of the last versions of the skin, but I don't know which one. Some time ago, even with Firefox, the interface was in French.

[cpd73]

With both Chrome for Android and Firefox for Android, icons for adding alarm clock or changing alarm clock have no effect. (No input interface is displayed when you click on these icons.)

Ah, yeah - this is broken. Simple one-line fix.

With Chrome for Android, the interface is in French. With Firefox for Android, the interface is in English. (My two browsers are configured in French.) It seems to me that the problem appeared with one of the last versions of the skin, but I don't know which one. Some time ago, even with Firefox, the interface was in French.

Can't test on a handset at the moment, but desktop Firefox and Chromium picked up the French translation when I configured LMS from French (both desktop and mobile layouts of material). Perhaps you need to empty your bowser's cache?

[mherger]

An issue I thought was only there in the old web UI code: on streams which update their metadata (eg. radio stream) the playlist would not always update, while the currently playing song does. I thought I fixed this in the web UI a few days ago... but anyway, Material isn't using that code at all. Are you caching some data a bit too aggressively?



You can see the correct title at the bottom. In the playlist panel the previous title is shown. This might have been this way for a long time. But the great new artwork background makes it really obvious.

The problem here might be that the URL does not change. But it's metadata. If you cached that data based on the URL or something, you might get stuck with stale title information.

[cpd73]

An issue I thought was only there in the old web UI code: on streams which update their metadata (eg. radio stream) the playlist would not always update, while the currently playing song does. I thought I fixed this in the web UI a few days ago... but anyway, Material isn't using that code at all. Are you caching some data a bit too aggressively?

That's odd. I can see why the item in the queue would be different. But the background image's URL should be set by the currentcover.js file. This listens for the current track, and 'emits' the cover URL. Both the now-playing and queue views listen for this, and set the background too it. So, its odd that they are different. Not sure how that could occur. I'll look into this.

[cpd73]

An issue I thought was only there in the old web UI code: on streams which update their metadata (eg. radio stream) the playlist would not always update, while the currently playing song does.

I think this is now fixed in git. Michael, can you update your git checkout and confirm? I've tested with one station, and the cover and meta data now update for me.