[elm-discuss] Re: Trouble initializing input with value

If you type some text, move the cursor back a few characters and then type quickly the cursor will jump to the end. It's an issue that all VDOM implementations have to workaround but as yet Elm doesn't have one. I believe there's an issue open for it somewhere but I wasn't able to track it

[elm-discuss] Re: HIIT sessions?

Many apologies, a sleepy post to the wrong group... On Tuesday, 30 May 2017 11:37:14 UTC+2, Roman Frołow wrote: > > This mailing list is about > https://en.wikipedia.org/wiki/Elm_(programming_language) > > On Tuesday, 30 May 2017 00:28:11 UTC+2, Oliver Searle-Barnes wrote: &

[elm-discuss] HIIT sessions?

Just about to receive my Wahoo Elemnt and am curious if you can setup HIIT sessions? I haven't seen much talk about them so I suspect they aren't supported at the moment. If not is there any intention to add support for HIIT sessions? -- You received this message because you are subscribed to

[elm-discuss] Re: Implementing a protocol on top of WebSocket: should I build a effect module ?

You might find https://github.com/saschatimme/elm-phoenix useful to look at, it's an effects manager phoenix channels built on top of the websocket effects manager. On Tuesday, 16 May 2017 15:30:18 UTC+1, Christophe de Vienne wrote: > > Hi everyone, > > I am attempting to implement the pub/sub

Re: [elm-discuss] Literature reviews repo

That's great! People have been pretty responsive with calls for examples of code from existing projects, would it be worth adding a section to the template? On Monday, 1 May 2017 17:48:48 UTC+2, Max Goldstein wrote: > > Here, I've set up a repo: > >

[elm-discuss] Literature reviews repo

In https://groups.google.com/forum/#!topic/elm-discuss/yHiAJ_wcG3c Max proposes that we put together some literature reviews. If we're to collaborate on this effort we'll need to consolidate our investigations somewhere. Having seen the success of the RFCS repos for Ember

[elm-discuss] Re: Discovery: Model /= Database

The pattern we use is to have our Page.update functions return (model, cmd, storeCmd) the main update then applies the storeCmd to the Store. (the actual code supports a few other things but that's the basic gist of it). Hit me up on slack if you want to chat about it. On Sunday, 30 April

Re: [elm-discuss] Re: Moving on

I've been using Elm for about 10 months now and have had an app in production for the last 2, I share the general feeling of this thread. I've addressed Evan directly here because it's impossible not to when discussing these topics, I hope my thoughts are taken as sincere and full of respect.

Re: [elm-discuss] Resources guiding towards shifting to Functional Thinking

I found this talk really useful coming from an OO background, https://www.youtube.com/watch?v=E8I19uA-wGY=youtu.be=1s. The code examples are in F# but it's an ML based language and the talk is mainly conceptual rather than code heavy. On Wednesday, 26 April 2017 12:44:17 UTC+2, Jiggneshh Gohel

Re: [elm-discuss] Re: Comments on the TEA Components package

You've definitely given me some great advice along the way, I'm very grateful! I feel like this discussion has covered a few different scaling techniques and I feel like there's a good time to use all of them. Perhaps it would be good to just catalogue the different approaches along with some

Re: [elm-discuss] Re: Comments on the TEA Components package

> > > If you have time, would you mind describing how the app works? > This is a fairly high view of our app and how it's architected but hopefully it's a useful level of detail (I've mentioned it a couple of times already but here's a rough gist of the folder/file structure we use

Re: [elm-discuss] Re: Comments on the TEA Components package

Yes we spoke about how the idea of having "sections" within a page that function as independent units. The idea of mini-apps seems to encompass the approach of splitting out the app into Pages and page Sections. I don't have time now but I'll try to put down a description of our app later on

Re: [elm-discuss] Re: Comments on the TEA Components package

> I have not seen the reverse happening. We did spend the first 6 months or so of our project following the advice to not use nested TEA components. Our experience was that the perceived complexity of the app grew exponentially to the point where it was difficult to make progress. We

[elm-discuss] Re: Scaling Elm

That appears to have much in common with our app. It seems useful to compare what people building SPAs are currently doing so here's a rough gist of the folder/file structure that we're using https://gist.github.com/opsb/d0977bcb30b42302f3f2dc3daf0befec. There's a few differences worth pulling

[elm-discuss] Re: Scaling Elm

Now that I think of I remember that Josh Adams has been working on https://github.com/dailydrip/firestorm which is open source and has an Elm client. It's written as an SPA so it may serve as a good subject for this discussion. On Wednesday, 19 April 2017 17:21:04 UTC+2, Marek Fajkus wrote: >

[elm-discuss] Re: Scaling Elm

I think this would be fantastically useful :) I've kept out of discussions regarding architecture as they've been going in circles for the last 6 months or so. An example SPA seems like a great way to move forwards. Something which every SPA I've ever written has included is a Store of some

[elm-discuss] Unsafe mechanism

(prompted by discussion of firebase integration on elm-dev) Given that it would be really helpful to have more integration libraries available for Elm (auth0, firebase, aws...) I've been wondering if the current state of affairs is ideal for achieving: 1) Maximum number of integration

[elm-discuss] Re: Local third-party packages

ng dependencies for) sets a source it will be the one we use >- 1 - packages dependency - if the current package doesn't have >dependency for a package but an other has we use that >- 0 - Github - if no package defines dependency for a package we fall >back to Github &g

