Start on section 04

This commit is contained in:
petehunt
2013-07-14 17:07:57 -07:00
parent a36bcd33c6
commit 151997b1e1
2 changed files with 18 additions and 1 deletions
+3 -1
View File
@@ -27,7 +27,8 @@ Handling user input
Scaling up: using multiple components
- Motivation: separate concerns
- Composition example
- Handling events
- Ownership
- Data flow (one-way data binding)
- A note on performance
- You should build a reusable component library (CSS, testing etc)
- Mixins
@@ -41,6 +42,7 @@ Forms
Touching the DOM
- Refs / getDOMNode()
- Component lifecycle
- DOM differences
Integrating with other UI libraries
- Using jQuery plugins
+15
View File
@@ -0,0 +1,15 @@
# Scaling Up: Using Multiple Components
So far, we've looked at how to write a single component to display data and handle user input. Next let's examine one of React's finest features: composability.
## Motivation: separation of concerns
By building modular components that reuse other components using well-definted interfaces, you get much of the same benefits that you get by using functions or classes. Specifically you can *separate the different concerns* of your app however you please simply by building new components. By building a custom component library for your application, you are expressing your UI in a way that best fits your domain.
## Composition example
```javascript
/** @jsx React.DOM */
```