Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

make nomenclature of "palette" or "hexplt" consistent #134

Open
earthbound19 opened this issue Feb 22, 2023 · 0 comments
Open

make nomenclature of "palette" or "hexplt" consistent #134

earthbound19 opened this issue Feb 22, 2023 · 0 comments
Labels
3 - annoyance annoying but doesn't break essential functionality. pls fix kthxbai

Comments

@earthbound19
Copy link
Owner

earthbound19 commented Feb 22, 2023

Make nomenclature of "palette" or "hexplt" consistent in all code, comments, and script names.

That will mean updating inter-script calls on updated names.

It's different and inconsistent depending on whether my neurons fired strange or down at the time I made scripts.

It's actually a usability problem. I just spent too long finding a script because I was searching for "palette," not "hexplt."

"Palette" is more immediately understandable.

And technically it should probably be the more lengthy "sRGBpalette," to admit the possibility of a variety of future palette types. And for more technical detail/accuracy.

Maybe even "sRGBhexPalette," because it's only a convention of mine that I store sRGB color codes only as hex color codes (0-9a-f). But triplets of numbers from 0 to 255 is another common convention (which I don't use).

@earthbound19 earthbound19 created this issue from a note in _ebDev tracker (backlog) Feb 22, 2023
@earthbound19 earthbound19 added the 3 - annoyance annoying but doesn't break essential functionality. pls fix kthxbai label Feb 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3 - annoyance annoying but doesn't break essential functionality. pls fix kthxbai
Projects
_ebDev tracker
  
backlog
Development

No branches or pull requests

1 participant