There are quite a few open source grids out there already. What features are you planning and how are you going to set this apart from the other grids. For instance, my favorite grid is dgrid [1]. Go to their main site and go to the features [2] (scrolling down just a bit there will give you a comparison table to other grids) and let us know if you plan on implementing any of those (especially i18n) or if you're going to have any differentiating features.<p>[1] -- <a href="https://github.com/sitepen/dgrid" rel="nofollow">https://github.com/sitepen/dgrid</a><p>[2] -- <a href="http://dojofoundation.org/packages/dgrid/#features" rel="nofollow">http://dojofoundation.org/packages/dgrid/#features</a>
I'm a little surprised at the comments asking if another grid is needed since "theres other open source projects out there like the one I use at work (insert crappy grid here)".<p>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.<p>I've yet to see one that:<p>- 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.
From a dev's point of view, as someone who has been exhaustively searching for the perfect JS data grid editor for a few years now:<p>What prompted you to write your own, rather than going with something like (the excellent and liberally licensed) Handsontable?
From a user perspective. providing the bower or component support will be better, and maybe you should place the dependency(jquery) in bower.json or component.json. but not directly in git folder.
Haven't looked at the code throughly, but from a quick glance looks like a grid I'd considering using in a personal project vs. the all the other crappy grids out there.