Akonadi and AddressBook/zh-cn: Difference between revisions
mNo edit summary |
m (Created page with '''缓存数据(cached data)''则是真实数据的副本,放置在数据库中便于更快速的访问和作为离线缓存。数据库还同时保留着用来管理数据...') |
||
Line 7: | Line 7: | ||
对于 ''真实数据(real data)''我们指的像是联系人或事件这类数据。这些数据或是存储在「群件服务器(groupware server)」,或是存储在本地文件中。具体存储的位置取决于你使用的资源,比如,''个人联系人(Personal Contacts)''资源就是把数据存储到 $HOME/.local/share/contacts,同时 ''VCard File'' 资源(已经不推荐使用了[[Image:Face-smile.png|16px]])则存储数据到 $HOME/.kde/share/apps/kabc/std.vcf。 | 对于 ''真实数据(real data)''我们指的像是联系人或事件这类数据。这些数据或是存储在「群件服务器(groupware server)」,或是存储在本地文件中。具体存储的位置取决于你使用的资源,比如,''个人联系人(Personal Contacts)''资源就是把数据存储到 $HOME/.local/share/contacts,同时 ''VCard File'' 资源(已经不推荐使用了[[Image:Face-smile.png|16px]])则存储数据到 $HOME/.kde/share/apps/kabc/std.vcf。 | ||
''缓存数据(cached data)''则是真实数据的副本,放置在数据库中便于更快速的访问和作为离线缓存。数据库还同时保留着用来管理数据的''元数据(meta data)'','''Akonadi'''需要元数据才能正常工作。 | |||
The ''configuration data'' are the data that configure the '''Akonadi''' server and the individual resources. The configuration data for the server can be found under $HOME/.config/akonadi, the configuration for the resources are mostly stored under $HOME/.kde/share/config/akonadi_xyz_resourcerc# ('''''xyz''''' is name of resource and '''''#''''' its instance number). | The ''configuration data'' are the data that configure the '''Akonadi''' server and the individual resources. The configuration data for the server can be found under $HOME/.config/akonadi, the configuration for the resources are mostly stored under $HOME/.kde/share/config/akonadi_xyz_resourcerc# ('''''xyz''''' is name of resource and '''''#''''' its instance number). |
Revision as of 12:30, 9 August 2010
这里的资料由 KDE-PIM 开发人员 Tobias Koenig 提供。
一些定义
对于 真实数据(real data)我们指的像是联系人或事件这类数据。这些数据或是存储在「群件服务器(groupware server)」,或是存储在本地文件中。具体存储的位置取决于你使用的资源,比如,个人联系人(Personal Contacts)资源就是把数据存储到 $HOME/.local/share/contacts,同时 VCard File 资源(已经不推荐使用了)则存储数据到 $HOME/.kde/share/apps/kabc/std.vcf。
缓存数据(cached data)则是真实数据的副本,放置在数据库中便于更快速的访问和作为离线缓存。数据库还同时保留着用来管理数据的元数据(meta data),Akonadi需要元数据才能正常工作。
The configuration data are the data that configure the Akonadi server and the individual resources. The configuration data for the server can be found under $HOME/.config/akonadi, the configuration for the resources are mostly stored under $HOME/.kde/share/config/akonadi_xyz_resourcerc# (xyz is name of resource and # its instance number).
Organising Backups
So now we need to decide what to back up. If you want to backup the "real data", then it depends on the resources you have configured... if you use a groupware server, then the backup should be done there. For contacts, the files under $HOME/.local/share/contacts will normally be what you need.
The Akonadi tray icon offers you a backup and restore function. That backs up the "cache data" which might not include all of your data! It can be helpful if you want to clone a system 1:1, then you can copy the cached data together with the real data and the configuration, so you don't have to load the data again from the sources (e.g. groupware server).
Examining your Resources
KRunner offers you Akonadi Resource Configuration, or you can access this through the
. You may find several resources set up. You may find one labelledAddress Book - No KDE address book plugin configured yet.
That's the old compatibility bridge (possibly created by the migrator tool). You should remove this one!
std.vcf - Ready
This is the VCard File Resource which points to $HOME/.kde/share/apps/kabc/std.vcf per default. It is not recommended that you use that one, as it doesn't share the benefit of Akonadi.
Personal Contacts - Offline
That's the preferred resource for your local contacts which points to
$HOME/.local/share/contacts
Note that this may say "Offline" when in fact you are using it. This is a display bug, and can safely be ignored.
And when more components use Akonadi?
When the rest of the components move to Akonadi, will all the data be under ~/.local/share? That should make backup easy. Well, contacts and mails are stored there now, I don't know what the plan for events/todos is, but it would make sense to store them there as well. We'll keep it in mind when discussion pops up!