[elm-discuss] Re: Local third-party packages

elm-github-install has a separate dependency-sources section which you can use to override the dependency versions. The readme has the following example "dependencies": { "gdotdesign/elm-install-test": "1.0.0 <= v < 2.0.0", "elm-lang/core": "5.0.0 <= v < 6.0.0", "elm-lang/svg":

[elm-discuss] Re: Local third-party packages

elm-install is using the ruby-git gem which supports local git URIs of the form file:///path/to/local/remote.git On Tuesday, 31 January 2017 11:00:13 UTC+1, Rupert Smith wrote: > > On Monday, January 30, 2017 at 6:48:13 AM UTC, Lyle Kopnicky wrote: >> >> What's the best way of referencing

Re: [elm-discuss] Building a Store without boilerplate

les of persistence frameworks with other statically typed languages such as Java and Scala, in those cases introspection is available so solutions tend to lean on those. On Monday, 30 January 2017 12:03:07 UTC+1, Peter Damoc wrote: > > > > On Mon, Jan 30, 2017 at 12:17 PM, Oliver Sea

[elm-discuss] Building a Store without boilerplate

# Building a Store without boilerplate The app that I’ve been building has a Store abstraction which is built on top of elm-phoenix (websockets). Typical methods in the API are: Store.addProject projectAttributes store Store.renameProject projectId name store Store.deleteProject projectId store

Re: [elm-discuss] Re: Pseudo Web Components in Elm

Thank you for putting this together Peter, it's certainly something that I've given more than a little thought to. While I believe that sticking to a flat structure where possible is beneficial there really does seem to be a place for components like text editors, calendars etc. I'll try to

[elm-discuss] Re: Feature: 'where' expressions (continued from GitHub)

As a non haskeller I do find my something constantly wishing that where expressions had been chosen instead if let/in. Let/in leads to a sort of vertigal zig zagging as you need to jump to the bottom then scan backwards for the supporting information. In other languages I've always ordered my

[elm-discuss] Re: Introducing Firestorm - An Elm-powered forum engine built atop Elixir and Phoenix

I thought the concept was great in the first place so I ponied up a while back. I would have gladly paid just for the exploration of webcomponents though, very much looking forward to seeing that :) On Wednesday, 14 December 2016 20:41:05 UTC+1, Josh Adams wrote: > > tl;dr > > DailyDrip is

[elm-discuss] Re: Using flat-file JSON fixtures in elm-test and API tests

