Scripting

[Casper Boemann]

Sounds right. I tentatively support kross as well.

However lets start by defining what we what krita to do/provide in the end:

- Provide acces to functionallity, ie being able to say load,scale, filter
and save images from a script.
- Support an (in theory) unlimited number of languages
- Allow scripts to be executed from other scripts (cross language), and from
menus in krita

is that it. how about:
- "record" the user actions into any script language?

Do we have cases where "like in a texteditor that uses script to provide
highlighting for different languages". We have such cases but until now
colorspaces, filters and tools have all been written in C++. Are we moving
towards allowing those things to be scripted?

more?

is this as complex as it gets?

best regards / venlig hilsen
Casper Boemann

----- Original Message ----- 
From: "Cyrille Berger" <cyrille.berger at lepi.org>
To: "Krayon (KImageShop)" <kimageshop at kde.org>
Sent: Monday, June 06, 2005 8:23 AM
Subject: Scripting


> Hello,
>
> I am back with some time for hacking on krita. And I was thinking about
the
> scripting feature, and I have notice that we have all a different
> prefference, so I think it would be best to use some tools to generate the
> wrappers, we have, at least, three options :
>  - make our own
>  - kross ( http://www.kexi-project.org/wiki/wikiview/index.php?Scripting )
> advantage : good integration in kde/qt/koffice, problem : currently
support
> only python, but plan for kjs, but it should'nt be too hard to add other
> languages
>  - swig ( http://www.swig.org/ ) advantage : support a lot of language
> problem : it's heavyheight
>
> I personnaly favor kross, but I would like to have your opinion on the
> subject ?
>
> -- 
> --- Cyrille Berger ---
> _______________________________________________
> kimageshop mailing list
> kimageshop at kde.org
> https://mail.kde.org/mailman/listinfo/kimageshop
>