author | zautrix <zautrix> | 2004-06-26 19:01:18 (UTC) |
---|---|---|
committer | zautrix <zautrix> | 2004-06-26 19:01:18 (UTC) |
commit | b9aad1f15dc600e4dbe4c62d3fcced6363188ba3 (patch) (unidiff) | |
tree | 2c3d4004fb21c72cba65793859f9bcd8ffd3a49c /bin/kdepim/korganizer/howtoSYNC.txt | |
download | kdepimpi-b9aad1f15dc600e4dbe4c62d3fcced6363188ba3.zip kdepimpi-b9aad1f15dc600e4dbe4c62d3fcced6363188ba3.tar.gz kdepimpi-b9aad1f15dc600e4dbe4c62d3fcced6363188ba3.tar.bz2 |
Initial revision
Diffstat (limited to 'bin/kdepim/korganizer/howtoSYNC.txt') (more/less context) (show whitespace changes)
-rw-r--r-- | bin/kdepim/korganizer/howtoSYNC.txt | 197 |
1 files changed, 197 insertions, 0 deletions
diff --git a/bin/kdepim/korganizer/howtoSYNC.txt b/bin/kdepim/korganizer/howtoSYNC.txt new file mode 100644 index 0000000..e73709b --- a/dev/null +++ b/bin/kdepim/korganizer/howtoSYNC.txt | |||
@@ -0,0 +1,197 @@ | |||
1 | NOTE: | ||
2 | YOU MAY GET UNEXSPECTED (I.E. WRONG) SYNCHRONIZATION RESULTS, | ||
3 | IF YOU CHANGE AN EVENT ON THE FIRST DEVICE AND SYNC IMMEDIATELY FROM | ||
4 | THE OTHER DEVICE WITH THIS DEVICE, IF THE CLOCKS OF THE TWO DEVICES | ||
5 | HAVE TOO MUCH DIFFERENCE. | ||
6 | |||
7 | |||
8 | CONTENT: | ||
9 | |||
10 | 0) How syncing works | ||
11 | 1) Qick overview of settings | ||
12 | 2) Sync settings in sync dialog | ||
13 | 3) Syncing background | ||
14 | 4) Sync preferences | ||
15 | |||
16 | ************************************************************************* | ||
17 | 0) How syncing works | ||
18 | ************************************************************************* | ||
19 | |||
20 | In KO/Pi you can synchronize ( sync ) your calendar | ||
21 | with another calendar, by syncing your (local) calendar with a | ||
22 | (remote) file. This remote file may on your local filesystem | ||
23 | or on another (remote) device. | ||
24 | If it is on another device, you have to specify a | ||
25 | command line download/upload command ( like scp, ftp, ...) to | ||
26 | a) download the remote file to your local machine to a temp file | ||
27 | b) sync with this temp file | ||
28 | c) upload the synced file to the remote device | ||
29 | |||
30 | You should create for every device, to sync with, a sync profile. | ||
31 | |||
32 | NOTE: | ||
33 | Before syncing, it is recommended to close | ||
34 | a running KO/Pi on the remote device. | ||
35 | (Note: KO/Pi running on Zaurus with | ||
36 | FastLoad enabled will never be closed!) | ||
37 | After syncing with a running KO/Pi on the remote device, | ||
38 | a "save" on the remote device will tell you that it needs to merge (sync). | ||
39 | After merging (just a syncing with the changed file) | ||
40 | you will get the new data showing in remote KO/Pi. | ||
41 | |||
42 | ************************************************************************* | ||
43 | 1) Qick overview of settings | ||
44 | ************************************************************************* | ||
45 | |||
46 | a) Open sync settings dialog | ||
47 | b) Give your device a unique name. | ||
48 | (unique in the set of all devices you want to sync with). | ||
49 | If you have already configured another devive and created | ||
50 | there a sync profile to sync with this device, give your device | ||
51 | the same name as this sync profile! The same name is important! | ||
52 | c) Create a new sync profile and give it a unique name. | ||
53 | (unique in the set of all sync profiles on this device). | ||
54 | If you want to sync with a device, where KO/Pi is already installed | ||
55 | and which has a given unique device name, use this device name as | ||
56 | your profile name. | ||
57 | d) Coose the profile kind of your syncing method: | ||
58 | (i) Local file or | ||
59 | (ii) Remote file | ||
60 | c) If you did choose (i), | ||
61 | specify the file name you want to sync with. | ||
62 | If you did choose (ii), | ||
63 | specify the system (command line) | ||
64 | download/upload command of the remote file. | ||
65 | d) Choose the other profile options. | ||
66 | Detailed explanation in 2.) | ||
67 | e) Close sync dialog with OK. | ||
68 | f) Sync. | ||
69 | |||
70 | NOTE: | ||
71 | AFTER SYNCING THERE ARE "SYNC EVENTS" CREATED | ||
72 | (OR UPDATED, IF IT ALREADY EXITS) FOR EACH SYNC PROFILE. | ||
73 | YOU MAY NOT DELETE OR CHANGE THESE EVENTS. | ||
74 | |||
75 | ************************************************************************* | ||
76 | 2) Sync settings in sync dialog | ||
77 | ************************************************************************* | ||
78 | |||
79 | a) Local device name: | ||
80 | -> 1) b) | ||
81 | b) Profile: | ||
82 | -> 1) c) | ||
83 | c) Include in multiple sync: | ||
84 | In the Synchronize menu, there is a multiple sync menu entry. | ||
85 | If you choose this menu entry, all user defined profiles with this | ||
86 | 'Include in multiple sync' option enabled will be synced | ||
87 | one after another. And this twice. This will take some time. | ||
88 | After that sync, on all devices should be the same data. | ||
89 | d) Ask for preferences before sync: | ||
90 | Check this to be asked for sync settings before each sync. | ||
91 | e) Sync preferences: | ||
92 | Choose here your sync preferences. | ||
93 | Details -> 4) | ||
94 | f) Show summary after sync: | ||
95 | Check this to get a small summary dialog after sync | ||
96 | about number of added/changed/deleted events on local/remote. | ||
97 | g) Write back existing entries only: | ||
98 | Check this to update the remote calendar only. | ||
99 | I.e. no event/todo from yor local calendar is added to the | ||
100 | remote calendar. You may use this option to | ||
101 | sync against some kind of "public calendar" without | ||
102 | writing back your personal data. | ||
103 | h) Write back file: | ||
104 | Check this to update the local calendar only. | ||
105 | I.e. your local calendar is synced with the remote calendar | ||
106 | but nothing on the remote calendar is changed. | ||
107 | i) Profile kind: | ||
108 | -> 1) d) | ||
109 | |||
110 | ************************************************************************* | ||
111 | 3) Syncing background | ||
112 | ************************************************************************* | ||
113 | |||
114 | Synchronizing calendars ( i.e. files ) means, | ||
115 | to merge two calendars in a useful way. | ||
116 | If the two calendars are completely different, | ||
117 | there is no problem, the resulting calendar contains | ||
118 | all data from the local and from the remote calendar. | ||
119 | |||
120 | Problems will occur, if you have edited items | ||
121 | from the local calendar on the remote machine. | ||
122 | Then it could be, that items are in conflict. | ||
123 | Two items are "in conflict", if they have the | ||
124 | same unique ID (which get an item at time of | ||
125 | creation and owns it until it is deleted ) | ||
126 | and they both are modified after the last | ||
127 | synchronization. | ||
128 | |||
129 | At first sync of two calendars there is no item deleted. | ||
130 | If the calendars are synced before and there is an item, | ||
131 | which is not edited after the last sync and is only | ||
132 | available in one calendar, then this item is deleted | ||
133 | in this calendar. | ||
134 | |||
135 | But when was the last synchronization between two calendars? | ||
136 | |||
137 | To know that, KO/Pi creates at first syncing | ||
138 | of two files an unique event "<profile name> - sync Event" | ||
139 | on the remote and the local calendar. | ||
140 | After syncing, the start time of this event is set | ||
141 | to the time of syncing. | ||
142 | The event is read only and the user may not change it. | ||
143 | |||
144 | If two such files are synced, that both have an event | ||
145 | "<profile name> - sync Event" and the events have | ||
146 | the same start time, then deleted items on the one calendar | ||
147 | are deleted on the other as well. | ||
148 | |||
149 | |||
150 | ************************************************************************* | ||
151 | 4) Sync preferences | ||
152 | ************************************************************************* | ||
153 | |||
154 | Two items are "in conflict", if they have the same unique ID | ||
155 | and they both are modified after the last synchronization. | ||
156 | (Details -> 3) ). | ||
157 | |||
158 | If an item is not modified after the last sync and | ||
159 | it is not found in the other calendar, it is deleted. | ||
160 | |||
161 | On the first sync, there is no item deleted. | ||
162 | |||
163 | SYNC PREFERENCES: | ||
164 | -Take local entry on conflict: | ||
165 | Takes the local entry on conflict. | ||
166 | If it is the first sync, | ||
167 | "Ask for every entry" | ||
168 | is chosen automatically, | ||
169 | if this is selected. | ||
170 | |||
171 | -Take remote entry on conflict: | ||
172 | Takes the remote entry on conflict. | ||
173 | If it is the first sync, | ||
174 | "Ask for every entry" | ||
175 | is chosen automatically, | ||
176 | if this is selected. | ||
177 | |||
178 | -Take newest entry on conflict: | ||
179 | This takes the newest entry on conflict. | ||
180 | May be the most useful syncing mode. | ||
181 | |||
182 | -Ask for every entry on conflict: | ||
183 | Pops up an event viewer dialog and | ||
184 | shows the two conflicting entries there. | ||
185 | The user can chose, which entry he would like to take. | ||
186 | The button for the newest entry | ||
187 | is automatically set as default button. | ||
188 | The color for the newest entry is green. | ||
189 | |||
190 | -Force: Take local entry always: | ||
191 | Even if the calendars are already synced | ||
192 | there is no item deleted on local. | ||
193 | |||
194 | -Force: Take remote entry always: | ||
195 | Analogous to | ||
196 | "Force: Take local entry always" | ||
197 | |||