This is a slightly different approach to the problem but thought you might be interested to see it, https://github.com/realestate-com-au/pact. On Monday, 12 December 2016 00:16:21 UTC+1, Jan Fornoff wrote: > > Hi everyone! > > I'd like to propose an idea that I've been playing with for a bit. >

[elm-discuss] Re: Any other implementations of elm-test runners besides rtfeldman/node-test-runner?

There's also https://github.com/rtfeldman/html-test-runner (yep, that would be Richard again :) ) On Friday, 2 December 2016 17:24:18 UTC+1, Rupert Smith wrote: > > Any other implementations of elm-test runners besides > rtfeldman/node-test-runner? > -- You received this message because you

[elm-discuss] Documentation on Effects Managers

Hey cloudie, I started a project yesterday for adding optimistic ui on too of elm-phoenix. It's very much a sketch at the moment (although working at least), you can take a look at https://github.com/opsb/elm-optimist/tree/initial-example?files=1. I'm curious what you've got in mind with the

[elm-discuss] Documentation on Effects Managers

Hey cloudie, I started a project yesterday for adding optimistic ui on too of elm-phoenix. It's very much a sketch at the moment (although working at least), you can take a look at https://github.com/opsb/elm-optimist/tree/initial-example?files=1. I'm curious what you've got in mind with the

Re: [elm-discuss] What Elm needs to move forward

I know it's > worth a shot though! > > John > > On Thu, 24 Nov 2016 at 11:34 Oliver Searle-Barnes <oli...@opsb.co.uk > > wrote: > >> I'm definitely still in the process of moving my thinking into a >> functional approach (currently working through Prog

Re: [elm-discuss] What Elm needs to move forward

r even mid-level developers to get going quickly. On Thursday, 24 November 2016 11:00:36 UTC+1, Peter Damoc wrote: > > On Thu, Nov 24, 2016 at 11:17 AM, Oliver Searle-Barnes <oli...@opsb.co.uk > > wrote: > >> The fact remains though that I don't feel I can offer a sound &

Re: [elm-discuss] What Elm needs to move forward

I'm going to touch on a couple of sensitive areas here, hopefully you'll take my comments in the manner they're intended, to try and expose problems that newcomers from other frameworks face so that we can think about how we might improve the situation. I've been using Elm a good portion of

[elm-discuss] Re: Tag new releases in the elm platform repo

This caught me out yesterday, I wanted to have a look at the source for 0.18.0 and was surprised to see that there wasn't a tag for it in github. On Tuesday, 22 November 2016 11:34:53 UTC+1, futtetennista wrote: > > I recently contributed to the docker-elm repo >

Re: [elm-discuss] Rename Just to Something, as the counterpart to Nothing?

he Maybe > type now to understand where it's needed in my app. > > So I'd tend to lean with Joey, the wording works for me and changing it > would feel arbitrary and break the current grammatical 'symmetry' as in > weapon = Just sword > vs > weapon = Something sword > >

Re: [elm-discuss] Rename Just to Something, as the counterpart to Nothing?

I have to admit I did find `Just` very confusing when I first encountered it, as mentioned earlier in this thread it implies some kind of limitation which doesn't match the semantics of Maybe at all. That said, it was one of those little oddities that very quickly become second nature, just

Re: [elm-discuss] Re: Is Elm really wrong?

I'm surprised this hasn't come up already, http://package.elm-lang.org/packages/eeue56/elm-all-dict/latest -- 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

Re: [elm-discuss] Re: How do you test a TEA `update` function?

This is an area I've been a little uncomfortable with. There seems two be a couple of options though: 1) https://github.com/avh4/elm-testable - I haven't used it but it seems that it provides replacement commands that you can run assertions against. This approach seems limited as it only

Re: [elm-discuss] Structure for large Elm apps

@Mark this is a pattern I've been exploring recently. An area that I haven't found a solution to is keeping the view model in sync with the shared models. For instance, let's say I have a view with a list of checkboxes next to each user. The state for the checkboxes would be kept in the view

[elm-discuss] Re: Another case of functions in the model

Have you had a look at (the currently not released) https://github.com/saschatimme/elm-phoenix? Phoenix channels have request/response semantics built in which you can use in elm-phoenix via Phoenix.push - https://github.com/saschatimme/elm-phoenix/blob/master/src/Phoenix.elm#L85. See Push.ok

[elm-discuss] Re: Simple Fade In/Out effect?

Another option, which avoids having to add anything to your model, would be ``` crossFadeTextTo text = Animation.interrupt [ Animation.to [Animation.opacity 0] , Animation.send (DoneFadingOutOldTextPleaseSwitchModelToNewText text) , Animation.to [Animation.opacity 1] ] ``` On

[elm-discuss] Re: Json.Decode list of objects without known fields

You can do this with a Dict but it's a little fiddly because you need to use an ADT to represent the different types of the values import Html import Json.Decode as JD import Dict import String json : String json = """ [{"a": 1, "foo": "bar", "bar": "baz"}, {"a": 2, "foo": "baz", "bar":

[elm-discuss] Re: Syntax suggestion: record property shorthand

While I like the JS style syntax it feels a little early to be optimising out line noise. In particular nested updates don't seem entirely resolved yet, if new syntax were introduced it would be good to be aware of it when deciding whether this optimisation is appropriate. On Sunday, 11

[elm-discuss] Services (with corrected formatting)

*Apologies for the repost, I missed off the formatting in the original post, and as we're using google groups, there's no edit... Hopefully mods can delete the original.* This is following on from the discussion "Private state: A contrived example". It was going to be a reply but it got

[elm-discuss] Services

This is following on from the discussion "Private state: A contrived example". It was going to be a reply but it got rather long and seems like a large enough topic by itself. I'm currently working on a Store service. It's an abstraction over a websocket that provides an API for persisting

Re: [elm-discuss] Private state: A contrived example

Mark, have you considered the approach that Evan took with elm-autocomplete ? Personally, I found this a satisfactory approach to the problem of private state/events, I'd be interested to hear

Re: [elm-discuss] Feature proposal: Html.none

This is something that comes up a lot in the #beginners channel. After seeing Cmd.none and Sub.none people instinctively reach for Html.none for conditionally rendered parts of the view and are surprised when it doesn't exist. Using `text ""` is a great practical solution but Html.none is

Re: [elm-discuss] Installing packages direct from github

8b95bd98e34a0dfb4f721489407> > ). > ​ > > 2016-08-19 14:37 GMT+02:00 Oliver Searle-Barnes <oli...@opsb.co.uk > >: > >> I've recently started using >> https://github.com/gdotdesign/elm-github-install in place of the usual >> package manager. It allows you to instal

