Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We鈥檒l occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kiosk/remote control/fullscreen/cast mode #71

Open
Madis0 opened this issue May 24, 2020 · 9 comments
Open

Kiosk/remote control/fullscreen/cast mode #71

Madis0 opened this issue May 24, 2020 · 9 comments

Comments

@Madis0
Copy link

Madis0 commented May 24, 2020

I got a simple idea that can be used in devices with an outdated browser, but not necessarily the best controls (smart TVs, kiosks, public tablets in buses maybe 馃槃).

How about one page with all controls and one page with just the rendered image? The contents would be identical, including screen size setting. Related: #58

@tenox7
Copy link
Owner

tenox7 commented May 24, 2020

Thats sounds exciting but could you provide some more details?

This is a good timing because I'm working on a templatized version of html controls.

@Madis0
Copy link
Author

Madis0 commented May 25, 2020

Here's a quick mockup comparing my idea - first image is yours and therefore the "remote control" client, the second is a mockup that just has the web contents and a different port.
The "kiosk UI" is literally just the same contents displayed without other UI elements.
remote control
kiosk

@Madis0 Madis0 changed the title Kiosk mode/remote control/full screen mode Kiosk/remote control/fullscreen/cast mode May 25, 2020
@tenox7
Copy link
Owner

tenox7 commented May 26, 2020

Do the controls and image have to be on a different port or just a different url?

@Madis0
Copy link
Author

Madis0 commented May 26, 2020

Could be different URL too, whichever is easier.

@tenox7
Copy link
Owner

tenox7 commented Oct 27, 2020

I have checked in an update to wrp that allows to use html template file, this way you can customize the ui any way you want using the wrp.html file

please let me know if this helps you with this issue?

note that you will need to build wrp from master head to get the latest update

@Madis0
Copy link
Author

Madis0 commented Oct 27, 2020

Well, customizing the UI is a different subject, here I just want a direct link to the content without the UI (but the UI should be available in a separate URL).

@tenox7
Copy link
Owner

tenox7 commented Oct 27, 2020

I was reading your earlier comments and looked like you wanted to disable the UI components

The "kiosk UI" is literally just the same contents displayed without other UI elements.

You should be able to do it by customizing wrp.html to remove these components or make them in to hidden form elements rather.

Reading your last comment are you saying that you would like to say listen on a different port or perhaps different url and as such display a different html page for it?

If yes does it have to be a separate port or could it be a different uri, for example:

http://1.2.3.4:8080/ - normal
http://1.2.3.4:8080/kiosk/ - stripped ui?

@Madis0
Copy link
Author

Madis0 commented Oct 27, 2020

Yes, /kiosk would be fine.

The point with my sentence was that I want to remove the elements for kiosk, yes, but still be able navigate the UI in the "control page", that then would change the contents of kiosk page too.

@tenox7
Copy link
Owner

tenox7 commented Oct 27, 2020

ok, this is much better explanation, let me see what can be done

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants