From kde-core-devel  Thu Jul 11 18:23:47 2002
From: Zack Rusin <zackrat () att ! net>
Date: Thu, 11 Jul 2002 18:23:47 +0000
To: kde-core-devel
Subject: KDE scripting architecture.
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=102641185508593

Hi,

has anyone thought of it? Let's say I have application A and I want to=20
create a plugin interface for it (Perl, Python, Guile - whatever). At=20
this point it's a problem, as there's no easy way to do it. Maybe it's=20
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:
=2D-----
use APlugin;
sub load { APlugin::connect( "onStart", &handler ); }
sub handler { APlugin::printMessage( "Hello, World!" );
=2D-----
meaning one class exposes interface to all scripting languages. This=20
solution would most probably involve another daemon which would make=20
those plugins work in a similar manner to kioslaves. Hmm, I don't know,=20
but maybe it's time to do some brain-storming.

Zack Rusin

=2D-=20
So many pedestrians -- so little time.=20