Re: [elm-discuss] Ahead-of-time generation of server-side JSON data to drive client app

For the Haskell option, you may want to take a look at https://github.com/krisajenkins/elm-export and https://github.com/agrafix/elm-bridge. Am Montag, 5. September 2016 schrieb Matt McHenry : > I've just started learning Elm, and am starting to think about how to > structure my first

Re: [elm-discuss] `Uncaught ReferenceError: Elm is not defined` in Electron app

Worked like a charm. Thanks! - Alex On September 5, 2016 at 10:07:18 AM, Leroy Campbell (artison...@gmail.com) wrote: You can require the script (as a CommonJS module). -- You received this message because you are subscribed to a topic in the Google Groups "Elm Discuss" group. To unsubscribe

[elm-discuss] Ahead-of-time generation of server-side JSON data to drive client app

I've just started learning Elm, and am starting to think about how to structure my first application. The app in question is a photo album viewer (in the spirit of http://bins.sautret.org/). The idea is to start with a directory tree of images (on a local FS, served by a plain HTTP server.)

[elm-discuss] `Uncaught ReferenceError: Elm is not defined` in Electron app

Hi all, I am attempting to use Elm 0.17 for an Electron app (using `electron-prebuilt` 1.3.5). However, I've run into a snag where an `Elm is not defined` error raises on launch. For some reason, `Elm` isn't a global variable in Electron. It is global when run in the browser though. Does

Re: [elm-discuss] Please can I have some feedback on my first Elm app, a Github user lookup

Thanks On Sunday, 4 September 2016 20:38:08 UTC+1, Peter Damoc wrote: > > I assume you have already been through the Guide. > > If you haven't read that, please start there: > http://guide.elm-lang.org/ > > > > On Sun, Sep 4, 2016 at 10:31 PM, Rory Smith > wrote: > >> Hi

Re: [elm-discuss] Please can I have some feedback on my first Elm app, a Github user lookup

I assume you have already been through the Guide. If you haven't read that, please start there: http://guide.elm-lang.org/ On Sun, Sep 4, 2016 at 10:31 PM, Rory Smith wrote: > Hi Peter and thanks for your reply. > I am mainly seeking for best practise approaches to my code

Re: [elm-discuss] Re: Nested JSON decoder issue

Oh sweet. I guess that makes sense since := is an infix function. I guess I'm surprised that the compiler didn't say anything. Precedence issues usually end up sending the wrong things to functions in my experience. Anyway, I appreciate the help! -- You received this message because you are

Re: [elm-discuss] Re: Nested JSON decoder issue

It looks like a precedence problem in yer decoders redditJsonResponseDecoder : Decoder RedditJsonResponse redditJsonResponseDecoder = object2 RedditJsonResponse ("kind" := string) ("data" := object1 (\children -> { children = children }) ("children"

[elm-discuss] Re: Nested JSON decoder issue

Any by "array" I mean "list" -- 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+unsubscr...@googlegroups.com. For more options, visit

Re: [elm-discuss] Building a UI component library: the Elm compiler

I may do that --Zach ᐧ On Thu, Sep 1, 2016 at 11:17 PM, OvermindDL1 wrote: > Well get to PR'ing into `elm-mdl`, or make a new one based on `elm-parts` > (which is what `elm-mdl` is built off of)? ^.^ > > > On Thursday, September 1, 2016 at 12:22:31 PM UTC-6, Zachary