qsa, kjsembed, python

Boudewijn Rempt boud at valdyas.org
Wed Jul 28 17:09:27 CEST 2004

On Wednesday 28 July 2004 14:31, Boudewijn Rempt wrote:
> On Wednesday 28 July 2004 14:27, Boudewijn Rempt wrote:
> > Kexi uses qsa
> Except that it stopped to do so... What now?

Okay, I've been through kdebindings/kjsembed (not too thoroughly) and through 
the qsa docs, and I think the following is a nice plan:

* Put scripting functionality in plugins
* Initially create a qsa plugin. Until kjsembed sports a user-friendly GUI 
with dialog editor and macro management as nice as qsa, it's going to be too 
much work to integrate. When Zack comes off with kjsembed-for-koffice, we can 
always do a second plugin. But I consider an integrated development and 
management environment essential for any plugin.
* Create a single facade QObject that sports the most important functionality 
for qsa to wrap (transactions, setpixel/getpixel, blit, create new image).
* Only build the qsaplugin when qsa is present on the developer's system; 
perhaps even make it a standalone plugin outside the KOffice tree.

Boudewijn Rempt | http://www.valdyas.org/fading/index.cgi

More information about the kimageshop mailing list