Giters

jaames / iro.js

🎨 Modular color picker widget for JavaScript, with support for a bunch of color formats

Home Page:https://iro.js.org

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Feature request: handle Kelvin as WW + CW

Olifant1990 opened this issue · comments

commented

There are a lot of devices on the market with 5 channels, Red, green, blue, warm white and cool white.
These devices are also known as RGB+CCT devices or RGBWW.

Is it possible to implement a way of using a kelvin slider, maybe together with a value slider, to get an output of WW: 255, CW: 0 for (for example) 2000 kelvin and WW: 0, CW: 255 for 40000 kelvin?

commented

Or, if not easyli done, maybe an method/option to get a slider percentage?
Like 0 is fully at left/100 is fully at right?
Then I can calculate my needs for which WW/CW value I need to set.

commented

For what it's worth, I'm not taking feature requests for this library any longer, here's what I wrote about that in the iro v6 thread:

Unless you're a GitHub sponsor or using iro.js in an a large open-source project, I will no longer be taking general feature requests nor will I be providing support outside of bugs/issues.

This isn't necessarily a change that I want to make, because I like helping people out! However I've easily spent >100 hours providing free support (over email, particularly) for this library over the years, with people that are often either outright rude, waste my time with generic webdev questions they could search on Google, or just want me to develop some feature for their commercial product... for free.

Considering that apparently even a big LED panel manufacturer is willing to use iro.js yet stoop so low as to ask me to develop custom features for them for free (yes, really), I'm deciding that my time will be better spent doing other things.

Thank you for understanding

commented

I can live with your decision to not spend a lot of time in feature requests.
But Github is a place to colaborate with other developers in open source projects.
Maybe you can leave these requests open to other developers, or maybe I will solve this myself and will do a PR for it.
Then it would be nice to keep track of requests/issues right?

If not, even good friends, thanks for this nice piece of code!

commented

I'm picky about features generally speaking, because I really don't want this library to get bloated -- anything added means more stuff that I end up having to maintain in the long-term.

But sure, I'll open it up to see if anyone else wants to contribute it. That seems fair.