Status of project

[jiangts]

Thanks for writing this library and giving your talk!

I'm wondering if this is still being actively maintained, and if there are any gotchas to beware of.

So far, I've noticed in
examples/QuantumCalc/src/quantumcalc/statechart/main.cljs it states that bubbling from concurrent states needs to be fixed, and in
src/nodename/stately/chart.cljs there are multiple instances of ;; TODO invoke directly.

I'm not altogether sure what to make of these comments. Perhaps these problems were fixed but accidentally left in?

[nodename]

Hi,
No, sorry, those are still to be done.
The "invoke directly" todos are not crucial, just a performance thing. The other, frankly I don't remember, because I have been doing "other things" recently. I was using stately in production on a project that has since been terminated, and it is likely that I will be porting it to Swift in 2017. At that time I will address any problems. The main thing that I want to complete is making it fully independent of re-frame.
Of course I would have to pay attention sooner if someone actually tries it out...

[jiangts]

aha. I've been reading the the code a bit and realized the "invoke directly" dispatches were fine.

curious why you want to make it re-frame independent though. I'm considering introducing it to a re-frame app I currently have in production, and have been altering some of the stately.comms calls to reflect the new re-frame api. Do you need it in a project outside of re-frame?

Also curious how your experience was using statecharts for UI development. I'm quite new to it but the talk was pretty provoking. Wondering if you've found them useful in more traditional UI components (lists, trees, forms, video players), and if there are any workarounds to address in UIs that are not as heavily state driven as a calculator :)

[nodename]

I want to make it re-frame independent so I can use it in Swift on iOS. The re-frame implementation should remain in place though. If you PR the re-frame api updates I'd be happy to incorporate them.

We were working on a re-frame and React Native version of our app, and (setting aside the fact that it was just too early for RN to do what we needed) Stately was excellent at orchestrating our screen transitions. I'm not sure it would be appropriate for the lower-level UI elements. I don't remember if I mentioned in the talk that statecharts are more of a top-down development approach, in contrast to the usual Clojure bottom-up style.