Help with app/overlay

[delos23]

I am trying to get youtube to just work in full screen with a way to go back to the main screen from the touch screen, I got the example for the idle screen to work, but i can not figure out for the life of me where to go from there. Any helps appreciated. Thank you

[hudiy]

It will be easiest to do this using separate overlays and an application. One overlay will be used to display YouTube in full screen and the second one for the "Go Home" icon. Both overlays will be configured to appear only on a specific application (e.g., a dummy YouTube app).

You can create the Go Home button (in HTML/JS using the Hudiy API) based on an example such as go_back.html or simply use the go_back.html directly. The HTML/JS utilizing the API should be served via an HTTP server due to the Same Origin Policy - https://developer.mozilla.org/en-US/doc ... gin_policy.

https://github.com/wiboma/hudiy/tree/ma ... javascript
https://github.com/wiboma/hudiy/blob/ma ... _back.html

Here is an example configuration:

applications.json

Code: Select all

        {
            "action": "youtube_app",
            "controlAudioFocus": false,
            "audioStreamCategory": "NONE",
            "allowBackground": false
        }

applications_menu.json

Code: Select all

        {
            "categories": [
                "Music"
            ],
            "iconFontFamily": "Material Symbols Rounded",
            "iconName": "music_video",
            "action": "youtube_app",
            "label": "YouTube"
        }

overlays.json

Code: Select all

        {
            "identifier" : "youtube_overlay",
            "action" : "youtube_app",
            "width" : "100vw",
            "height" : "100vh",
            "x" : 0,
            "y" : 0,
            "visibility" : "ALWAYS",
            "url" : "https://youtube.com",
            "controlAudioFocus" : true,
            "audioStreamCategory" : "ENTERTAINMENT",
            "visibleOnActions" : [
                "youtube_app"
            ],
            "staticPosition" : true
        },
        {
            "identifier" : "go_home_button",
            "action" : "",
            "width" : "7vw",
            "height" : "7vw",
            "x" : 0,
            "y" : 0,
            "visibility" : "ALWAYS",
            "url" : "http://127.0.0.1:12345/go_home.html",
            "controlAudioFocus" : false,
            "audioStreamCategory" : "NONE",
            "visibleOnActions" : [
                "youtube_app"
            ],
            "staticPosition" : false
        }

yt_1.png

yt_2.png

[delos23]

Perfect! Thank you!

[wkl3968]

I wonder where should the go_home.html located?

[wkl3968]

not sure why I couldn't load the home button. however, when tried view using the browser, I get to see the home icon via when loaded 127.0.0.1:12345/go_home.html. also the navigation keys like (1,2, arrow keys) are not functioning when it is on youtube. am I right?

[hudiy]

External websites will not support scroll (1, 2) and d-pad (left, right, up, down) controls. Regarding the home button, the URL was likely unreachable from Hudiy - the HTTP server is either down or was started after Hudiy tried to load the URL.

[wkl3968]

Thanks. After I launched the Hudiy, launch the http server manually, then the YouTube overlays, yet it still show this ! Mark. Should put the http launch earlier during Hudiy bootup?
For the YouTube app, what can I do to enable the navigation? Writing my a custom UI to host the YouTube?

[Kaiis]

Yes, that's a crucial point! Hudiy absolutely needs to be able to access the `go_home.html` file as soon as it launches; otherwise, the overlay won't appear. In my case, I added a systemd task to start the HTTP server before Hudiy at startup. Here’s a quick snippet of my config:

Code: Select all

[Service]
ExecStartPre=/usr/bin/python3 -m http.server 12345 --directory /home/pi/hudiy_overlays/
ExecStart=/usr/bin/hudiy

This way, the server is running before Hudiy attempts to load the overlay. I recommend testing this by fully rebooting your Raspberry Pi to ensure the startup sequence works correctly.