2005/9/17, Matt Broadstone <<a href="mailto:mbroadst@gmail.com">mbroadst@gmail.com</a>>:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Unfortunately the bindings that are created your (and richard's) way<br>are not what we need for Plasma. We're currently researching into<br>things like Kross, which provide swappable interpreters on runtime..<br>perhaps you'd be interested in working with that, join us in #plasma.
</blockquote><div><br>
I have just read the Kross page:<br>
</div></div><a href="http://www.kexi-project.org/wiki/wikiview/index.php?Scripting">http://www.kexi-project.org/wiki/wikiview/index.php?Scripting</a><br>
<br>
and found out that it is exaclty the project that the guy of Kexi
started. Hi had problems dealing with more than one script languagens
in the same language.<br>
<br>
But it does not change the thing, if you are runnig the Python (or
whatever) interpreter, you can still link it to the C++ app with the
script, just have to implement the interface (that he calls Kross). So
we are talking about the same thing. Just need to implement a simple
backend.<br>
<br>
Indeed, reading the page, I discovered that the Kexi guy had some deals
with licensing. He wanted to publish Kross under LGPL and Qt is GPL, so
you cannot. That's why Kross is so loose(not binded to the Qt lib). But
KDE is GPL, so is Qt and python-qt4 (my bindings). So why do twice the
job if we can have one complete solution?<br>
<br>
Another thing he pointed is that bindings were done with SIP or SWIG,
that have many limitations. But python-qt4 uses Boost.Python (from the
Boost libraries) and is very powefull, and you can do bindings in the
same language (C++) you are exposing from.<br>
<br>
So... now we have a point?<br>
<br>
[Eric Jardim]<br>