Re: [elm-discuss] Cmd.map

If you have a series of pages that each has Cmds and you have these pages unified under one app, you need to lift each page Cmd to become an app Cmd. There used to be a nesting architecture where this was demonstrated but now that's been dropped in favor of the Config approach. On Wed, Mar 29,

Re: [elm-discuss] Debugger becomes useless with time and mouse movement events

> > All my messages are wrapped and appear the same at the top-level; the > filter is not sophisticated enough to deal with that. Yeah, I've discovered the same problem. My main module only has one subcomponent and all the relevant messages are wrapped in it's Msg. I would think that's a very

[elm-discuss] Cmd.map

I’m having trouble thinking of a scenario in which you’d use `Cmd.map`. Is it for a case where you create a `Cmd a` where `a` is something different than the usual `Msg`, then transform it into a `Msg`? (When would you do such a thing?) Or for a case where you want to change the `Msg`

[elm-discuss] Re: Elm webcomponents for microservice front-end

On Tuesday, March 28, 2017 at 4:56:53 PM UTC+1, Charles-Edouard Cady wrote: > > The Gruntfile is pretty scary! That's really the thing with webcomponents > I think: the boilerplate is quite huge... > A lot of it is not really needed for this demo, it just got cut and pasted across from some

[elm-discuss] Re: Help with Jupyter/IPython notebook kernel for Elm

Klipse looks interesting, but I'm hoping to use Jupyter to make a presentation so I'm going to stick with that for now. Regarding Jupyter needing a server: there are places that host notebooks, so the server requirement is only partly true. Your point is a good one, though. Sometime the

[elm-discuss] Re: Elm webcomponents for microservice front-end

The Gruntfile is pretty scary! That's really the thing with webcomponents I think: the boilerplate is quite huge... On Tuesday, March 28, 2017 at 5:50:13 PM UTC+2, Rupert Smith wrote: > > On Tuesday, March 28, 2017 at 2:04:22 PM UTC+1, Charles-Edouard Cady wrote: >> >> I tried your application

[elm-discuss] Re: Elm webcomponents for microservice front-end

Wonderful! It works! Nice & green! On Tuesday, March 28, 2017 at 5:50:13 PM UTC+2, Rupert Smith wrote: > > On Tuesday, March 28, 2017 at 2:04:22 PM UTC+1, Charles-Edouard Cady wrote: >> >> I tried your application on Iceweasel. The checkboxes never get checked, >> but opening the Javascript

[elm-discuss] Re: Elm webcomponents for microservice front-end

On Tuesday, March 28, 2017 at 2:04:22 PM UTC+1, Charles-Edouard Cady wrote: > > I tried your application on Iceweasel. The checkboxes never get checked, > but opening the Javascript console I can see the messages are getting > through: > > "Main: SelectChanged (Dict.fromList

[elm-discuss] Re: Elm webcomponents for microservice front-end

There's a polyfill for non-chrome browsers: https://github.com/WebComponents/webcomponentsjs Haven't tested it with your code though. On Tuesday, March 28, 2017 at 5:45:49 PM UTC+2, Rupert Smith wrote: > > On Tuesday, March 28, 2017 at 2:04:22 PM UTC+1, Charles-Edouard Cady wrote: >> >> I

[elm-discuss] Re: Elm webcomponents for microservice front-end

On Tuesday, March 28, 2017 at 2:04:22 PM UTC+1, Charles-Edouard Cady wrote: > > I tried your application on Iceweasel. The checkboxes never get checked, > but opening the Javascript console I can see the messages are getting > through: > > "Main: SelectChanged (Dict.fromList

[elm-discuss] Re: Help with Jupyter/IPython notebook kernel for Elm

Hi Austin, I like Jupyter/iPython a lot as a concept. I did not use it a lot though. And Elm seems to be like a natural fit. My dream would be to have live aka. living documents where static text and live code are intermingled. Jupyter is a step in the right direction. But, you still need a

Re: [elm-discuss] Re: Help with Jupyter/IPython notebook kernel for Elm

If you join the https://elmlang.slack.com and join #elm-dev, I can help you out (eeue56) On Tue, Mar 28, 2017 at 4:53 PM, Berry Groenendijk wrote: > Hi Austin, > > I like Jupyter/iPython a lot as a concept. I did not use it a lot though. > And Elm seems to be like a

