thoughts on modularity, real re-use, app-wide coordination about elm-architecture-tutorial HOT 4 CLOSED

Here's the beginning of advice on this kind of stuff: http://guide.elm-lang.org/reuse/

We will have more resources coming in the next few months, but that is the gist. If you are thinking about components, if you are thinking about parents and children and communication, something has already gone wrong.

Also, this community uses forums like elm-discuss and the Elm slack for discussions like this. Issues are for tracking concrete problems and work, not for discussions.

from elm-architecture-tutorial.

As you have seen with MessageBoxAction msg an action can hold a value. Why not make MessageBox.Action.MessageSent hold the send message as a string? But I myself am very new to Elm too, so feel free to submit better solutions.

from elm-architecture-tutorial.

Hi, i'm trying to build websites using elm.
As far as modularity is concerned, Why not allow simple communications between modules, like subscriptions do?
This would allow one to build apps bottom up.
For instance, i want an input component, and an "accumulator of inputs" component
When enter is hit, the whole input is piped to listening components ...
The Top down approach will have the "supervisor" (Top most component) have to store a lot of information ...
If the hierrachy is deeply nested, then it might get tedious to maintain "sense" in that top most component ...
What you guys think?

from elm-architecture-tutorial.

Expect more discussion.

from elm-architecture-tutorial.