Color Library / Color Palette - #WorkFlow
Color Library - The feature, or should I say, improvement to the existing "Asset Libraries" and Color-Picker, allows users to name and store color values in a .blend file. Saving a color could be done by clicking the Save-Icon (needs to be added) in the "Color-Picker-Menu". Loading a color could also be done from the "Color-Picker-Menu" in the new TAB called LIB. The new TAB structure could be like this: [ RGB - HSV - HEX -
LIB
].
The content of the
LIB
Tab could be the same as the HEX tab, except instead of a value to type (or paste), you pick (or type) a Color-Name (that you named during saving) from the dropdown menu.
Right now If you have 10 materials and 10 colors, you need to create 100 materials if you want to maintain some order in your projects, and if you want to change 1 material, you need to repeat the same change to the material but with a different color, 10 times ,and that's assuming the material has only one color.
Thanks "-L0Lock-" for the GREAT suggestion / follow-up:
Solution might be color palette node in which you can create swatches and output a specific color from them.
palettes data-blocs already exists (half the job is done), we can export/link/append them, I guess it would be also relatively easy to make them registrable in the asset browser, and it works kind of similarly to the Color Ramp node (select a swatch/handle, or type its index, and edit its color).
This feature was requested multiple times in the past, with a lot of upvotes, but never made to the any release.
blender.community/c/rightclickselect/Rtcbbc/
blender.community/c/rightclickselect/Nlfbbc/
Honestly... This should be implemented Years ago ( in any way )
I do believe its not that time consuming to implement/code now that we have "Asset Library"
7 Comments
I have the feeling that what you want is actually to share a specific color across materials? If that's so, then a node group isn't a workaround, it is THE solution to share node data across materials.
But let's say we have to consider having a specific solution for that specific case: I don't think it belongs to the color picker (whose role is to define a color from values, and inputs/outputs RGB data).
What you want really sounds like a palette system, which already exists in Grease Pencil:
Maybe the solution is to make this into a color palette node in which you can create swatches and output a specific color from them.
I like this idea more, because palettes data-blocs already exists (half the job is done), we can export/link/append them, I guess it would be also relatively easy to make them registrable in the asset browser, and it works kind of similarly to the Color Ramp node (select a swatch/handle, or type its index, and edit its color).
What a great reply and clean answer. Especially that the ground works is already done and, as you say, it should be relatively easy to implement. Can we get some UpVotes ? #SpreadTheWord.
If you agree with my proposal, feel free to implement it in your post, that's the main visible thing to begin with.
Updated
This should have more upvotes. +1
I personally use a group node with all the colors I repeatedly use in multiple materials.
That is also a way to do this, but it still not an elegant solution. Or should i say: I should not look for workarounds for such a ( imho ) key function