I’ve had another look, and it’s difficult to see what I need to do without documentation or a dedicated development Pi on-hand.
From what I can figure:
tile.js seems to want to:
- contain a template for the settings when you click on a scheduled player item
tile.lua seems to want to:
- contain logic for rendering onto the screen
- return
MwithM.task(starts, ends, config, x1, y1, x2, y2)implemented (whatever the arguments mean)- maybe
M.data_trigger(path, data)and other functions are supported(?)
some examples of tile.lua and tile.js are here:
- https://github.com/info-beamer/package-scheduled-player/tree/master/weather
- https://github.com/info-beamer/package-scheduled-player/tree/master/frab
- https://github.com/info-beamer/package-scheduled-player/tree/master/scroller (broken… no
tile.js?) - https://github.com/info-beamer/package-scheduled-player/tree/master/twitter
can you only develop on a pi? can you develop on a raspbian virtual machine? the answer to these questions is not obvious to me.
Some links I have been reading to figure things out:
- dev info: https://info-beamer.com/doc/building-packages
- some info on
tile.lua: https://community.info-beamer.com/t/documentation-on-creating-scheduled-player-plugins/1035/4 and https://community.info-beamer.com/t/infoscreen-for-sports-club/959/4
It was also not obvious whether tile.lua could re-use lua code/logic from node.lua, or if they are completely separate items (are the functions in node.lua available? I feel maybe not? I have no idea).
Finally, to be “importable”, presumably there is some sort of specification (in json?) of “this package can be used in scheduled player”.
As I said, I’m happy to do work to add scheduled player support, but it seems difficult to develop packages unless you have a dedicated Pi device for development, and you understand a lot of undocumented stuff. I would appreciate guidance, but without it: I’ll probably set up a Pi in the near future for development and just throw stuff at it until it sticks…