W3C home > Mailing lists > Public > public-browserext@w3.org > January 2017

Re: Revised Web2Native Bridge interface

From: Florian Rivoal <florian@rivoal.net>
Date: Tue, 10 Jan 2017 11:14:10 +0900
Cc: "public-browserext@w3.org" <public-browserext@w3.org>
Message-Id: <E16D1B73-218A-4A56-BC97-92C400CDF7BC@rivoal.net>
To: Anders Rundgren <anders.rundgren.net@gmail.com>
> On Jan 7, 2017, at 06:08, Anders Rundgren <anders.rundgren.net@gmail.com> wrote:
> 
> W2NB (Web2Native Bridge) now runs on Chrome/Chromium and Firefox desktop browsers.
> https://chrome.google.com/webstore/detail/web2native-bridge-emulato/jphfmfbdedghfhhjijaogeloiehomfni
> https://addons.mozilla.org/en-US/firefox/addon/web2native-bridge-emulator/
> 
> The two demo Web applications as well as their native Java counterparts runs completely unmodified on the browsers above, on Windows, MacOS, and Linux.
> 
> Since W2NB is (deliberately) detached from the in-browser extension system, each native extension is now required having a manifest file which controls what domains which may invoke them: https://github.com/cyberphone/web2native-bridge#manifest
> 
> Getting W2NB to run on Android is though an entirely different story but I will at least try :-)

Hi,

Thanks for keeping us updated. I'll try to take some time to dive in W2NB, and encourage others to do so as well. Once a few more people get a good grasp of how it works, and of what it can do, we could take some time during an upcoming teleconf and discuss if and how this could affect what we do.

—Florian
Received on Tuesday, 10 January 2017 02:14:41 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 10 January 2017 02:14:42 UTC