oesmith

6 ms·

31.
by oesmith 14y ago
I really don't like the idea of "no controller tests at all" as a best practice. If you're having to mixin Rack::Test::Methods to write your "full-coverage" integration spec, then you're really writing a controller test. It should go in
32.
by oesmith 14y ago
... and that's why I unsubscribed from LRUG this afternoon. There's more discussion about recruiters than ANYTHING ELSE.
33.
Draw simple, easy line charts and donut charts with Morris.js v0.3.0(oesmith.github.com)
1 points by oesmith 14y ago|0 comments
34.
by oesmith 14y ago
> The relatively few websites which genuinely might be jeopardising user's privacy - Facebook, Google, Amazon etc - tend to be large, ubiquitous and mostly ad networks. The average 10 page company website is not technically sophisticate
35.
by oesmith 15y ago
Not yet, but it'll be an easy fix. https://github.com/oesmith/morris.js/issues/12
36.
by oesmith 15y ago
Thanks! Refactoring redraw() is high up on my list of priorities now that other people can see the code ;)
37.
by oesmith 15y ago
It uses Raphaël.js to insert an SVG (or VML on old IE) element into the container. There's definite potential for hooking into DOM events, although there's no code to support that at the moment. Zooming/panning isn't something I've had a n
38.
by oesmith 15y ago
Simplicity was definitely the prime motivator when I chose to write the graphing code from scratch for howmanyleft.co.uk (instead of using flot or similar). I also wanted something that worked reasonably well on mobile and desktop. Morris.
39.
by oesmith 15y ago
This is my first (proper) open-source release. I'd be very grateful for feedback from HN!
40.
Morris.js: Pretty time-series line graphs(oesmith.github.com)
169 points by oesmith 15y ago|25 comments