mirror of
https://github.com/facebook/react.git
synced 2025-11-01 09:12:30 +00:00
Paul O’Shannessy
596 lines
75 KiB
XML
596 lines
75 KiB
XML
<?xml version="1.0" encoding="UTF-8"?>
|
|
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
|
|
<channel>
|
|
<title>React</title>
|
|
<description>A JavaScript library for building user interfaces</description>
|
|
<link>http://facebook.github.io/react</link>
|
|
<atom:link href="http://facebook.github.io/react/feed.xml" rel="self" type="application/rss+xml" />
|
|
|
|
<item>
|
|
<title>React v0.5</title>
|
|
<description><p>This release is the result of several months of hard work from members of the team and the community. While there are no groundbreaking changes in core, we&#39;ve worked hard to improve performance and memory usage. We&#39;ve also worked hard to make sure we are being consistent in our usage of DOM properties.</p>
|
|
|
|
<p>The biggest change you&#39;ll notice as a developer is that we no longer support <code>class</code> in JSX as a way to provide CSS classes. Since this prop was being converted to <code>className</code> at the transform step, it caused some confusion when trying to access it in composite components. As a result we decided to make our DOM properties mirror their counterparts in the JS DOM API. There are <a href="https://github.com/facebook/react/blob/master/src/dom/DefaultDOMPropertyConfig.js#L156">a few exceptions</a> where we deviate slightly in an attempt to be consistent internally.</p>
|
|
|
|
<p>The other major change in v0.5 is that we&#39;ve added an additional build - <code>react-with-addons</code> - which adds support for some extras that we&#39;ve been working on including animations and two-way binding. <a href="/react/docs/addons.html">Read more about these addons in the docs</a>.</p>
|
|
<h2 id="thanks-to-our-community"><a href="#thanks-to-our-community">Thanks to Our Community</a></h2>
|
|
<p>We added <em>22 new people</em> to the list of authors since we launched React v0.4.1 nearly 3 months ago. With a total of 48 names in our <code>AUTHORS</code> file, that means we&#39;ve nearly doubled the number of contributors in that time period. We&#39;ve seen the number of people contributing to discussion on IRC, mailing lists, Stack Overflow, and GitHub continue rising. We&#39;ve also had people tell us about talks they&#39;ve given in their local community about React.</p>
|
|
|
|
<p>It&#39;s been awesome to see the things that people are building with React, and we can&#39;t wait to see what you come up with next!</p>
|
|
<h2 id="changelog"><a href="#changelog">Changelog</a></h2><h3 id="react"><a href="#react">React</a></h3>
|
|
<ul>
|
|
<li>Memory usage improvements - reduced allocations in core which will help with GC pauses</li>
|
|
<li>Performance improvements - in addition to speeding things up, we made some tweaks to stay out of slow path code in V8 and Nitro.</li>
|
|
<li>Standardized prop -&gt; DOM attribute process. This previously resulting in additional type checking and overhead as well as confusing cases for users. Now we will always convert your value to a string before inserting it into the DOM.</li>
|
|
<li>Support for Selection events.</li>
|
|
<li>Support for <a href="https://developer.mozilla.org/en-US/docs/Web/API/CompositionEvent">Composition events</a>.</li>
|
|
<li>Support for additional DOM properties (<code>charSet</code>, <code>content</code>, <code>form</code>, <code>httpEquiv</code>, <code>rowSpan</code>, <code>autoCapitalize</code>).</li>
|
|
<li>Support for additional SVG properties (<code>rx</code>, <code>ry</code>).</li>
|
|
<li>Support for using <code>getInitialState</code> and <code>getDefaultProps</code> in mixins.</li>
|
|
<li>Support mounting into iframes.</li>
|
|
<li>Bug fixes for controlled form components.</li>
|
|
<li>Bug fixes for SVG element creation.</li>
|
|
<li>Added <code>React.version</code>.</li>
|
|
<li>Added <code>React.isValidClass</code> - Used to determine if a value is a valid component constructor.</li>
|
|
<li>Removed <code>React.autoBind</code> - This was deprecated in v0.4 and now properly removed.</li>
|
|
<li>Renamed <code>React.unmountAndReleaseReactRootNode</code> to <code>React.unmountComponentAtNode</code>.</li>
|
|
<li>Began laying down work for refined performance analysis.</li>
|
|
<li>Better support for server-side rendering - <a href="https://github.com/facebook/react-page">react-page</a> has helped improve the stability for server-side rendering.</li>
|
|
<li>Made it possible to use React in environments enforcing a strict <a href="https://developer.mozilla.org/en-US/docs/Security/CSP/Introducing_Content_Security_Policy">Content Security Policy</a>. This also makes it possible to use React to build Chrome extensions.</li>
|
|
</ul>
|
|
<h3 id="react-with-addons-new"><a href="#react-with-addons-new">React with Addons (New!)</a></h3>
|
|
<ul>
|
|
<li>Introduced a separate build with several &quot;addons&quot; which we think can help improve the React experience. We plan to deprecate this in the long-term, instead shipping each as standalone pieces. <a href="/react/docs/addons.html">Read more in the docs</a>.</li>
|
|
</ul>
|
|
<h3 id="jsx"><a href="#jsx">JSX</a></h3>
|
|
<ul>
|
|
<li>No longer transform <code>class</code> to <code>className</code> as part of the transform! This is a breaking change - if you were using <code>class</code>, you <em>must</em> change this to <code>className</code> or your components will be visually broken.</li>
|
|
<li>Added warnings to the in-browser transformer to make it clear it is not intended for production use.</li>
|
|
<li>Improved compatibility for Windows</li>
|
|
<li>Improved support for maintaining line numbers when transforming.</li>
|
|
</ul>
|
|
</description>
|
|
<pubDate>2013-10-16T00:00:00-07:00</pubDate>
|
|
<link>http://facebook.github.io/react/blog/2013/10/16/react-v0.5.0.html</link>
|
|
<guid isPermaLink="true">http://facebook.github.io/react/blog/2013/10/16/react-v0.5.0.html</guid>
|
|
</item>
|
|
|
|
<item>
|
|
<title>Community Round-up #9</title>
|
|
<description><p>We organized a React hackathon last week-end in the Facebook Seattle office. 50 people, grouped into 15 teams, came to hack for a day on React. It was a lot of fun and we&#39;ll probably organize more in the future.</p>
|
|
|
|
<p><img src="/react/img/blog/react-hackathon.jpg" alt=""></p>
|
|
<h2 id="react-hackathon-winner"><a href="#react-hackathon-winner">React Hackathon Winner</a></h2>
|
|
<p><a href="http://bold-it.com/">Alex Swan</a> implemented <a href="http://qu.izti.me/">Qu.izti.me</a>, a multi-player quiz game. It is real-time via Web Socket and mobile friendly.</p>
|
|
|
|
<blockquote>
|
|
<p>The game itself is pretty simple. People join the &quot;room&quot; by going to <a href="http://qu.izti.me/">http://qu.izti.me</a> on their device. Large displays will show a leaderboard along with the game, and small displays (such as phones) will act as personal gamepads. Users will see questions and a choice of answers. The faster you answer, the more points you earn.</p>
|
|
|
|
<p>In my opinion, Socket.io and React go together like chocolate and peanut butter. The page was always an accurate representation of the game object.
|
|
<figure><a href="http://bold-it.com/javascript/facebook-react-example/"><img src="/react/img/blog/quiztime.png" alt=""></a></figure></p>
|
|
|
|
<p><a href="http://bold-it.com/javascript/facebook-react-example/">Read More...</a></p>
|
|
</blockquote>
|
|
<h2 id="jsconf-eu-talk-rethinking-best-practices"><a href="#jsconf-eu-talk-rethinking-best-practices">JSConf EU Talk: Rethinking Best Practices</a></h2>
|
|
<p><a href="http://www.petehunt.net/">Pete Hunt</a> presented React at JSConf EU. He covers three controversial design decisions of React:</p>
|
|
|
|
<ol>
|
|
<li>Build <strong>components</strong>, not templates</li>
|
|
<li>Re-render the whole app on every update</li>
|
|
<li>Virtual DOM</li>
|
|
</ol>
|
|
|
|
<p>The video will be available soon on the <a href="http://2013.jsconf.eu/speakers/pete-hunt-react-rethinking-best-practices.html">JSConf EU website</a>, but in the meantime, here are Pete&#39;s slides:</p>
|
|
|
|
<figure><iframe src="http://www.slideshare.net/slideshow/embed_code/26589373" width="550" height="450" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" allowfullscreen></iframe></figure>
|
|
<h2 id="pump---clojure-bindings-for-react"><a href="#pump---clojure-bindings-for-react">Pump - Clojure bindings for React</a></h2>
|
|
<p><a href="http://solovyov.net/">Alexander Solovyov</a> has been working on React bindings for ClojureScript. This is really exciting as it is using &quot;native&quot; ClojureScript data structures.</p>
|
|
<div class="highlight"><pre><code class="ruby language-ruby" data-lang="ruby"><span class="p">(</span><span class="n">ns</span> <span class="n">your</span><span class="o">.</span><span class="n">app</span>
|
|
<span class="p">(</span><span class="ss">:require</span><span class="o">-</span><span class="n">macros</span> <span class="o">[</span><span class="n">pump</span><span class="o">.</span><span class="n">def</span><span class="o">-</span><span class="n">macros</span> <span class="ss">:refer</span> <span class="o">[</span><span class="n">defr</span><span class="o">]]</span><span class="p">)</span>
|
|
<span class="p">(</span><span class="ss">:require</span> <span class="o">[</span><span class="n">pump</span><span class="o">.</span><span class="n">core</span><span class="o">]</span><span class="p">))</span>
|
|
|
|
<span class="p">(</span><span class="n">defr</span> <span class="no">Component</span>
|
|
<span class="ss">:get</span><span class="o">-</span><span class="n">initial</span><span class="o">-</span><span class="n">state</span> <span class="c1">#(identity {:some-value &quot;&quot;})</span>
|
|
|
|
<span class="o">[</span><span class="n">component</span> <span class="n">props</span> <span class="n">state</span><span class="o">]</span>
|
|
|
|
<span class="o">[</span><span class="ss">:div</span> <span class="p">{</span><span class="ss">:class</span><span class="o">-</span><span class="nb">name</span> <span class="s2">&quot;test&quot;</span><span class="p">}</span> <span class="s2">&quot;hello&quot;</span><span class="o">]</span><span class="p">)</span>
|
|
</code></pre></div>
|
|
<p><a href="https://github.com/piranha/pump">Check it out on GitHub...</a></p>
|
|
<h2 id="jsxhint"><a href="#jsxhint">JSXHint</a></h2>
|
|
<p><a href="http://blog.selfassembled.org/">Todd Kennedy</a> working at <a href="http://www.condenast.com/">Cond&eacute; Nast</a> implemented a wrapper on-top of <a href="http://www.jshint.com/">JSHint</a> that first converts JSX files to JS.</p>
|
|
|
|
<blockquote>
|
|
<p>A wrapper around JSHint to allow linting of files containg JSX syntax. Accepts glob patterns. Respects your local .jshintrc file and .gitignore to filter your glob patterns.</p>
|
|
<div class="highlight"><pre><code class="text language-text" data-lang="text">npm install -g jsxhint
|
|
</code></pre></div>
|
|
<p><a href="https://github.com/CondeNast/JSXHint">Check it out on GitHub...</a></p>
|
|
</blockquote>
|
|
<h2 id="turbo-react"><a href="#turbo-react">Turbo React</a></h2>
|
|
<p><a href="https://twitter.com/ssorallen">Ross Allen</a> working at <a href="http://mesosphere.io/">Mesosphere</a> combined <a href="https://github.com/rails/turbolinks/">Turbolinks</a>, a library used by Ruby on Rails to speed up page transition, and React.</p>
|
|
|
|
<blockquote>
|
|
<p>&quot;Re-request this page&quot; is just a link to the current page. When you click it, Turbolinks intercepts the GET request and fetchs the full page via XHR.</p>
|
|
|
|
<p>The panel is rendered with a random panel- class on each request, and the progress bar gets a random widthX class.</p>
|
|
|
|
<p>With Turbolinks alone, the entire <body> would be replaced, and transitions would not happen. In this little demo though, React adds and removes classes and text, and the attribute changes are animated with CSS transitions. The DOM is otherwise left intact.
|
|
<figure><a href="https://turbo-react.herokuapp.com/"><img src="/react/img/blog/turboreact.png" alt=""></a></figure></p>
|
|
|
|
<p><a href="https://turbo-react.herokuapp.com/">Check out the demo...</a></p>
|
|
</blockquote>
|
|
<h2 id="reactive-table"><a href="#reactive-table">Reactive Table</a></h2>
|
|
<p><a href="http://www.phpied.com/">Stoyan Stefanov</a> continues his series of blog posts about React. This one is an introduction tutorial on rendering a simple table with React.</p>
|
|
|
|
<blockquote>
|
|
<p>React is all about components. So let&#39;s build one.</p>
|
|
|
|
<p>Let&#39;s call it Table (to avoid any confusion what the component is about).</p>
|
|
<div class="highlight"><pre><code class="javascript language-javascript" data-lang="javascript"><span class="kd">var</span> <span class="nx">Table</span> <span class="o">=</span> <span class="nx">React</span><span class="p">.</span><span class="nx">createClass</span><span class="p">({</span>
|
|
<span class="cm">/*stuff goeth here*/</span>
|
|
<span class="p">});</span>
|
|
</code></pre></div>
|
|
<p>You see that React components are defined using a regular JS object. Some properties and methods of the object such as render() have special meanings, the rest is upforgrabs.</p>
|
|
|
|
<p><a href="http://www.phpied.com/reactive-table/">Read the full article...</a></p>
|
|
</blockquote>
|
|
</description>
|
|
<pubDate>2013-10-03T00:00:00-07:00</pubDate>
|
|
<link>http://facebook.github.io/react/blog/2013/10/03/community-roundup-9.html</link>
|
|
<guid isPermaLink="true">http://facebook.github.io/react/blog/2013/10/03/community-roundup-9.html</guid>
|
|
</item>
|
|
|
|
<item>
|
|
<title>Community Round-up #8</title>
|
|
<description><p>A lot has happened in the month since our last update. Here are some of the more interesting things we&#39;ve found. But first, we have a couple updates before we share links.</p>
|
|
|
|
<p>First, we are organizing a <a href="http://reactjshack-a-thon.splashthat.com/">React Hackathon</a> in Facebook&#39;s Seattle office on Saturday September 28. If you want to hack on React, meet some of the team or win some prizes, feel free to join us!</p>
|
|
|
|
<p>We&#39;ve also reached a point where there are too many questions for us to handle directly. We&#39;re encouraging people to ask questions on <a href="http://stackoverflow.com/questions/tagged/reactjs">StackOverflow</a> using the tag <a href="http://stackoverflow.com/questions/tagged/reactjs">[reactjs]</a>. Many members of the team and community have subscribed to the tag, so feel free to ask questions there. We think these will be more discoverable than Google Groups archives or IRC logs.</p>
|
|
<h2 id="javascript-jabber"><a href="#javascript-jabber">Javascript Jabber</a></h2>
|
|
<p><a href="http://www.petehunt.net/">Pete Hunt</a> and <a href="https://github.com/jordwalke">Jordan Walke</a> were interviewed on <a href="http://javascriptjabber.com/073-jsj-react-with-pete-hunt-and-jordan-walke/">Javascript Jabber</a> for an hour. They go over many aspects of React such as 60 FPS, Data binding, Performance, Diffing Algorithm, DOM Manipulation, Node.js support, server-side rendering, JSX, requestAnimationFrame and the community. This is a gold mine of information about React.</p>
|
|
|
|
<blockquote>
|
|
<p><strong>PETE:</strong> So React was designed all around that. Conceptually, how you build a React app is that every time your data changes, it&#39;s like hitting the refresh button in a server-rendered app. What we do is we conceptually throw out all of the markup and event handlers that you&#39;ve registered and we reset the whole page and then we redraw the entire page. If you&#39;re writing a server-rendered app, handling updates is really easy because you hit the refresh button and you&#39;re pretty much guaranteed to get what you expect.</p>
|
|
|
|
<p><strong>MERRICK:</strong> That&#39;s true. You don&#39;t get into these odd states.</p>
|
|
|
|
<p><strong>PETE:</strong> Exactly, exactly. In order to implement that, we communicate it as a fake DOM. What we&#39;ll do is rather than throw out the actual browser html and event handlers, we have an internal representation of what the page looks like and then we generate a brand new representation of what we want the page to look like. Then we perform this really, really fast diffing algorithm between those two page representations, DOM representations. Then React will compute the minimum set of DOM mutations it needs to make to bring the page up to date.</p>
|
|
|
|
<p>Then to finally get to answer your question, that set of DOM mutations then goes into a queue and we can plug in arbitrary flushing strategies for that. For example, when we originally launched React in open source, every setState would immediately trigger a flush to the DOM. That wasn&#39;t part of the contract of setState, but that was just our strategy and it worked pretty well. Then this totally awesome open source contributor Ben Alpert at Khan Academy built a new batching strategy which would basically queue up every single DOM update and state change that happened within an event tick and would execute them in bulk at the end of the event tick.</p>
|
|
|
|
<p><a href="http://javascriptjabber.com/073-jsj-react-with-pete-hunt-and-jordan-walke/">Read the full conversation ...</a></p>
|
|
</blockquote>
|
|
<h2 id="jsxtransformer-trick"><a href="#jsxtransformer-trick">JSXTransformer Trick</a></h2>
|
|
<p>While this is not going to work for all the attributes since they are camelCased in React, this is a pretty cool trick.</p>
|
|
|
|
<div style="margin-left: 74px;"><blockquote class="twitter-tweet"><p>Turn any DOM element into a React.js function: JSXTransformer.transform(&quot;/** <a href="https://twitter.com/jsx">@jsx</a> React.DOM */&quot; + element.innerHTML).code</p>&mdash; Ross Allen (@ssorallen) <a href="https://twitter.com/ssorallen/statuses/377105575441489920">September 9, 2013</a></blockquote></div>
|
|
|
|
<script async src="//platform.twitter.com/widgets.js" charset="utf-8"></script>
|
|
<h2 id="remarkable-react"><a href="#remarkable-react">Remarkable React</a></h2>
|
|
<p><a href="http://www.phpied.com/">Stoyan Stefanov</a> gave a talk at <a href="http://braziljs.com.br/">BrazilJS</a> about React and wrote an article with the content of the presentation. He goes through the difficulties of writting <em>active apps</em> using the DOM API and shows how React handles it.</p>
|
|
|
|
<blockquote>
|
|
<p>So how does exactly React deal with it internally? Two crazy ideas - virtual DOM and synthetic events.</p>
|
|
|
|
<p>You define you components in React. It builds a virtual DOM in JavaScript land which is way more efficient. Then it updates the DOM. (And &quot;virtual DOM&quot; is a very big name for what is simply a JavaScript object with nested key-value pairs)</p>
|
|
|
|
<p>Data changes. React computes a diff (in JavaScript land, which is, of course, much more efficient) and updates the single table cell that needs to change. React replicates the state of the virtual DOM into the actual DOM only when and where it&#39;s necessary. And does it all at once, in most cases in a single tick of the <code>requestAnimationFrame()</code>.</p>
|
|
|
|
<p>What about event handlers? They are synthetic. React uses event delegation to listen way at the top of the React tree. So removing a node in the virtual DOM has no effect on the event handling.</p>
|
|
|
|
<p>The events are automatically cross-browser (they are React events). They are also much closer to W3C than any browser. That means that for example <code>e.target</code> works, no need to look for the event object or checking whether it&#39;s <code>e.target</code> or <code>e.srcElement</code> (IE). Bubbling and capturing phases also work cross browser. React also takes the liberty of making some small fixes, e.g. the event <code>&lt;input onChange&gt;</code> fires when you type, not when blur away from the input. And of course, event delegation is used as the most efficient way to handle events. You know that &quot;thou shall use event delegation&quot; is also commonly given advice for making web apps snappy.</p>
|
|
|
|
<p>The good thing about the virtual DOM is that it&#39;s all in JavaScript land. You build all your UI in JavaScript. Which means it can be rendered on the server side, so you initial view is fast (and any SEO concerns are addressed). Also, if there are especially heavy operations they can be threaded into WebWorkers, which otherwise have no DOM access.</p>
|
|
|
|
<p><a href="http://www.phpied.com/remarkable-react/">Read More ...</a></p>
|
|
</blockquote>
|
|
<h2 id="markdown-in-react"><a href="#markdown-in-react">Markdown in React</a></h2>
|
|
<p><a href="http://benalpert.com/">Ben Alpert</a> converted <a href="https://github.com/chjj/marked">marked</a>, a Markdown Javascript implementation, in React: <a href="https://github.com/spicyj/marked-react">marked-react</a>. Even without using JSX, the HTML generation is now a lot cleaner. It is also safer as forgetting a call to <code>escape</code> will not introduce an XSS vulnerability.
|
|
<figure><a href="https://github.com/spicyj/marked-react/commit/cb70c9df6542c7c34ede9efe16f9b6580692a457"><img src="/react/img/blog/markdown_refactor.png" alt=""></a></figure></p>
|
|
<h2 id="unite-from-bugbusters"><a href="#unite-from-bugbusters">Unite from BugBusters</a></h2>
|
|
<p><a href="https://twitter.com/renajohn">Renault John Lecoultre</a> wrote <a href="https://www.bugbuster.com/">Unite</a>, an interactive tool for analyzing code dynamically using React. It integrates with CodeMirror.
|
|
<figure><a href="https://unite.bugbuster.com/"><img src="/react/img/blog/unite.png" alt=""></a></figure></p>
|
|
<h2 id="reactjs-irc-logs"><a href="#reactjs-irc-logs">#reactjs IRC Logs</a></h2>
|
|
<p><a href="http://blog.vjeux.com/">Vjeux</a> re-implemented the display part of the IRC logger in React. Just 130 lines are needed for a performant infinite scroll with timestamps and color-coded author names.</p>
|
|
|
|
<iframe width="100%" height="300" src="http://jsfiddle.net/vjeux/QL9tz/embedded/" allowfullscreen="allowfullscreen" frameborder="0"></iframe>
|
|
</description>
|
|
<pubDate>2013-09-24T00:00:00-07:00</pubDate>
|
|
<link>http://facebook.github.io/react/blog/2013/09/24/community-roundup-8.html</link>
|
|
<guid isPermaLink="true">http://facebook.github.io/react/blog/2013/09/24/community-roundup-8.html</guid>
|
|
</item>
|
|
|
|
<item>
|
|
<title>Community Round-up #7</title>
|
|
<description><p>It&#39;s been three months since we open sourced React and it is going well. Some stats so far:</p>
|
|
|
|
<ul>
|
|
<li>114 285 unique visitors on this website</li>
|
|
<li><a href="https://github.com/facebook/react/stargazers">1933 stars</a> and <a href="https://github.com/facebook/react/network/members">210 forks</a></li>
|
|
<li><a href="https://groups.google.com/forum/#!forum/reactjs">226 posts on Google Group</a></li>
|
|
<li><a href="https://gist.github.com/vjeux/6335762">76 Github projects using React</a></li>
|
|
<li><a href="https://github.com/facebook/react/graphs/contributors">30 contributors</a></li>
|
|
<li><a href="http://facebook.github.io/react/blog/">15 blog posts</a></li>
|
|
<li>2 early adopters: <a href="http://benalpert.com/2013/06/09/using-react-to-speed-up-khan-academy.html">Khan Academy</a> and <a href="http://usepropeller.com/blog/posts/from-backbone-to-react/">Propeller</a></li>
|
|
</ul>
|
|
<h2 id="wolfenstein-rendering-engine-ported-to-react"><a href="#wolfenstein-rendering-engine-ported-to-react">Wolfenstein Rendering Engine Ported to React</a></h2>
|
|
<p><a href="http://www.petehunt.net/">Pete Hunt</a> ported the render code of the web version of Wolfenstein 3D to React. Check out <a href="http://www.petehunt.net/wolfenstein3D-react/wolf3d.html">the demo</a> and <a href="https://github.com/petehunt/wolfenstein3D-react/blob/master/js/renderer.js#L183">render.js</a> file for the implementation.
|
|
<figure><a href="http://www.petehunt.net/wolfenstein3D-react/wolf3d.html"><img src="/react/img/blog/wolfenstein_react.png" alt=""></a></figure></p>
|
|
<h2 id="react-amp-meteor"><a href="#react-amp-meteor">React &amp; Meteor</a></h2>
|
|
<p><a href="https://twitter.com/benjamn">Ben Newman</a> made a <a href="https://github.com/benjamn/meteor-react/blob/master/lib/mixin.js">13-lines wrapper</a> to use React and Meteor together. <a href="http://www.meteor.com/">Meteor</a> handles the real-time data synchronization between client and server. React provides the declarative way to write the interface and only updates the parts of the UI that changed.</p>
|
|
|
|
<blockquote>
|
|
<p>This repository defines a Meteor package that automatically integrates the React rendering framework on both the client and the server, to complement or replace the default Handlebars templating system.</p>
|
|
|
|
<p>The React core is officially agnostic about how you fetch and update your data, so it is far from obvious which approach is the best. This package provides one answer to that question (use Meteor!), and I hope you will find it a compelling combination.</p>
|
|
<div class="highlight"><pre><code class="javascript language-javascript" data-lang="javascript"><span class="kd">var</span> <span class="nx">MyComponent</span> <span class="o">=</span> <span class="nx">React</span><span class="p">.</span><span class="nx">createClass</span><span class="p">({</span>
|
|
<span class="nx">mixins</span><span class="o">:</span> <span class="p">[</span><span class="nx">MeteorMixin</span><span class="p">],</span>
|
|
|
|
<span class="nx">getMeteorState</span><span class="o">:</span> <span class="kd">function</span><span class="p">()</span> <span class="p">{</span>
|
|
<span class="k">return</span> <span class="p">{</span> <span class="nx">foo</span><span class="o">:</span> <span class="nx">Session</span><span class="p">.</span><span class="nx">get</span><span class="p">(</span><span class="s1">&#39;foo&#39;</span><span class="p">)</span> <span class="p">};</span>
|
|
<span class="p">},</span>
|
|
|
|
<span class="nx">render</span><span class="o">:</span> <span class="kd">function</span><span class="p">()</span> <span class="p">{</span>
|
|
<span class="k">return</span> <span class="o">&lt;</span><span class="nx">div</span><span class="o">&gt;</span><span class="p">{</span><span class="k">this</span><span class="p">.</span><span class="nx">state</span><span class="p">.</span><span class="nx">foo</span><span class="p">}</span><span class="o">&lt;</span><span class="err">/div&gt;;</span>
|
|
<span class="p">}</span>
|
|
<span class="p">});</span>
|
|
</code></pre></div>
|
|
<p>Dependencies will be registered for any data accesses performed by getMeteorState so that the component can be automatically re-rendered whenever the data changes.</p>
|
|
|
|
<p><a href="https://github.com/benjamn/meteor-react">Read more ...</a></p>
|
|
</blockquote>
|
|
<h2 id="react-page"><a href="#react-page">React Page</a></h2>
|
|
<p><a href="https://github.com/jordwalke">Jordan Walke</a> implemented a complete React project creator called <a href="https://github.com/facebook/react-page/">react-page</a>. It supports both server-side and client-side rendering, source transform and packaging JSX files using CommonJS modules, and instant reload.</p>
|
|
|
|
<blockquote>
|
|
<p>Easy Application Development with React JavaScript
|
|
<figure><a href="https://github.com/facebook/react-page/"><img src="/react/img/blog/react-page.png" alt=""></a></figure></p>
|
|
|
|
<p><strong>Why Server Rendering?</strong></p>
|
|
|
|
<ul>
|
|
<li>Faster initial page speed:
|
|
|
|
<ul>
|
|
<li>Markup displayed before downloading large JavaScript.</li>
|
|
<li>Markup can be generated more quickly on a fast server than low power client devices.</li>
|
|
</ul></li>
|
|
<li>Faster Development and Prototyping:
|
|
|
|
<ul>
|
|
<li>Instantly refresh your app without waiting for any watch scripts or bundlers.</li>
|
|
</ul></li>
|
|
<li>Easy deployment of static content pages/blogs: just archive using recursive wget.</li>
|
|
<li>SEO benefits of indexability and perf.</li>
|
|
</ul>
|
|
|
|
<p><strong>How Does Server Rendering Work?</strong></p>
|
|
|
|
<ul>
|
|
<li><code>react-page</code> computes page markup on the server, sends it to the client so the user can see it quickly.</li>
|
|
<li>The corresponding JavaScript is then packaged and sent.</li>
|
|
<li>The browser runs that JavaScript, so that all of the event handlers, interactions and update code will run seamlessly on top of the server generated markup.</li>
|
|
<li>From the developer&#39;s (and the user&#39;s) perspective, it&#39;s just as if the rendering occurred on the client, only faster.</li>
|
|
</ul>
|
|
|
|
<p><a href="https://github.com/facebook/react-page/">Try it out ...</a></p>
|
|
</blockquote>
|
|
</description>
|
|
<pubDate>2013-08-26T00:00:00-07:00</pubDate>
|
|
<link>http://facebook.github.io/react/blog/2013/08/26/community-roundup-7.html</link>
|
|
<guid isPermaLink="true">http://facebook.github.io/react/blog/2013/08/26/community-roundup-7.html</guid>
|
|
</item>
|
|
|
|
<item>
|
|
<title>Use React and JSX in Python Applications</title>
|
|
<description><p>Today we&#39;re happy to announce the initial release of <a href="https://github.com/facebook/react-python">PyReact</a>, which makes it easier to use React and JSX in your Python applications. It&#39;s designed to provide an API to transform your JSX files into JavaScript, as well as provide access to the latest React source files.</p>
|
|
<h2 id="usage"><a href="#usage">Usage</a></h2>
|
|
<p>Transform your JSX files via the provided <code>jsx</code> module:</p>
|
|
<div class="highlight"><pre><code class="python language-python" data-lang="python"><span class="kn">from</span> <span class="nn">react</span> <span class="kn">import</span> <span class="n">jsx</span>
|
|
|
|
<span class="c"># For multiple paths, use the JSXTransformer class.</span>
|
|
<span class="n">transformer</span> <span class="o">=</span> <span class="n">jsx</span><span class="o">.</span><span class="n">JSXTransformer</span><span class="p">()</span>
|
|
<span class="k">for</span> <span class="n">jsx_path</span><span class="p">,</span> <span class="n">js_path</span> <span class="ow">in</span> <span class="n">my_paths</span><span class="p">:</span>
|
|
<span class="n">transformer</span><span class="o">.</span><span class="n">transform</span><span class="p">(</span><span class="n">jsx_path</span><span class="p">,</span> <span class="n">js_path</span><span class="p">)</span>
|
|
|
|
<span class="c"># For a single file, you can use a shortcut method.</span>
|
|
<span class="n">jsx</span><span class="o">.</span><span class="n">transform</span><span class="p">(</span><span class="s">&#39;path/to/input/file.jsx&#39;</span><span class="p">,</span> <span class="s">&#39;path/to/output/file.js&#39;</span><span class="p">)</span>
|
|
</code></pre></div>
|
|
<p>For full paths to React files, use the <code>source</code> module:</p>
|
|
<div class="highlight"><pre><code class="python language-python" data-lang="python"><span class="kn">from</span> <span class="nn">react</span> <span class="kn">import</span> <span class="n">source</span>
|
|
|
|
<span class="c"># path_for raises IOError if the file doesn&#39;t exist.</span>
|
|
<span class="n">react_js</span> <span class="o">=</span> <span class="n">source</span><span class="o">.</span><span class="n">path_for</span><span class="p">(</span><span class="s">&#39;react.min.js&#39;</span><span class="p">)</span>
|
|
</code></pre></div><h2 id="django"><a href="#django">Django</a></h2>
|
|
<p>PyReact includes a JSX compiler for <a href="https://github.com/cyberdelia/django-pipeline">django-pipeline</a>. Add it to your project&#39;s pipeline settings like this:</p>
|
|
<div class="highlight"><pre><code class="python language-python" data-lang="python"><span class="n">PIPELINE_COMPILERS</span> <span class="o">=</span> <span class="p">(</span>
|
|
<span class="s">&#39;react.utils.pipeline.JSXCompiler&#39;</span><span class="p">,</span>
|
|
<span class="p">)</span>
|
|
</code></pre></div><h2 id="installation"><a href="#installation">Installation</a></h2>
|
|
<p>PyReact is hosted on PyPI, and can be installed with <code>pip</code>:</p>
|
|
<div class="highlight"><pre><code class="text language-text" data-lang="text">$ pip install PyReact
|
|
</code></pre></div>
|
|
<p>Alternatively, add it into your <code>requirements</code> file:</p>
|
|
<div class="highlight"><pre><code class="text language-text" data-lang="text">PyReact==0.1.1
|
|
</code></pre></div>
|
|
<p><strong>Dependencies</strong>: PyReact uses <a href="https://github.com/doloopwhile/PyExecJS">PyExecJS</a> to execute the bundled React code, which requires that a JS runtime environment is installed on your machine. We don&#39;t explicitly set a dependency on a runtime environment; Mac OS X comes bundled with one. If you&#39;re on a different platform, we recommend <a href="https://code.google.com/p/pyv8/">PyV8</a>.</p>
|
|
|
|
<p>For the initial release, we&#39;ve only tested on Python 2.7. Look out for support for Python 3 in the future, and if you see anything that can be improved, we welcome your <a href="https://github.com/facebook/react-python/blob/master/CONTRIBUTING.md">contributions</a>!</p>
|
|
</description>
|
|
<pubDate>2013-08-19T00:00:00-07:00</pubDate>
|
|
<link>http://facebook.github.io/react/blog/2013/08/19/use-react-and-jsx-in-python-applications.html</link>
|
|
<guid isPermaLink="true">http://facebook.github.io/react/blog/2013/08/19/use-react-and-jsx-in-python-applications.html</guid>
|
|
</item>
|
|
|
|
<item>
|
|
<title>Community Round-up #6</title>
|
|
<description><p>This is the first Community Round-up where none of the items are from Facebook/Instagram employees. It&#39;s great to see the adoption of React growing.</p>
|
|
<h2 id="react-game-tutorial"><a href="#react-game-tutorial">React Game Tutorial</a></h2>
|
|
<p><a href="https://twitter.com/CalebCassel">Caleb Cassel</a> wrote a <a href="https://rawgithub.com/calebcassel/react-demo/master/part1.html">step-by-step tutorial</a> about making a small game. It covers JSX, State and Events, Embedded Components and Integration with Backbone.
|
|
<figure><a href="https://rawgithub.com/calebcassel/react-demo/master/part1.html"><img src="/react/img/blog/dog-tutorial.png" alt=""></a></figure></p>
|
|
<h2 id="reactify"><a href="#reactify">Reactify</a></h2>
|
|
<p><a href="http://andreypopp.com/">Andrey Popp</a> created a <a href="http://browserify.org/">Browserify</a> helper to compile JSX files.</p>
|
|
|
|
<blockquote>
|
|
<p>Browserify v2 transform for <code>text/jsx</code>. Basic usage is:</p>
|
|
<div class="highlight"><pre><code class="text language-text" data-lang="text">% browserify -t reactify main.jsx
|
|
</code></pre></div>
|
|
<p><code>reactify</code> transform activates for files with either <code>.jsx</code> extension or <code>/** @jsx React.DOM */</code> pragma as a first line for any <code>.js</code> file.</p>
|
|
|
|
<p><a href="https://github.com/andreypopp/reactify">Check it out on Github...</a></p>
|
|
</blockquote>
|
|
<h2 id="react-integration-with-este"><a href="#react-integration-with-este">React Integration with Este</a></h2>
|
|
<p><a href="http://daniel.steigerwald.cz/">Daniel Steigerwald</a> is now using React within <a href="https://github.com/steida/este">Este</a>, which is a development stack for web apps in CoffeeScript that are statically typed using the Closure Library.</p>
|
|
<div class="highlight"><pre><code class="coffeescript language-coffeescript" data-lang="coffeescript"><span class="nv">este.demos.react.todoApp = </span><span class="nx">este</span><span class="p">.</span><span class="nx">react</span><span class="p">.</span><span class="nx">create</span> <span class="p">(</span><span class="o">`</span><span class="sr">/** @lends {React.ReactComponent.prototype} */</span><span class="o">`</span><span class="p">)</span>
|
|
<span class="nv">render: </span><span class="nf">-&gt;</span>
|
|
<span class="nx">@div</span> <span class="p">[</span>
|
|
<span class="nx">este</span><span class="p">.</span><span class="nx">demos</span><span class="p">.</span><span class="nx">react</span><span class="p">.</span><span class="nx">todoList</span> <span class="s">&#39;items&#39;</span><span class="o">:</span> <span class="nx">@state</span><span class="p">[</span><span class="s">&#39;items&#39;</span><span class="p">]</span>
|
|
<span class="k">if</span> <span class="nx">@state</span><span class="p">[</span><span class="s">&#39;items&#39;</span><span class="p">].</span><span class="nx">length</span>
|
|
<span class="nx">@p</span> <span class="s">&quot;</span><span class="si">#{</span><span class="nx">@state</span><span class="p">[</span><span class="s">&#39;items&#39;</span><span class="p">].</span><span class="nx">length</span><span class="si">}</span><span class="s"> items.&quot;</span>
|
|
<span class="nx">@form</span> <span class="s">&#39;onSubmit&#39;</span><span class="o">:</span> <span class="nx">@onFormSubmit</span><span class="p">,</span> <span class="p">[</span>
|
|
<span class="nx">@input</span>
|
|
<span class="s">&#39;onChange&#39;</span><span class="o">:</span> <span class="nx">@onChange</span>
|
|
<span class="s">&#39;value&#39;</span><span class="o">:</span> <span class="nx">@state</span><span class="p">[</span><span class="s">&#39;text&#39;</span><span class="p">]</span>
|
|
<span class="s">&#39;autoFocus&#39;</span><span class="o">:</span> <span class="kc">true</span>
|
|
<span class="s">&#39;ref&#39;</span><span class="o">:</span> <span class="s">&#39;textInput&#39;</span>
|
|
<span class="nx">@button</span> <span class="s">&quot;Add </span><span class="err">#</span><span class="si">#{</span><span class="nx">@state</span><span class="p">[</span><span class="s">&#39;items&#39;</span><span class="p">].</span><span class="nx">length</span> <span class="o">+</span> <span class="mi">1</span><span class="si">}</span><span class="s">&quot;</span>
|
|
<span class="p">]</span>
|
|
<span class="p">]</span>
|
|
</code></pre></div>
|
|
<p><a href="https://github.com/steida/este-library/blob/master/este/demos/thirdparty/react/start.coffee">Check it out on Github...</a></p>
|
|
<h2 id="react-stylus-boilerplate"><a href="#react-stylus-boilerplate">React Stylus Boilerplate</a></h2>
|
|
<p><a href="http://zaim.github.io/">Zaim Bakar</a> shared his boilerplate to get started with Stylus CSS processor.</p>
|
|
|
|
<blockquote>
|
|
<p>This is my boilerplate React project using Grunt as the build tool, and Stylus as my CSS preprocessor.</p>
|
|
|
|
<ul>
|
|
<li>Very minimal HTML boilerplate</li>
|
|
<li>Uses Stylus, with nib included</li>
|
|
<li>Uses two build targets:
|
|
|
|
<ul>
|
|
<li><code>grunt build</code> to compile JSX and Stylus into a development build</li>
|
|
<li><code>grunt dist</code> to minify and optimize the development build for production</li>
|
|
</ul></li>
|
|
</ul>
|
|
|
|
<p><a href="https://github.com/zaim/react-stylus-boilerplate">Check it out on Github...</a></p>
|
|
</blockquote>
|
|
<h2 id="webfui"><a href="#webfui">WebFUI</a></h2>
|
|
<p><a href="http://lisperati.com/">Conrad Barski</a>, author of the popular book <a href="http://landoflisp.com/">Land of Lisp</a>, wants to use React for his ClojureScript library called <a href="https://github.com/drcode/webfui">WebFUI</a>.</p>
|
|
|
|
<blockquote>
|
|
<p>I&#39;m the author of &quot;<a href="http://landoflisp.com/">Land of Lisp</a>&quot; and I love your framework. I built a somewhat similar framework a year ago <a href="https://github.com/drcode/webfui">WebFUI</a> aimed at ClojureScript. My framework also uses global event delegates, a global &quot;render&quot; function, DOM reconciliation, etc just like react.js. (Of course these ideas all have been floating around the ether for ages, always great to see more people building on them.)</p>
|
|
|
|
<p>Your implementation is more robust, and so I think the next point release of webfui will simply delegate all the &quot;hard work&quot; to react.js and will only focus on the areas where it adds value (enabling purely functional UI programming in clojurescript, and some other stuff related to streamlining event handling)
|
|
<figure><a href="https://groups.google.com/forum/#!msg/reactjs/e3bYersyd64/qODfcuBR9LwJ"><img src="/react/img/blog/landoflisp.png" alt=""></a></figure></p>
|
|
|
|
<p><a href="https://groups.google.com/forum/#!msg/reactjs/e3bYersyd64/qODfcuBR9LwJ">Read the full post...</a></p>
|
|
</blockquote>
|
|
</description>
|
|
<pubDate>2013-08-05T00:00:00-07:00</pubDate>
|
|
<link>http://facebook.github.io/react/blog/2013/08/05/community-roundup-6.html</link>
|
|
<guid isPermaLink="true">http://facebook.github.io/react/blog/2013/08/05/community-roundup-6.html</guid>
|
|
</item>
|
|
|
|
<item>
|
|
<title>Use React and JSX in Ruby on Rails</title>
|
|
<description><p>Today we&#39;re releasing a gem to make it easier to use React and JSX in Ruby on Rails applications: <a href="https://github.com/facebook/react-rails">react-rails</a>.</p>
|
|
|
|
<p>This gem has 2 primary purposes:</p>
|
|
|
|
<ol>
|
|
<li>To package <code>react.js</code> in a way that&#39;s easy to use and easy to update.</li>
|
|
<li>To allow you to write JSX without an external build step to transform that into JS.</li>
|
|
</ol>
|
|
<h2 id="packaging-react.js"><a href="#packaging-react.js">Packaging react.js</a></h2>
|
|
<p>To make <code>react.js</code> available for use client-side, simply add <code>react</code> to your manifest, and declare the variant you&#39;d like to use in your environment. When you use <code>:production</code>, the minified and optimized <code>react.min.js</code> will be used instead of the development version. For example:</p>
|
|
<div class="highlight"><pre><code class="ruby language-ruby" data-lang="ruby"><span class="c1"># config/environments/development.rb</span>
|
|
|
|
<span class="ss">MyApp</span><span class="p">:</span><span class="ss">:Application</span><span class="o">.</span><span class="n">configure</span> <span class="k">do</span>
|
|
<span class="n">config</span><span class="o">.</span><span class="n">react</span><span class="o">.</span><span class="n">variant</span> <span class="o">=</span> <span class="ss">:development</span>
|
|
<span class="c1"># use :production in production.rb</span>
|
|
<span class="k">end</span>
|
|
</code></pre></div><div class="highlight"><pre><code class="js language-js" data-lang="js"><span class="c1">// app/assets/javascript/application.js</span>
|
|
|
|
<span class="c1">//= require react</span>
|
|
</code></pre></div><h2 id="writing-jsx"><a href="#writing-jsx">Writing JSX</a></h2>
|
|
<p>When you name your file with <code>myfile.js.jsx</code>, <code>react-rails</code> will automatically try to transform that file. For the time being, we still require that you include the docblock at the beginning of the file. For example, this file will get transformed on request.</p>
|
|
<div class="highlight"><pre><code class="js language-js" data-lang="js"><span class="cm">/** @jsx React.DOM */</span>
|
|
<span class="nx">React</span><span class="p">.</span><span class="nx">renderComponent</span><span class="p">(</span><span class="o">&lt;</span><span class="nx">MyComponent</span><span class="o">/&gt;</span><span class="p">,</span> <span class="nb">document</span><span class="p">.</span><span class="nx">body</span><span class="p">)</span>
|
|
</code></pre></div><h2 id="asset-pipeline"><a href="#asset-pipeline">Asset Pipeline</a></h2>
|
|
<p><code>react-rails</code> takes advantage of the <a href="http://guides.rubyonrails.org/asset_pipeline.html">asset pipeline</a> that was introduced in Rails 3.1. A very important part of that pipeline is the <code>assets:precompile</code> Rake task. <code>react-rails</code> will ensure that your JSX files will be transformed into regular JS before all of your assets are minified and packaged.</p>
|
|
<h2 id="installation"><a href="#installation">Installation</a></h2>
|
|
<p>Installation follows the same process you&#39;re familiar with. You can install it globally with <code>gem install react-rails</code>, though we suggest you add the dependency to your <code>Gemfile</code> directly.</p>
|
|
</description>
|
|
<pubDate>2013-07-30T00:00:00-07:00</pubDate>
|
|
<link>http://facebook.github.io/react/blog/2013/07/30/use-react-and-jsx-in-ruby-on-rails.html</link>
|
|
<guid isPermaLink="true">http://facebook.github.io/react/blog/2013/07/30/use-react-and-jsx-in-ruby-on-rails.html</guid>
|
|
</item>
|
|
|
|
<item>
|
|
<title>React v0.4.1</title>
|
|
<description><p>React v0.4.1 is a small update, mostly containing correctness fixes. Some code has been restructured internally but those changes do not impact any of our public APIs.</p>
|
|
<h2 id="react"><a href="#react">React</a></h2>
|
|
<ul>
|
|
<li><code>setState</code> callbacks are now executed in the scope of your component.</li>
|
|
<li><code>click</code> events now work on Mobile Safari.</li>
|
|
<li>Prevent a potential error in event handling if <code>Object.prototype</code> is extended.</li>
|
|
<li>Don&#39;t set DOM attributes to the string <code>&quot;undefined&quot;</code> on update when previously defined.</li>
|
|
<li>Improved support for <code>&lt;iframe&gt;</code> attributes.</li>
|
|
<li>Added checksums to detect and correct cases where server-side rendering markup mismatches what React expects client-side.</li>
|
|
</ul>
|
|
<h2 id="jsxtransformer"><a href="#jsxtransformer">JSXTransformer</a></h2>
|
|
<ul>
|
|
<li>Improved environment detection so it can be run in a non-browser environment.</li>
|
|
</ul>
|
|
|
|
<p><a href="/react/downloads.html">Download it now!</a></p>
|
|
</description>
|
|
<pubDate>2013-07-26T00:00:00-07:00</pubDate>
|
|
<link>http://facebook.github.io/react/blog/2013/07/26/react-v0-4-1.html</link>
|
|
<guid isPermaLink="true">http://facebook.github.io/react/blog/2013/07/26/react-v0-4-1.html</guid>
|
|
</item>
|
|
|
|
<item>
|
|
<title>Community Round-up #5</title>
|
|
<description><p>We launched the <a href="https://www.facebook.com/react">React Facebook Page</a> along with the React v0.4 launch. 700 people already liked it to get updated on the project :)</p>
|
|
<h2 id="cross-browser-onchange"><a href="#cross-browser-onchange">Cross-browser onChange</a></h2>
|
|
<p><a href="http://benalpert.com/">Ben Alpert</a> from <a href="https://www.khanacademy.org/">Khan Academy</a> worked on a cross-browser implementation of <code>onChange</code> event that landed in v0.4. He wrote a blog post explaining the various browser quirks he had to deal with.</p>
|
|
|
|
<blockquote>
|
|
<p>First off, what is the input event? If you have an <code>&lt;input&gt;</code> element and want to receive events whenever the value changes, the most obvious thing to do is to listen to the change event. Unfortunately, change fires only after the text field is defocused, rather than on each keystroke. The next obvious choice is the keyup event, which is triggered whenever a key is released. Unfortunately, keyup doesn&#39;t catch input that doesn&#39;t involve the keyboard (e.g., pasting from the clipboard using the mouse) and only fires once if a key is held down, rather than once per inserted character.</p>
|
|
|
|
<p>Both keydown and keypress do fire repeatedly when a key is held down, but both fire immediately before the value changes, so to read the new value you have to defer the handler to the next event loop using <code>setTimeout(fn, 0)</code> or similar, which slows down your app. Of course, like keyup, neither keydown nor keypress fires for non-keyboard input events, and all three can fire in cases where the value doesn&#39;t change at all (such as when pressing the arrow keys).</p>
|
|
|
|
<p><a href="http://benalpert.com/2013/06/18/a-near-perfect-oninput-shim-for-ie-8-and-9.html">Read the full post...</a></p>
|
|
</blockquote>
|
|
<h2 id="react-samples"><a href="#react-samples">React Samples</a></h2>
|
|
<p>Learning a new library is always easier when you have working examples you can play with. <a href="https://github.com/jhw">jwh</a> put many of them on his <a href="https://github.com/jhw/react-samples">react-samples Github repo</a>.</p>
|
|
|
|
<blockquote>
|
|
<p>Some simple examples with Facebook&#39;s React framework</p>
|
|
|
|
<ul>
|
|
<li>Bootstrap action bar, modal and table <a href="https://rawgithub.com/jhw/react-samples/master/html/actionbar.html">#1</a>,
|
|
<a href="https://rawgithub.com/jhw/react-samples/master/html/bootstrap_actionbar.html">#2</a>,
|
|
<a href="https://rawgithub.com/jhw/react-samples/master/html/bootstrap_modal.html">#3</a>,
|
|
<a href="https://rawgithub.com/jhw/react-samples/master/html/bootstrap_striped_table.html">#4</a></li>
|
|
<li>Comments <a href="https://rawgithub.com/jhw/react-samples/master/html/comments1.html">#1</a>,
|
|
<a href="https://rawgithub.com/jhw/react-samples/master/html/comments2.html">#2</a></li>
|
|
<li>Data Table <a href="https://rawgithub.com/jhw/react-samples/master/html/datatable.html">#1</a>,
|
|
<a href="https://rawgithub.com/jhw/react-samples/master/html/datatable2.html">#2</a>,
|
|
<a href="https://rawgithub.com/jhw/react-samples/master/html/datatable3.html">#3</a>,
|
|
<a href="https://rawgithub.com/jhw/react-samples/master/html/datatable4.html">#4</a>,
|
|
<a href="https://rawgithub.com/jhw/react-samples/master/html/datatable5.html">#5</a></li>
|
|
<li>Filter Bar <a href="https://rawgithub.com/jhw/react-samples/master/html/filterbar.html">#1</a>,
|
|
<a href="https://rawgithub.com/jhw/react-samples/master/html/filterbar2.html">#2</a>,
|
|
<a href="https://rawgithub.com/jhw/react-samples/master/html/filterbar3.html">#3</a>,
|
|
<a href="https://rawgithub.com/jhw/react-samples/master/html/filterbar4.html">#4</a>,
|
|
<a href="https://rawgithub.com/jhw/react-samples/master/html/filterbar5.html">#5</a></li>
|
|
<li>Fundoo Rating <a href="https://rawgithub.com/jhw/react-samples/master/html/fundoo.html">#1</a></li>
|
|
<li>Line Char: <a href="https://rawgithub.com/jhw/react-samples/master/html/linechart.html">#1</a>,
|
|
<a href="https://rawgithub.com/jhw/react-samples/master/html/linechart2.html">#2</a></li>
|
|
<li>Multi tabs <a href="https://rawgithub.com/jhw/react-samples/master/html/multitabs.html">#1</a></li>
|
|
<li>Select <a href="https://rawgithub.com/jhw/react-samples/master/html/select.html">#1</a></li>
|
|
<li>Simple Tabs <a href="https://rawgithub.com/jhw/react-samples/master/html/simpletabs.html">#1</a>,
|
|
<a href="https://rawgithub.com/jhw/react-samples/master/html/simpletabs2.html">#2</a>,
|
|
<a href="https://rawgithub.com/jhw/react-samples/master/html/simpletabs3.html">#3</a>,
|
|
<a href="https://rawgithub.com/jhw/react-samples/master/html/simpletabs4.html">#4</a></li>
|
|
<li>Toggle <a href="https://rawgithub.com/jhw/react-samples/master/html/toggle.html">#1</a></li>
|
|
</ul>
|
|
</blockquote>
|
|
<h2 id="react-chosen-wrapper"><a href="#react-chosen-wrapper">React Chosen Wrapper</a></h2>
|
|
<p><a href="https://github.com/chenglou">Cheng Lou</a> wrote a wrapper for the <a href="http://harvesthq.github.io/chosen/">Chosen</a> input library called <a href="https://github.com/chenglou/react-chosen">react-chosen</a>. It took just 25 lines to be able to use jQuery component as a React one.</p>
|
|
<div class="highlight"><pre><code class="javascript language-javascript" data-lang="javascript"><span class="nx">React</span><span class="p">.</span><span class="nx">renderComponent</span><span class="p">(</span>
|
|
<span class="o">&lt;</span><span class="nx">Chosen</span> <span class="nx">noResultsText</span><span class="o">=</span><span class="s2">&quot;No result&quot;</span> <span class="nx">value</span><span class="o">=</span><span class="s2">&quot;Harvest&quot;</span> <span class="nx">onChange</span><span class="o">=</span><span class="p">{</span><span class="nx">doSomething</span><span class="p">}</span><span class="o">&gt;</span>
|
|
<span class="o">&lt;</span><span class="nx">option</span> <span class="nx">value</span><span class="o">=</span><span class="s2">&quot;Facebook&quot;</span><span class="o">&gt;</span><span class="nx">Facebook</span><span class="o">&lt;</span><span class="err">/option&gt;</span>
|
|
<span class="o">&lt;</span><span class="nx">option</span> <span class="nx">value</span><span class="o">=</span><span class="s2">&quot;Harvest&quot;</span><span class="o">&gt;</span><span class="nx">Harvest</span><span class="o">&lt;</span><span class="err">/option&gt;</span>
|
|
<span class="o">&lt;</span><span class="err">/Chosen&gt;</span>
|
|
<span class="p">,</span> <span class="nb">document</span><span class="p">.</span><span class="nx">body</span><span class="p">);</span>
|
|
</code></pre></div><h2 id="jsx-and-es6-template-strings"><a href="#jsx-and-es6-template-strings">JSX and ES6 Template Strings</a></h2>
|
|
<p><a href="http://domenicdenicola.com/">Domenic Denicola</a> wrote a slide deck about the great applications of ES6 features and one slide shows how we could use Template Strings to compile JSX at run-time without the need for a pre-processing phase.</p>
|
|
|
|
<figure><iframe src="http://www.slideshare.net/slideshow/embed_code/24187146?rel=0&startSlide=36" width="600" height="356" frameborder="0" marginwidth="0" marginheight="0" scrolling="no" style="border:1px solid #CCC;border-width:1px 1px 0;margin-bottom:5px" allowfullscreen webkitallowfullscreen mozallowfullscreen> </iframe></figure>
|
|
<h2 id="react-presentation"><a href="#react-presentation">React Presentation</a></h2>
|
|
<p><a href="http://tomocchino.com/">Tom Occhino</a> and <a href="https://github.com/jordwalke">Jordan Walke</a>, React developers, did a presentation of React at Facebook Seattle&#39;s office. Check out the first 25 minutes for the presentation and the remaining 45 for a Q&amp;A. I highly recommend you watching this video.</p>
|
|
|
|
<figure><iframe width="650" height="400" src="//www.youtube.com/embed/XxVg_s8xAms" frameborder="0" allowfullscreen></iframe></figure>
|
|
<h2 id="docs"><a href="#docs">Docs</a></h2>
|
|
<p><a href="http://www.petehunt.net/">Pete Hunt</a> rewrote the entirety of the docs for v0.4. The goal was to add more explanation about why we built React and what the best practices are.</p>
|
|
|
|
<blockquote>
|
|
<p>Guides</p>
|
|
|
|
<ul>
|
|
<li><a href="/react/docs/why-react.html">Why React?</a></li>
|
|
<li><a href="/react/docs/displaying-data.html">Displaying Data</a>
|
|
|
|
<ul>
|
|
<li><a href="/react/docs/jsx-in-depth.html">JSX in Depth</a></li>
|
|
<li><a href="/react/docs/jsx-gotchas.html">JSX Gotchas</a></li>
|
|
</ul></li>
|
|
<li><a href="/react/docs/interactivity-and-dynamic-uis.html">Interactivity and Dynamic UIs</a></li>
|
|
<li><a href="/react/docs/multiple-components.html">Multiple Components</a></li>
|
|
<li><a href="/react/docs/reusable-components.html">Reusable Components</a></li>
|
|
<li><a href="/react/docs/forms.html">Forms</a></li>
|
|
<li><a href="/react/docs/working-with-the-browser.html">Working With the Browser</a>
|
|
|
|
<ul>
|
|
<li><a href="/react/docs/more-about-refs.html">More About Refs</a></li>
|
|
</ul></li>
|
|
<li><a href="/react/docs/tooling-integration.html">Tooling integration</a></li>
|
|
<li><a href="/react/docs/top-level-api.html">Reference</a></li>
|
|
</ul>
|
|
</blockquote>
|
|
</description>
|
|
<pubDate>2013-07-23T00:00:00-07:00</pubDate>
|
|
<link>http://facebook.github.io/react/blog/2013/07/23/community-roundup-5.html</link>
|
|
<guid isPermaLink="true">http://facebook.github.io/react/blog/2013/07/23/community-roundup-5.html</guid>
|
|
</item>
|
|
|
|
<item>
|
|
<title>React v0.4.0</title>
|
|
<description><p>Over the past 2 months we&#39;ve been taking feedback and working hard to make React even better. We fixed some bugs, made some under-the-hood improvements, and added several features that we think will improve the experience developing with React. Today we&#39;re proud to announce the availability of React v0.4!</p>
|
|
|
|
<p>This release could not have happened without the support of our growing community. Since launch day, the community has contributed blog posts, questions to the <a href="http://groups.google.com/group/reactjs">Google Group</a>, and issues and pull requests on GitHub. We&#39;ve had contributions ranging from documentation improvements to major changes to React&#39;s rendering. We&#39;ve seen people integrate React into the tools they&#39;re using and the products they&#39;re building, and we&#39;re all very excited to see what our budding community builds next!</p>
|
|
|
|
<p>React v0.4 has some big changes. We&#39;ve also restructured the documentation to better communicate how to use React. We&#39;ve summarized the changes below and linked to documentation where we think it will be especially useful.</p>
|
|
|
|
<p>When you&#39;re ready, <a href="/react/downloads.html">go download it</a>!</p>
|
|
<h3 id="react"><a href="#react">React</a></h3>
|
|
<ul>
|
|
<li>Switch from using <code>id</code> attribute to <code>data-reactid</code> to track DOM nodes. This allows you to integrate with other JS and CSS libraries more easily.</li>
|
|
<li>Support for more DOM elements and attributes (e.g., <code>&lt;canvas&gt;</code>)</li>
|
|
<li>Improved server-side rendering APIs. <code>React.renderComponentToString(&lt;component&gt;, callback)</code> allows you to use React on the server and generate markup which can be sent down to the browser.</li>
|
|
<li><code>prop</code> improvements: validation and default values. <a href="http://facebook.github.io/react/blog/2013/07/11/react-v0-4-prop-validation-and-default-values.html">Read our blog post for details...</a></li>
|
|
<li>Support for the <code>key</code> prop, which allows for finer control over reconciliation. <a href="http://facebook.github.io/react/docs/multiple-components.html">Read the docs for details...</a></li>
|
|
<li>Removed <code>React.autoBind</code>. <a href="http://facebook.github.io/react/blog/2013/07/02/react-v0-4-autobind-by-default.html">Read our blog post for details...</a></li>
|
|
<li>Improvements to forms. We&#39;ve written wrappers around <code>&lt;input&gt;</code>, <code>&lt;textarea&gt;</code>, <code>&lt;option&gt;</code>, and <code>&lt;select&gt;</code> in order to standardize many inconsistencies in browser implementations. This includes support for <code>defaultValue</code>, and improved implementation of the <code>onChange</code> event, and circuit completion. <a href="http://facebook.github.io/react/docs/forms.html">Read the docs for details...</a></li>
|
|
<li>We&#39;ve implemented an improved synthetic event system that conforms to the W3C spec.</li>
|
|
<li>Updates to your component are batched now, which may result in a significantly faster re-render of components. <code>this.setState</code> now takes an optional callback as its second parameter. If you were using <code>onClick={this.setState.bind(this, state)}</code> previously, you&#39;ll want to make sure you add a third parameter so that the event is not treated as the callback.</li>
|
|
</ul>
|
|
<h3 id="jsx"><a href="#jsx">JSX</a></h3>
|
|
<ul>
|
|
<li>Support for comment nodes <code>&lt;div&gt;{/* this is a comment and won&#39;t be rendered */}&lt;/div&gt;</code></li>
|
|
<li>Children are now transformed directly into arguments instead of being wrapped in an array
|
|
E.g. <code>&lt;div&gt;&lt;Component1/&gt;&lt;Component2/&gt;&lt;/div&gt;</code> is transformed into <code>React.DOM.div(null, Component1(null), Component2(null))</code>.
|
|
Previously this would be transformed into <code>React.DOM.div(null, [Component1(null), Component2(null)])</code>.
|
|
If you were using React without JSX previously, your code should still work.</li>
|
|
</ul>
|
|
<h3 id="react-tools"><a href="#react-tools">react-tools</a></h3>
|
|
<ul>
|
|
<li>Fixed a number of bugs when transforming directories</li>
|
|
<li>No longer re-write <code>require()</code>s to be relative unless specified</li>
|
|
</ul>
|
|
</description>
|
|
<pubDate>2013-07-17T00:00:00-07:00</pubDate>
|
|
<link>http://facebook.github.io/react/blog/2013/07/17/react-v0-4-0.html</link>
|
|
<guid isPermaLink="true">http://facebook.github.io/react/blog/2013/07/17/react-v0-4-0.html</guid>
|
|
</item>
|
|
|
|
</channel>
|
|
</rss>
|