On Thursday, September 22, 2016 at 3:12:27 PM UTC+1, OvermindDL1 wrote: > > You can compile multiple main files together and they will share a > code-base, standard library, and all such. >
I had not considered that - useful if you want to take a one page, one main approach rather than nested TEA with a router in a single main. Still, you'd have to compile the components all together at the same time would you not? If I used some components from one auther and some from another, the code sharing would be lost. > > On Thursday, September 22, 2016 at 8:01:58 AM UTC-6, Rupert Smith wrote: >> >> On Wednesday, September 21, 2016 at 10:59:00 PM UTC+1, John Mayer wrote: >>> >>> I also posit that automatically generating a web component for every >>> top-level Elm app is isomorphic and maybe even superior interface to our >>> existing method of embedding Elm in native HTML pages, and could even >>> increase adoption as we could publish web components written in Elm for >>> consumption by anybody. >>> >> >> The output .js from Elm is quite big, even once minified. Does that mean >> that every web component written in Elm will have 100K+ of javascript >> embedded inside it? Its a great idea, but perhaps there needs to be a way >> to share the code that is common. >> > -- 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.
