summaryrefslogtreecommitdiff
path: root/README.md
diff options
context:
space:
mode:
authorTobias Brox <tobias@redpill-linpro.com>2014-03-07 23:28:55 +0100
committerTobias Brox <tobias@redpill-linpro.com>2014-03-07 23:28:55 +0100
commit06fd72260d003c9c01c98eccfeb0dbc6e8b87872 (patch)
tree648224b963c6b3019f36d06c5222872fc82c8723 /README.md
parent9bc2572fd579902773323cdc36e727685a7879ba (diff)
downloadcalendar-cli-06fd72260d003c9c01c98eccfeb0dbc6e8b87872.zip
library exchange
Diffstat (limited to 'README.md')
-rw-r--r--README.md4
1 files changed, 3 insertions, 1 deletions
diff --git a/README.md b/README.md
index a0f675c..63bd746 100644
--- a/README.md
+++ b/README.md
@@ -11,7 +11,7 @@ GUIs and Web-UIs are nice for some purposes, but I really find the command line
* Minor stuff that are repeated often. Writing something like "todo add make a calendar-cli system" or "cal add 'tomorrow 15:40+2h' doctor appointment" is just very much faster than navigating into some web calendar interface and add an item there.
* Things that are outside the scope of the UI. Here is one of many tasks I'd like to do: "go through the work calendar, find all new calendar events that are outside office hours, check up with the personal calendar if there are potential conflicts, add some information at the personal calendar if appropriate", and vice versa - it has to be handled very manually if doing it through any normal calendar application as far as I know, but if having some simple CLI or python library I could easily make some interactive script that would help me doing the operation above.
-I've been looking a bit around, all I could find was cadaver and CalDAVClientLibrary. Both of those seems to be a bit shortcoming; they seem to miss the iCalendar parsing/generation. CalDAVClientLibrary is already a python library, and there also exist python libraries for iCalendar parsing/generation, so all that seems to be missing is the "glue" between those libraries.
+I've been looking a bit around, all I could find was cadaver and CalDAVClientLibrary. Both of those seems to be a bit shortcoming; they seem to miss the iCalendar parsing/generation. CalDAVClientLibrary is already a python library, and there also exist python libraries for iCalendar parsing/generation, so all that seems to be missing is the "glue" between those libraries. Or, eventually, not. After some problems I decided to ditch CalDAVClientLibrary.
Synopsis
--------
@@ -117,3 +117,5 @@ Status
2013-09-28: version 0.02 - possible to add a calendar item to the caldav server
2013-10-02: version 0.03 - support for configuration file
2013-10-05: version 0.04 - no need to specify URL for the default calendar
+2013-12 - 2014-03: helped cyrilrbt on making a new release of the caldav library
+2014-03-07: version 0.05 - rewrote parts of the tool to using the caldav library. Nice!!!