The rewrite of virtual-dom in 0.17 does not provide any mechanism for knowing when a dom element is created, re-rendered, or removed. Which would be essential for initializing a third party control.
Even in the version used in 0.16 I'm not sure the entire life-cycle for a dom node was available. Therefore, I'm suspicious that the solutions presented in the past have suffered from memory leaks. I'm wondering if dom node life-cycle events will ever become a priority for this project? On Friday, June 24, 2016 at 4:45:38 AM UTC-5, Robert Walter wrote: > > I'm also interested to learn if this can be ported to 0.17 and if not, > what the reasons are. Looking at the Upgrade site > <https://github.com/elm-lang/elm-platform/blob/master/upgrade-docs/0.17.md>, > I couldn't see why this shouldn't be possible, but then again I haven't > tried it. > > Maybe someone can also help me out why hooks would be a preferable > solution integrating something like CodeMirror compared to using ports. Is > it that with hooks we can control whether or not a component like code > mirror makes changes to the DOM? > > Thanks > > On Sunday, March 27, 2016 at 2:12:30 PM UTC+2, San Gillis wrote: >> >> You can find a live demo here: >> http://sgillis.github.io/elm-highcharts/ >> >> Code can be found here: >> https://github.com/sgillis/elm-highcharts/tree/master/examples >> >> On Saturday, March 26, 2016 at 12:24:01 PM UTC+1, debois wrote: >>> >>> Huh. I never managed to make that work, but I really need it. Could you >>> link to an example I can play with where there is a Highchart component and >>> some updates to the virtualdom as the application runs? >> >> -- 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.
