Announce: Material Skin

[cpd73]

Even in the classic web interface I didn't see an update alert. Yet when I went into the Settings Plugins tab, the Material Skin update was waiting right at the top.

Perhaps a plugin from an external repo will not trigger an update message from LMS?

The update check parsing was broken. It was never a fully tested piece of code.

And perhaps unrelated: in Squeezelite-X with Material Skin, before and after applying the plugin update I get "Failed to determine plugin status".

You need a very recent (last few weeks-ish) version of LMS for the update check.

[left channel]

You need a very recent (last few weeks-ish) version of LMS for the update check.

OK thanks. I've got the October 5th LMS. I've requested a newer release be added to the next Sonicorbiter server update.

[mherger]

Announce: Material Skin

> Even in the classic web interface I didn't see an update alert. Yet when
> I went into the Settings Plugins tab, the Material Skin update was
> waiting right at the top.

The check only happens every x hours. If you visit the page, then it'll
be updated unless it's fresher than 5 minutes old.

> Perhaps a plugin from an external repo will not trigger an update
> message from LMS?

I guess by "external repo" you mean a manually added url? As the main
repository is still updated semi-manually by myself, the repository
sometimes takes some time to pick up the latest changes. When I'm
asleep, you'll need to be a bit more patient :-)

--

Michael

[left channel]

> I guess by "external repo" you mean a manually added url? As the main
repository is still updated semi-manually by myself, the repository
sometimes takes some time to pick up the latest changes. When I'm
asleep, you'll need to be a bit more patient :-)

--

Michael

Yes that's what I meant, because I manually added the Material Skin repo. But now that you mention it, I see that by definition all the third-party plugins are external.

Wait... you sleep? Doesn't seem like it. :-)

[rgdawson]

OK, just got v0.2.0. I notice that you now have a setting for Application Layout. So I guess, I should not be going to .../material/mobile or .../material/desktop anymore as that does not determine the layout any longer?

In Squeezelite-X, I currently have the option where the user can select Material (Mobile) or Material (Desktop). Then it goes to the appropriate URL according to the selection. Now that won't work anymore with v0.2.0, so I should have a single option in SLX for material skin and let the layout be controlled there, right?

R Greg Dawson

[cpd73]

OK, just got v0.2.0. I notice that you now have a setting for Application Layout. So I guess, I should not be going to .../material/mobile or .../material/desktop anymore as that does not determine the layout any longer?

In Squeezelite-X, I currently have the option where the user can select Material (Mobile) or Material (Desktop). Then it goes to the appropriate URL according to the selection. Now that won't work anymore with v0.2.0, so I should have a single option in SLX for material skin and let the layout be controlled there, right?

No. The application layout setting has been there since there were 2 layouts, nothing has changed with this. The only change (for 0.2.0) is that if layout is set to "auto" and you are on a desktop browser, it will auto switch between desktop and mobile depending on the width.

material/mobile and material/desktop should still work as before - at least they do for me.

[MainSqueeze]

Settings persistence on desktop

The pace at which this skin improves is amazing. If only the self-styled "agile" teams I've been working with, with their military-style standups, were half as fast as this...

Just a couple of minor questions, both about the desktop version:

1
Whenever I open the skin, it defaults to a particular player. Can I set another player as the default? Or can I have the skin remember the last player used?

2
I've set "Split artist (and album) lists into A-Z" to "on", but, unlike other settings, e.g. "Use a grid for albums", it doesn't seem to stick. When I close and restart my browser, it reverts to "off". How do I make it persist?

This affects only the desktop version; on Android tablets the skin remembers both the last player used and all the settings.

I'm using Firefox Quantum (60.3.0esr) on Debian 9 (Stretch) on the desktop; on the tablets it's Firefox for Android 63.0.2.

Thanks!

[slartibartfast]

The pace at which this skin improves is amazing. If only the self-styled "agile" teams I've been working with, with their military-style standups, were half as fast as this...

Just a couple of minor questions, both about the desktop version:

