IRC Log Viewer » #firebreath » 2015-10-08

IRC Nick Time (GMT-7) Message
Enkindler 14:10 It seems i've managed to somewhat wake the extension at the very least. Using the snippets you gave me in the group conversations. The code launches and everything, and going into Debug I see that the extension scripts are loading, however, when ever i enter the <object> label, chrome still says the plugin is not supported.... any ideas here?. i changed the company name in the window.postMessage to FBDevTeam, for testing purpos
It seems i've managed to somewhat wake the extension at the very least. Using the snippets you gave me in the group conversations. The code launches and everything, and going into Debug I see that the extension scripts are loading, however, when ever i enter the <object> label, chrome still says the plugin is not supported.... any ideas here?. i changed the company name in the window.postMessage to FBDevTeam, for testing purpos
taxilian 15:10 Enkindler the extension doesn't use the object
the company name should be your company name
whatever you put in your PluginConfig
how well do you know javascript?
(and Enkindler, if you want to get my attention make sure you mention my nick "taxilian" so my IRC client pings me... otherwise I don't see it until I happen to glance at the correct window, and that sometimes gets a bit buried =])
with chrome, it's not actually a plugin. no <object> tag. pure javascript. it basically sets up a message relay through the extension and a wrapper; when it calls functions on the "plugin" object (which is just a fancy ECMAScript 5 object) it serializes the calls into json and sends it through the message bus to the plugin on the backend and the promise it returns resolves with the result
Enkindler 15:10 Alright!... Didn't know that...
PluginConfig?
I know mostly basic javascript...
very well, I'll use your nick next time...
Meaning, in chrome, i should only have the initializing code, and not the <plugin> tag itself, yes? taxilian
did that work?
taxilian 15:10 yes
yes
but I wasn't at my desk =]
but I wasn't at my desk =]
PluginConfig.cmake -- the configuration file for your plugin build which has all your metadata in it
PluginConfig.cmake -- the configuration file for your plugin build which has all your metadata in it
Enkindler 15:10 Alright then...
Saw it just now...
Saw it just now...
Does this kinda mean that to make the plugin work with both chrome and firefox, i'd have to make to different sites?, or basically check which explorer the user is using and then load plugin or go with the exntesion?
taxilian 15:10 the goal (which may not be 100% complete, but should be very close) is that they are API compatible once you instantiate it
so you'll just have to detect enough to know how to load the plugin
once loaded, you should be able to use them the same way
Enkindler 15:10 Alright... they'll just work diferently behind the scenes then?
taxilian 15:10 right
right
that's really what FireBreath is.. it's an abstraction to let you write a plugin using one method and have it work on different browsers with different interfaces
that's really what FireBreath is.. it's an abstraction to let you write a plugin using one method and have it work on different browsers with different interfaces
the FireWyrm protocol allows that to be over any text-based protocol as well
it's the main reason that FB2 is all asynchronous
it's the main reason that FB2 is all asynchronous
Enkindler 15:10 Alright Then!... Guess I'll just keep working on it and see if i can improve anything for it!
taxilian 15:10 =] as you are seeing, the #1 biggest thing you could do to help is provide some sample pages and a little documenation to help others starting out