On Monday, November 17, 2014 12:02:32 PM UTC-5, Diogo Almeida wrote: > This is really cool (especially if what Ruslan said is the case). What would > the best practice be for stateful effects? Do you have any plans of adding > the equivalent of React's lifecycle methods?
So I plan to write more about this soon as I have it all more or less worked out in my head. Briefly, :on-show and :on-hide are "lifecycle" callbacks - I intend to rename them to something like :did-mount and :will-unmount respectively. The only other lifecycle callbacks make sense in freactive's update cycle are :will-mount and :did-unmount - but I'm not even sure there is a use case or it's a good idea. freactive tries to manage state in a different way that is fundamentally tied to IDeref watches (and invalidation watches which aren't yet documented). Input definitely welcome as these facilities are developed. As for state transitions, they will be based on the "data-state" attribute and have :on-state and :after-state callbacks. The recommended way will be to use a "state-machine" ref bound to :data-state - I also have this more or less worked out in my head... more details soon. > > Also, the reagent comparison doesn't work over https, because you use the > http version of React.js. Fixed! http://aaronc.github.io/freactive-reagent-comparison/ -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en --- You received this message because you are subscribed to the Google Groups "Clojure" group. To unsubscribe from this group and stop receiving emails from it, send an email to clojure+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
