HSL is an interesting way of specifying color in a device independent way. It feels more natural to some than does RGB. Every color your monitor can represent can be specified using RGB; it's the "hmmm, I'd like to see that a bit more saturated" or "not quite so orange" type of change that make HSL convenient. Read this:
"HSL color values refer to hue-saturation-lightness numerical codes for colors. They were added to solve some specific problems with RGB colors: RGB is hardware-oriented. It references CRTs and assumes that color model for displaying the colors. Most professional printers are not RGB based, but CMYK and the translation from screen to print is not always good. RGB is non-intuitive. In other words, most people think of colors in reference to the hue (red versus yellow), saturation (grey versus red), or lightness (dark red to red to pink) but RGB forces you to put the colors in a machine-generated way. Red in HSL would be written: hsl(0,100%,50%); HSL also has an alphavalue notation - HSLA - which allows you to specify opacity with this color notation just like RGBA. HSL is not supported by most browsers, so it's a good idea to just remember this notation for the future"[1] [1] http://webdesign.about.com/od/color/a/aa051407.htm On Jun 18, 2007, at 12:42 AM, [EMAIL PROTECTED] wrote: > > Correct me if im wrong,but doesnt adding an equal amount of RGB make > the colour brighter? eg. > :background-color = !base_color + #151515 > or > :background-color = !base_color + #323232 > > On Jun 17, 12:27 am, rebo <[EMAIL PROTECTED]> wrote: >> Just want to say thanks for taking this suggestion seriously, >> i think its an excellent opportunity to extend the abilities of css >> but at the same time allowing it to work in all browsers. >> >> On Jun 15, 4:50 am, Nathan Weizenbaum <[EMAIL PROTECTED]> wrote: >> >>> There are several reasons for keeping functions out of normal >>> CSS. The >>> first is that it becomes much, much easier to parse; we don't >>> have to >>> think about the content of the attributes at all. This is a good >>> thing. >>> A slightly less Nathan-is-lazy reason is that CSS3 defines a lot >>> more >>> function-like things, including stuff like hsl, and I don't want to >>> interfere with that at all. >> >>> - Nathan >> >>> s.ross wrote: >>>> I think you're right about the undefined functions evaluating to >>>> CSS. >>>> That seems like a cool way to treat it. Also, would it be >>>> desirable to >>>> use the quoted form to explicitly coerce something into CSS? >> >>>> Is there a particular reason not to allow functions as an >>>> attribute? I >>>> certainly prefer specifying colors as constants in a block at >>>> the top >>>> of my Sass, but a CSS person might expect that functions would be >>>> available in that context. >> >>>> Steve > > > > Steve Ross [EMAIL PROTECTED] http://www.calicowebdev.com --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Haml" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/haml?hl=en -~----------~----~----~----~------~----~------~--~---
