[elm-discuss] Using extensible records for optional attributes?

2017-08-01 Thread Mike Austin
I'm curious if it's possible to use extensible records for HTML attributes instead of lists of function application such as [id "foo", class "bar"]? I've poked around a bit, but didn't find too much on specifically this. For example, something along the lines of this: let x = anchor { href =

[elm-discuss] elm-tools/parser: how to access intermediate parsed objects downstream in parsing pipeline?

2017-08-01 Thread Dave Doty
The elm-tools/parser documentation recommends using parsing pipelines such as type alias Point = { x : Float, y : Float} point : Parser Pointpoint = succeed Point |. symbol "(" |. spaces |= float |. spaces |. symbol "," |. spaces |= float |. spaces |.

Re: [elm-discuss] Passing whole state to each view function

2017-08-01 Thread Andrew Stoeckley
Hi Mark, feel free to hit me up on Slack sometime to discuss further. My last two messages to this list have had more than one week delay in posting (ignore the timestamp, I'm posting this on Friday July 21), so that might be easier. I discussed these ideas quite a bit with @ilias and he made

Re: [elm-discuss] Best practices for designing models in the Elm Architecture - lean or rich?

2017-08-01 Thread John Bortins
Ha! I just stumbled onto this recently to solve an ugly performance issue and it works great. The cost is a layer of complexity added to the update function. In this way, the intermediate calculations need be done just once per update rather than spread out many times over the view. Well worth

Re: [elm-discuss] Re: Elm.fullscreen is not a function

2017-08-01 Thread Allan Clark
Also new to Elm so I may be wrong, but assuming your program is defined in the module 'Main.elm' I think you want: Elm.Main.fullscreen(); On 7 July 2017 at 21:38, Denis Kolodin wrote: > Another reason for 0.18: I take `Elm.MyApp.fullscreen is not a function` > when I

[elm-discuss] Re: Separating model state structure from the view hierarchy

2017-08-01 Thread ajs
I got plenty of discussion on this in Slack while this was awaiting moderation for a week or so; I don't think there is need to get into it again. I'm comfortable with the feedback I got there. Thanks for all the input and (spirited) talks about this! :) On Friday, July 21, 2017 at 3:55:42 PM