Named colors? about one-color HOT 6 CLOSED

The only thing that has kept us from adding the list of standard CSS colors is that it would add precious kilobytes to the library. Maybe it could be in some kind of plugin and there could be a one-color-thefullmonty.js build?

from one-color.

I tried snatching the named color list from https://github.com/matthewbj/Colors/blob/master/colors.js and added it as an optional module. It adds 3430 bytes (1422 gzipped).

I pushed the code to the namedcolors branch. Now there's both a one-color.js and a one-color-all.js plus separate -debug versions.

Now you can go one.color('maroon').red(.4).hue(.6).

@Munter, please review.

from one-color.

"Maybe it could be in some kind of plugin" Yes, that is fare. It's just that without it doing things like parsing real-life web page CSS is not complete.

For https://github.com/willowsystems/jSignature we needed code that detects the colors from parent elem and computes mid-shades (between background and pen color) for decor like signature line.

Had to roll our own color parsing logic at the time and chose to ignore the named colors (just pick some grey for decor). My fingers are itching to roll in one-color + named colors as you seems to support HSL-based manipulation.

from one-color.

You can use canvas for browsers which support it to get the value as an rgb @papandreou

https://gist.github.com/1929015

from one-color.

@minikomi Thats a very neat idea. I think we'll need to keep it to the hardcoded list so far to be sure that we have universal browser support, at least for the default packages.
I can write it as a plugin which you can combine with the base class though, so the website author has the option to choose using the smaller canvas based variant :)

from one-color.

Added the named colors support in 2.1.0. It's part of the node.js package, but in the browser you need to use the one-color-all.js build.

from one-color.