You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
UDP is already working. Compression with JavaScript works too but is not fast enough to send more than 5 Fps with 484 pixels. I don't think is worth adding it unless we find a faster way to implement it (web assembly?)
If that is efficient enough we can use this as a proof of concept and make a branch in the tester to see how that works out.
Note that there a few quirks that need tonne take in account when making an app. For example you cannot use eval() or Function unless you put that part in a sandbox. Doing that will let that work but has the undesired effect that loading a video will fail unless it is send with the right allow origin CSP so I would have to serve it with apache or a php wrapper. But that's still ok as long as is transparent for the user.
The mission of this whole thing is that the user gets a no brained one click install thing without needing to install or setup anything.
I will be only 5 days more working on this and submit it next Friday to Chrome web store.
The text was updated successfully, but these errors were encountered:
Chrome App is a wild try to make UDP and compression work without the need of usIng a nodejs backend.
Branch: feature/tv-chrome app
cC @hputzek @iotpanik
UDP is already working. Compression with JavaScript works too but is not fast enough to send more than 5 Fps with 484 pixels. I don't think is worth adding it unless we find a faster way to implement it (web assembly?)
If that is efficient enough we can use this as a proof of concept and make a branch in the tester to see how that works out.
Note that there a few quirks that need tonne take in account when making an app. For example you cannot use eval() or Function unless you put that part in a sandbox. Doing that will let that work but has the undesired effect that loading a video will fail unless it is send with the right allow origin CSP so I would have to serve it with apache or a php wrapper. But that's still ok as long as is transparent for the user.
The mission of this whole thing is that the user gets a no brained one click install thing without needing to install or setup anything.
I will be only 5 days more working on this and submit it next Friday to Chrome web store.
The text was updated successfully, but these errors were encountered: