IRC Log Viewer » #firebreath » 2013-10-01

IRC Nick Time (GMT-7) Message
lok 06:10 hi, how I know what is servername.typename of ActiveX object for IE. I tried application/x-test and it doesn't work.
lok 06:10 thanx a lot. I found it by myself
MIDIMan_ 08:10 Has anyone used firbreath to make a plugin for forwarding MIDI-over-USB data to JS for web app usage?
taxilian 08:10 MIDIMan_ not that I know of
MIDIMan_ 08:10 Would Firebreath be overkill for something like that?
taxilian 08:10 no, that actually seems pretty reasonable to me; however, not that Chrome is planning to remove NPAPI support in the next year
for something like that you could probably do native messaging in Chrome, but that'd mean implementing it twice; NPAPI for everything else (FireBreath uses NPAPI in all browsers but IE)
kylehuff 09:10 if I have an API, say, SimpleMathAPI in a subdirectory of my project root, i.e. myPlugin/SimpleMathAPI/SimpleMathAPI.{ccp,h}, is the myPlugin/CMakeLists.txt the proper place to reference that sub directory?
taxilian 09:10 generally yes
unless the subdirectory is in and of itself a separate project
kylehuff 09:10 it is not a separate project, but I intend to make it one eventually. I am separating out the main logic of my plugin into a separate, standalone library (libwebpg), and just reference it within the plugin. that way I'm not maintaining separate code for the generic library, the plugin and whatever feeds native messaging (or whatever I end up using for chrome), they can all include libwebpg
taxilian 10:10 makes sense
that's kinda what I'm considering building as a framework is something that will make that easier
nirvdrum 13:10 taxilian: I suppose you saw that Chrome is dropping NPAPI in a few months?
taxilian 13:10 sure did
nirvdrum 13:10 Fun stuff.
Oh. I should have seen the topic.
My bad.
taxilian 13:10 lol
nirvdrum 13:10 I argued with some Google and Mozilla folks about this on Twitter :-P
taxilian 13:10 hehe
nirvdrum 13:10 It was suggested I use the largely undocument PPAPI.
And Mozilla indicated they're unlikely to support it because it's not document and Google just keeps changing it as they need to.
taxilian 13:10 wait, ppapi does actually work for normal plugins?
nirvdrum 13:10 It's how Flash is implemented in Chrome, I believe.
taxilian 13:10 yeah, but I figured it was a closed API
if we can use PPAPI we may be able to target it with FireBreath
nirvdrum 13:10
taxilian 13:10 if they plan to keep it for any period of time
nirvdrum 13:10 I don't think it's going anywhere any time soon.
taxilian 13:10 I was under the impression that the only way to use PPAPI is to use NaCL
do you have any idea who I would email at google to find out?
nirvdrum 13:10 You could try tweeting to this guy:
Otherwise, I'll see if I can dig up a contact more in the know.
This came up in the context of Selenium.
taxilian 14:10 nirvdrum: if you can find out anything definite that would be really helpful
MIDIMan_ 14:10 So are there any alternatives to FB that will be cross-platform and wont get dropped any time soon?
taxilian 14:10 if there were, FireBreath would be targetting the same thing they do
kylehuff 14:10 the issue not so much with the framework to build the solutions; the issue is that the solutions do not exist. There is no other mechanism that supports the same features as NPAPI available in the multiple browsers.
taxilian 14:10 however, nirvdrum's lead that ppapi might be directly targetable could be worth following up on
kylehuff 14:10 yes, indeed. if that provides the same functionality as googles native-client (without the sandbox), I'm set.
but even with that, that is not a cross-browser solution. Mozilla is still dropping NPAPI, and they have no plans to implement PPAPI
taxilian 15:10 Mozilla is not, yet, dropping NPAPI
there is some possibility that they will, but they have not yet done so
kylehuff 15:10 I had read they will stop accepting extensions with NPAPI into the addons.mozilla as early as January
then of course, it's downhill from there...
taxilian 15:10 really? haven't seen that. link?
kylehuff 15:10 looking for it now.
searching through my history with a keyword of NPAPI or Mozilla is so utterly futile...
taxilian 15:10 lol
kylehuff 15:10 I misread that, with the release of Firefox 26 they will "block NPAPI plugins", meaning "click to play"
nirvdrum 15:10 kylehuff: To be clear, Mozilla isn't dropping NPAPI. It's just going to be click-to-activate.
At least that's the latest word.
Ahh, I see you already said that.
I need to read faster.
taxilian 15:10 hehe
kylehuff 15:10 yes, the article I read was misleading. "Mozilla will block NPAPI plugins" means something different than "click to play" to me.
taxilian 15:10 in fact, some of what I have read seems to indicate that you can disable click to play for a plugin in an extension
kylehuff 15:10 yes, that is my current hack of the century. I check the nsiPref value, toggle it, load my plugin, then restore the user defined pref.
I first tried adding it to the whitelist, but the whitelist doesn't support the "chrome://" protocol as a valid source value, so I had to result to boyish hackery...
taxilian 16:10 well that was fun
my primary server locked up
kylehuff 16:10 when I saw you bail out I thought it might be the rapture. other than a netsplit, your nick is to #firebreath what `ping` is to my connectivity tests -- always there.
taxilian 17:10 lol
I'll have to migrate ZNC ot the data center when I migrate the websites
MIDIMan_ 17:10 Anyone have any luck using the Chrome Hardware API to create an extension?
taxilian 17:10 never tried it :-/
good night all, I'm headed out