-- https://github.com/sitepen/dgrid
 -- http://dojofoundation.org/packages/dgrid/#features
Personally I spent ages waiting for WaveMaker to move to 1.7 and start using dgrid. Before I gave up on WaveMaker and dojo toolkit in favour of other technologies.
After first glance it seems that Dgrid requires dojo framework which I have no interest to depend on and also provides too much functionality for us. Datazenit needs something simple, stable and extensible. Sensei Grid will definitely have just a tiny fraction of Dgrid features. If you need something fully featured and complex, then Sensei Grid is not for you and you should stick with Dgrid or any other alternative.
Nice. I wish more developers took this approach. I've lost count of how many times I needed some specific functionality (that was advanced/complex enough to make me not want to write it on my own) and ended up using a gigantic library that came with a gazillion other features that I never used.
There really aren't a whole lot of open source grids that compete with some of the commercial solutions like extJS or kendoUI. These suck because you can't use the data grid in piecemeal fashion, you have to adopt an entire widget library.
I've yet to see one that:
- Is lightweight and standalone.
- Is easy to modify the look and feel
- Has good performance with tons of rows
- Has a super easy api
- Integrates easily with client side mvc frameworks.
What prompted you to write your own, rather than going with something like (the excellent and liberally licensed) Handsontable?
There are currently 571 open issues for Handsontable on Github. Each new release breaks something major and we can't wait forever for them to fix the issues. I wrote two blog posts regarding this (without mentioning Handsontable, but it was the library in question):
These articles may shed some light on why did we start development on our own library.
 Handsontable open issues on Github - https://github.com/handsontable/jquery-handsontable/issues
Any plans for developing Sensei Grid past what your use case requires? I hear all the cool kids get to paste cell ranges into their grid plugins :)
Sensei Grid will be kept simple, but additional functionality will be provided through plugins. I don't want to flood the core grid with functionality that would lead to complexity. However smart pasting is something I would consider including in the core.
Btw I just updated README.me file and added goals, blog posts and other info related to Sensei Grid - https://github.com/datazenit/sensei-grid/blob/master/README....
EDIT: Found the tree demo:
There are more demos here: