Re:Integrating Elm and Phoenix Channels via Elm-Phoenix-socket
by knewter on Monday June 06, 2016 @07:16PM
(#11851274)
You can easily "sprinkle a little elm component in" for what it's worth to try it out in production. I know NoRedInk pulled it into a heavy React-based project. You basically set up intercommunication between components via ports. It's a fantastic solution once you grok it.
[ Parent
| on HN ]
Re:Integrating Elm and Phoenix Channels via Elm-Phoenix-socket
by aidos on Monday June 06, 2016 @07:26PM
(#11851322)
And the other way around? What if you had a big existing submodule in JS that you wanted to make use of within an Elm app? Is that doable?
One of the things that's really attractive about React is that there are already a lot of components you can drop in to handle behaviours for you. If I could somehow utilise those within Elm, it would lower the entry barrier for me.
Re:Integrating Elm and Phoenix Channels via Elm-Phoenix-socket
by knewter on Monday June 06, 2016 @07:31PM
(#11851345)
You could just create a communication scheme between the two parts. They're basically 2 sides of the same coin. I promise it's easy and great!
Re:Integrating Elm and Phoenix Channels via Elm-Phoenix-socket
by aidos on Monday June 06, 2016 @07:43PM
(#11851399)
:) Ok, I'm going to take your word for it! Hopefully I should get to that stage tomorrow and it will all become clear.
It's not that I even have a clear picture of what I need to achieve but with each of these different tools I'm trying to poke at them to see where they fall down. So far, Elm feels the nicest, but it's the smaller ecosystem / lack of libraries that's the most obvious shortcoming so I'm trying to understand what the options are for interoperability on that front.