Ahoy,
I was daydreaming; visualizing (somewhat abstractly) the dynamics of Roku's SDK and the whole sandbox security topology.
Screen savers have accesss to tmp:// because thats how cover art is delivered from a parent audio app (eg. Pandora or audioapp.zip). So then couldn't I create a generic screen saver and then select said screen saver as system default from Roku's traditional Settings --> Screensaver. Now said screen saver could have access to the tmp:// filesystem of any app currently running on the system...? Right? Or would it have it's own tmp:// space created specifically for the duration of the system activity timeout?
Would said screen saver have access to its own pkg:// file system or the pkg:// of the parent app. Eg. Could I pause playback in Hulu or goto an episode screen of Netflix, wait for the system to timeout & load my screen saver which in reality could be a filebrowser or minime webserver?
It is not my intent to create problems or to break anything... My only motivation is to further understand technology & hopefully make it better. I'm a fixer, have been my whole life.
Sincerely,
Grant