Mark, have you considered the approach that Evan took with elm-autocomplete 
<https://github.com/thebritican/elm-autocomplete/blob/master/src/Autocomplete/Autocomplete.elm#L164>?
 
Personally, I found this a satisfactory approach to the problem of private 
state/events, I'd be interested to hear your take on it.

> From my view, the issue here is with how you scale a page when it is full 
of such "components". 

This is definitely the issue that feels the least resolved for me. The 
elm-parts approach hasn't been endorsed, but I'm not aware of any other 
approach being put forward.


On Saturday, 10 September 2016 16:39:53 UTC+2, Mark Hamburg wrote:
>
> > On Sep 10, 2016, at 1:22 AM, Peter Damoc <[email protected] <javascript:>> 
> wrote: 
> > 
> > Charlie was right, an accordion is a better example. 
>
> I'm sure it is. As is a date picker. As with lists of counters as models 
> in the Elm Architecture documents, my example is entirely contrived — 
> hence, my subject line — with the intent that in being so contrived and yet 
> so simple, attention could instead focus on the proposed pattern for 
> handling a combination of public/shared state and private/local state. I 
> figured that these discussions had come around enough that that context 
> would be as clear as the context for why a list of counters is interesting. 
> I seem to have been wrong in that regard. 
>
> > From my view, the issue here is with how you scale a page when it is 
> full of such "components". 
>
> I rather hoped that if the approach I took could be endorsed as being 
> closer to what some would argue is the right way to write Elm code that the 
> scalability issue could be the next discussion point. But to get there we 
> need something that's being scaled and we can't even seem to get to that 
> point. 
>
> Mark 
>
>

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

Reply via email to