[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-core-devel
Subject:    Re: KDE Scripting Interface [2nd Try]
From:       David Faure <david () mandrakesoft ! com>
Date:       2001-07-22 3:00:54
[Download RAW message or body]

On Fri, Jul 20, 2001 at 11:11:48PM +0200, Martin Konold wrote:
> On Friday 20 July 2001 10:25 pm, Martijn Klingens wrote:
> 
> > If that is true, then you're completely right and we should all stop
> > worrying. I don't know, I only know that KDE probably needs scripting
> > capabilities up to par with VBA to gain real corporate ground. Whether one
> > uses KOffice macros or real scripts for that... What would a corporate user
> > prefer? I think we should adapt our choice to the answer on that question.
> 
> I used to develop word macros for a large company and only did this because 
> there is nothing better available for MS-Office.
> 
> The fact that we have the powerful and secure dcop scripting capabilities 
> makes powerful scripting embedded in documents rather unimportant. I can even 
> imagine that we do not really need it anymore ;-)

Just to confirm that my take on this (as a KWord developer), is that I
don't want embedded scripts either. External scripts using DCOP can
do the job just fine, without the "macro virus" risk (a separate script
_will_ be treated as such - i.e. like an executable, with big warnings from
KMail and Konqueror -, whereas the document will only have the data.
This is a much better design anyway (separating the data from the processing) !
The only missing thing is an easy way to launch those scripts. Maybe
the Tools menu could be extendable by the user, so that it's possible to
run an external DCOP script from KWord itself [but not in an automated way!]

-- 
David FAURE
david@mandrakesoft.com, faure@kde.org
http://home.clara.net/faure/, http://www.konqueror.org/
KDE, Making The Future of Computing Available Today

[prev in list] [next in list] [prev in thread] [next in thread]