About krita internals

[Boudewijn Rempt]

On Mon, 11 Dec 2017, Brendan Scott wrote:

> Hi
> 
> I am interested in doing some work with Python scripting in Krita, and am
> trying to decipher how Krita goes about doing what it's doing. I can see that
> there are nodes and actions, but it's not clear to me how actions are used
> programmatically.
> 
> I have found this:
> http://download.vikis.lt/doc/kde/HTML/en/krita/developers-plugins.html

Oh gosh, that's so incredibly old -- eleven years adn two version of Qt!

> But are there any other documents that explain how Krita is put together?

I'm afraid not... We're working on a kind of developers handbook, but 
haven't progressed much beyond "how to report a bug". 

The way actions work in Krita, though, is defined by the toolkit, Qt:
http://doc.qt.io/qt-5/qaction.html and the way KDE Frameworks extends it:
https://api.kde.org/frameworks/kxmlgui/html/classKActionCollection.html

The short version is, the action collection allows us to retrieve actions
by name, and then you can programmatically trigger them. Actions are used
to build up the user interface: menu, toolbar buttons and shortcuts and 
so on. So, triggering an action is exactly like pressing the shortcut
or selecting a menu item.



-- 
Boudewijn Rempt | http://www.krita.org, http://www.valdyas.org