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

List:       koffice-devel
Subject:    Re: Scripting status for koffice?
From:       Simon Hausmann <sh () caldera ! de>
Date:       2001-01-03 10:37:46
[Download RAW message or body]

Hi,

I do believe that for scripting in KOffice we should use the combination
of DCOP and python. Please everyone have a quick look at 
kdenonbeta/python/test/ . IMHO it's beautiful :-) (Thanks to Torben!)

Those bindings are in pretty early stages, but they are a nice beginning,
IMHO, while still being already very powerful ! (there is marshalling/
demarshalling support for most data types, what's missing are structured
types like QRect, QPoint, etc. ) . What's also missing is server support,
meaning support for writing dcop server objects in python, but it appears
to be rather complicated (I once tried, but failed when it came to
demarshalling the method arguments and turn them into python types) .
But anyway, server support doesn't appear to be thaaat important for koffice
scripting, to me. What do you think?

Another argument for using this combination is that we already have support
for it in the framework (the koffice libraries) :-) . Even though it's just
kind of basic stuff it allows quite some scripting based on actions, and
applications can easily extend this to export application specific
functionality (see kspread,kpresenter) .

Bye,
 Simon

On Tue, Jan 02, 2001 at 05:10:00PM -0500, John Califf wrote:
> Mostly (but not entirely) offtopic reply to question about scripting:
> 
> On Tuesday 02 January 2001 08:19 am, Shaheed Haque wrote:
> > Hi all,
> >
> > What is the status of scripting for KOffice? I'm vaguely aware that some
> > work on scripting was done in the past but I'm not sure where we are now!
> > Some specific questions:
> >
> > 1. Is DCOP expected to be used as the API for scripting?
> >
> 
> I'd assume that DCOP can be used if an interface is provided with any Koffice 
> app but that DCOP will not replace more conventional scripting languages like
> Python which can be used more comprehensively than DCOP can be used.  What 
> about koscript?  Is that no longer being maintained? 
> 
> > 2. Is there a preferred script language to start with (python? java?
> > kscript - where/what is that, anyway?)
> >
> 
> It seems that Python is the preferred scripting language but that's only 
> becasue there are so few bindings for Kde/Qt other than Python.  Much to my 
> surprise I discovered just last week a new Ruby/Qt and Ruby/Kde release for
> Qt 2.2x and Kde 2.x.  It works.  Not many people know about this but it's 
> important news because it shows how easily bindings can be done for Qt and 
> Kde with almost any language.  Unlike PyQt and PyKde, Ruby-Qt and Ruby-Kde 
> use the more conventional swig glue. Ruby-Qt takes only a few hours to 
> compile on my old box, but I don't have enough memory to even compile the 
> latest PyQt.  Ruby is such a great language and works beautifully with Qt now.
> Much more elegant than Python in my opinion and just as easy to use.
> 
> > I also recall some mention of VB scripting. Where did that all go?
> >
> > Thanks, Shaheed
> > _________________________________________________________________________
> 
> I'd be interested in a better response to you query, Shaheed, from someone 
> who knows more about these topics.  But, for starters, does anyone have a 
> comprehensive list of ALL the scripting (and other) languages with bindings 
> for Qt and/or Kde?
> 
> John
> _______________________________________________
> Koffice-devel mailing list
> Koffice-devel@master.kde.org
> http://master.kde.org/mailman/listinfo/koffice-devel
_______________________________________________
Koffice-devel mailing list
Koffice-devel@master.kde.org
http://master.kde.org/mailman/listinfo/koffice-devel

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