[elm-discuss] Re: Got runtime error with nested json decoders

I've created a post about this decoder problem, I hope it helps other people: https://medium.com/@adrian_ribao/recursive-decoders-on-elm-to-manage-server-side-validation-errors-82bee47cc38c El lunes, 27 de marzo de 2017, 12:37:38 (UTC+2), Adrian Ribao escribió: > > Hello, > > I'm creating a

[elm-discuss] Re: Elm webcomponents for microservice front-end

I tried your application on Iceweasel. The checkboxes never get checked, but opening the Javascript console I can see the messages are getting through: "Main: SelectChanged (Dict.fromList [("1","one"),("2","two")])" wood.js:907:2 "_itemsChanged : newValue = 1,one,2,two,3,three, oldValue =

[elm-discuss] Re: Elm webcomponents for microservice front-end

Thanks a lot, that's exactly what I was looking for! For my application, the webcomponents' state will be concatenated & sent to a server for evaluation, because the server needs the state of all webcomponents to perform that evaluation. What I'll do is ask the webcomponent to generate a JSON on

[elm-discuss] Re: Elm webcomponents for microservice front-end

On Tuesday, March 28, 2017 at 10:21:02 AM UTC+1, Rupert Smith wrote: > > On Tuesday, March 28, 2017 at 7:26:37 AM UTC+1, Charles-Edouard Cady wrote: >> >> (2) the ability to write webcomponents in Elm. >> >> I'm not too sure about number 2: what I've seen in the list so far is >> mainly interest

[elm-discuss] Re: Elm webcomponents for microservice front-end

On Tuesday, March 28, 2017 at 7:26:37 AM UTC+1, Charles-Edouard Cady wrote: > > (2) the ability to write webcomponents in Elm. > > I'm not too sure about number 2: what I've seen in the list so far is > mainly interest in using webcomponents but not so much in writing them. > Does anybody have

Re: [elm-discuss] Re: To wrap or not to wrap

On Tuesday, March 28, 2017 at 10:15:42 AM UTC+1, Rupert Smith wrote: > > -- API > > computeIt : Model -> Model > computeIt (Wrapped impl) = > computeItImpl impl |> Impl > > Should have been: computeIt : Model -> Model computeIt (Wrapped impl) = computeItImpl impl |> Wrapped -- You received

Re: [elm-discuss] Re: To wrap or not to wrap

On Tuesday, March 28, 2017 at 3:31:34 AM UTC+1, Mark Hamburg wrote: > > A lot of the code I've written that has dealt with wrapped models has used > the `as` keyword but I've found that it makes the code harder to follow > because the pieces working with the unwrapped model are mixed with the >

Re: [elm-discuss] Elm webcomponents for microservice front-end

My suggestion is to create a playground to explore this approach and proceed with the actual implementation only after you get the details right. There are so many ways that this can break that have nothing to do with Elm. On Tue, Mar 28, 2017 at 11:19 AM, Charles-Edouard Cady <

[elm-discuss] Re: Help with Jupyter/IPython notebook kernel for Elm

FWIW, I see that when the generated javascript is passed back to the Jupyter client, the client calls eval() on the javascript. This seems to work OK, insofar as it doesn't throw an exception. However - and this is where I'm a bit out of my depth - none of the bindings made in the javascript

Re: [elm-discuss] Elm webcomponents for microservice front-end

On Tue, Mar 28, 2017 at 9:26 AM, Charles-Edouard Cady < charlesedouardc...@gmail.com> wrote: > I'm composing a single-page application from several microservices > back-ends. Each back-end should render a part of the page. > > Right now I'm considering using webcomponents: > > - main page is in

[elm-discuss] Debugger becomes useless with time and mouse movement events

Here's some more context: https://groups.google.com/forum/m/?source=mog=us#!topic/elm-dev/cn5EPjyF1uU -- 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

[elm-discuss] Elm webcomponents for microservice front-end

I'm composing a single-page application from several microservices back-ends. Each back-end should render a part of the page. Right now I'm considering using webcomponents: - main page is in Elm and subscribes to a websocket giving it the list of microservices it can get webcomponents from -