Thanks so much for writing that up! This is exactly the point in my Elm learning that I'm struggling with at the moment, so this extremely helpful. In the past I've always made my "components" as self-contained M/U/V modules - that was great because I could re-use them in other projects just by dropping the .elm module file into my new project folder and it would just work. So if I needed a button, I'd just drop my button from Project A into Project B, and voila! I had been building my own little library of these components. And, I *love* the fact that sub-modules have exactly the same M/U/V structure as the parents modules in a kind of fractal nested way - that makes my code really easy for me to understand. But, I always found updating submodules and bubbling up their effects a bit of a chore, so I'm looking forward to exploring the (seemingly?) simpler world of pure components.
But.. I'm still a bit confused! :) I found both Evan's sortable table example and your (excellent!) dropdown menu just a few levels too advanced for my poor beginner's brain to fully grok. I have a request! Could anyone point me to a blindingly, brain-dead-simple example of this system in action? For example, what would a simple, stand-alone, reusable, "pure" button component look like that just triggers a message update in the parent module when clicked? -- 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.
