Done. Currently deployed https://elixir-color.fly.dev preserves the seed across tabs. Color version 0.9.0 released too so the public visualizer and the private one are both fixed.
kip
ex_cldr Core Team
a-maze-d
@kip you really have god speed and it’s hard to keep up with you 
I wanted to get back to you regarding the LED discussion.
I had a deeper look at your library, gave it some good thoughts on whether the LED parts should be with your library, and whether I should swap my color functions to your library.
Swap to your library:
For now I decided against it for 2 reasons.
- Extra dependency & size: I intend my library to also be runable on very small devices a-la-atomvm
- Usage of
floatinstaed ofintegers. It does make a lot of sense for your library, but in my case (see previous point) I’m afraid to make the swap, because I might regret it on those small devices
Thus I will keep my simpler (more limited) version.
Still, I want to enable your library as an optional library with good interops.
Led specific conversion functions in your library:
This is really up to you to decide on whether you want to leave it in. I have to admit it is very much an edge case. No hard feelings if you drop it again.
Extra idea/thought:
Your various color spaces have to_xyz and from_xyz functions. Wouldn’t it make sense to move them to a (two) protocol(s)?
0
kip
ex_cldr Core Team
@a-maze-d, Thanks for the thoughtful reply, much appreciated.
I think, given your constraints, I’d stick with a simpler, more specific approach too. Floats make sense when dealing with multiple color spaces (and conforming to the color spaces domain when required). But much less sense if you’re working in one colourspace.
I will keep the LED colors in color. I did bill it as comprehensive is I consider them in scope and almost no extra heft to the library. I may, as @LostKobrakai suggested, remove the component specific shortcuts.
And while I do have a behaviour defined for to/from_xyz, a protocol sounds a very good idea too. Thanks for the suggestion.
1
kip
ex_cldr Core Team
I think we’re getting pretty stable on Color so I expect to move this to 1.0 release soon. I just published color version 0.10.0 with a couple of small new goodies.
New features
- Add
Color.Rec2020andColor.AppleRGBspaces - Extended
Color.Spectralwith B, C, F2, F7, F11 illuminants andblackbody/1.
Yes, quite niche I know 
2
tcoopman
Hi Kip,
I was just trying the latest versions published on fly, but this isn’t fixed yet I believe, or am I missing something?
0
kip
ex_cldr Core Team
I’ll try with your seed when I get back online im an hour or so. Please do open an issue at Issues · elixir-image/color · GitHub
1
kip
ex_cldr Core Team
Tuns out that #ff9900 is as orange as you can get in the sRGB world, and building a palette around that while staying within gamut is close to breaking the laws of physics. Color has a gamut viewer that helps illustrate the challenge. But this issue definitely helped prompt some usability improvements of the gamut visualizer - like plotting the palettes gamut curve automatically and adding some knobs and dials to help squeeze as much as possible out of your chosen colourspace. Thanks to @tcoopman for raising the issue and giving Color a good workout!
2