That gist is old. For current Elm Architecture, please refer to the guide. http://guide.elm-lang.org/
I don't know about "the best way" but I can share how my App is structured. I have two types of pages in my app: Interactive and Informational. The informational pages are typically generated from markdown and are rendered all by the MainView. The interactive pages typically live inside their own modules. Some of the interactive pages generate actions for the entire App. Those pages' update typically evaluate to a 3 element tuple: (Model, Cmd Msg, Maybe OutMsg) The recommendation I have is to keep your app one "component" as long as you can. Rethink the code structure in terms of smart types that can generate what you need with simple functions. Move to "components" as late as possible. Yes, you might end up with quite large update and view functions but, most of the time, *flat is better than nested*. On Fri, Aug 5, 2016 at 1:45 AM, Ryan Erb <[email protected]> wrote: > Well after a bit more searching found this > > https://gist.github.com/evancz/2b2ba366cae1887fe621 > > Seems like one large Elm app divided into modules seems to be the way to > go? > > -- > 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. > -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