1
Whenever I open the skin, it defaults to a particular player. Can I set another player as the default? Or can I have the skin remember the last player used?

2
I've set "Split artist (and album) lists into A-Z" to "on", but, unlike other settings, e.g. "Use a grid for albums", it doesn't seem to stick. When I close and restart my browser, it reverts to "off". How do I make it persist?

This affects only the desktop version; on Android tablets the skin remembers both the last player used and all the settings.

I'm using Firefox Quantum (60.3.0esr) on Debian 9 (Stretch) on the desktop; on the tablets it's Firefox for Android 63.0.2.

Thanks!

Are you deleting your cache when you close the browser?

Sent from my SM-G900F using Tapatalk

[cpd73]

The pace at which this skin improves is amazing. If only the self-styled "agile" teams I've been working with, with their military-style standups, were half as fast as this...

Just a couple of minor questions, both about the desktop version:

1
Whenever I open the skin, it defaults to a particular player. Can I set another player as the default? Or can I have the skin remember the last player used?

2
I've set "Split artist (and album) lists into A-Z" to "on", but, unlike other settings, e.g. "Use a grid for albums", it doesn't seem to stick. When I close and restart my browser, it reverts to "off". How do I make it persist?

This affects only the desktop version; on Android tablets the skin remembers both the last player used and all the settings.

I'm using Firefox Quantum (60.3.0esr) on Debian 9 (Stretch) on the desktop; on the tablets it's Firefox for Android 63.0.2.

Thanks!

Settings are stored in browser's local storage. Looks like you have either configured your browser to delete storage when it quits, or have an extension that does this. I have my browser configured this way - so I use another browser (epiphany) just for web-apps like this.

[MainSqueeze]

Settings are stored in browser's local storage. Looks like you have either configured your browser to delete storage when it quits, or have an extension that does this. I have my browser configured this way - so I use another browser (epiphany) just for web-apps like this.

Cool, I'll install Epiphany. I had a feeling it was something to do with my privacy settings.

[rgdawson]

No. The application layout setting has been there since there were 2 layouts, nothing has changed with this. The only change (for 0.2.0) is that if layout is set to "auto" and you are on a desktop browser, it will auto switch between desktop and mobile depending on the width.

material/mobile and material/desktop should still work as before - at least they do for me.

For me, with layout set to auto in Material Skin, going to material/mobile did not force mobile on the desktop. In any case, now that you have this as a setting in Material Skin, it makes no sense for SLX to also have the choice, so I have removed it from SLX. Now in SLX, you just select Material Skin and it goes to /material, then layout is according to Material Skin Settings. Makes better sense this way.

And, by the way, I like it. I like having the setting in Material Skin and I like "auto", and I like having the ability to set/force mobile if I want to. So its all good. Your skin just keeps getting better and better.

Also, I noticed the desktop layout scrollbar initialization issue is fixed, too. Thanks again.

R Greg Dawson

[left channel]

You need a very recent (last few weeks-ish) version of LMS for the update check.

OK thanks. I've got the October 5th LMS. I've requested a newer release be added to the next Sonicorbiter server update.

Apparently there are only 5 small patches since the version we have now (October 5) and the current version (October 28). Edit: I had my misgivings, but Andrew checked them and thinks it will be OK to release to all Sonicorbiter users. I updated my server — it doesn't inform us of small updates, but when I clicked the Update button I saw it install a new version of LMS — and now in Material's Information I see "All plugins up to date".

[cpd73]

The update checking code is not working in 0.2.0. As started earlier, it's not a piece of code I got round to checking.

[left channel]

The update checking code is not working in 0.2.0. As started earlier, it's not a piece of code I got round to checking.

No rush! You're doing so much already. But now with this LMS update available to us as well, all Sonicorbiter users are ready when you are.

[left channel]

The update checking code is not working in 0.2.0. As started earlier, it's not a piece of code I got round to checking.

No rush! You're doing so much already. But now with this LMS update available, all Sonicorbiter OS server owners are ready when you are.