The library for web and native user interfaces.
Start on section 04
petehunt committed
Jul 10, 2013 at 17:11 UTC
151997b1e1ab28c39f2ef7c05d0d705c4a418df4
2 files changed
+18
-1
docs/docs/refactor/00-table-of-contents.md
+3
-1
@@ -27,7 +27,8 @@ Handling user input
27
Scaling up: using multiple components
28
- Motivation: separate concerns
29
- Composition example
30
-- Handling events
30
+- Ownership
31
+- Data flow (one-way data binding)
32
- A note on performance
33
- You should build a reusable component library (CSS, testing etc)
34
- Mixins
@@ -41,6 +42,7 @@ Forms
42
Touching the DOM
43
- Refs / getDOMNode()
44
- Component lifecycle
45
+- DOM differences
46
47
Integrating with other UI libraries
48
- Using jQuery plugins
docs/docs/refactor/04-scaling-up.md
new
+15
@@ -0,0 +1,15 @@
1
+# Scaling Up: Using Multiple Components
2
+
3
+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.
4
+
5
+## Motivation: separation of concerns
6
+
7
+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.
8
+
9
+## Composition example
10
+
11
+```javascript
12
+/** @jsx React.DOM */
13
+
14
+
15
+```
\ No newline at end of file