diff --git a/_posts/2013-06-02-jsfiddle-integration.md b/_posts/2013-06-02-jsfiddle-integration.md index b67ee2f0..01683170 100644 --- a/_posts/2013-06-02-jsfiddle-integration.md +++ b/_posts/2013-06-02-jsfiddle-integration.md @@ -3,7 +3,7 @@ title: JSFiddle Integration author: vjeux --- -[JSFiddle](https://jsfiddle.net) just announced support for React. This is an exciting news as it makes collaboration on snippets of code a lot easier. You can play around this **[base React JSFiddle](https://jsfiddle.net/vjeux/kb3gN/)**, fork it and share it! A [fiddle without JSX](https://jsfiddle.net/vjeux/VkebS/) is also available. +[JSFiddle](https://jsfiddle.net) just announced support for React. This is an exciting news as it makes collaboration on snippets of code a lot easier. You can play around this **[base React JSFiddle](http://jsfiddle.net/vjeux/kb3gN/)**, fork it and share it! A [fiddle without JSX](http://jsfiddle.net/vjeux/VkebS/) is also available.

React (by Facebook) is now available on JSFiddle. facebook.github.io/react/

— JSFiddle (@jsfiddle) June 2, 2013
diff --git a/_posts/2013-06-05-why-react.md b/_posts/2013-06-05-why-react.md index 2bde1501..102a7621 100644 --- a/_posts/2013-06-05-why-react.md +++ b/_posts/2013-06-05-why-react.md @@ -56,7 +56,7 @@ to the DOM. > lightweight description of what the DOM should look like. We call this process **reconciliation**. Check out -[this jsFiddle](https://jsfiddle.net/fv6RD/3/) to see an example of +[this jsFiddle](http://jsfiddle.net/fv6RD/3/) to see an example of reconciliation in action. Because this re-render is so fast (around 1ms for TodoMVC), the developer diff --git a/_posts/2013-06-19-community-roundup-2.md b/_posts/2013-06-19-community-roundup-2.md index 6fc67231..1de3fe34 100644 --- a/_posts/2013-06-19-community-roundup-2.md +++ b/_posts/2013-06-19-community-roundup-2.md @@ -38,7 +38,7 @@ Since the launch we have received a lot of feedback and are actively working on > > [Read the full post...](https://www.quora.com/Pete-Hunt/Posts/Facebooks-React-vs-AngularJS-A-Closer-Look) -In the same vein, [Markov Twain](https://twitter.com/markov_twain/status/345702941845499906) re-implemented the examples on the front-page [with Ember](http://jsbin.com/azihiw/2/edit) and [Vlad Yazhbin](https://twitter.com/vla) re-implemented the tutorial [with Angular](https://jsfiddle.net/vla/Cdrse/). +In the same vein, [Markov Twain](https://twitter.com/markov_twain/status/345702941845499906) re-implemented the examples on the front-page [with Ember](http://jsbin.com/azihiw/2/edit) and [Vlad Yazhbin](https://twitter.com/vla) re-implemented the tutorial [with Angular](http://jsfiddle.net/vla/Cdrse/). ## Web Components: React & x-tags diff --git a/_posts/2013-07-03-community-roundup-4.md b/_posts/2013-07-03-community-roundup-4.md index f3d5a737..42db7f3e 100644 --- a/_posts/2013-07-03-community-roundup-4.md +++ b/_posts/2013-07-03-community-roundup-4.md @@ -26,12 +26,12 @@ Over the past several weeks, members of our team, [Pete Hunt](http://www.petehun > [Listening Scroll Event](https://groups.google.com/forum/#!topic/reactjs/l6PnP8qbofk) > -> * [JSFiddle](https://jsfiddle.net/aabeL/1/): Basically I've given you two mixins. The first lets you react to global scroll events. The second is, IMO, much more useful: it gives you scroll start and scroll end events, which you can use with setState() to create components that react based on whether the user is scrolling or not. +> * [JSFiddle](http://jsfiddle.net/aabeL/1/): Basically I've given you two mixins. The first lets you react to global scroll events. The second is, IMO, much more useful: it gives you scroll start and scroll end events, which you can use with setState() to create components that react based on whether the user is scrolling or not. > > [Fade-in Transition](https://groups.google.com/forum/#!topic/reactjs/RVAY_eQmdpo) > -> * [JSFiddle](https://jsfiddle.net/ufe8k/1/): Creating a new `` component and using jQuery `.fadeIn()` function on the DOM node. -> * [JSFiddle](https://jsfiddle.net/R8f5L/5/): Using CSS transition instead. +> * [JSFiddle](http://jsfiddle.net/ufe8k/1/): Creating a new `` component and using jQuery `.fadeIn()` function on the DOM node. +> * [JSFiddle](http://jsfiddle.net/R8f5L/5/): Using CSS transition instead. > > [Socket.IO Integration](https://groups.google.com/forum/#!topic/reactjs/pyUZBRWcHB4) > @@ -41,7 +41,7 @@ Over the past several weeks, members of our team, [Pete Hunt](http://www.petehun > > [Sortable jQuery Plugin Integration](https://groups.google.com/forum/#!topic/reactjs/mHfBGI3Qwz4) > -> * [JSFiddle](https://jsfiddle.net/LQxy7/): Your React component simply render empty divs, and then in componentDidMount() you call React.renderComponent() on each of those divs to set up a new root React tree. Be sure to explicitly unmountAndReleaseReactRootNode() for each component in componentWillUnmount(). +> * [JSFiddle](http://jsfiddle.net/LQxy7/): Your React component simply render empty divs, and then in componentDidMount() you call React.renderComponent() on each of those divs to set up a new root React tree. Be sure to explicitly unmountAndReleaseReactRootNode() for each component in componentWillUnmount(). ## Introduction to React Screencast