Summary: | Wish: Hide Akonadi, or allow Akonadi resources to be renamed | ||
---|---|---|---|
Product: | [Frameworks and Libraries] Akonadi | Reporter: | Jeffrey <eljefedelito> |
Component: | GoogleData Resource | Assignee: | Volker Krause <vkrause> |
Status: | RESOLVED UNMAINTAINED | ||
Severity: | wishlist | CC: | anderslund, dvratil, janow49420, kdepim-bugs, martin.tlustos, vkrause |
Priority: | NOR | ||
Version: | 4.3 | ||
Target Milestone: | --- | ||
Platform: | Debian testing | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Jeffrey
2009-09-22 16:56:48 UTC
*** Bug 215201 has been marked as a duplicate of this bug. *** My experience is different. In my case, the migration went completely wrong, so i ended up deleting the akonadi database and starting over by adding resources manually in the systemsettings module. I do not get to pick names except i use the akonadi resource types representing the traditional resources. I expect that the "akonadi compatibility resource" will go away ASAP. I maintain that using the file name for default name for resources is bad - files can have the same name, and from a user POV, "akonadi" is a confusing word that does not mean anything - so it should never be visible at all! But a good start would be letting the user choose a name for each resource! *** Bug 228026 has been marked as a duplicate of this bug. *** *** This bug has been confirmed by popular vote. *** *** Bug 316706 has been marked as a duplicate of this bug. *** |