On Sun, Aug 8, 2010 at 6:10 PM, Andrew Vit <[email protected]> wrote: > Hi Chris, > > I haven't done much new work with Sass lately but I do remember using > the math arithmetic (probably from before the functions were added). > I'll probably have some deprecation warnings to take care of... Not a > big deal I guess, but figuring out the right percentages to avoid > colour shifts might be a bugger. >
Agreed. I don't want to create a barrier to upgrade so we need to think about how to make this relatively painless. Perhaps the deprecation warnings could suggest a functional composition that returns the same value. > > The arithmetic operators like (#ccc - #333) produce a more predictable > output (#999) than lighten() with a percentage. I agree. I often find myself converting an amount of color to percent in my head. I wonder: if we define 1sh (sh = shade) as a #010101 (or #01 in a particular color dimension = 1/256th of a color). Then we could do: lighten(#ccc, 16sh) and this would be equivalent to #ccc + #111 (in the grayscale color space). > Generally it shouldn't > matter what the final hex looks like as long as the actual colour > looks right, but I'm wondering if there's still some value in using > the arithmetic operators to produce absolute colour steps (e.g. "web- > safe" colours). > This makes me wonder if we should have web-safe($color) that would round to the nearest web safe color. Do people even care about "web safe" colors anymore? It's been a while since I have. -Chris -- 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.
