[prev in list] [next in list] [prev in thread] [next in thread]
List: kde-core-devel
Subject: KDE scripting architecture.
From: Zack Rusin <zackrat () att ! net>
Date: 2002-07-11 18:23:47
[Download RAW message or body]
Hi,
has anyone thought of it? Let's say I have application A and I want to
create a plugin interface for it (Perl, Python, Guile - whatever). At
this point it's a problem, as there's no easy way to do it. Maybe it's
time that we come with something up. Ideally something like :
class APlugin : public KScriptIface
{
Q_OBJECT
...
public slots:
void printMessage( const QString& );
void ringBell();
signals:
void onStart();
void onEnd();
};
would let one write script like:
------
use APlugin;
sub load { APlugin::connect( "onStart", &handler ); }
sub handler { APlugin::printMessage( "Hello, World!" );
------
meaning one class exposes interface to all scripting languages. This
solution would most probably involve another daemon which would make
those plugins work in a similar manner to kioslaves. Hmm, I don't know,
but maybe it's time to do some brain-storming.
Zack Rusin
--
So many pedestrians -- so little time.
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic