As Matthew already said, I think it would be a bad idea to put Color in elm-graphics.
Color is a general concept and very useful also outside elm-graphics. In my 2d game library <https://github.com/Zinggi/elm-2d-game> I'm also making use of Color for drawing colored rectangles. I wouldn't want to add a dependency on elm-graphics! I think it would make sense to either leave it in core or to move it in its own module, e.g. probably to elm-community/color Plus gradient should either be exposed or moved to elm-graphics. On Thursday, 29 September 2016 22:16:30 UTC+2, Nick H wrote: > > Hi everybody, > > Since 0.18 is going to involve some module juggling in core, I thought > this would be a good time to bring this up. > > This is a follow-up to an elm-discuss thread from last month. Robin argued > that the Color module should not be in elm-lang/core. I agreed and > suggested that it be moved to evancz/graphics. > > For me the strongest indicator that Color doesn't belong in core is to > look at who depends on it. Neither of the UI-related elm-lang packages > (html, svg) use it. elm-css and elm-mdl both define their own color types. > > The only library that operates well with Color is evancz/graphics. > Furthermore, it is the only one that can use the entire thing. The Gradient > type is opaque, so it's impossible for anyone but evancz/graphics to use it. > > I hate to suggest "one more thing" to add to the release, but it feels > like low-hanging fruit. I'm sure there is a reason Color stayed behind when > Graphics was extracted. One way or the other, it should be easy to decide. > And if it makes sense to move it, the lack of dependencies means the change > would be easy to implement. > > Thanks for humoring me, > > ~Nick > -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
