From kde-core-devel  Fri Mar 28 16:55:48 2008
From: "Aaron J. Seigo" <aseigo () kde ! org>
Date: Fri, 28 Mar 2008 16:55:48 +0000
To: kde-core-devel
Subject: Re: Guidance in KDE Admin
Message-Id: <200803281055.48541.aseigo () kde ! org>
X-MARC-Message: https://marc.info/?l=kde-core-devel&m=120672394926435
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--nextPart2494168.ieJjAnOB2C"

--nextPart2494168.ieJjAnOB2C
Content-Type: text/plain;
  charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Friday 28 March 2008, Luciano Montanaro wrote:
> > the first gen EEE PC comes with python on it already; the next generati=
on
> > devices will have even more storage. so these really aren't the devices
> > that we need to be worried about here. when we're talking about "can we
> > fit a python interpreter" on it, we're talking small devices like phone=
s,
> > ultraportable tablets, blackberries, etc..
>
> All right; I do not oppose Python specifically, but I'm worried of a chain
> reaction where all kinds of interpreters get used all over the modules.
> I'd rather have one blessed scripting language, but I fear that's going to
> be a policy problem...

i think we can get away with 2 or 3 languages. Allen W. sent a really nice=
=20
list of requirements for such languages to the release team list and it=20
really knocks it down to a few realistic choices: python, ruby and java.

> > > That may be Python, or something else... I'd prefer one of the
> > > ecmascript interpreters we ship, actually...
> >
> > for in-application scripting, absolutely. for full apps, something with
> > more available libraries, more application dev appropriate docs, etc
> > would be nice. in fact, many of the things that make ecmascript really
> > great for in application scripting are hindrances for full app devel im=
e.
>
> Well, we are talking of configuration modules just now, aren't we? Not
> "real" applications.

the difference in this particular case between "real app" and a "plugin" is=
=20
small enough that quibbling would be silly imho ... some of the control=20
panels have as much lines of code as the plasma app (the binary, not=20
libplasma) does.

> > > It would be nice if we had one javascript interpreters instead of two=
=2D-
> > > soon three, but that's another problem.
> >
> > a third? oi.. whre's this?
>
> we have KJS and QtScript... and JavaScriptCore, as soon as 4.4 is release=
d.
> Am I miscounting? Not all may be used for scripting, but still we'll have
> three.

ah, right JSC. i really do hope at some point that they do manage to find a=
=20
way to replace the guts of that with QtScript (leaving just the web specifi=
c=20
API). iirc someone was looking into that at some point.

=2D-=20
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

KDE core developer sponsored by Trolltech

--nextPart2494168.ieJjAnOB2C
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.4-svn0 (GNU/Linux)

iD8DBQBH7SMU1rcusafx20MRApkwAJ4t2FLKYXRbQFVZ4d451x9KpVrsAwCaAudQ
TSsjI4ZLWwV+xODhOG1q2J8=
=7mdC
-----END PGP SIGNATURE-----

--nextPart2494168.ieJjAnOB2C--