Open murtezayesil opened 4 years ago
Strict table structure till Meta column optional columns must be blank
Title | StartDate | EndDate | StartTime | EndTime | Repeats | RepeatsUntil | Reminder1 | Reminder2 | Reminder3 | Meta (for description and attachment)
Event #1 | Day/Month/Year | HH:MM | D:daily OR W:weeekly OR Y:yearly | DD/MM/YYYY | Notify.10m for Notification 10min before event | Can have as many seperators as you want from this point onward.
Event #2 | Day/Month/Year | --:-- = whole day | OR MTWTFSS OR MTWTF-- OR -----SS | DD/MM/YYYY | Alarm.09:00 OR Urgent.3H OR Alarm.3D | It can be checkbox (-[] github markdown style), String for description,
| Notify.0m for Notification on start of event | webpage URL, or client specific features
| Alarm.1w.remember to submit assignment |
Flight to London | 09/05/2020 | 10/05/2020 | 22:45 | 04:15 | | | Alarm.4H | Urgent.2H | Notify.6H | LondonTicket.png | -[] Passport | -[] Gift bag for grandma | -[x] buy birthday gift for Jessica
Jessica's Birthday|16/05/1999|16/05/1999|--:--|--:--|Y||Notify.1D.Jessica likes turquoise color|||Birthday party will start on 21.00
Reply to this issue to submit your design idea for calendar.txt format.
I personally want it something similar to todo.txt but calendars can become much longer as we use them. So we shouldn't be scared of using something drastically different to sustain good performance in the long run.