Difference between revisions of "Krita/Scripting"

Jump to: navigation, search
(Added some ideas)
Line 46: Line 46:
 
* Resize the image to have 800px width.
 
* Resize the image to have 800px width.
 
* save as 'filename-800pxwide.png'
 
* save as 'filename-800pxwide.png'
 +
 +
Example use-case: Live export
 +
Export the image as displayed on-screen (all layers merged) to a shared memory region for other applications to read. Interesting for game-developers et cetera who would like to have a preview of the texture they are editing right in their game.
 +
* Example with gimp: https://www.youtube.com/watch?v=2M9-_zpfEm4
 +
* Requires efficient access to pixel-data
 +
* Requires access to pixel-data that is generated by already merging all layers correctly
 +
 +
Example use-case: Control brush parameters
 +
Some artists like to use e.g. external hardware (e.g. with a scrollwheel or thumbstick) to interact with their painting program. It would be cool if it was possible for a plugin to manipulate brush parameters (size, flow, ...) on the fly through input it receives from e.g. external control-hardware or other such sources.
 +
 +
Example use-case: Warmup-script
 +
I like to use a script that deletes the entire canvas when I lift the stylus off my wacom tablet. Together with repeated or symmetry mode, as well as a speed sketch brush, it makes for a very nice way to generate shapes very quickly and warm up your "visual library". Currently I have this implemented in a very hacky way, if it was possible for plugins to listen for events such as "stroke end" or "pen lifted" and then issue a "clear canvas" command, this could be a simple 10-line script.
 +
 +
Big idea:
 +
A way to conveniently share scripts, similar to the GHNS mechanism that many other KDE components have, or the gimp/blender plugin registry? Users probably need to be told that plugins are not sandboxed!

Revision as of 18:26, 29 May 2015

This page is going to collect ideas on how to write the new scripting API for Krita 3.x

IRC log

19:22 < a----> C------B perhaps I think layer management would be important and useful to start with 19:22 < a----> E.g. adding a layer, positioning a layer and controlling common attributes like opacity special layers like masks etc. can come later. 19:23 < C------B> a----: that is actually what I am looking at now 19:24 < a----> that would be a good place to start I think. 19:24 < a----> Things like brush engines, brush opacity control are better done from within Krita and should not need to be used externally. 19:28 < A-----o> C------B, I'd love to make a plugin that deletes the current layer (or fills it with a color) when I lift the pen from the tablet, so I guess being able to listen to pen

                events would be cool

19:28 < A-----o> C------B, I'd also love to make some plugins that allow you to use external hardware to control e.g. brush parameters, so that would be cool 19:33 < a----> C------B I think its better to start from the outside gross functionalioty and then go to more deeper layers of Krita like an onion.

Usecases

What do people use scripting for in a program like Krita? To automate jobs!

What kind of jobs could be automated with ease?

  1. Exporting and Importing of files and to different filetypes(already possible with the command line)
  2. Layer handling -> Visible, lock, etc.
  3. Filters, or a set of filters.
  4. Transforms.
  5. Pseudo filters like 'split alpha' or 'split layer' or 'seperate image'.

Example use-case: Game Texturer: Has a file with three layers, called 'specular', 'diffuse', 'normal'. What they want to do is to make 'specular' the alpha channel of 'diffuse', and have the diffuse and normal layers exported as filename-layername.tiff. So the commands needed would be...

  • Find layer 'specular'
  • Convert layer to transparency mask.
  • Find layer 'diffuse'
  • Attach transparency mask 'specular' to 'diffuse'.
  • Export layer 'diffuse' as 'filename-diffuse.tiff'
  • Find layer 'normal'
  • Export layer 'normal' as 'filename-normal.tiff'

Example use-case: Comic artist. Has a file with several 'sketchlayers' a 'colour-layer' and 'lineart' layers. They would want to resize their files, and maybe even grayscale them:

  • Find all layers with name 'sketch'
  • Turn all these layers invisible.
  • Find all layers named 'colour'.
  • Put a 'greyscale' filter on all these layers.
  • Flatten the image.
  • Resize the image to have 800px width.
  • save as 'filename-800pxwide.png'

Example use-case: Live export Export the image as displayed on-screen (all layers merged) to a shared memory region for other applications to read. Interesting for game-developers et cetera who would like to have a preview of the texture they are editing right in their game.

Example use-case: Control brush parameters Some artists like to use e.g. external hardware (e.g. with a scrollwheel or thumbstick) to interact with their painting program. It would be cool if it was possible for a plugin to manipulate brush parameters (size, flow, ...) on the fly through input it receives from e.g. external control-hardware or other such sources.

Example use-case: Warmup-script I like to use a script that deletes the entire canvas when I lift the stylus off my wacom tablet. Together with repeated or symmetry mode, as well as a speed sketch brush, it makes for a very nice way to generate shapes very quickly and warm up your "visual library". Currently I have this implemented in a very hacky way, if it was possible for plugins to listen for events such as "stroke end" or "pen lifted" and then issue a "clear canvas" command, this could be a simple 10-line script.

Big idea: A way to conveniently share scripts, similar to the GHNS mechanism that many other KDE components have, or the gimp/blender plugin registry? Users probably need to be told that plugins are not sandboxed!


Content is available under Creative Commons License SA 4.0 unless otherwise noted.