[elm-discuss] Installing packages direct from github

I've recently started using https://github.com/gdotdesign/elm-github-install in place of the usual package manager. It allows you to install dependencies direct from github whilst still handling the semantic versioning resolution. Here are some scenarios where this is really helpful 1) Fixing

[elm-discuss] Re: We need a clearer story on architecture

Thanks Richard and Erik for your input, I am taking this all onboard and giving it lots of thought. I think the next step for me is to experiment and refactor my app into a couple of different structures. That should give me a feel for what works well and what doesn't. Thanks again. On

Re: [elm-discuss] Re: Elm UI boilerplate

In my experience every large SPA I've worked on has ended up building a set of it's own components similar to elm-mdl. They've usually been used alongside other components that have been provided by libraries such as elm-mdl but they're still a significant part of the codebase. From this

[elm-discuss] We need a clearer story on architecture

I've been using Elm for about 4 weeks now and having generally been loving it. An area that I'm really having trouble with though is architecture. The basic TEA is a fantastic foundation but the guidelines are really very limited with regards to requirements of a typical SPA. * Components -

Re: [elm-discuss] Re: Design of Large Elm apps

Thanks, this is really practical advice. The first three things you should reach for are, in no particular order: > >1. Splitting view into smaller functions (without reorganizing Model >or update) > > >1. Splitting Model into smaller values (without reorganizing view or >