Or having the membership status of “Regular” (as you have)…
1 Like
Thanks @Jan_Koudijs for updating the title of this thread.
I take the occasion to ask you if you’re ok if I reimplement QueueBot in this project.
I use QueueBot a lot, and it could just be a way to have one less docker container running…
I totally understand the policies and was not complaining about them. 
No worries - just clarifying the situation for the readers of this thread. 
Currently I am using the 10 foot interface on a small touchscreen because it looks the best. Is there a way to make the control buttons slightly larger Jan?
Hi @Jelte_Dijkstra,
I’m the dev of this extension, @Jan_Koudijs has been a kind supporter of this project and helping me for the integration in the Roon-extension-manager and for some forum related permission, because, let’s face it, he’s a legend around here .
First of all, thanks for the feedback on this new layout!
Regarding the size of the control (I assume you’re talking about the play/pause, next, previous button? or maybe it’s all buttons?), as stated, this layout is not responsive (a fancy word to describe the fact that its elements are not dynamically sized based on the size of the screen they are displayed).
As it has been developed for the big TV screen first, it should not change quickly.
But if there is a lot of interest to reuse the UX it brings for other screen sizes, I could implement changes in the coming weeks.
Let all me know if there is interest to reuse this kind of UX in a broader context.
Happy roon
Oops, my bad! Sorry nihil for not recognizing you as the dev of this beloved extension.
Yes I do like the 10 foot display mode for use on my 1920x1200 7" (!) touchscreen. The OS (DietPi) does not scale well on that particular machine (Pipo X9S mini-PC) and the 10 foot mode remedies that.
And yes I was referring to the play/pause , next , previous buttons. And the ‘track progress indicator’ (?) at the bottom.
If these were 1,5x or double the size I believe it would be perfect.
No offense @Jelte_Dijkstra
I’m focusing on another topic right now, but will definitely take your feedback to create more flexible layout option based on the new 10 feet layout after the subject I’m on right now.
Great! I’ll wait patiently. Unfortunately I don’t have the skills required to make a contribution.
Keep up the good work!
1 Like
That’s ok. Do you want to stick to the dummy track approach, or have queue stops otherwise integrated in the UI?
I will do both, to let the choice to the user.
It will be an occasion to implement settings.
Dummy track with basic settings is already merged in main branch.
Still need to find time to implement the UI/backend version.
Dummy track approach will have all the pros of being fully manageable through any official roon remotes but not in the app (as there’s no API to manage queue and I don’t think that the roon team wants to invest that much to maintain/expand the API).
UI/backend will be more flexible from the app, but won’t be manageable through other remotes or community apps…
It will be a virtual/custom queue item that will be injected by the backend and handled by the frontend. This will make the stop at the end of current album feature I’d like to have possible, on top of opening the possibility to move the item from the app. But, as stated, the tradeoff is it won’t be nor visible nor modifiable via any other clients (official or community driven).
At the end, it all depends on how people will want to use it, hence the possibility to drive that through settings in the extension.