[elm-discuss] Re: Cell - simple web framework

Very interesting and minimalistic approach for building web apps. Thanks for sharing, Franček! On Wednesday, 14 June 2017 11:42:24 UTC+1, Franček Prijatelj wrote: > > Hi > > Cell is very simple web framework (no APPI). > > http://www.celljs.org/index.html?hn >

[elm-discuss] Re: How do you name messages?

Why not both? Usually I find myself using the first approach more, especially when I have "actions" coming from the view (e.g. ChangeInput, SubmitForm). However I also use the second approach when I get some value back from a task (e.g. ParsedInput, ReceivedData). On Friday, 21 October 2016

[elm-discuss] Re: Can I use css animations normally in elm?

I think it's worth mentioning your Elm code can be totally independent from any animation done in an external stylesheet. See this style for example: https://github.com/simonewebdesign/elm-double-folding-pattern/blob/a27de84ba14f46f46d4d3878b233dcd32b31d13d/style.css#L357 The animation starts

[elm-discuss] Re: elm-new, a CLI tool for initializing new Elm projects

te-elm-app is pretty cool indeed, however it's also very different from elm new. My tool not only is independent from Node, it also tries to stay unopinionated. I'll write a blog post to explain my view when I have time. On Monday, 8 August 2016 08:11:15 UTC+1, Simone Vittori wrote: > > I

[elm-discuss] Re: Is over-use of 'let... in' considered an anti-pattern?

I agree with everything said, however there's a specific case where I personally try to avoid `let` if possible. Sometimes view functions can be quite big, hence it makes sense to split them into smaller composable functions. So far so good, but as soon as we introduce the `let ... in` block,

[elm-discuss] Re: How to order imports?

At my company we have our own conventions, which are always good to have I think, even though the order doesn't really matter in this case. This is our convention: 1) Core modules; 2) Public modules from elm-lang; 3) Other public modules; 4) Project modules. Anyway I see you mentioned List and

[elm-discuss] Re: Which text editor do you prefer for Elm?

> Any idea how to tell linter-elm-make where to pick up the elm-package.json > from? > Go to linter-elm-make's settings and tick "Always Compile Main". -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and stop

[elm-discuss] Re: Which text editor do you prefer for Elm?

I tried Atom recently, it gets pretty good when you start using the linter-elm-make package. You get inline errors and some other goodies. Anyway I've been a happy Sublime Text user for a long time now. Elm support is quite good too, I used to have

[elm-discuss] elm-new, a CLI tool for initializing new Elm projects

I recently worked on elm-new, a tool for creating a project scaffolding to get started with Elm more easily and quickly. Please check it out: https://github.com/simonewebdesign/elm-new Personally I had the need to do some quick prototyping with Elm, but always having to manually create a

[elm-discuss] Re: Form with union type

Elm <http://elm-lang.org/try>). > Union type was not wrong. The `on` function assumes an event object to be > decoded, but you expect a string. > So I used `targetValue` decoder, which is a shortcut for `e.target.value`. > > > 2016年7月28日木曜日 0時25分46秒 UTC+9 Simone Vittori: >&g

[elm-discuss] Form with union type

I'm building a language selector and I'd like to map the options to a union type. Here's what I tried: import Json.Decode exposing (Decoder, customDecoder, string) {-| Currently supported languages. -} type Language = English | Japanese {-| A JSON decoder of Language. -}