Mercurial > hg > gcmultimerge
comparison README.txt @ 79:0ccf3fd49181
Add license and some documentation.
author | Matti Hamalainen <ccr@tnsp.org> |
---|---|
date | Wed, 13 Jul 2016 12:59:50 +0300 |
parents | 8ef792b573a9 |
children | 286ccecf9257 |
comparison
equal
deleted
inserted
replaced
78:784cac877428 | 79:0ccf3fd49181 |
---|---|
1 Google Calendar MultiMerge(tm) 9000 | 1 Google Calendar MultiMerge |
2 =================================== | 2 ========================== |
3 By Matti 'ccr' Hämäläinen <ccr@tnsp.org> | 3 Programmed and designed by Matti 'ccr' Hämäläinen <ccr@tnsp.org> |
4 (C) Copyright 2016 Tecnic Software productions (TNSP) | |
5 | |
6 For license information, see file "COPYING". | |
7 | |
8 Introduction | |
9 ============ | |
10 | |
11 Google Calendar Multimerge (GCMM) is a simple Python utility for | |
12 creating a "merged" calendar from a number of "source" calendars. | |
13 Through Google Calendar API, events are copied from source calendars | |
14 to the target calendar and updated on each run. Deleted events will | |
15 be accordingly deleted from the target. | |
16 | |
17 In practice, the target is always an amalgamate of the sources, if | |
18 any events are added or deleted from it manually, they will be deleted | |
19 or re-added accordingly from it on the next run of GCMM. | |
20 | |
21 The reason for GCMM is that while an amalgamate view of all calendars | |
22 (shared or not) can be viewed through the main calendar site, the | |
23 amalgamate view can't be shared or viewed as an embedded element | |
24 directly. | |
4 | 25 |
5 | 26 |
27 How to use | |
28 ========== | |
6 | 29 |
7 First, we need to install the required Python tools in order to | 30 First, we need to install the required Python tools in order to |
8 install the required Google API Python modules ... in Debian/Ubuntu, | 31 install the required Google API Python modules ... in Debian/Ubuntu, |
9 chant the following magic incantations: | 32 chant the following magic incantations: |
10 | 33 |