Re: [Swig-devel] javascript module

[Oliver B. <oli...@jk...>]

Am 07.03.2011 10:56, schrieb Matthias:
> Am 07.03.2011, 08:54 Uhr, schrieb Oliver Buchtala<oli...@jk...>:
>
>> Am 07.03.2011 08:29, schrieb William S Fulton:
>>> On 04/03/11 18:54, Matthias wrote:
>>>> Hello,
>>>>
>>>> is there any swig module which targets javascript? The target js engine
>>>> doesn't matter for now.
>>>>
>>> No, although Oliver Buchtala mentioned developing such a module in Dec
>>> 2010 on this list. There was something called SwigJS once upon a time
>>> but I don't know what happened to it.
> Thanks William. I think SwigJS was based on swig-1.1 and I couldn't find
> any traces to the code.
>
>> Hi Matthias,
>> Hi William,
>>
>> I started developing a module for the v8 engine and managed to get a
>> simple prototype working. My main aim for this module is in hybrid
>> development (html5 + c++). So after having a first proto, I headed
>> towards an integration with webkit-qt - and got stuck. v8 support is in
>> webkit-qt only prototypically and by far not stable yet.
>> Without webkit-qt (or another v8-rich browser thingie), there is still
>> node.js - a server side solution with a v8 inside which could be
>> extended by generated modules.
>>
>> In the next weeks, I will return to work on the v8 module.
>> If somebody like's to join, it would be me a pleasure :)
> If I decide to work on this my target would likely be firebreath
> (http://www.firebreath.org). It's a library to write your own
> cross-platform cross-browser plugins (using ActiveX and NPAPI). As part of
> this it exposes a javascript api:
>
> http://www.firebreath.org/display/documentation/JSAPI+Methods
>
> As you can see there's already built-in support for STL containers etc.
>
> The downside of this approach is that you need to run a plugin inside a
> browser to make use of this, you cannot run the javascript engine
> standalone.
>
> -Matthias
>
> ------------------------------------------------------------------------------
> What You Don't Know About Data Connectivity CAN Hurt You
> This paper provides an overview of data connectivity, details
> its effect on application quality, and explores various alternative
> solutions. http://p.sf.net/sfu/progress-d2d
> _______________________________________________
> Swig-devel mailing list
> Swi...@li...
> https://lists.sourceforge.net/lists/listinfo/swig-devel

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)

Bye,
Oliver