From: Matthias <ni...@dr...> - 2011-03-07 11:13:35
|
Am 07.03.2011, 11:50 Uhr, schrieb Oliver Buchtala <oli...@jk...>: > Hi Matthias, > > thank you for this information. > NPAPI plugins are a well supported technique. Moreover, you can create a > slim application based on qt-webkit. > > For me, this approach has one central drawback (if I understand NPAPI > alright): NPAPI plugins are bound to handle mime-types for the browser. > It is thus not a general means to provide an API to a JS engine. > (Correct me if I am wrong) You can embed npapi plugins with <object> tags in your html page. Based on the mimetype parameter the corresponding plugin will be loaded. So if you control the creation of the html page you can just put an <object> tag in there and you'll always have a plugin running. Of course if you want to extend the js engine with new functions (let's say some number crunching) which should be available to any html page this will not work. Unless you can just pre/postprocess the page before loading it into the browser and adding a silent <object> tag there. The good thing about the firebreath is your plugin will work in any browser with any js engine. I think there's currently no way to do this if you want to do it without a plugin. What's your specific usecase? I want to provide a wrapper to a C++ library which I want to access from JS. And I always have a plugin running anyways... -Matthias |