emacs-ipython-notebook VS hsluv

the github source : https://github.com/millejoh/emacs-ipython-notebook

I used https://github.com/millejoh/emacs-ipython-notebook at one employer and it works quite well for Jupyter. Of course Org is great but if your coworkers are unfamiliar it's probably a non-starter.

Looking at https://github.com/millejoh/emacs-ipython-notebook/issues this person seems to be using the github issues tracker as a combination of their personal tech support line + ranting board.

Maybe Emacs should have went down the road to have good Jupyter notebooks support instead, even EIN's maintainer was advising against using notebooks.

So that project was forked and this is the better location https://millejoh.github.io/emacs-ipython-notebook/

Except when it doesn't work. I tried using it a few months ago on both Windows and WSL, but I had to give up. Surprisingly, EIN¹ running a Maxima kernel worked.

I was going to try again before commenting, but I broke my WSL setup last week and didn't have time to fix it yet, but I sure will try it again next month.

¹ http://millejoh.github.io/emacs-ipython-notebook/

EIN also looks good but I haven't used it.

From my perspective when I had to turn ML models from a "real scientist" to something I could use in production, emacs-ipython-notebooks[1] was immensely helpful for me, since it allowed to connect to the jupyter server and edit and copy things from emacs to other code places as if I'm looking at an org mode file.

I see the appeal of Jupyter notebooks for someone testing out things or experimenting, but it's a bit like a brain dump that isn't that trivial to navigate around when a second or third person is involved.

[1] https://github.com/millejoh/emacs-ipython-notebook

Hey all! I'm quite attracted by the Emacs IPython Notebook (ein) package and would love to incorporate it into my workflow. However last time I tried (about a year and a half ago) it was officially unsupported in spacemacs and my experiments led to constant headaches like undotree failing, notebooks not saving, native compilation crashing, and a reliance on elpy for IDE features (afaik the only elpy layer available can be found here, uses ESS bindings, and seems to be orphaned.)

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/