Using scripting languages for KDE4 main modules

[Aaron J. Seigo]

On Saturday 07 October 2006 10:51, Boudewijn Rempt wrote:
> It only means that you and I have very different things in mind when
> talking about scriptable applications: you are thinking about extensions
> developers who make their extensions available to users, and I am thinking
> about users and companies (even small ones) who need to write scripts for
> themselves. 

while i do enjoy it when people tell me what i'm thinking, i can't quite agree 
with your assessment of my thoughts in this case ;)

> Like we could with WordPerfect 4.2 or Word 2. To create some 
> functionality that is needed at the user's workplace, but not necessarily
> elsewhere.

having looked at an unfortunate number of ms office documents in past lives, 
this is indeed quite a common pattern. given the language these people used 
for this (mostly vbscript and other more complete bastardizations of basic) 
i'm failing to understand the issue.

as i noted, it's wonderful if we can provide a choice of languages (that's one 
of my favourite features of postgresql, to draw on a completely out-of-band 
example), but we should at least provide one throughout all of our scriptable 
apps.

and this is my concern: we'll end up with 8 different choices in 8 different 
apps due to the author's personal preferences or feelings on what a user is 
and should be capable of doing. Cyrille noted that there is a commitment to 
support js in koffice and if so, that would suffice as far as i'm concerned.

can you also confirm this is the koffice plan?

-- 
Aaron J. Seigo
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA  EE75 D6B7 2EB1 A7F1 DB43

Full time KDE developer sponsored by Trolltech (http://www.trolltech.com)
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 191 bytes
Desc: not available
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20061007/859d2910/attachment.sig>