
Ideally, KoColorSet is refactored to have the import export seperated into plugins.This should have a special spot in the UI.


This is very common in palettes out in the wild, especially ones with spot colors where the ID is a unique code like 'OY348' and the name is some flowery nonsense like 'naive peachy pink' ID - string number unique to this color.The XML stores the name, version, columns and comment and then has a child element ‘ColorSetEntry’ which is then used to store the data from the KoColorSetEntry.Outside of LCMS ‘built-in’ profiles all profiles should be stored and retrieved from the zip.We chose for a zip file, with a colors.xml, and the referenced icc-profiles.To some extent, the native file-format is an expression of the data-model, but in Krita we try to avoid data-dumps, so not quite that extreme. The native file format and internal datamodel. The native file format and internal data model.Palettes (from discussion during halloween) Develop format for high bit depths and scene reffered colours.Better save and edit dialogues.(New palette UI is kinda.Exposing tagging of palettes to the UI.Palettes are also limited to 8 bit sRGB colors, so we'll also create a new swatchbook format that allows for higher channel depth colors." We want to add tagging, searching, creating, saving and editing of palettes.
