hsluv VS symengine

Here's a potential solution to having consistent accessible color palettes in Koala: https://www.hsluv.org

If you want to take a step further, take a look into perceptually uniform color spaces, like HSL(uv) or LCh(uv).

Maxima enabled me to make my color space [HSLuv](https://www.hsluv.org/). I encoded CIELUV <-> RGB transformation functions into Maxima, ran `solve` and converted the output back into code. It's great to be able to commit [Maxima code](https://github.com/hsluv/hsluv/tree/master/math) into your repository and not leave the math as an "exercise to the reader".

If you want to make it more useful than a browser's built-in color picker, perhaps support other color spaces? Maybe HSLuv or CIE L*a*b*?

Chroma could be included, but as a minor criterion. When I look at color pickers that try to balance human perception against geometric simplicity like HSLuv and Okhsl, chroma is the property that gets distorted the most. Perceptual brightness and hue seem to be more important.

> Now, HSL isn't necessarily the best color mode to use in every situation; it tends to produce gradients that can be overly bright and vivid, because it doesn't take into account human perception.

Shout-out to to [HSLUV](https://www.hsluv.org/) which does exactly that.

I'm a little bit of a color freak. Allow me to leave some suggestions :)

- Picking from the 256 color pallete will likely give you colors with different brightness. This may hurt readability of darker colors on a dark background, and may make some color stand out unintentionally. Consider using something like HSLuv [1] to pick colors with the same lightness, then convert to the closest Xterm color [2].

- To make it obvious there is a gradient, I'd pick one lightness (assuming HSLuv) and one saturation (I usually stick to 100%), then pick a distance in hue for each step. For example if I expect to see a maximum of 7 steps on the screen at once, one way is to start at 0, then 30, then 60, etc. You may choose to go over 180, but keep in mind 360 will be the same as 0 so maybe stop at 240. Note how by picking adjacent colors from the table you are still picking a distance, but the distance is too small so it's hard to see.

- You may want to choose a different starting point than 0, and maybe different direction for the steps, depending on whether you want the colors to "mean" anything. For example red is commonly associated with warning, so you can arrange to have the top of the range aligned with red. Or arrange to avoid the red region if you don't want that association.

[1] https://www.hsluv.org/

Check out HSLuv as an alternative for UI design: https://www.hsluv.org/

HSLuv is a HSL alternative, which aims to maintain the perceived lightness of colors across the hue spektrum. It also includes a HPLuv variant, which additionally maintains saturation, at the cost of color coverage. Both are very useful for procedually generating or modifying colors. More Info: https://www.hsluv.org/comparison/

SymEngine will do this: https://github.com/symengine/symengine

If you need programmability or interoperability, Sympy is way nicer. If you just want an interactive symbolic calculator, Maxima is fine but sometimes quirky (has odd conventions due mainly to its age). As heisig points out, Maxima can be quite a bit faster (but I run into slow things with it too). Using Maxima via Sage is in some ways the best of both worlds.

You may also be interested in SymEngine: https://github.com/symengine/symengine

Context: I'm making a application for robotics calculations, making symbolic calculations using (symengine), and at some point I would like to be able to see the steps of these calculations, symengine has a function that returns the latex code do the elements you want. So I was trying to find a library or something of sorts to render that text into an image, I'm using Dear IMGUI in the docking branch to make a simple UI where I would like to display these equations. I know it might not even exists but I would like to give it a try. I found KLateXFormula, which depends on Qt as far as I understood, so I would like to avoid that if possible, I also studied a bit about the TeXStudio repo and found they use Qt to render previews. I also tried to understand the miktex repo searching for a function that I could use, but I barely understood the structure of the repo. I'm getting frustraded. I also found approaches where people would call latex executables to parse latex to DVI(Or something like this) but I would also like to avoid this approaches if possible.

- Might there be any way to leverage the work of https://github.com/symengine/symengine ? I assume a straight-up language binding to symengine might be a completely separate project, but possibly for some specific features symengine, maybe... (It is a pity they chose c++ and not rust to implement symengine in. In the end, the main target seems python/sympy here and not c++.)