I am not sure how Elm Architecture scales for dozens or hundreds of modules because it's tough to pass a global context object down to all submodules and components. I love the way Cerebral <http://www.cerebraljs.com/> works. Every component is connected to it's part in the immutable main model. UI components are isolated from the state controlled by modules. A component register it's signals. Every signal execute a chain of actions. They are always sequential, sync, and asynch are executed in the order. Actions can be grouped in higher older factories as well as the signals. It's very clean and scalable. Every module has access to global context object. Every component has access to any part of one, global model object. Cerebral is like Redux-Saga but much simpler.
Did anybody try to address the issues raised by these two articles? * http://www.christianalfoni.com/articles/2015_11_30_Exploring-Elm-part1 * http://www.christianalfoni.com/articles/2015_12_17_Exploring-Elm-part2 On Thursday, August 4, 2016 at 11:15:53 PM UTC+1, Ryan Erb wrote: > > Got a few questions regarding the best way, or what options there are for > scaling up to a large site. > If i have a site with lots of features what is the best way to orgainze > everything? > > *One Elm page to rule them all?* With this approach you only have to deal > with one update happening, you can separate code into different modules, > but the update function would be HUGE. Guess this would be the same as a > single page application? > > *One Elm page per HTML page?* This way every page deals with only what it > is used for. You can write common things in reusable modules. One problem > might be switching to other elm pages. The only really good way right now > that i have is using a port to "window.locaion.href" to another elm page. > Then pulling all the data it requires from the server using more ports. > > *One Elm page per feature?* This way you can write separate apps for each > part of your page. One for the header menu bar, one for a sidebar, and one > for each main feature. This way you can mix and match and piece together > for a full page. BUT you might have to do a lot of port talking between > each section. > > *Some other way?*????? > > Been searching around a cant seem to find any blogs or topics on this > subject. Our stack is Elm/Phoenix/Elixir/Postgres. > > If anyone has created a large application using Elm would happy to have > your input on what worked/ didn't work for you. > > Thanks, > > -- 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.
