PC? I’m practically drawing on an iPad! (Keyboard-less experience): The main idea here is to reduce the number of devices we’re dependent on as much as possible.Luckily the popup palette solves most of the issues. I love hotkeys as much as the next person, but sometimes some combinations are way too awkward to use frequently with one hand. This single tool made the transition much easier. Frequent actions must not require more than 2 clicks (God bless the popup palette!): By far, the popup palette has possibly been the most useful tool in Krita I’ve encountered.But I will later write about feature requests that might help expand upon this. Bare necessities only: Naturally, since important dockers such as layers and toolbox aren’t visible, this philosophy might lean more towards the sketches/doodles rather than extravagant pieces.As someone who uses a Kamvas 12, being able to go “truly” fullscreen in Krita was a boon to say the least, as it was not something I was able to take advantage of in CSP. Only canvas is visible (UI-less experience): We all know that it’s good practice to look at the entire illustration rather than spending too long on minute details that won’t even be noticeable in the final overall piece.This is just something I’m tossing out there from my personal workflow and through my micro-journey transitioning across the two softwares. I apologize beforehand if some features that I’m proposing/requesting already exists, be it vanilla or through 3rd party plugins. I am curious as to what the community has to say about this.

It was because of the differences I noticed in how Krita handled certain tools/features (and lack thereof) that gave me the idea to make this post. But now, due to “certain reasons” I got the push I needed to make the jump and am pretty glad I took the day to tinker around. From a distance, it has always felt to me like it was the Blender of 2D art and animation, but I never got truly get into it since I was used to Clip Studio Paint and its workflow. It is for reference only.Firstly, I’d like to mention that I’m a huge advocate of FOSS and am super impressed at how much Krita is capable of for what it is. Because the Create wiki is down, it’s contents are reproduced here. The following is the Color Swatch definition from the old create wiki. Color swatch definition from the Create Wiki: ¶ Note that Krita supports unbounded colors as long as the bitdepth is F32.

Krita supports Gray, sRGB, RGB, XYZ, CMYK, Lab and in theory YCrCb. The other child element is a Create Swatch defintion. The Position element is the position of the swatch inside the parent group grid. This is currently not used elsewhere in Krita, but the intend is to use it for encoding spot colors as only the id. Whether or not the color is a spot color. Lab and CMYK don’t support F16, and for CMYK F32 is not recommended because it doesn’t deserialize the same way as the integer colorspaces. Values are U8 (Unassigned 8bit integer), U16 (Unassigned 16bit integer), F16 (16 bit Floating Point), and F32 (32 bit Floating Point). The bitdepth at which the color should be loaded. Often, the ID is used for referencing spot colors inside files. In the above example, which encodes the D65 standard illuminant at 0 stops, SI-D65-0EV is a clear unambiguous id, but “Noon daylight at 0 EV” is a much more human friendly way to refer to it. This is for complex colorsets where there is a human friendly name, and a name that uniquely identifies the color in the swatch database.

Unlike the create swatches, we don’t support translated color names.

Krita palette