[elm-discuss] Re: Announcing elm-lang/navigation for "routing in single-page apps"

AFAIK There isn't any circularity problem where you consider browser location as the reference, push changes to it through history API and let it flow from here through your app. Le jeudi 26 mai 2016 06:59:05 UTC+2, Ryan Rempel a écrit : > > Ah, it is good to know that, in the transition from

[elm-discuss] Re: Announcing elm-lang/navigation for "routing in single-page apps"

Ah, it is good to know that, in the transition from signals to subscriptions, our old friend, the initial value, has not ceased to be special! -- Ryan Rempel -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this group and

Re: [elm-discuss] Re: what's the preferred way to implement the submit mentioned in elm guide?

Looks a lot better to me, nice and testable too ! - You could consider having Error as a generic tag and let it take a String. That way you could populate with an error message in your validate function. That would make the viewValidation function slightly simpler. Btw you probably don't

[elm-discuss] Re: Announcing elm-lang/navigation for "routing in single-page apps"

Tx for this ! The final piece I've been waiting for before upgrading one of my apps. I think I'll go ahead and rip out the existing router package I'm using (which has served me well enough btw) and see if I can't manage fine with just these two building block. shame it's 01:30 over here,

[elm-discuss] Announcing elm-lang/navigation for "routing in single-page apps"

On Friday, Noah and I worked on "updating elm-history" so that folks can do "routing" with Elm 0.17. The results are these libraries: - elm-lang/navigation - evancz/url-parser

[elm-discuss] Re: proof of concept share/import feature for elm-lang.org/try

FWIW, I'd definitely want such feature. I think it is really useful for my use cases (schools and such). On Wednesday, May 25, 2016 at 11:29:21 AM UTC-5, Matteo Bertini wrote: > > I have a proof of concept share/import feature for elm-lang.org/try > > It uses the location.hash trick as in

Re: [elm-discuss] Nested components and async JS via ports

I have something like type Msg = ParentMsg Id Child.Msg My data is in Dicts and my views look like Dict.map \i v -> Child.view v |> Html.map (ParentMsg i) On Wednesday, 25 May 2016 15:05:34 UTC+2, Erik Simmler wrote: I have a rather gross implementation of what I'm hoping to achieve. I

[elm-discuss] proof of concept share/import feature for elm-lang.org/try

I have a proof of concept share/import feature for elm-lang.org/try It uses the location.hash trick as in play.rust, was so simple I'm now thinking that this is perhaps an unwanted feature. Here is the patch:

Re: [elm-discuss] Trigger child action from parent

There are two basic patterns that I've seen: You keep the child oblivious to parent actions and just extend the update signature to signify that it sends something upstream update : Msg -> Model -> (Model, Cmd Msg, Upstream) Here is an example of this:

Re: [elm-discuss] Accessing Elm Reactor on EC2

Another approach could be to use SSH port forwarding, like: ssh -L localhost:8000:localhost:8000 youru...@your.ec2.host and access elm-reactor at http://localhost:8000 on your machine, while the above ssh session is up. This has the advantage of not exposing elm-reactor to the world, and it

Re: [elm-discuss] Accessing Elm Reactor on EC2

Thanks so much Matt! On Wednesday, 25 May 2016 18:58:23 UTC+10, Matt Bray wrote: > > Two things: > > * Ask elm-reactor to bind to all addresses, not just localhost, using > "elm-reactor -a 0.0.0.0". > * On EC2, for your instance's security group, make sure there is a rule > allowing inbound TCP

Re: [elm-discuss] Accessing Elm Reactor on EC2

Two things: * Ask elm-reactor to bind to all addresses, not just localhost, using "elm-reactor -a 0.0.0.0". * On EC2, for your instance's security group, make sure there is a rule allowing inbound TCP traffic on port 8000. Note that you incur the (small?) risk of someone exploiting an unknown

Re: [elm-discuss] Making new Cmds

That worked, thanks. I guess I should hold off telling people stuff. Wil On Wednesday, May 25, 2016 at 12:00:48 AM UTC-7, Janis Voigtländer wrote: > > Task.perform never identity (Task.succeed NewMsg) > > with never from > http://package.elm-lang.org/packages/elm-community/basics-extra > ​ > >

Re: [elm-discuss] Elm 0.16 access

Hi Mark, Elm is in development and minor releases can still break things in a big way. This is what happened with the switch from 0.16 to 0.17. This release got rid of Signals which have been with Elm since its conception. Lua's development is in a different stage where you can do minor releases