--
---
You received this message because you are subscribed to the Google Groups "firebreath-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to firebreath-de...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
1) FireBreath 2.0 supports NPAPI, ActiveX, and FireWyrm. FireWyrm is a protocol that was created in conjunction with FireBreath 2.0 which works over any asynchronous string/JSON messaging protocol -- such as Native Messaging.
You'll need to fbgen a new project to start with or build EchoTestPlugin or FBTestPlugin since a FireBreath 1.x plugin will need to be changed to build with FireBreath 2.0, they are not source compatible.
The chrome extension source is found in the build directory after you build; you'll likely need to customize some of those files, which can be done by copying them to the folder "crx_template" under your project directory. You are correct that it requires the extension to function.
You will need Visual Studio 2013 or later and CMake 2.8 or later.
The installer has been updated to attempt to install the extension automatically, but Chrome must be restarted for that to work. Also, the extension has to be on the Chrome app store for any of this to work.
To prep with FireBreath2 you must provide the full path to the project you want to build, e.g:
prep2013 examples\EchoTestPlugin buildex
That will create buildex\EchoTestPlugin.sln
1) I mean the generated WiX installer from the fbgen project.