--nextPart2513304.JX6aluB6Al
Content-Type: text/plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

Boudewijn Rempt wrote:
>> For the former case, we already have decided on the official language
>> and it's JavaScript. We already have the interpreter in KDELibs (KJS).
>
>Not for Koffice, fortunately. We have Kross, which makes it really easy
> to offer one scripting interface that works with any language for which
> there's an interpreter plugin. We first used kjs for Krita's scripting
> language, but it was a pain to provide bindings to the objects we
> wanted to expose to script writers, and it was a pain to write scripts.

It doesn't have to be KJS, but it would be nice if it were, since it's=20
already installed and part of KDE Libs.

But if any scripting is provided, JavaScript (in some form or another)=20
should be supported. That's what was decided in aKademy 2005.

=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

--nextPart2513304.JX6aluB6Al
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)

iD8DBQBFH6ctM/XwBW70U1gRAtlLAJ9NuUIyyWVKlAHhOOpTr/0UXIMu1gCgwoRY
FSzpbswvV93wjFRXD9fWYQc=
=PWka
-----END PGP SIGNATURE-----

--nextPart2513304.JX6aluB6Al--