One thing I did not figure yet is how to make several components in a
page efficiently interact with each other.
Ideally I would like a single program with one model and several
sub-views mounted on several nodes in the dom-tree (for example a basket
widget and a "myaccount" one).
I did such a
I have just started programming in elm-lang because of the positive
responses I noticed on Twitter and various channels.
One of the selling points I have noticed is the intuitive error messages
Elm compiler generates while parsing code. Inline with this I would like to
share my experience
As several have asked, and Peter Damoc kindly reached out off-list, I'll
post here what I wrote to him. Please know that I do appreciate what
everyone has worked on, but this hasn't worked for me for the reasons I
outline. I've started auto-archiving email from elm-discuss, so if you have
any
Duane,
I'm curious what the roadblocks were in the 2 of 3 you didn't have success
with? This could definitely help others when making their decision. Also,
it may provide helpful feedback to more appropriately prioritize future elm
platform development.
Thanks!
On Monday, April 24, 2017 at
- Interacting with 3rd party libraries that use DOM and have multiple
event-related callbacks
- `Chaining` Cmds and Msgs
- Fighting the lack of interfaces while designing own data structures
On Monday, April 24, 2017 at 5:06:53 PM UTC+3, Jeff Schomay wrote:
>
> Hello,
>
> I am considering doing
Whoops. Html.map is correct...
view : Model -> Html Msg
view model =
div []
(model.items
|> List.map itemView
|> List.map (Html.map ItemMsg)
)
On Sunday, April 23, 2017 at 1:49:22 PM UTC-4, Max Goldstein wrote:
>
> Yes, Ian is correct.
>
>
Data modelling and refactoring. "Making impossible states impossible",
perhaps starting with basic problems and working up to more realistic
tangles of conditions.
On Monday, April 24, 2017 at 10:06:53 AM UTC-4, Jeff Schomay wrote:
>
> Hello,
>
> I am considering doing some training material on
Yes, please let us know how you failed so that we can try to improve it!
Zach
ᐧ
On Mon, Apr 24, 2017 at 5:23 PM, John Orford wrote:
> More info would be nice - just purely out of curiosity. If you have
> written about this elsewhere, pls pt this out. Thanks.
>
> On Mon,
One thing I struggle with is setting up a project structure where I can be
the most productive when using Elm. Things like editors, tooling,
hot-reloading, not having to keeping my backend models in sync with my Elm
models, etc. I feel like I'm not as productive as I can be when I'm writing
More info would be nice - just purely out of curiosity. If you have written
about this elsewhere, pls pt this out. Thanks.
On Mon, 24 Apr 2017 at 15:58 Juan Ibiapina wrote:
> Good to know I'm not the only one with this feeling!
>
> On Mon, Apr 24, 2017 at 3:45 PM, Duane
Hello,
I am considering doing some training material on working with Elm in
production. I want to focus on areas that people struggle with after they
are already familiar with Elm. What concepts continue to confuse you?
What product requirements have been difficult to achieve with Elm?
Good to know I'm not the only one with this feeling!
On Mon, Apr 24, 2017 at 3:45 PM, Duane Johnson
wrote:
> Hi all,
>
> I've decided to move on from Elm. I've only been successful in 1 of 3
> projects. I'm now in a role where I need to make an important decision
>
Hi all,
I've decided to move on from Elm. I've only been successful in 1 of 3
projects. I'm now in a role where I need to make an important decision
regarding the transition of a codebase from Angular to something else, and
I don't feel like I can responsibly recommend Elm as the replacement. So
13 matches
Mail list logo