cartodb/Backbone.Undo.js
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Minor changes

Browse Source
This commit is contained in:
Oliver Sartun 2013-05-28 16:53:46 +02:00
parent 7f9b2dbf3b
commit d8cd371991
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@ -5,23 +5,23 @@ An extremely simple Undo-Manager for Backbone.js
#### Advantages of Backbone.Undo.js #### Advantages of Backbone.Undo.js
* Easy to include and exclude * **Easy to include and exclude**
In comparison to other Backbone-based undo-managers like *memento*, you don't have to modify your models In comparison to other Backbone-based undo-managers like *memento*, you don't have to modify your models
or collections to use Backbone.Undo.js. You can have your whole application already set up with all the or collections to use Backbone.Undo.js. You can have your whole application already set up with all the
models and collections you need and then add the undo-manager. That makes it easy to not only include models and collections you need and then add the undo-manager. That makes it easy to not only include
Backbone.Undo.js, but also to remove it again if you don't longer want to use it at some point. Backbone.Undo.js, but also to remove it again if you don't longer want to use it at some point.
* Uses Backbone-Events * **Uses Backbone-Events**
To detect an action, Backbone.Undo.js listens to the events Backbone triggeres automatically. You don't have To detect an action, Backbone.Undo.js listens to the events Backbone triggeres automatically. You don't have
to do anything. You don't have to `store()` or `restore()` certain states. Nothing. to do anything. You don't have to `store()` or `restore()` certain states. Nothing.
* Memory-friendly * **Only what's necessary**
Backbone.Undo.js only stores changes, instead of snapshots (clones of models/collections). Backbone.Undo.js only stores the changes, instead of taking snapshots of the models' / collections' current state.
* Optimized for Usability * **Optimized for Usability**
In a sophisticated webapp one click of the user might trigger several Backbone-Events which are stored as In a sophisticated webapp one click of the user might trigger several Backbone-Events which are stored as
several Undo-Actions within the Undo-Stack. If the user then calls `undo()` it shouldn't just undo the latest several Undo-Actions within the Undo-Stack. If the user then calls `undo()` it shouldn't just undo the latest