5 ms·

This article kind of comes at a perfect time for me. I just recently started working on a project with a code editor and I've been battling for a while how to c

This article kind of comes at a perfect time for me. I just recently started working on a project with a code editor and I've been battling for a while how to communicate changes through react. I plan to use ace, and require the ability to get and apply patches as the user types into the ace editor, get code when they need to compile, as well as be able to modify other properties of the editor. At the most complex level, I need to keep two ace editors in-sync, doing this with cure javascript and ace is simple, as you just need to apply a patch from one editor to the other. Building large and complex applications has always been the big problem for me with React, and the author states it right up front we ran into issues finding examples of how React could apply to an application as complex as ours, given that most tutorials focus on the specifics of toy-sized demo apps as opposed to more general discussions of the problems specific to larger applications. This is just something that is going to take time though.

natmaster 12y ago
This is why they gave the presentation on Flux, which is architecturally how Facebook solves this problem. Basically the first principal you must learn is to find the lowest common ancestor to store state. (http://facebook.github.io/react/blog/2013/11/05/thinking-in-react.html http://facebook.github.io/react/blog/2013/11/05/thinking-in-...) After realizing this the immediate thing people do is pass call backs through children so grandchildren's actions can communicate with where the state is. This leaks through all the components however, which is why Flux separates actions out into something that all the components have access to.
- insin 12y ago
  Worth pointing out that you don't need a full Flux implementation to get the benefits of going sideways to an action module: https://github.com/ryanflorence/react-training/blob/gh-pages/lessons/04-less-simple-communication.md https://github.com/ryanflorence/react-training/blob/gh-pages...
adamnemecek 12y ago
this is something i really like about ember. there's a good number of large scale open source projects that you can steal ideas from.
- bronson 12y ago
  Examples? Hopefully ones that are using idomatic Ember of today?
  - adamnemecek 12y ago
    https://www.reddit.com/r/emberjs/comments/2b8wnw/meta_subreddit_suggestion_create_a_subreddit_wiki/ https://www.reddit.com/r/emberjs/comments/2b8wnw/meta_subred...

natmaster 12y ago

This is why they gave the presentation on Flux, which is architecturally how Facebook solves this problem. Basically the first principal you must learn is to find the lowest common ancestor to store state. (http://facebook.github.io/react/blog/2013/11/05/thinking-in-react.html http://facebook.github.io/react/blog/2013/11/05/thinking-in-...) After realizing this the immediate thing people do is pass call backs through children so grandchildren's actions can communicate with where the state is. This leaks through all the components however, which is why Flux separates actions out into something that all the components have access to.

insin 12y ago
Worth pointing out that you don't need a full Flux implementation to get the benefits of going sideways to an action module: https://github.com/ryanflorence/react-training/blob/gh-pages/lessons/04-less-simple-communication.md https://github.com/ryanflorence/react-training/blob/gh-pages...

adamnemecek 12y ago

this is something i really like about ember. there's a good number of large scale open source projects that you can steal ideas from.

bronson 12y ago
Examples? Hopefully ones that are using idomatic Ember of today?
- adamnemecek 12y ago
  https://www.reddit.com/r/emberjs/comments/2b8wnw/meta_subreddit_suggestion_create_a_subreddit_wiki/ https://www.reddit.com/r/emberjs/comments/2b8wnw/meta_subred...