Hello! Essentially there are some things I'd like to do that I wouldn't be able to express in elm-css (With this being said, elm-css is super-awesome, and this style-elements library is still experimental). I'm writing an article that goes more into detail but here's a general overview.
First, this library is both about providing a better interface to CSS and sometimes _removing_ parts that generally only exist to cause trouble. If this is just a collection of mixins for elm-css, then the library can't really "remove" a property. Secondly, there's a new version of this library in the works that has a different approach to how we bind a style to an html element. That may seem like there's only one way to do it (via classes), but I have an interesting approach to try out. I'm hoping to have something working by mid-January to show what I mean. Thirdly, I'm planning a sweet integration with elm-style-animation <https://github.com/mdgriffith/elm-style-animation> that can only be done if I, as a library, have complete control over if a style is rendered inline or as a stylesheet. Actually the plan is to dynamically switch between the two based on what the user wants. I really appreciate the interest :) On Monday, January 2, 2017 at 2:58:03 PM UTC-5, Kadzuya OKAMOTO wrote: > > Awesome! I completely agree with the policy to simplify CSS. > > I guess the policy may be also realized by providing a set of functions in > a manner of `rtfeldman/elm-css`'s `Mixin`s. > What is the dominant benefits of making another library rather than > providing set of `rtfeldman/elm-css` `Mixin`s? > > > On Thursday, October 27, 2016 at 10:20:14 PM UTC+9, Matthew Griffith wrote: >> >> >> It's easy to write valid CSS that is still broken and frustrating. What >> if we could make frustrating CSS styles not expressible? >> >> I've been working on an experimental style library for making styles that >> are harder to break and easier to use. >> >> There is also support for flow/flexbox style layouts, animations, >> transitions, and media queries. >> >> It takes a different approach on attaching styles to html nodes. Instead >> of using classes and ids, you create collections of styled html elements to >> pull from to build your view (with support for classList style variations >> that can be turned on/off). >> >> Let me know your thoughts! >> >> Note: I haven't published this on elm-package yet as I wanted to see if >> there was any feedback that might alter what 1.0 looks like. >> >> The Style Elements library <https://github.com/mdgriffith/style-elements> >> >> Simple Example >> <https://github.com/mdgriffith/elm-style-elements-simple-example> >> >> Complex Example >> <https://github.com/mdgriffith/elm-style-elements-complex-example> >> > -- 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.
