This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigECBB7D4A24FCD0B4F18A564C
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Aaron J. Seigo napisa=C5=82(a):
> p.s. and before someone jumps out with the bleeding obvious: yes, there=
 will=20
> be corner cases where javascript is completely, wholly and absolutely=20
> inappropriate due to the problem domain of the application (e.g. for in=
stance=20
> a scientific/math domain where there is already a standard language for=
=20
> working within that domain). but let's not derail on corner cases and r=
ather=20
> concentrate on the core uses.

I think the biggest problem with Javascript is that if you want to do
something more than standard set of actions prepared by author of
scripting plugin for application (like open your own configuration
window, message box, run some DCOP command, etc.), then you must use
Qt/KDE binding and AFAIK there is no Qt binding for JavaScript. Or am I
missing something?

	Krzysztof Lichota


--------------enigECBB7D4A24FCD0B4F18A564C
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2.2 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFFKWzTSHJB/1EhaUwRAq/8AJ9fIFBVFQB4AmNo8WFJ2O7x5tDGqwCgqja9
ZTxUBurHdk9Q6Su30JqlZFw=
=9BT9
-----END PGP SIGNATURE-----

--------------enigECBB7D4A24FCD0B4F18A564C--