Re: [elm-discuss] Listening to messages from different modules on an update

There used to be a "nesting" set of examples in The Elm Architecture but lately this approach has been discouraged. What you describe here is a kind of decomposition into components. It is recommended that you have one model and you decompose the functionality of update & view using regular

[elm-discuss] New implementation of elm arrays available on elm-package

Version 1.0.0 of the new elm array implementation is now available on elm-package. If you have elm 0.18 you can easily try it out by doing the following: 1) install the package with `elm package install Skinney/elm-array-exploration` 2) Use the correct namespace, `import Array.Hamt as Array`

[elm-discuss] elm-http-builder 4.0.0

Hi friends! I published elm-http-builder 4.0.0 just now for 0.18 There are a bunch of changes so I'm sharing the release notes below. Any longer-form concerns, share them here. If you'd like direct help, jump into the #http channel in slack . Thanks! Luke

Re: [elm-discuss] Anyone using Firebase 3.0 with Elm 0.17?

I would also be happy to test and contribute to an Elm 0.18 update to ElmFire. On Sunday, October 23, 2016 at 6:14:13 PM UTC-7, Scott Mueller wrote: > > Just a friendly bump and vote for Elm 0.18 and Firebase 3.0 support... > Also happy to help with this. > > On Wednesday, August 17, 2016 at

[elm-discuss] Re: What do you think about Eve?

The literate programming part and IDE seem pretty compelling. However the language itself looks to be another imperative, mutation -based language. The language is pretty brilliant. It's really a database programming model, but the "database" also allows

[elm-discuss] What do you think about Eve?

I wonder, what the elm community thinks about Eve: http://witheve.com/ ? Here is the syntax reference: https://witheve.github.io/assets/docs/SyntaxReference.pdf I think that this language/architecture is worth to look at. It has many similarities with elm. But it is more like logic programming.

Re: [elm-discuss] Re: Why Range syntax got removed in favor of List.range

It's also worth mentioning that adding syntax for something usually indicates that it's a "core" feature. In C-like languages, looping from integers in a range is the key iteration structure. But in Elm, fold and map are much more important. So having special syntax could give beginners the idea

Re: [elm-discuss] Re: Why Range syntax got removed in favor of List.range

Yup. It is just not used often enough to warrant special syntax. On Tue, Nov 15, 2016 at 10:09 AM, Witold Szczerba wrote: > I think List.range is just fine. No need for special syntax and strange > function names like ".." (hard to browse, find online, etc.). > > On Mon,

Re: [elm-discuss] Re: Why Range syntax got removed in favor of List.range

I think List.range is just fine. No need for special syntax and strange function names like ".." (hard to browse, find online, etc.). On Mon, Nov 14, 2016 at 10:29 PM, أحمد حبنكة wrote: > What do you think about my suggestion in previous reply ? replacing > List.range

Re: [elm-discuss] Re: Why Range syntax got removed in favor of List.range

What do you think about my suggestion in previous reply ? replacing List.range with List.(..) operator ? بتاريخ الاثنين، 14 نوفمبر، 2016 2:43:49 ص UTC+2، كتب Max Goldstein: > > Sometimes it's useful to pass arguments to List.range and have it be empty > when a > b. > > Perhaps there should be

[elm-discuss] Re: Why Range syntax got removed in favor of List.range

hmmm I agree, if we want to make it a function though then we can replace the `List.range` function with `..` operator and construct ranges like this `1..2` (no need for brackets) This is how it's done in ruby and it's a function :) , the range syntax removal is acceptable in this situation

Re: [elm-discuss] Re: How to decode a recursive JSON from a port?

I had to do this myself recently. The general solution is that for any recursive definition you have to have a lambda between the definition and it's use. Your example 1 does this in the decoder with the call to `lazy`. Example 2 doesn't, so it fails. I've heard (but haven't checked) that the

[elm-discuss] 0.18 Below the Hood

Can anyone add to the headline features in the blog? *http://elm-lang.org/blog/the-perfect-bug-report * Just want to geek out, but too lazy to follow / look at Elm dev. Happy Elm Day. -- You received this message because you are subscribed to

Re: [elm-discuss] Re: Update Delay

Simplifying is a wonderful way to bug-hunt, one of my go-to methods. :-) On Sunday, November 13, 2016 at 2:28:00 PM UTC-7, John Orford wrote: > > My mistake! I was querying the previous list of strings rather than the > updated one. Good exercise though, simplifying helped me find the bug > On

Re: [elm-discuss] How are you handling images references in Elm with Webpack?

We solved this recently! You can checkout the loader here -> https://github.com/NoRedInk/elm-assets-loader The code lives in index.js. It's currently not fully released yet, but some docs live here -> https://github.com/NoRedInk/elm-assets-loader/blob/master/index.js#L3 On Mon, Nov 14, 2016 at

[elm-discuss] Re: Convincing my team that Elm isn't just going to die like CoffeeScript

The comments here are great! There are even more in a previous thread on the topic: https://groups.google.com/d/msg/elm-discuss/BnvrQt0LIN4/GHE5HVMEAAAJ On Saturday, November 5, 2016 at 5:01:42 PM UTC-5, Zacqary Adam Xeper wrote: > > Hey Elmos, > > I've finally gotten an opportunity to pitch

Re: [elm-discuss] Re: Correct use of port subscriptions in a submodule reused multiple times?

Op maandag 14 november 2016 02:24:16 UTC+1 schreef Witold Szczerba: > > Can you provide some real-life example of "moving away from components"? > That could be helpful… > Sure. My background is in React, where everything there is components too. No examples of my own to share just yet. My app