Bug 463284 - Sharing remote caldav between several kalarm instances
Summary: Sharing remote caldav between several kalarm instances
Status: RESOLVED INTENTIONAL
Alias: None
Product: kalarm
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Other Linux
: NOR wishlist
Target Milestone: ---
Assignee: David Jarvie
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-12-20 20:33 UTC by Alex
Modified: 2022-12-21 08:02 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alex 2022-12-20 20:33:25 UTC
I use several desktop machines and I don't know how to share kalarm(s).

It would be nice if kalarm was able to use a caldav server like nextcloud to solve this problem
Comment 1 David Jarvie 2022-12-21 00:43:04 UTC
KAlarm accesses remote calendars only using remote file access protocols, and it doesn't implement other protocols.  Because it is primarily a personal reminder application, as opposed to a group one, other remote protocols seem unlikely to be required by many users. KAlarm used to use Akonadi, the KDE PIM data interface, to access calendar data, and this could potentially have been used for caldav access, but it caused so many bugs that it was eventually abandoned in favour of simple file access. This has had the extra benefit of keeping things simpler. So unfortunately for you, it is unlikely that remote protocols such as caldav will be implemented.
Comment 2 Alex 2022-12-21 08:02:51 UTC
That's a pity because kalarm is wonderfully useful and I'm addicted to it but when I'm not at my PC I lose all the informations and reminders and I'm lost :-(