Originally posted by kidstypike
View Post
Announcement
Collapse
No announcement yet.
Announce: Material Skin
Collapse
X
-
Material debug: 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here.
-
Originally posted by cpd73 View PostI can easily re-add 'Music Source', but I'm still not convinced. If you can do this from the player, and its not something you'd want to do often, I'm not sure if it belongs in the UI. If your want your players on mysqueezebox.com, why would you be using LMS?Server - LMS 8.4.0 RPi4B 4GB/NanoSound ONE case/pCP 8.1.0 - 75K library, playlists & LMS cache on Sata SSD (ntfs)
Lounge - DAC32 - AudioEngine B2
Office - RPi 3B+/HiFiBerry DAC HAT/RPi screen - Edifier D12
Bedroom - Echo Show 8
Spares - 1xSB Touch, 1xSB3, 4xRPi, AVI DM5 speakers
Comment
-
Originally posted by cpd73 View PostI can easily re-add 'Music Source', but I'm still not convinced. If you can do this from the player, and its not something you'd want to do often, I'm not sure if it belongs in the UI. If your want your players on mysqueezebox.com, why would you be using LMS?
Sent from my Pixel 3a using TapatalkLiving Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
Bedroom: Radio
Bathroom: Radio
Comment
-
Originally posted by slartibartfast View PostIn my extras list it is the only one that has a useful purpose otherwise I would leave extras turned off.Server - LMS 8.4.0 RPi4B 4GB/NanoSound ONE case/pCP 8.1.0 - 75K library, playlists & LMS cache on Sata SSD (ntfs)
Lounge - DAC32 - AudioEngine B2
Office - RPi 3B+/HiFiBerry DAC HAT/RPi screen - Edifier D12
Bedroom - Echo Show 8
Spares - 1xSB Touch, 1xSB3, 4xRPi, AVI DM5 speakers
Comment
-
Originally posted by slartibartfast View PostIn my extras list it is the only one that has a useful purpose otherwise I would leave extras turned off.Material debug: 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here.
Comment
-
Originally posted by cpd73 View PostI wasn't asking for things missing from Extras, more missing/unimplemented features in general.
The only reason I use classic is for the settings. Material is more touchscreen friendly (which is great), but some of the more complicated settings work better in classic (and you wouldn't be messing with those settings on a touch device anyways).
Comment
-
Originally posted by jeroen2 View PostAh, not for me really. I think the current material is quite perfect.
The only reason I use classic is for the settings. Material is more touchscreen friendly (which is great), but some of the more complicated settings work better in classic (and you wouldn't be messing with those settings on a touch device anyways).
Sent from my Pixel 3a using TapatalkLiving Room: Touch or Squeezelite (Pi3B) > Topping E30 > Audiolab 8000A > Monitor Audio S5 + BK200-XLS DF
Bedroom: Radio
Bathroom: Radio
Comment
-
Announce: Material Skin
> I can easily re-add 'Music Source', but I'm still not convinced. If you
> can do this from the player, and its not something you'd want to do
> often, I'm not sure if it belongs in the UI. If your want your players
> on mysqueezebox.com, why would you be using LMS?
That's a question that has been asked a lot. Only yesterday I tried to
figure out how many active players we had on mysqueezebox.com. And I saw
more activity for players than I saw connected players... there must be
a number of users still switching back and forth (or disconnecting, maybe).
FWIW: there's the "disconnect" command to send a player from server A to B.
But IIRC we disabled it for Receivers, as they don't have a UI to bring
it back easily if the target server wasn't available.
--
Michael
Michael
"It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
(LMS: Settings/Information)
Comment
-
Originally posted by slartibartfast View PostDo you mean Classic or Default?Material debug: 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here.
Comment
-
Originally posted by cpd73 View PostI'm currently developing what I think will be v2.0 of Material, and I'm trying to ensure Material has all the features of the Default skin, so would like to know of any that are missing? For 2.0 I've added:
- 'Extras' section. Disabled by default, and can be enabled in the 'Settings' dialog. Items are shown in the same manner as the settings pages; i.e. Material uses a re-themed Classic skin page embedded into an iframe.
- SugarCube pages are added to 'Extras' (so adding to customactions is not required).
- Added a directory chooser dialog to the 'Basic Settings' page
I noticed that 'TrackStat' and 'DynamicPlaylists' can appear under 'Extras', with some features that are not there when in Material's browse view. Currently I manually exclude these items, should I add them under 'Extras'? Have them in both places ('My Music' and 'Extras'), just 'My Music', or just 'Extras' ??
There are, of course, more changes than this for 2.0, but these are the features that are in the Default skin and were missing from Material. I'm not promising to implement all missing features, but I'd at least like to know what they are...
Someone remarked that the Default skin was better for some more complex server settings and a touch screen device shouldn't be used for that task anyway, but I like Material on a web browser too and I'd like to use it for Server Settings if at all possible.
Comment
-
Originally posted by mr-b View PostIf for #3 you mean an equivalent for the Browse button, then that appears in other places e.g. Advanced> Formatting and some plug-ins e.g. Music & Artist Information. The Browse function not only prevents silly typos but it shows that directories are reachable too, so it's useful functionality.
[Edit] No need for list, I should be able to find all by their class name.
[Edit2] I've also noticed my folder buttons dissapear when the page is changed!Last edited by cpd73; 2020-10-14, 14:20.Material debug: 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here.
Comment
-
Announce: Material Skin
>> If for #3 you mean an equivalent for the Browse button, then that
>> appears in other places e.g. Advanced> Formatting and some plug-ins e.g.
>> Music & Artist Information. The Browse function not only prevents silly
>> typos but it shows that directories are reachable too, so it's useful
>> functionality.
>
> Yes, that is what I mean. I'll have a look at those other places too.
> Can you provide full list?
The Default skin hasn't this hardcoded. But there's a script running
whenever a settings page is opened checking for elements with the
"selectFolder" class. All those items would get the browse handler.
The same applies for "selectFile", which can have additional classes
defining the accepted file type (to be handled in the picker code), eg.
"selectFile selectFile_png selectFile_jpg selectFile_jpeg".
You can use the "readdirectory" command to browse the filesystem.
--
Michael
Michael
"It doesn't work - what shall I do?" - "Please check your server.log and/or scanner.log file!"
(LMS: Settings/Information)
Comment
-
Originally posted by mr-b View Post
Someone remarked that the Default skin was better for some more complex server settings and a touch screen device shouldn't be used for that task anyway, but I like Material on a web browser too and I'd like to use it for Server Settings if at all possible.
Server - LMS 8.4.0 RPi4B 4GB/NanoSound ONE case/pCP 8.1.0 - 75K library, playlists & LMS cache on Sata SSD (ntfs)
Lounge - DAC32 - AudioEngine B2
Office - RPi 3B+/HiFiBerry DAC HAT/RPi screen - Edifier D12
Bedroom - Echo Show 8
Spares - 1xSB Touch, 1xSB3, 4xRPi, AVI DM5 speakers
Comment
-
Originally posted by kidstypike View PostI could be wrong, but I don't see any way of using any of the "Default" pages pictured below on Material? Mainly aimed at the older hardware players with VDU screen.Material debug: 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here.
Comment
-
Originally posted by mherger View Post>> If for #3 you mean an equivalent for the Browse button, then that
>> appears in other places e.g. Advanced> Formatting and some plug-ins e.g.
>> Music & Artist Information. The Browse function not only prevents silly
>> typos but it shows that directories are reachable too, so it's useful
>> functionality.
>
> Yes, that is what I mean. I'll have a look at those other places too.
> Can you provide full list?
The Default skin hasn't this hardcoded. But there's a script running
whenever a settings page is opened checking for elements with the
"selectFolder" class. All those items would get the browse handler.
I've added a callback for when "choose_setting" changes. This appears to be called eary, so I had to add a 1/4 second delay before looking for 'selectFolder' items - not nice
Originally posted by mherger View PostThe same applies for "selectFile", which can have additional classes
defining the accepted file type (to be handled in the picker code), eg.
"selectFile selectFile_png selectFile_jpg selectFile_jpeg".
Originally posted by mherger View PostYou can use the "readdirectory" command to browse the filesystem.Material debug: 1. Launch via http: //SERVER:9000/material/?debug=json (Use http: //SERVER:9000/material/?debug=json,cometd to also see update messages, e.g. play queue) 2. Open browser's developer tools 3. Open console tab in developer tools 4. REQ/RESP messages sent to/from LMS will be logged here.
Comment
Comment