What prompted you to write your own, rather than going with something like (the excellent and liberally licensed) Handsontable?
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[0] 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):
* http://lauris.github.io/development/2014/08/25/work-and-open...
* http://lauris.github.io/datazenit/2014/08/29/open-source-wor...
These articles may shed some light on why did we start development on our own library.
[0] 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....