Skip to content

Commit 508af5d

Browse files
author
Vlad Balin
committed
Updated readme
1 parent 738e064 commit 508af5d

File tree

1 file changed

+7
-4
lines changed

1 file changed

+7
-4
lines changed

README.md

Lines changed: 7 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,5 @@
11
# NestedReact
2-
This is React add-on providing advanced state management to React applications and convergence layer for intermixing React components and Backbone Views.
3-
4-
Brief feature list:
2+
This is React add-on providing advanced data binding and state management to React applications, as well as convergence layer for intermixing React components and Backbone Views.
53

64
- Advanced component's state management with [NestedTypes](https://github.com/Volicon/backbone.nestedTypes).
75
- Comprehensive two-way data binding - [Guide to Data Binding Use Cases](/example/databinding.md)
@@ -10,7 +8,12 @@ Brief feature list:
108
- Backbone Views can be used as React components. `<React.subview View={ MyView } />`
119
- Simplified refactoring of Backbone Views to React components. `this.$`, `this.$el`, `this.$( sel )`, `this.model` works for React components too, as well as `this.trigger` and `this.listenTo`.
1210

13-
Thus, if you have Bakcbone application and want to start writing with React - you have no excuses any more. Wanna keep some of your cool Views? They works just fine? Keep 'em. And use them in yout new components, written with React, which you will use in other Backbone Views.
11+
Check out [TodoMVC](https://github.com/gaperton/todomvc-nestedreact) example to see, how nice circular data flow
12+
looks without `Flux`.
13+
14+
Also, if you have Backbone application and want to start writing with React - you have no excuses any more.
15+
Wanna keep some of your cool Views? They works just fine? Keep 'em.
16+
And use them in your new components written with React, which in turn you may use in other Backbone Views.
1417

1518
# Breaking changes introduced in 0.3
1619
- `component.createView( props )` doesn't work any more, use `new component.View( props )` instead.

0 commit comments

Comments
 (0)