-
Notifications
You must be signed in to change notification settings - Fork 47.6k
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request #686 from vjeux/community_12
Community Round-up #12
- Loading branch information
Showing
5 changed files
with
105 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,105 @@ | ||
--- | ||
title: "Community Round-up #12" | ||
layout: post | ||
author: Vjeux | ||
--- | ||
|
||
React got featured on the front-page of Hacker News thanks to the Om library. If you try it out for the first time, take a look at the [docs](/react/docs/getting-started.html) and do not hesitate to ask questions on the [Google Group](http://groups.google.com/group/reactjs), [IRC](irc://chat.freenode.net/reactjs) or [Stack Overflow](http://stackoverflow.com/questions/tagged/reactjs). We are trying our best to help you out! | ||
|
||
## The Future of Javascript MVC | ||
|
||
[David Nolan](http://swannodette.github.io/) announced Om, a thin wrapper on-top of React in ClojureScript. It stands out by only using immutable data structures. This unlocks the ability to write a very efficient [shouldComponentUpdate](http://facebook.github.io/react/docs/component-specs.html#updating-shouldcomponentupdate) and get huge performance improvements on some tasks. | ||
|
||
> We've known this for some time over here in the ClojureScript corner of the world - all of our collections are immutable and modeled directly on the original Clojure versions written in Java. Modern JavaScript engines have now been tuned to the point that it's no longer uncommon to see collection performance within 2.5X of the Java Virtual Machine. | ||
> | ||
> Wait, wait, wait. What does the performance of persistent data structures have to do with the future of JavaScript MVCs? | ||
> | ||
> A whole lot. | ||
> <figure>[![](/react/img/blog/om-backbone.png)](http://swannodette.github.io/2013/12/17/the-future-of-javascript-mvcs/)</figure> | ||
> | ||
> [Read the full article...](http://swannodette.github.io/2013/12/17/the-future-of-javascript-mvcs/) | ||
|
||
|
||
## Scroll Position with React | ||
|
||
Managing the scroll position when new content is inserted is usually very tricky to get right. [Vjeux](http://blog.vjeux.com/) discovered that [componentWillUpdate](http://facebook.github.io/react/docs/component-specs.html#updating-componentwillupdate) and [componentDidUpdate](http://facebook.github.io/react/docs/component-specs.html#updating-componentdidupdate) were triggered exactly at the right time to manage the scroll position. | ||
|
||
> We can check the scroll position before the component has updated with componentWillUpdate and scroll if necessary at componentDidUpdate | ||
> | ||
> ``` | ||
componentWillUpdate: function() { | ||
var node = this.getDOMNode(); | ||
this.shouldScrollBottom = | ||
(node.scrollTop + node.offsetHeight) === node.scrollHeight; | ||
}, | ||
componentDidUpdate: function() { | ||
if (this.shouldScrollBottom) { | ||
var node = this.getDOMNode(); | ||
node.scrollTop = node.scrollHeight | ||
} | ||
}, | ||
``` | ||
> | ||
> [Check out the blog article...](http://blog.vjeux.com/2013/javascript/scroll-position-with-react.html) | ||
|
||
## Lights Out | ||
|
||
React declarative approach is well suited to write games. [Cheng Lou](https://github.com/chenglou) wrote the famous Lights Out game in React. It's a good example of use of [TransitionGroup](http://facebook.github.io/react/docs/animation.html) to implement animations. | ||
<figure>[![](/react/img/blog/lights-out.png)](http://chenglou.github.io/react-lights-out/)</figure> | ||
|
||
[Try it out!](http://chenglou.github.io/react-lights-out/) | ||
|
||
|
||
## Reactive Table Bookmarklet | ||
|
||
[Stoyan Stefanov](http://www.phpied.com/) wrote a bookmarklet to process tables on the internet. It adds a little "pop" button that expands to a full-screen view with sorting, editing and export to csv and json. | ||
<figure>[![](/react/img/blog/reactive-bookmarklet.png)](http://www.phpied.com/reactivetable-bookmarklet/)</figure> | ||
|
||
[Check out the blog post...](http://www.phpied.com/reactivetable-bookmarklet/) | ||
|
||
|
||
## MontageJS Tutorial in React | ||
|
||
[Ross Allen](https://twitter.com/ssorallen) implemented [MontageJS](http://montagejs.org/)'s [Reddit tutorial](http://montagejs.org/docs/tutorial-reddit-client-with-montagejs.html) in React. This is a good opportunity to compare the philosophies of the two libraries. | ||
|
||
<iframe width="100%" height="300" src="http://jsfiddle.net/ssorallen/fEsYt/embedded/result,html,js" allowfullscreen="allowfullscreen" frameborder="0"></iframe> | ||
|
||
[View the source on JSFiddle...](http://jsfiddle.net/ssorallen/fEsYt/) | ||
|
||
## Writing Good React Components | ||
|
||
[William Högman Rudenmalm](http://blog.whn.se/) wrote an article on how to write good React components. This is full of good advice. | ||
|
||
> The idea of dividing software into smaller parts or components is hardly new - It is the essance of good software. The same principles that apply to software in general apply to building React components. That doesn’t mean that writing good React components is just about applying general rules. | ||
> | ||
> The web offers a unique set of challenges, which React offers interesting solutions to. First and foremost among these solutions is the what is called the Mock DOM. Rather than having user code interface with the DOM in a direct fashion, as is the case with most DOM manipulation libraries. | ||
> | ||
> You build a model of how you want the DOM end up like. React then inserts this model into the DOM. This is very useful for updates because React simply compares the model or mock DOM against the actual DOM, and then only updates based on the difference between the two states. | ||
> | ||
> [Read the full article ...](http://blog.whn.se/post/69621609605/writing-good-react-components) | ||
|
||
## Hoodie React TodoMVC | ||
|
||
[Sven Lito](http://svenlito.com/) integrated the React TodoMVC example within an [Hoodie](http://hood.ie/) web app environment. This should let you get started using Hoodie and React. | ||
|
||
``` | ||
hoodie new todomvc -t "hoodiehq/hoodie-react-todomvc" | ||
``` | ||
|
||
[Check out on GitHub...](https://github.com/hoodiehq/hoodie-react-todomvc) | ||
|
||
## JSX Compiler | ||
|
||
Ever wanted to have a quick way to see what a JSX tag would be converted to? [Tim Yung](http://www.yungsters.com/) made a page for it. | ||
<figure>[![](/react/img/blog/jsx-compiler.png)](http://facebook.github.io/react/jsx-compiler.html)</figure> | ||
|
||
[Try it out!](http://facebook.github.io/react/jsx-compiler.html) | ||
|
||
|
||
|
||
## Random Tweet | ||
|
||
<center><blockquote class="twitter-tweet" lang="en"><p>.<a href="https://twitter.com/jordwalke">@jordwalke</a> lays down some truth <a href="http://t.co/AXAn0UlUe3">http://t.co/AXAn0UlUe3</a>, optimizing your JS application shouldn't force you to rewrite so much code <a href="https://twitter.com/search?q=%23reactjs&src=hash">#reactjs</a></p>— David Nolen (@swannodette) <a href="https://twitter.com/swannodette/statuses/413780079249215488">December 19, 2013</a></blockquote></center> |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.