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

List:       koffice-devel
Subject:    Re: KOffice Scripting for KDE4 (Was Re: Moving
From:       Cyrille Berger <cberger () cberger ! net>
Date:       2005-11-04 16:03:44
Message-ID: 200511041703.45311.cberger () cberger ! net
[Download RAW message or body]

> At Akademy it was decided that ECMAScript support was to be added at the
> core of KDE.  KJSEmbed is moving into kde's core libraries and will provide
> a scripting and automation interface for all KDE applications.  This will
> be done in a similar manner that dcop is done now.  Now you may ask "Why
> ECMAScript?  Why not Python?  Why not <fill in my pet language>"  Well the
> answer is pretty much "No-one cares". 
And why not every language ? Why not let the user choose his language ? And 
also, you need to consider, that KOffice might have to support StarBasic to 
be compatible with OpenOffice.

> If they cared about using all of the 
> languages they would have jumped on the KScriptInterface back in 3.0. 
Well, I had a look at KScriptInterface a while ago, but I never figure out how 
to make it work, nor what it was suppose to do ? How to integrate it in an 
application ? How to write the binding ? Maybe I am stupid, maybe there is 
somewhere an exemple, a documentation on how to make it works.

> The point is ECMAScript is the most popular scripting language out there.  
TT
> has done a few studies, 
I would love to see that study.

> as well as the fact that pretty much every web page 
> out there uses ECMAScript.
That's true, does that mean that ECMAScript is the best language for 
everything ? Does that mean that everybody that uses ECMAScript in a webpage 
knows to use it ? I would guess that more thant 90% of the ECMAScript is just 
a copy/paste of www.javascript.com or any other ressources site.

> > Personally, I think the Sebastian Sauer's kross thing is pretty cool --
> > and given that it works already, maybe something for the dreamers to take
> > a look at? And build upon kross, instead of reinventing the wheel again?
>
> I am not sure what kross gains us.  It seems pretty unclear what use it
> really would be.  Its way to heavy for automation scripting, and way to
> light for adding full plugins.
Did you jhave a look to the code ? It's very similar to what you can find in 
kjsembed, so it is as heavy, except that you can use any scripting language 
you want once you have writen the bridge between the interpreter and kross.

And well, Kross is not intented to write KPart with it, but you can definitely 
write filters with it, superkaramba themes and so on.

I have nothing again using a KParts::Plugin written in python or ruby or 
javascript or anything else, we already use a lot of C++ KParts::Plugin in 
krita. But there is the problem of bindings, you need to write by hands 
bindings for every language, or use scripts. The problem with automatic 
scripts is that the core API change a lot, which is not acceptable for users.

Oh, and KOffice people wants to work with the rest of KDE. We won't stick with 
kross if you have something better to offer.

-- 
--- Cyrille Berger ---
_______________________________________________
koffice-devel mailing list
koffice-devel@kde.org
https://mail.kde.org/mailman/listinfo/koffice-devel
[prev in list] [next in list] [prev in thread] [next in thread]