From kde-core-devel Sat Oct 07 22:42:54 2006 From: Thiago Macieira Date: Sat, 07 Oct 2006 22:42:54 +0000 To: kde-core-devel Subject: Re: Using scripting languages for KDE4 main modules Message-Id: <200610080043.03272.thiago () kde ! org> X-MARC-Message: https://marc.info/?l=kde-core-devel&m=116026101815814 MIME-Version: 1 Content-Type: multipart/mixed; boundary="--nextPart1799902.t2JsnQi2Ho" --nextPart1799902.t2JsnQi2Ho Content-Type: text/plain; charset="iso-8859-6" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Cyrille Berger wrote: >or we could all use a framework that allow scriptability through js, > ruby, python, (whatever) and dbus for a little effort, and with the > same level of support. With the interpreter available on the machine if > the user has install it, meaning that js and dbus will allways be > available. And python and ruby will be available if the user has > install them on its computer. D-Bus is not a scripting language. Let's not make the same mistake with=20 D-Bus that we did with DCOP: it's not meant for application extension.=20 Scripting is. =2D-=20 =A0 Thiago Macieira =A0- =A0thiago (AT) macieira.info - thiago (AT) kde.org =A0 =A0 PGP/GPG: 0x6EF45358; fingerprint: =A0 =A0 E067 918B B660 DBD1 105C =A0966C 33F5 F005 6EF4 5358 --nextPart1799902.t2JsnQi2Ho Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.5 (GNU/Linux) iD8DBQBFKC13M/XwBW70U1gRAkbGAJ90JNlCmrHNHYKjVUSp3rU59gOTVACgrNvg Kf1Ib05Ig2LKuFKTrdP17YQ= =bJVv -----END PGP SIGNATURE----- --nextPart1799902.t2JsnQi2Ho--