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

I think we are only differing on the details. We could use talks / blogposts on all of those things. If you want to write a guest blogpost on any of the above I would be happy to put it on my blog. Zach On Thu, Nov 24, 2016 at 9:31 AM, Peter Damoc wrote: > I beg to differ. >

[elm-discuss] What Elm needs to move forward

I've seen a short blogpost by Zach http://get-finch.com/2016/11/23/what_elm_needs_to_to_move_forward.html and it got me curious. What do the rest of you think Elm needs to move forward faster? (it is already moving forward and will continue to do so but... maybe some things can accelerate the

Re: [elm-discuss] Re: Structure for multiple small "apps" when using Elm with webpack (elm-webpack-loader)

At NoRedInk, we use a single elm code base with multiple entry points for each different page with a unique elm app. This is ideal in terms of build time and reliabitly, as everything can be built and once and share a single lot of packages. We also use the webpack loader for this style of app

[elm-discuss] Re: Structure for multiple small "apps" when using Elm with webpack (elm-webpack-loader)

I would just keep everything in one Elm app, then use a router to display the correct page. When it comes to google closure, Elm only works with SimpleOptimizations. There are two-three lines in the runtime which causes problems with AdvancedOptimizations. In any case, the difference between

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

It didn't take any adaptation that I recall to get used to Just and Nothing. In fact, I probably made more errors on Nothing. But if there were a real move to rename the cases to be more "friendly" — which I doubt — then I will offer the colloquially friendly: Maybe a = Yep a | Nope Yes/No

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

*Thing a | Nothing *is also my favourite between the proposed ones. If the type label is thought of as an adjactive, like for example, in type *Entry* = *Male Person* *| Female Person * then *Just* makes more sense. However, my observation is that these type labels are more often named after

[elm-discuss] Re: Using Navigation - is Events.onWithOptions required?

Op woensdag 23 november 2016 23:52:54 UTC+1 schreef Brian Marick: > > So I suspect I’m doing something wrong. Am I? > Not wrong, I guess, but it is kind of a peculiar setup. I also use elm-lang/navigation, and never ran into this issue. After checking my code: - Either I use an `a [ href

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

The fact that you have to have a way of making sense of it is exactly my point. I think if it was Thing a | Nothing you wouldn’t have to do this to understand it. > On 23 Nov 2016, at 22:01, Erkal Selman wrote: > > I don't have a strong opinion about this issue, but

Re: [elm-discuss] What ways are there of running Elm server side?

On Wednesday, November 23, 2016 at 9:44:05 PM UTC, Rupert Smith wrote: > > Thanks man, that sounds interesting. There doesn't appear to be a huge > amount of javascript involved, so I guess that makes it fairly portable as > to which javascript engine it can be run on? > I've got used to

Re: [elm-discuss] What ways are there of running Elm server side?

On Wednesday, November 23, 2016 at 9:35:21 PM UTC, Noah Hall wrote: > > The canoncial server-side Elm example is the take-home, > https://github.com/noredink/take-home, written by me. AFAIK it is > still the only full stack-Elm application. It also lists good reasons > as to not take that

Re: [elm-discuss] What ways are there of running Elm server side?

The canoncial server-side Elm example is the take-home, https://github.com/noredink/take-home, written by me. AFAIK it is still the only full stack-Elm application. It also lists good reasons as to not take that approach and why it should be avoided at all costs. If you want to render code on the

[elm-discuss] How to structure the code for a PersonSection widget?

Hey guys! 8-) I’m playing with an app for bailiffs. For the data entry UI I need a PersonSection widget to enter the data for a party that participates in a case. So a person can be either an individual or a company, so I’m imagining this as: a “Person type” dropdown + a set of

[elm-discuss] Re: Structure for multiple small "apps" when using Elm with webpack (elm-webpack-loader)

For the posterity, I implemented said "architecture" in one of my side projects. https://github.com/ravicious/rails-elm-forms/commit/b5ac6964f The only difference from what I said above is that the Elm apps don't have their own entry points in the webpack config. Instead, the entry points are

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

:) On Wednesday, November 23, 2016 at 10:59:24 AM UTC-7, Rex van der Spuy wrote: > > > > On Wednesday, November 23, 2016 at 12:15:50 PM UTC-5, Daniel Walker wrote: >> >> My opinion on this isn't nothing, it's just that just makes the most >> sense. >> > > Maybe. > > -- You received this

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

On Wednesday, November 23, 2016 at 12:15:50 PM UTC-5, Daniel Walker wrote: > > My opinion on this isn't nothing, it's just that just makes the most sense. > Maybe. -- You received this message because you are subscribed to the Google Groups "Elm Discuss" group. To unsubscribe from this

Re: [elm-discuss] Proposed addition for Task package

I'm definately with Wouter on this one. Using tasks to do something that isn't a side-effect sounds much more like a code smell than using plain old function calls and function return values to compose your logic (when that is possible, which I would imagine would be true most of the time, if

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

My opinion on this isn't nothing, it's just that just makes the most sense. On Tuesday, November 22, 2016 at 6:11:31 PM UTC-7, Nick H wrote: > > OK, here are the suggestions so far: > > type Maybe a = ... > > Nothing | Just a > Nothing | Something a > None | Some a > NoValue | Some a > Nothing |

[elm-discuss] Re: Tell me how to teach Web Apps

I agree - 100% JavaScript (node on the backend) if finding jobs is important. I would stay away from TypeScript in an introductory course because it's important for students to learn how to problem-solve the deficiencies of working in raw JS. -- You received this message because you are

[elm-discuss] Re: Proposed addition for Task package

Seems like these could all be handled in state. ``` type DataStatus = IsFetching | IsUpdating | IsCreating | IsDeleting type Page = Login | SomeOtherPage -- etc... Then you update your model with these type alias Model = { currentPage : Page , dataStatus :

Re: [elm-discuss] Re: Dynamic Unsubscribing to subscriptions?

Brilliant - I always kind of wondered what the model was there for ... now I know! On 23 November 2016 at 10:07, Wouter In t Velt wrote: > Your subscriptions also take model as input, so you could do something > like this: > > subscriptions : Model -> Sub Msg >

Re: [elm-discuss] Re: Unpublishing a package

On Tuesday, November 22, 2016 at 8:32:46 PM UTC, Martin DeMello wrote: > > It's not a question of being antisocial or uncivilised; it's that it is > really hard to say "I just want to patch this for 0.18 and continue using > it in my project" without having globally visible effects. It is >

[elm-discuss] Re: Dynamic Unsubscribing to subscriptions?

Your subscriptions also take model as input, so you could do something like this: subscriptions : Model -> Sub Msg subscriptions model = if model.followMouse then Mouse.moves MyMsg else Sub.none You could look at the drag-and-drop example elm-lang.org examples to see how

[elm-discuss] Dynamic Unsubscribing to subscriptions?

In the Mouse library we have: moves : ( Position -> msg) -> Sub msg Subscribe to mouse moves anywhere on screen. It is best to unsubscribe if you

[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 >