https://bugs.kde.org/show_bug.cgi?id=481166
Flossy Cat changed:
What|Removed |Added
Resolution|INTENTIONAL |FIXED
--- Comment #10 from Flossy Cat ---
(In
https://bugs.kde.org/show_bug.cgi?id=481166
David Jarvie changed:
What|Removed |Added
Resolution|--- |INTENTIONAL
Status|REPORTED
https://bugs.kde.org/show_bug.cgi?id=481166
--- Comment #8 from Flossy Cat ---
(In reply to David Jarvie from comment #7)
> Many of your proposals go beyond the intended scope of KAlarm, and if
> implemented would expand its function from being a stand-alone personal
> alarm application to
https://bugs.kde.org/show_bug.cgi?id=481166
--- Comment #7 from David Jarvie ---
Many of your proposals go beyond the intended scope of KAlarm, and if
implemented would expand its function from being a stand-alone personal alarm
application to something more general. This would add more code
https://bugs.kde.org/show_bug.cgi?id=481166
--- Comment #6 from Flossy Cat ---
(In reply to David Jarvie from comment #5)
> Yes, KAlarm is for both technical and non-technical users, but to serve the
> latter, it needs a simple interface. More advanced users can expand the
> range of displayed
https://bugs.kde.org/show_bug.cgi?id=481166
--- Comment #5 from David Jarvie ---
Yes, KAlarm is for both technical and non-technical users, but to serve the
latter, it needs a simple interface. More advanced users can expand the range
of displayed options, and use such things as command alarms.
https://bugs.kde.org/show_bug.cgi?id=481166
--- Comment #4 from Flossy Cat ---
(In reply to David Jarvie from comment #3)
> As stated in its handbook, KAlarm is designed as a personal message, email
> and command scheduler. It is not designed for group use.
I do not intend group use – only
https://bugs.kde.org/show_bug.cgi?id=481166
--- Comment #3 from David Jarvie ---
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
https://bugs.kde.org/show_bug.cgi?id=481166
--- Comment #2 from Flossy Cat ---
(In reply to David Jarvie from comment #1)
> By design, KAlarm stores all its alarms in VEVENT, and in order to provide
> all its functionality it uses quite a few custom properties in VEVENT and
> VALARM.
Perhaps I
https://bugs.kde.org/show_bug.cgi?id=481166
--- Comment #1 from David Jarvie ---
By design, KAlarm stores all its alarms in VEVENT, and in order to provide all
its functionality it uses quite a few custom properties in VEVENT and VALARM.
Giving full support to VTODO would be outside the current
10 matches
Mail list logo
