I wasn't aware of Jade Templates being a common use case for the Cycle.js community. I was only aware of this issue- https://github.com/cyclejs/cyclejs/issues/321 resulting in this proof of concept- http://www.webpackbin.com/Nkd5aKiIf which is made possible by Cycle.JS not attaching event handlers in the view function, as noted by Andre Statlz in this discussion, https://www.reddit.com/r/javascript/comments/3zr6i0/conversation_whats_the_core_differences_between/ unlike Elm.
I really enjoy thinking in the pure functions of Hyperscript-Helpers or Elm of the Html package, for which the creator of Cycle.JS seemingly strongly supports http://staltz.com/some-problems-with-react-redux.html https://medium.com/@jador/jsx-4b978fbeb290#.8g4fr4fnc over "templates" like JSX. But to each their own. On Friday, January 20, 2017 at 10:17:32 AM UTC-8, Илья Толлю wrote: > > Hello, everybody! > > I'm new to Elm and I like its architecture very much. Except one nuance > annoys me. > If you take e.g. CycleJS there we observe view's events by selectors > external to view. I.e. view is not responsible for routing its events. That > responsibility is given to another part of code, which creates Observables. > So, we can use Jade/Pug or another templating technology and cleanly > separate view declaration and events listening declaration. > Considering that Elm is functional language, there can be some pattern > that aims to achieve the same result, so I could write View and Observables > in different sections. > > It would be great to know your opinion and experience. > > Best regards! > Ilja Tollu > -- 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.
