News for hackers. Stuff that matters.
Re:McFly – Flux Architecture Made Easy by bengotow on Wednesday November 05, 2014 @01:05PM (#8563178)
I wish someone would create a large Flux/Reflux demo app. I love the "one-way data flow" model and the patterns established by Flux/Reflux, but I feel like I would really benefit from seeing a large, complex application where stores depend on stores (or keep state independently?) etc. The example ToDo apps everyone publishes are too trivial to really gain an understanding of how to apply the patterns.
Re:McFly – Flux Architecture Made Easy by thekenwheeler on Wednesday November 05, 2014 @01:06PM (#8563189)
I don't know if it's "large", but I wrote an article and supplied a demo that is a bit more complex than the usual examples you might see are.

http://scotch.io/tutorials/javascript/creating-a-simple-shop...

Re:McFly – Flux Architecture Made Easy by andrewvc on Wednesday November 05, 2014 @04:42PM (#8564445)
We were in a similar spot. Our startup is building a relatively large flux app. We interviewed Ian Obermiller of FB on a lot of the concerns of a large app. You can find a lot of answers to tough questions in our transcript: http://ianobermiller.com/blog/2014/09/15/react-and-flux-inte...
Re:McFly – Flux Architecture Made Easy by cnp on Wednesday November 05, 2014 @06:11PM (#8564823)
Awesome, thank you so much for this.
Re:McFly – Flux Architecture Made Easy by rajivtiru on Wednesday November 05, 2014 @03:09PM (#8563977)
Facebook came out with a flux chat example: https://github.com/facebook/flux/tree/master/examples/flux-c...

Yahoo has a good take on making it isomorphic here: https://github.com/yahoo/flux-examples

Re:McFly – Flux Architecture Made Easy by cnp on Wednesday November 05, 2014 @04:36PM (#8564405)
This was posted today on the React forums asking the same question: How should you structure a large Flux project? https://groups.google.com/forum/#!topic/reactjs/d33IinfVI0o