That's an interesting way of showing a calendar. Is this common practice? I've never seen this before. I think the only yearly calendar I've seen more often lately is the one used on the GitHub profiles (here's a d3 one: <a href="http://bl.ocks.org/mbostock/4063318" rel="nofollow">http://bl.ocks.org/mbostock/4063318</a>).
I'd like to see an option to move the start of the week (first column and bolded column) to Monday (for those of us who prefer w/c monday).<p>I'll have a go myself when I get home, if I'm successful I'll submit a pull request.
Sorry for asking this here, but I'm trying wrap my head around React.
With the fact that we want to isolate styles for each component, how do we go about theming the components later on?
You might consider some people won't be able to use this calendar as-is; it isn't accessible. Consider <a href="http://www.456bereastreet.com/archive/201302/making_elements_keyboard_focusable_and_clickable/" rel="nofollow">http://www.456bereastreet.com/archive/201302/making_elements...</a> and perhaps change the spans to native HTML elements with visual and keyboard focus. Thanks for sharing!
I'm confused.<p>1. This is a fork from Hanse Kristian, who doesn't appear to work for your company. That is, it doesn't look like BelkaLab did anything but change package.json to name itself as the author.<p>2. It's a bit confusing why you put the generated demo.js file as part of the repository and have npm (.npmignore) ignore the src files. Is there something special about this demo.js file instead of it being browserify output?
Nice work!!.<p>Side comment: I was expecting some sort of a 'marketplace' to emerge for react components. I am surprised by so few reusable react components.
Is that really worth showing to HN? I mean, I dont want to be rude -- your code is ok, no problem here -- but it's not even a library, it is just a widget in 200 LOC, that renders a single table. What's the achievement here?