Looks pretty feature-full, and I really like the idea of compression / decompression of data for the browser. I don't like how complicated the PourOver API seems to be, but maybe that's just a side-effect of it being so feature-rich.
We open-sourced our client-side datatable, Knockout Datatable. [0] While it definitely doesn't come shipped with as many of the niceties of Pourover, the built-in ':'-delimeted filtering is really handy for quickly providing both searching and a dropdown of pre-built filter choices. Additionally, it uses Knockout.js which, in my opinion, is much easier to extend and use than many other client-side MV* frameworks.
This looks really useful. I may take a stab at creating a Node.js encoder later today. If it can integrate nicely with Express and/or Restify and use content negotiation to allow the client to specify when it has support for Tamper then that would be a very useful piece of middleware.
We open-sourced our client-side datatable, Knockout Datatable. [0] While it definitely doesn't come shipped with as many of the niceties of Pourover, the built-in ':'-delimeted filtering is really handy for quickly providing both searching and a dropdown of pre-built filter choices. Additionally, it uses Knockout.js which, in my opinion, is much easier to extend and use than many other client-side MV* frameworks.
[0] https://github.com/immense/knockout-datatable