Re: [elm-discuss] Poll for Intermediate to Advanced topics that people struggle with

[Kurt Mueller]

I really like this list. I would also like authorization discussed as well.

Kurt

On Monday, April 24, 2017 at 10:24:05 AM UTC-4, Peter Damoc wrote:
>
> Scaling. 
>
> Most successful Elm adoption approach has been the NoRedInk approach of 
> implementing bits of the UI in Elm. 
> This effectively creates a self contained Component that one can interact 
> with from some container framework (e.g. React). 
>
> There is however another path, a more dangerous path, where one starts 
> with Elm and stays in Elm as much as possible. 
> On this path there is very little assistance. 
>
> Here are some topics: 
>
> - structuring large apps 
> - using build managers with Elm (webpack, gulp, etc.) 
> - options around responsibilities (e.g. using Elm with CSS libraries like 
> Bootstrap via webpack & SASS loaders) 
> - managing routing
> - non-hash SPA routing
> - managing authentication
> - storage interfaces (interfacing the code with the databases with some 
> kind of Store construct) 
>   
> Besides these topics, you could also explore integrating external 
> libraries with Elm
>
> - implementing a command processor that allows an Elm app to interact with 
> a bunch of JS libraries though a single pair of ports. 
> - interacting with famous UI libraries like CodeMirror or Google Maps 
> - using web-components 
>  
>
>  
>
> On Mon, Apr 24, 2017 at 5:06 PM, Jeff Schomay  > wrote:
>
>> 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 elm-discuss...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>
>
> -- 
> There is NO FATE, we are the creators.
> blog: http://damoc.ro/
>

-- 
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 https://groups.google.com/d/optout.

Re: [elm-discuss] Poll for Intermediate to Advanced topics that people struggle with

[Christophe de Vienne]

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 elm-discuss+unsubscr...@googlegroups.com
> .
> 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 elm-discuss+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[elm-discuss] Poll for Intermediate to Advanced topics that people struggle with

[Jeff Schomay]

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 elm-discuss+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.