QtScript

[David Faure]

On Tuesday 06 February 2007, Simon Hausmann wrote:
> instead of duplicating your entire existing API, which is 
> what you have to do with kross. Just look at kword's scripting plugin to see 
> what I mean.

Actually this might be a good example of the opposite. Having scripting API very close
to the C++ code is what we had with the DCOP interfaces in koffice-1.x, and it was so close
to the code that there is _no_ way to provide the same interfaces after a rewrite of the core
like it is happening for koffice-2.x. All the internal notions (the need to create a KWTextFrameSetEdit
before inserting text, etc.) are exposed to the scripting API; which kills any possibility of
refactoring later. Instead, we want to define clean scripting APIs that are independent from
the application design. That looks like duplication but it's IMHO the only way to ensure
stability of the scripting API.

-- 
David Faure, faure at kde.org, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).