It's possible I'll add a more traditional 'controller' to the mix at some point, but I mostly wanted a similar structure to that of Backbone, without the need for jQuery/underscore.
For how small the library is, this is pretty fantastic though. Significantly smaller than Backbone for similar syntax.
I can't seem to edit the title of the HN article anymore. Must be past a certain time or something.
What is the main advantage of this over Backbone?
For most of my work, I'll also be sticking to Backbone or something more supported/fully-featured. But I do have tinsy projects here and there that are mobile-focused one-offs that work really well with something like this. I found myself recreating this thing over and over, so I figured I'd just standardize it for me and see if anyone else felt the same need. :)
Thanks for checking it out and for the feedback!
- Tiny footprint for mobile networks (~5kb minified).
- Extremely fast DOM query/selection engine. No need for jQuery!
- Mobile first - no legacy hackery for ie < 10.
- Great for spinning up small, mobile-specific apps.
To Do
- More useful event delegation. Currently, views must call _setElement() every time they render new DOM elements
-Currently no router for fancy SPA style urls
Installation
npm install ity