IRC Log Viewer » #firebreath » 2015-04-20

IRC Nick Time (GMT-7) Message
walter_ 10:04 hi guys
anybody online?
taxilian 10:04 whats up?
walter_ 10:04 hi ;)
Do you know guys, what is the status of FireWyrm?
Regarding: http://www.firebreath.org/display/documentation/FireBreath+2.0%3A+Browser+Plugins+in+a+post-NPAPI+world
taxilian 10:04 I do know the status of FireWyrm, since I'm the one working on it
walter_ 10:04 Google just release Chrome 42 - which by default turned off NPAPI support
taxilian 10:04 yes they did
walter_ 10:04 where can I read about FireWyrm?
taxilian 10:04 what do you want to know?
I have been spending all my time working on it, so I haven't had time to document it all yet
walter_ 10:04 Well - I have a plugin using Firebreath - basically used just for some binary stuff, like reading/writting to file... and more.... No GUIs
taxilian 10:04 okay
walter_ 10:04 Well - it seems now - I have to implement this code using NACL / Native Messaging ..... I was waiting for Firebreath to support it.... As I understand FireWyrm is the answer for me, right?
Well - it seems now - I have to implement this code using NACL / Native Messaging ..... I was waiting for Firebreath to support it.... As I understand FireWyrm is the answer for me, right?
taxilian 10:04 well, that depends
basically if you can do it using nacl or emscripten I'd recommend doing that, simply because you don't have to deal with an installer
basically if you can do it using nacl or emscripten I'd recommend doing that, simply because you don't have to deal with an installer
but yes, you could probably use a FireBreath2 plugin and access it via FireWyrm over native messaging
walter_ 10:04 I have Firebreath plugin - that I use with IE, Chrome, Firefox and Safari.... Also ported for MAC - so I'm quite heavily dependant on Firebreath
taxilian 10:04 and that functionality is pretty much done
walter_ 10:04 My Firebreath plugin also uses some 3'rd party libraries.... Like for webcam...
I was rather thinking to come up with a solution to load my firebreath DLL as it is - but to make it working with Chrome over Native Messaging...
but it seems FireWyrm will do that for me
kylehuff 10:04 NACL = Native Client (which is different from Native Messaging), and it is a heavily sandboxed API. there is no filesystem access w/ NACL.
taxilian 10:04 it still may well be possible to do it using emscripten tied to javascript, but there is no reason you couldn't use FireBreath2 for that
walter_ 10:04 sorry, I'm just reviewing the topic since today
taxilian 10:04 kylehuff: there is a way to do it, similar to how you can with html FileSystem API
not sure if you can do it directly from NaCL but I think you can, it just requires more interaction from the user
not sure if you can do it directly from NaCL but I think you can, it just requires more interaction from the user
walter_ 10:04 When do you expect FireWyrm to be published?
it's going to be separate project tided with Firebreath - or is going to be part of Firebreath btw. ?
taxilian 10:04 depending on how you define "published" it already is
it's an open source project; I've been working on it in the firebreath repo. it's in the refactor branch
it's an open source project; I've been working on it in the firebreath repo. it's in the refactor branch
walter_ 10:04 oh...
oh...
taxilian 10:04 at this precise moment I don't know when I'll document it because frankly I'm a little frustrated with people asking me about it expecting me to give it to them all on a silver platter but apparently unwilling to help
and thus unless others (possibly kylehuff who is the only one who has actually been helping) take on the documentation I don't know when people will actually start using it
kylehuff 10:04 well, yes, but that is hardly filesystem access. my understanding that it is an abstracted and sandboxed filesystem, basically writing to localStorage.
taxilian 10:04 kylehuff: I'm pretty sure you can actually access real files, but I don't know what the requirements are. You certainly can using the HTML5 FileSystem libraries such as Filereader, but I haven't used anything beyond that
kylehuff: I'm pretty sure you can actually access real files, but I don't know what the requirements are. You certainly can using the HTML5 FileSystem libraries such as Filereader, but I haven't used anything beyond that
walter_ 10:04 sorry to hear that
taxilian 10:04 walter_: if you want to use it, I recommend you check out the refactor branch and start playing with it. Chip in where you can and I'll be happy to help you in any way I can
walter_ 10:04 I see refactor branch
taxilian 10:04 on windows you'll need vs2013 and the only real limitation at the moment (other than no drawing support) is that the ActiveX updates haven't been completed
kylehuff 10:04 that may be, it has been about 8 months or so since I've looked at the NaCL API.
walter_ 10:04 hehe, ok I guess I'll try it out ;) I wonder if I will be able to figure it out without docs ;) I hope there are some comments in the code ;)
kylehuff 10:04 that may be, it has been about 8 months or so since I've looked at the NaCL API.
walter_ 10:04 hehe, ok I guess I'll try it out ;) I wonder if I will be able to figure it out without docs ;) I hope there are some comments in the code ;)
I'm using VS2013
taxilian 10:04 you'll need to fbgen a new project; you can convert your other one over but there are a lot of little breaking changes
walter_ 10:04 I'll definitelly try out new empty project first
I'll definitelly try out new empty project first
Everything related to FireWyrm is inside src/FireWyrm ?
just asking - in case I'll read the code for some understanding...
taxilian 10:04 most things are actually pretty much the same; the main difference is that all APIs return a promise
FireWyrm itself is just a transport, like NPAPI
to use it with Native Messaging you'll need to build the FireWyrmNativeMessageHost project and then build the _install project which will put the files in place needed to use the extension
would you be willing to write up some instructions on getting this going for the next person?
would you be willing to write up some instructions on getting this going for the next person?
walter_ 10:04 ok - thats a lot guys, I'll review it...
kylehuff 10:04 taxilian: RE: documentation - I should have more time later this week and most of next week. I can get started on the documentation. I don't yet know what the breaking changes are, I will probably start with the chrome extension related documentation, and then port a FBv1 plugin to FB2, and go through the experience.
walter_ 10:04 sure, If I get success - I'll document my findings...
taxilian 10:04 kylehuff that would be awesome. Right now I'm so burned out on this I can barely keep myself working on it... any assistance helps a lot
walter_: let me know when you get it built; you can try building the echotestplugin or fbtestplugin to try it out
walter_ 11:04 found small issue - I used "prep2013.cmd fbprojects fbbuild" - and it's looking for firebreath files inside fbprojects folder....
C:\inetpub\wwwroot\npapi-2.0\fbbuild>cmake -G "Visual Studio 12" -DFB_ROOT="C:\inetpub\wwwroot\npapi-2.0\firebreath" "C:\inetpub\wwwroot\npapi-2.0\fbprojects" CMake Error: The source directory "C:/inetpub/wwwroot/npapi-2.0/fbprojects" does not appear to contain CMakeLists.txt. Specify --help for usage, or press the help button on the CMake GUI.
taxilian 11:04 so that's not an issue, it's a change. prepscript takes the path to the project, not the path to a projects folder
walter_ 11:04 oh
taxilian 11:04 =]
forgot to mention that one, sorry
forgot to mention that one, sorry
walter_ 11:04 looks like it will work (I need to update CMake), but FYI only if I have "fbprojects" and "fbbuild" inside firebreath directory
taxilian 11:04 ?
you can put those anywhere you want
I do it all the time
my standard dir structure is to have ./firebreath ./my_project ./build
walter_ 11:04 In my project I had it diffently - I had fbprojects and fbbuild in upper folder - so it doesn't change "firebreath" files at all... Which is directly pulled from git
taxilian 11:04 and I run prep2013.cmd my_project build
that's how I do it
walter_ 11:04 let me check sth
taxilian 11:04 also, you don't really need to know this, but the root CMakeLists.txt is now your project's, not FireBreath's
that will change some things
that will change some things
walter_ 11:04 FYI: CMake Error: The source directory "C:/inetpub/wwwroot/npapi-2.0" doesnot appear to contain CMakeLists.txt. Specify --help for usage, or press the help button on the CMake GUI.
taxilian 11:04 what is your prep script command line?
what are you running?
walter_ 11:04 I have npapi-2.0 folder - and inside: firebreath, fbbuild, fbprojects
firebreath/prep2013.cmd fbprojects/EchoTestPlugin fbbuild
taxilian 11:04 try using \ instead of /
unless you're using cygwin or something?
walter_ 11:04 hehe, worked ;)
ok, let me update my CMake now... thx btw.
great, I have the demo project prepared
taxilian 11:04 let me know when it finishes building
walter_ 11:04 ok
13> FireWyrmNativeMessageHost.vcxproj -> C:\inetpub\wwwroot\logmeonce\npapi-2.0\fbbuild\firebreath\NativeMessageHost\Release\FireWyrmNativeMessageHost.exe --- looks promising ;)
just a suggestion - shoudln't EXE name be the same as project name?
like the NPAPI DLL name is the same as project name
========== Build: 15 succeeded, 0 failed, 0 up-to-date, 2 skipped ==========
taxilian 11:04 excellent. There should be a target that is something like plugin_install
run that
walter_ 11:04 sorry?
taxilian 11:04 it'll show up as a project
if you're building EchoTestPlugin it would be EchoTestPlugin_devinstall
walter_ 11:04 ohh - you mean project in solution
well - this one doesn't work
error MSB6006: "cmd.exe" exited with code 4
taxilian 11:04 interesting. no extra details?
interesting. no extra details?
hmm. are you using visual studio express?
walter_ 11:04 Visual Studio Community edition
taxilian 11:04 so yeah; the free one
so yeah; the free one
the issue is that it's not able to regsvr32 the dll because of some missing dependencies
I don't know why the dependencies are there; it's one of the things we need to figure out
walter_ 11:04 community one is suppose to be the same as prof I guess
community one is suppose to be the same as prof I guess
taxilian 11:04 however, I believe kylehuff was able to fix that by installing the vs2013 runtime (weird, I know)
community is the free one, no?
walter_ 11:04 It was Release build btw
let me try Debug
let me try Debug
yes community is free
taxilian 11:04 ... hmm. that's concerning, actually. I was hoping Release wouldn't have the issue
walter_ 11:04 yes community is free
taxilian 11:04 community is not the same. I don't know the exact differences, but pro doesn't have this issue
community is not the same. I don't know the exact differences, but pro doesn't have this issue
you'll probably have to install the vs2013 runtime unless you want to try to figure out (using depends.exe) which dependencies are missing and why they are being linked in the first place
you'll probably have to install the vs2013 runtime unless you want to try to figure out (using depends.exe) which dependencies are missing and why they are being linked in the first place
which would be really awesome if you could, btw :-P
walter_ 11:04 Debug is the same...
kylehuff 11:04 taxilian: I was never able to nail down what makes it work. I have successfully built with the latest community edition, but after setting up a new windows VM, it doesn't work. complains about entry points when passed to regsrv32
walter_ 11:04 Well - I'm leaving for today - I'm from Poland btw....
Well - I'm leaving for today - I'm from Poland btw....
I'll try to figure it out tomowrow morning - If I suceed - I'll keep you posted
I'll try to figure it out tomowrow morning - If I suceed - I'll keep you posted
and you are saying it works with PRO version, right?