TodoMVC app rendering function implemented using virtual-dom
npm install --save virtual-todos
Then from the main application that uses virtual-dom call the single exported function, passing an object with a list of todos
var render = require('virtual-todos')
var virtualTree = render(Todos)The virtual tree will become DOM tree, and the user will try to add, remove and mark todos
as done. Thus we need to have the following callbacks on the Todos object. Each may be a noop.
var Todos = {
items: [{
what: 'do something',
id: 'ex102'
}],
add: function (what) {},
remove: function (item) {},
mark: function (id, done) {},
clearCompleted: function () {}
}I recommend generating Todos.items using fake-todos
I have full application using this rendering function at hydrate-vdom-todo in both online src/app.js and offline hydrate-app.js modes.
- fake-todos to generate fake todo items
- todomvc-model is the model that keeps todo items and responds to outside events
Author: Gleb Bahmutov © 2015
License: MIT - do anything with the code, but don't blame me if it does not work.
Spread the word: tweet, star on github, etc.
Support: if you find any problems with this module, email / tweet / open issue on Github
Copyright (c) 2015 Gleb Bahmutov
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.