https://bugs.kde.org/show_bug.cgi?id=481166
--- Comment #3 from David Jarvie <djar...@kde.org> --- As stated in its handbook, KAlarm is designed as a personal message, email and command scheduler. It is not designed for group use. It aims to present a simple interface (unless the user chooses to expand the options displayed) to allow ordinary (i.e. non-technical) users to schedule alarms. Most users only use it with its default calendars, and not with any calendars created by other applications. The fact that KOrganizer reminders have been messed up in recent times is unfortunate, but I don't want KAlarm to be amended or expanded in any way in order to be used as an adjunct to KOrganizer to provide its reminder functionality. It's up to KOrganizer to sort out its own deficiencies. For these reasons, I don't see it as important to provide KAlarm with the ability to read VTODOs, but I wouldn't object. It would be important to first of all decide on how reading calendars containing VTODOs should fit into KAlarm's user interface. As I said previously, I would see it as being via some sort of import function, but I don't know whether that would satisfy your goal of users not being surprised when VTODOs are ignored if KAlarm is told to use a calendar which it didn't create itself. Bear in mind that if VTODOs were edited in KAlarm, or if they contained recurrences, they would need to be rewritten as VEVENTs (and of course, functions specific to todos would be not show in KAlarm). -- You are receiving this mail because: You are watching all bug changes.
