What edits to the MJPEG Stream Viewer would be required to make it able to be added to the Scheduled Player? I am technically able to consider some amount of development/configuration, if it is possible.
Sorry for the delay. The package cannot be directly added as the MJPEG player only knows how to run exclusively as a top-level package. It doesn’t implement the necessary API to be embeddable into the scheduled player. In theory that would probably not be too difficult: The package service (in the file service) can remain unchanged, but it would need a new tile.lua file and tile.js. I could take a look at that next week.
That makes sense! Thanks for taking a look. I’m interested to know what it needs, so I’ll keep track of the diffs on GitHub - info-beamer/package-mjpeg-viewer: A mjpeg viewer for info-beamer hosted. If you don’t find time for it, I can have a go, for which I’d appreciate: an example of another simple package that already implements tile.lua and tile.js; any “gotchas” that the mjpeg viewer might come with when these files are created; a general link to contributing guidelines/etc. :] … otherwise, I wish you luck with it ^.^ … thanks !
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…