Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Show HN: One Page Calendar 2020

davebakker.io

Post reply on HN
Print view View original

101–108 of 108 posts

Re: Show HN: One Page Calendar 2020

#101

Post by alabut »

barroomhero wrote: post #66
joelanman wrote: post #50

A few years back I took part in an online design challenge to make a pocket calendar - it was a lot of fun, my designs are here: https://www.flickr.com/photos/joelanman/albums/7215759450272... One of them is very similar to this one (Design 2) - I was tidying up someone else's idea. Dunno if David Seah's was related in any way or just people came up with the same idea.

Design 3 is quite nice. For me, it's the quickest to read.

Agreed. I love stacking the months like that and turning it into a never-ending river of days, looks like it'd be easier to estimate the length of time between two different months.

Re: Show HN: One Page Calendar 2020

#102

Post by kseistrup »

tzs wrote: post #98
kseistrup wrote: post #78

This reminds me of the Doomsday algorithm¹. The doomsday for 2020 falls on a saturday, which is aligned neatly as the diagonal in the one page calendar. Once you know the doomsday of a given year, you can calculate the day of week for any date in that year in your head. [1] http://rudy.ca/doomsday.html

Here's a probably faster/easier way for most people to compute the Doomsday for a given year. The Doomsday is the sum of a factor determined by the century part of the year and a factor determined by year within the century. The century factor is: Century Factor 20xx 2 21xx 0 22xx 5 23xx 3 This pattern repeats every 4 centuries indefinitely forward, and however far back you can go in your jurisdiction before you hit…

I really like the “2053” pattern, it's easy to remember. But I doubt I will be able to remember the rest. I think I'd rather do like this:

Given a year CCXX, we know the doomsday of year CC00 from the “2053“ rule, and then:

    (a, b) = divmod(XX, 12)
    c = b // 4
    offset = a + b + c
Then add the offset to the day found by the “2053” rule, and you have the doomsday of the year.

E.g., for 2020 we have:

    start = 2  # from the 2053 rule
    (a, b) = divmod(20, 12)  # (1, 8)
    c = 8 // 4  # 2
    offset = 1 + 8 + 2 = 4 (mod 7)
    doomsday = 2 + 4 = 6  # saturday

Re: Show HN: One Page Calendar 2020

#103

Post by IshKebab »

intrepidhero wrote: post #56

This is pretty clever and I admire the author for coming up with an elegant way to show the mapping of week days to dates. I'd be particularly interested to see the algorithm behind it. Date computations are very tricky. A few years ago I made script to generate a one page calendar because the ones they hand out at work are particularly ugly. In addition to showing the date weekday mapping I also wanted it to show ho…

Date computations like this are not at all tricky.

Re: Show HN: One Page Calendar 2020

#105

Post by AdrianTP »

j1elo wrote: post #33

For the last 3 years I've been printing several copies of the Compact Calendar by David Seah [1]. It's as its name implies a compact form calendar that spans the whole year in a single page, and leaves enough side space to annotate stuff as needed. It's very cool and useful, although it would be nice having an open-source based version (i.e. LibreOffice), for those of us that don't have an MS Office license... [1]: h…

It renders fine for me in Firefox, but garbled in Chrome. Disabling this CSS rule "fixes" the layout for me in Chrome, without breaking anything obvious in Firefox:

@media (min-width: 500px) .calendar td, .calendar th { max-width: 0; }

I'm not actually sure what benefit that rule provides in the first place, but I haven't done any serious CSS hacking in forever.

Re: Show HN: One Page Calendar 2020

#106

Post by bordercases »

sh87 wrote: post #94
j1elo wrote: post #33

For the last 3 years I've been printing several copies of the Compact Calendar by David Seah [1]. It's as its name implies a compact form calendar that spans the whole year in a single page, and leaves enough side space to annotate stuff as needed. It's very cool and useful, although it would be nice having an open-source based version (i.e. LibreOffice), for those of us that don't have an MS Office license... [1]: h…

I print a bunch of these (sometimes multiple calendars on a page) and stick them up on the wall. Very useful to separate events / agendas of different classes on separate calendars e.g. birthdays, travel plans, project deadlines, appointments, goal tracking, habit tracking all go on different calendars but on the same wall. Much cleaner than putting them all on the same calendar and fight for space.

I'm thinking of doing it on tracing paper so I can overlay one over the other to check for double booking.

Re: Show HN: One Page Calendar 2020

#108

Post by roosgit »

timfrietas wrote: post #65
kryogen1c wrote: post #40

how in the holy hell do you read this? there are only 5 dates columns; how do you read days in month columns 6 and 7 (feb aug mar nov)? am i suppossed to matrix multiply this thing or what. im not normally too dumb for things but boy this is totally opaque to me.

I am guessing that people outside the US do not have as much trouble, as the format is naturally dd/mm/yyyy instead of mm/dd/yy, so reading left to right is more natural. It took me a brief moment to acclimate to this, but after I did I felt it was pretty straightforward and elegant.

To me, this looks complicated as well. For a full year calendar I prefer a standard one https://calendaroptions.com/2020-calendar/. If you're into space, NASA has a pretty cool science calendar(PDF) https://eospso.nasa.gov/sites/default/files/publications/202...
Post reply on HN