#Ics file details how to
#Ics file details update
#Ics file details series

ics file contains at least as many events as the previous. The first event is “baseid-calendarid-event-1”, the second “baseid-calendarid-event-2”, and so on.Īs long as any updated. So currently, the script defaults to incrementing an event number, starting at 1. If it were based on the title, date, and/or time, it would then change when the event’s title, date, or time changed, and would thus not replace the old event.

#Ics file details how to

I have no idea how to create a unique, unchanging identifier from the event information alone without defeating that purpose.

#Ics file details update

Never change a slug once it’s been created! A changed slug doesn’t update the old versions of what it referred to. It looks for “slug:text” and uses that as the calendar or event slug, combining it with a base identifier built in to the script. So currently the script allows you to specify a slug for the calendar and for each event. With event identifiers, the calendar program will automatically replace the old set with the new set.įor any gathering of any reasonable size, they’re a necessity, because you’ll almost certainly be updating your event information. Without event identifiers, when a participant adds the calendar a second time they’ll get a second set of events and have to manually delete all of the events in the first set. ics file) make it possible to update events that already exist in the user’s calendar. These identifiers (X-WR-RELCALID and UID in the. I don’t like how the script handles calendar and event identifiers. It is one of the many great joys of programming. There remains a joy in exploring the hidden crevasses of an interchange format such as icalendar, teasing out its benefits and working around its flaws, to create something that can be shared throughout a wide community.

#Ics file details series

It does this by filtering the text through a series of regular expressions. Once it sees an event headline, the script only looks for new events and their information. And default years are recognized by being a four-digit number starting with a “2”. Timezones are recognized by being one of the zone keys in the timezone hash. The title of the overall calendar is a single pound symbol, a space, and then anything: it’s a Markdown level-1 headline. die('Unknown calendar-wide option $_ ') īefore the script detects an event, it’s looking for the very few items it can use as part of the overall calendar: a title, a time zone, a default year, and a unique identifier (“slug”) for the calendar.It is very similar to the my and local keywords. You can share variables between the main script and the package by defining them with our. Each have to go after the package line that names the class.

So the Event class goes into a BEGIN section, which is basically treated as its own file by Perl it has its own use lines and its own globals. However, I have no intention of re-using this class anywhere if I do, I’ll move it out, but it’s simple enough that putting this class into its own separate file violates the second law of Perl: keep easy things easy. While Perl is much more freeform than other scripting languages-it’s first law is, after all, “There’s more than one way to do it”-it is generally accepted that class definitions go into their own file for re-use elsewhere. First, it isn’t very Perl-like in how it handles the event class. There are two potentially interesting things in this script. The script assumes that events are taking place in the current year, but you can specify a year on the date line (“July 15, 2023” instead of “July 15”) or you can specify a default year at the top of the file If the script doesn’t recognize a piece of information, it assumes that it’s part of the description. Except for the title of the event, which must always come first (and always be preceded by two hash marks-that is, a Markdown level-2 headline), the order of information doesn’t matter. The script is meant to take files created for human purposes, not computer purposes. It’s also easy enough for a Perl script to convert to a. In fact, if you open this in pretty much any modern text editor it will be formatted to highlight the important bits and to keep the separate events readable as separate events, because this is very simple Markdown text. Very simple, and it’s obvious what this text means. Only adventurers of stout heart and cunning can hope to penetrate the forest and return alive. The Deep Forest is a dangerous place, home to many strange creatures.Only vague references remain to taunt treasure hunters and spell seekers. The Astronomers, in the Deep Forest south of the Leather Road, have been silent for a hundred years, unheard from since the goblin wars that so devastated Highland. The mountains of West Highland are dotted with the ruins of lost scholarly orders.