narrowstacks / word-calendar-generator Goto Github PK

If there are enough events in the calendar on any given day, it can push the contents of the calendar further down, sometimes reaching another page. If the program were to change to size of the text dynamically based on the number of events in the column with the most events, this could be likely prevented.

Perhaps others might WANT the calendar to extend to two pages, though?

In the header of the docx file, a "last updated" field adds the date of the file's creation. It places zeroes in front of months or days that are single digits.

Currently, it looks like this, errant zero highlighted in grey:

When it should look something like this:

Right now, if a user is generating a weekly calendar, the program relies on the user to select the specific Sunday/Monday of their chosen week. The program should allow the user to select any given day of the week and find the appropriate Sunday/Monday to start the week on.

If a user forgets an option inside of config.cfg, it breaks the program as no defaults are set by the program.

Example:

If a user forgets to include a line like
TIMEZONE = America/Los_Angeles
The program has nothing to work with, so an exception is raised.

Currently the program uses Gooey, which builds an interface based on command line arguments. It’s a workaround for usability and for me to make sure the core of the program works. But I would eventually like the interface to be a little nicer looking while adding some more functionality.

Ideally it would be nice if users would be able to edit the config file from within the interface. Color pickers for the location colors, etc.

When the program generates the table in the word document for monthly calendars, it is not aware of how many rows it actually needs, so we currently use the max that would ever be used. As a result, if a month doesn't take up all 13 rows, the program doesn't remove the empty rows at the bottom.
If the true number of rows needed could be calculated before the table is created, this would fix it.

In the image below, the errant rows at the bottom are highlighted in grey: