Hey there! Nifty little project :) A few questions: - Is it made for a specific use-cases? I.e. is it meant to replace the classic month-by-month date pickers or something else entirely? - Have you considered making it responsive? - How big is the final dist version? I see 200kb one place and 800kb another. - I think the default theme could be a bit more neutral and clean in it's color choice, here's my take on it: https://dl.dropboxusercontent.com/u/2192236/react-yearly-calendar_redesign.png
Yes, it's for a specific use-case. We designed that for a tariff configuration software connected to specific hardware (http://belka.us/en/ucs-software-configurator-for-internet-of-things/). Basically we needed it to display how an year is subdivided into 4 different periods. Here we also highlighted the working, festive and prefestive days. I think it turned out to be an interesting layout, you can see it here: http://postimg.org/image/4yqaywm2r/
Yes, and I don't think this view make sense in a smaller screen. Do you have any idea on how to show all this information in less space?
Thanks for the fast redesign. It looks way better. When I will have time I could push it into master. Regarding the final dist version I will ask Giovanni which is the author, I just worked on the design part but I'm not involved in the code.
Hi Lasse! I used your own mockup as inspiration for the little restyling we did to this component! You can find the discussion here: https://www.designernews.co/stories/65223-show-dn-reactyearlycalendar-updates-gets-a-fresh-look-and-new-features
It is cool to see an entire year in a component, but it is actually hard to decipher quickly by scanning. I think people are more used to each month broken out in month blocks with Sunday through Saturday rows (quicker to scan / pick the month / date they are interested in...). I am also not sure how actually useful this would be within an application somewhere... what are the actual goals of how a person would interact with this?
Hey Nick, I answered that in the previous comment. It was for a very specific case. We had to show quite a lot of data. Feel free to ask me more questions if the explanation I wrote in the other comment is not enough.