[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-panel-devel
Subject:    Re: [Panel-devel] Introducing me
From:       Eric Jardim <ericjardim () gmail ! com>
Date:       2005-09-17 21:07:59
Message-ID: 432ec6c50509171407354b7950 () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


2005/9/17, Aaron J. Seigo <aseigo@kde.org>:
>
> indeed. the guarantees should be that the plasma API is fully bound, and
> that
> the KDE API is also available. the full KDE bindings should only be
> brought
> in when necessary though, which is to say the plasma API should NOT be
> reliant on the KDE/Qt bindings. that way leads to madness =)
>

Ok, so it should be separate. But indeed we can do some "tricks" to
interoperate even if you redefine all base classes (especialy QObject and
QWigget) in the Plasma, and don't tell Qt4 bindings before.

That's just a fact that, unless you use something like a "sandbox" behaviour
to the interpreter, any Python script can access any extension module, and
this include Qt4/KDE4 bindings if avaliable.

[Eric Jardim]

[Attachment #5 (text/html)]

2005/9/17, Aaron J. Seigo &lt;<a \
href="mailto:aseigo@kde.org">aseigo@kde.org</a>&gt;:<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;"> indeed. the \
guarantees should be that the plasma API is fully bound, and that<br>the KDE API is \
also available. the full KDE bindings should only be brought<br>in when necessary \
though, which is to say the plasma API should NOT be <br>reliant on the KDE/Qt \
bindings. that way leads to madness =)<br></blockquote></div><br> Ok, so it should be \
separate. But indeed we can do some &quot;tricks&quot; to interoperate even if you \
redefine all base classes (especialy QObject and QWigget) in the Plasma, and don't \
tell Qt4 bindings before.<br> <br>
That's just a fact that, unless you use something like a &quot;sandbox&quot;
behaviour to the interpreter, any Python script can access any
extension module, and this include Qt4/KDE4 bindings if avaliable.<br>
<br>
[Eric Jardim]<br>



_______________________________________________
Panel-devel mailing list
Panel-devel@kde.org
https://mail.kde.org/mailman/listinfo/panel-devel


[prev in list] [next in list] [prev in thread] [next in thread]