In traditional media, the artist would create a dedicated premixed palette based on a gamut mask (new or reused) for every artwork.
In Krita, there is no need for a premixed palette, the artist can work straight from the color selector with the mask applied. For that, the artist needs to know which mask was used when last working on a document and it's parameters.
A solution is to assign the gamut mask with the parameters to the document.
The artist assigns currently selected mask to active document with a button in the gamut masks docker. Assigning again with another mask selected changes the mask assigned to the document. The mask can be unlinked from the document.
The mask is reapplied upon opening the document.
When switching view, if the document in the view has a mask assigned, the mask is applied to selectors, if not, the previous mask is disabled in the selector.
The mask and it's parameters need to be either (1) linked to
**How does the user assign the mask?**
- with a button in the kra file, or (2) embedded in it.
(1)gamut masks docker
- Less bloat i- In the document, just metadatagamut masks toolbar
- The mask has to be identified by an uuid- It is done automatically if there is a mask selected, which changes upon any edit of the mask shapes. Otherwise the artist ends upcan be toggled on/off somewhere (where?)
with different colors upon reopening.**Restoration of selector settings**
The artistic color selector saves it’s color model within the .kra file. The color model is set with the mask upon opening the document, to ensure color consistency.
- Should there be a setting for it somewhere? In the selector?
- Sharing is harder -- How does the user revert the mask has to be exported and shared withchange if she doesn’t like it?
The mask resource is embedded in the documentKRA file. On the other artist's installatioWhile the document is in the mask must not collide with any ofcurrent view, it is present in their masks.
(2) resource server.
- Adds data to the document (<50kB)
Selector settings are saved in the XML:
- Sharing is straightforward -- Advanced selector: the wheel stays the mask is insame regardless of the file and loaded upon opening the documentcolor model set, no need to save
- The mask needs to be visible for the active document only, but it needs to be editable in the gamut masks docker, etc.
Another thing to consider is the selector and it's settings. The actual colors that the mask shows can vary depending on which color selector is used (artistic and advanced selectors show slightly different colors on the same position in the wheel), which color model is used (HSY will yield different colors than HSV), or other parameters (e.g. inverted saturation). Should those settings be saved along with the mask? Should they be set upon document opening?Artistic selector: color model