I was thinking the Chromecast extension used NaCL for some reason. Also thinking it had some sort of special integration with Chrome's Pepper Flash because its able to cast the Flash directly to the Chromecast (still thinking this must be the case). Click one of the buttons below to download the Google Home app on your mobile phone or tablet. Tap the button below to download the Google Home app. If you have the Chromecast extension installed on your PC, it’s as simple as clicking here to select your free reward. Red delete icon outlook for mac. If you don’t have the Chromecast extension installed, you will need to download it from the Chrome Store here. ![]() How does it get to the local network? I assumed it used either special internal abilities in the browser or implemented a platform shim. Is WebRTC enough? If this ported version of the extension does work, then I'd ask the question if the license allows for it to just be taken and posted on Mozilla's store. If not, yours still has use. Also, if it does work, but can't be made freely and openly available, then perhaps you can learn from it's code how it accomplishes stuff (.or maybe you could already before). Discovery and communication with the Chromecast is done by sending multicast DNS messages. You can't do this in Firefox through the browser due to not having permissions to freely create UDP sockets to implement the protocol. This can be done on FirefoxOS, but not browser Firefox. The Google Cast extension may very well might be using either internal APIs from Chrome or NaCL. I didn't see anything in the WebExtensions spec that would let me broadcast and receive multicast DNS messages. I solved this by using WebSockets on the Firefox JavaScript extension side to communicate with the Firefox plugin UI (to display the available cast devices) and a NodeJS webserver (which does the actual casting). The NodeJS server does all the heavy lifting. However, packaging a NodeJS app as a single binary is nontrivial when mdns is involved. So, I wanted to reimplement the my webserver using a different language so it'd be easier to package it up as a single statically linked binary along with the JavaScript extension. I think that you should definitely complete the Chromecast extension. Try not to base it on XUL though. As long as you don't I think you'll be good for the future with native.js addons. I'm hoping js-ctypes is allowed in native.js as well because js-ctypes is extremely addon dev friendly - (1) same environment as you use for developing javascript (2) no need for purchasing expensive equipment like Mac to run xcode etc (3) copy paste and run. I assume you may have needed js-ctypes for this huh? I heavily use js-ctypes across all my addons. It has enabled me to bring about features not thought of.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |