[Panel-devel] Introducing me

Eric Jardim ericjardim at gmail.com
Sat Sep 17 07:34:52 CEST 2005


2005/9/17, Matt Broadstone <mbroadst at gmail.com>:
>
> This has already been done for you (PyQt/PyKDE). See Richard Dale's
> work at http://developer.kde.org/language-bindings/. The bindings are
> already automatically generated.


I think you misunderstood something. I am talking about Python bindings for
Qt4, not Qt3 (old PyQt). Richard Dale is working in QtRuby for Smoke for Qt4
(I think). I also in the kde-bindings mailing list.

BTW, there is not AFAIK any complete bindings for Qt4 for any scriptable
language.


Unfortunately the bindings that are created your (and richard's) way
> are not what we need for Plasma.


What do you mean by that? Could you be more specific? I have started a few
time ago, and we can adapt to achieve bigger goals (KDE4/Plasma).

We're currently researching into
> things like Kross, which provide swappable interpreters on runtime..
> perhaps you'd be interested in working with that, join us in #plasma.
>

I am not sure of what you are talking about. If you are saying about
embedding a Python (or any other script) extended QWidget into a C++
aplication, this is already possible.

I have already made a Python widgets get into QtDesigner. This is a great
revolution for us.

Of couse we need something more generic for KDE to handle all script
languages, but I think that it is very easy. You just have to provide us the
C++ interface to conform and I provide the implementation of the Python
interpreter. Every binder will do the same.

I think the guy of Kexi already have started something like this.

So, please, let's clear things quickly so everybody start playing with
plasma applets :)

[Eric Jardim]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mail.kde.org/pipermail/panel-devel/attachments/20050917/1d3d5091/attachment.html


More information about the Panel-devel mailing list