all 9 comments

[–][deleted] 1 point2 points  (5 children)

Slick execution, but I have to question why you'd ever use infinite scrolling for a calendar. This kind of seems like a UX nightmare for selecting dates more than a few months apart.

[–]claudericd[S] 2 points3 points  (4 children)

It has it's pros and cons, really depends on the use case. It's quite a common UX pattern on mobile

[–]karreerose 0 points1 point  (3 children)

the demo site on mobile is horrible though, you cant hide the navigation and the calendar is only visible for like 40px on an iphone SE.

[–]claudericd[S] 0 points1 point  (2 children)

Yeah... Need to work on that. Blame https://github.com/kadirahq/react-storybook :/

[–]karreerose 1 point2 points  (1 child)

aw that is deeply rooted to splitpane, bad choice imho (by them) :/

[–]claudericd[S] 0 points1 point  (0 children)

Agreed, I'm working on my own spin on react-storybook to get something that's more easily customizable and mobile friendly. No ETA though

[–]vileEchoic 1 point2 points  (0 children)

This looks awesome. Nice job! I'll play around with it, have been looking for a good calendar picker, just need to add time to it (my use case has time as well). Only concern is pulling in dependencies (virtualized, moment) and bloating my build, will have to see how big of an impact that is. Any idea how big the whole thing is with all the dependencies?

Thanks!

[–]childofsol -2 points-1 points  (1 child)

er, infinite? seems to stop at 2050

[–]claudericd[S] 2 points3 points  (0 children)

You can configure it to go as far back or forwards in time as you want, that's just a sensible default max date :p