Sean's elm-style is the successor of the elm package inspired by that presentation:
http://package.elm-lang.org/packages/seanhess/elm-style/1.0.1/ On Thu, Jun 2, 2016 at 4:43 PM, Yosuke Torii <[email protected]> wrote: > I'm from the first group but on the way of experimenting inline style > inspired by "CSS in JS" from React community :) > > > 2016-06-02 21:18 GMT+09:00 Peter Damoc <[email protected]>: > >> I'm actually from the third group and I'm primed to be the most >> dissatisfied. >> I come from traditional GUI programming. ;) >> >> >> >> On Thu, Jun 2, 2016 at 12:55 PM, Tim Stewart <[email protected]> >> wrote: >> >>> I see your point Peter, I think it depends on where you're coming from. >>> I get the impression Elm draws interest from two groups - those with a >>> front-end web-dev background interested in an alternative to the prevailing >>> view that "the answer to the problems in JavaScript is ... more JavaScript" >>> (ES6/ES7/JSX...) and those from a functional programming background >>> interested in how functional principals are being applied in a new language >>> and environment. Probably the former are glad to be able to leverage >>> existing assets (stylesheets) and skills on the styling front while the >>> latter are keen to explore how things can be done better using functional >>> principles. It's great to have both options. >>> >>> On Thursday, June 2, 2016 at 7:35:52 PM UTC+10, Peter Damoc wrote: >>>> >>>> I understand how using Elm for CSS might look like a case of "I've got >>>> a hammer..." and the external CSS has its merits, especially when it comes >>>> to transitioning from a traditional HTML+CSS+JS to Elm. >>>> >>>> CSS in Elm comes with its own set of advantages and, in the long run, I >>>> think it might be a way better option. >>>> It can use types to make sure that changes to IDs or Classes are >>>> consistent throughout. Named values can make for an additional line of >>>> defense against typos. >>>> It has way better composition and much more flexibility due tot the >>>> fact that one can create style on the fly based on information from the >>>> environment (e.g. device size and/or DPI). >>>> >>>> >>>> >>>> >>>> >>>> On Thu, Jun 2, 2016 at 11:30 AM, Tim Stewart <[email protected]> >>>> wrote: >>>> >>>>> Ondrej's approach makes sense to me too. The advantages Elm brings to >>>>> the table - ensuring program validity, eliminating runtime errors and >>>>> issues related to mutable state etc. - just aren't really problems in CSS. >>>>> The shortcomings that CSS does have are mainly addressed by LESS, it's >>>>> quick and easy to iterate by copying styling experiments in the browser >>>>> directly back to source, and I'm guessing it's a smoother workflow when >>>>> collaborating with designers, embedding into existing sites etc. Using Elm >>>>> for CSS seems to me a bit like a case of "I've got a hammer...". >>>>> >>>>> >>>>> On Thursday, June 2, 2016 at 4:48:35 AM UTC+10, Ondřej Žára wrote: >>>>>> >>>>>> I used Elm.embed, static <link rel="stylesheet"> in my parent >>>>>> document and (obviously) an external stylesheet, preferrably using a Less >>>>>> preprocessor. >>>>>> >>>>>> O. >>>>>> >>>>>> On Tuesday, May 31, 2016 at 11:26:37 AM UTC+2, Peter Damoc wrote: >>>>>>> >>>>>>> How do you handle styling in your Elm programs? >>>>>>> >>>>>>> Do you use one of the following libraries? >>>>>>> >>>>>>> rtfeldman/elm-css >>>>>>> >>>>>>> seanhess/elm-style >>>>>>> >>>>>>> massung/elm-css >>>>>>> >>>>>>> Or do you do something completely different (manual style inlining, >>>>>>> classes and external css) ? >>>>>>> >>>>>>> I tried using Sean's library but I quickly ran into pseudo-selectors >>>>>>> trouble wanting to implement a simple hover effect. >>>>>>> >>>>>>> Somehow, keeping a set of hover states for some simple nav-link >>>>>>> seams such an overkill. >>>>>>> >>>>>>> How do you handle such scenarios? >>>>>>> >>>>>>> >>>>>>> >>>>>>> -- >>>>>>> There is NO FATE, we are the creators. >>>>>>> blog: http://damoc.ro/ >>>>>>> >>>>>> -- >>>>> 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. >>>>> >>>> >>>> >>>> >>>> -- >>>> There is NO FATE, we are the creators. >>>> blog: http://damoc.ro/ >>>> >>> -- >>> 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. >>> >> >> >> >> -- >> There is NO FATE, we are the creators. >> blog: http://damoc.ro/ >> >> -- >> You received this message because you are subscribed to a topic in the >> Google Groups "Elm Discuss" group. >> To unsubscribe from this topic, visit >> https://groups.google.com/d/topic/elm-discuss/AC6cqdeKDOs/unsubscribe. >> To unsubscribe from this group and all its topics, send an email to >> [email protected]. >> For more options, visit https://groups.google.com/d/optout. >> > > -- > 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. > -- There is NO FATE, we are the creators. blog: http://damoc.ro/ -- 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.
