People are coming to Elm from different backgrounds. Some have years of front-end development experience and have grown with the current tools, mastering them as they appeared.
Some, like myself, have very little front-end know how (My main experience was in GUI programming). One of the issues I face when approaching a project in web-dev is that I need to be able to produce a stable deliverable, something I can give to a client. This might be transparent to a person with experience but to a beginner it could be a big hurdle. For example, I learned about vulcanize by reading Fred's makefile. I had to figure out to install it. Playing with Elm is simple when all you need to do is go to elm-lang.org/try , copy&paste some code there and then change some things. After one plays a little bit more, they run into the issue of not having some library installed on elm/try and they need to solve the issue of installing Elm on their system. After that's done and everything hums along with the help of elm-package/elm-reactor, there comes the issue of starting to need functionality that is beyond the elm-platform There comes a point when you start needing to install tools with npm or bower. One starts to need makefiles (like Fred used) or gulp/webpack. Again, this might be transparent to a veteran but to a beginner it might be a big hurdle. Some assistance here would help a lot. What I want is to edit some Elm files and have an experience similar to "elm-make"... one command and I get a deliverable. In order for this to happen, I have to be constrained by the environment, in other words, there needs to be a system I can trust that does all the wiring of the needed tools in the most efficient way. On Wed, Sep 28, 2016 at 8:40 AM, Ossi Hanhinen <[email protected]> wrote: > Peter, what exactly do you mean by this: > > "Now the need is for some kind of structure and way of delivering Elm > products that embed this kind of web-components." > > How do you deliver applications without Web Components? How do you think > using WCs makes it different? > > On Wed, Sep 28, 2016, 01:41 Frederick Yankowski <[email protected]> wrote: > >> I took Peter’s gist as a basis and made a repo out of it: >> https://github.com/fredcy/elm-polymer-calendar >> >> My version uses a small bit of native code to convert the JS Date value >> from the calendar component (sent as a JS event) into an Elm Date value. >> That avoids the kluge I had before using toString and Date.fromString to >> do the conversion (with manual munging of the string necessary in between). >> >> I spent a little time getting it to work in the latest Chrome, Firefox, >> and IE. I also packaged it up into a near-minimal distribution which can be >> seen at https://fredcy.github.io/elm-polymer-calendar/ >> >> >> -- >> 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/8Q2xwRh6UYc/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.
