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 thing with react/redux in a transition phase toward a SPA, and it was a nice way to iteratively integrate the new architecture in an existing application. The only way I can think of right with my current knowledge of elm is to use ports to have some messages sent from a component to the others, but it feels non optimal. I think having a clear way to achieve this would makes it easier to progressively integrate elm in an existing app. Le 24/04/2017 à 16:06, Jeff Schomay a écrit : > 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? > What is most painful about your Elm codebase? > > Some topics I have already thought of: > > - decoders > - debouncing (http autocomplete input field for example) > - scroll to element > - testing > - unwieldy update functions > - api design > > If you have anything you'd like me to consider, please add it to the > list. Thank you! > > -- > 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 [email protected] > <mailto:[email protected]>. > For more options, visit https://groups.google.com/d/optout. -- Christophe de Vienne -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
