
Source (link to git-repo or to original if based on someone elses unmodified work): Add the source-code for this project on opencode.net
KAlarm is a personal alarm scheduler which displays messages, executes commands, plays sounds or sends emails, at scheduled times. You can set up recurring alarms, or restrict alarms to working hours. Among its options, it allows you to choose the message font and color, whether to display an advance reminder, whether to speak the message or play a sound when it is displayed, whether to cancel the alarm if it can't be triggered on time (e.g. if you are logged out when it triggers).
You can optionally use multiple alarm calendars, or share calendars. This allows, for example, sharing alarm calendars between laptops and desktop computers.
As well as using the graphical interface to configure alarms, you can use the command line, and there is a DCOP interface for other applications.
KAlarm is part of the official KDE kdepim package. The KAlarm version for KDE 4 downloadable from here is an update to the current KDE 4 release. The KDE 3 package is no longer supported; the last released KDE 3 version is functionally the same as the KDE 4 2.6.2 version, and offers considerable improvements compared to the version supplied with KDE 3.5.10.
8 years ago
Version 2.9.0: This release adds a new option to execute a pre-alarm action before deferred alarms trigger, and new options to auto-hide the system tray icon when no alarms are due. The Try button in the audio alarm edit dialogue now toggles playback start and stop. There are other minor improvements and bug fixes. It includes a new Catalan translation of the handbook.
8 years ago
Version 2.9.0: This release adds a new option to execute a pre-alarm action before deferred alarms trigger, and new options to auto-hide the system tray icon when no alarms are due. The Try button in the audio alarm edit dialogue now toggles playback start and stop. There are other minor improvements and bug fixes. It includes a new Catalan translation of the handbook.
thstaerk
9 years ago
regards
Thorsten
Report
djarvie
9 years ago
Report
google01103
9 years ago
regards,
Report
djarvie
9 years ago
Report
google01103
9 years ago
Report
google01103
9 years ago
Report
STurtle
10 years ago
Is there a Plasmoid Widget for KAlarm that could display the same info as the tooltip (the time to the next alarm) on the desktop?
KAlarm is pretty neat! Thanks!
Report
djarvie
10 years ago
Report
spell
10 years ago
Report
djarvie
10 years ago
If so, would you prefer it to be a global option for KAlarm applying to all alarms, or should it be selectable for individual alarms?
Report
spell
10 years ago
Report
xtekhne
12 years ago
It does not show any items that had been set with the standard 1.5.1
Any hints?
thank you
--
Pol.
Report
djarvie
12 years ago
You can check the calendar file's location by displaying the resources view (in the menu, View -> Show Resources). Hover the cursor over the active calendar entry and it will display its file location. Check whether this is indeed the same file as was used by the previous version of KAlarm, which would usually be ~/.kde/share/apps/kalarm/calendar.ics .
Report
xtekhne
12 years ago
Should i add that variable, anywhere?
I am starting kalarm as a local host, not being the owner of the kde session.
On a terminal, that user gets 'permission denied' to
.kde/share/apps/kalarmd/calendar.ics
Actually, the kalarmd directory does not exist at all.
.
Finally message pops up:
"Failure to create menus
(perhaps kalarmui.rc missing or corrupted)"
Any ideas?
thank you
--
Pol
Report
xtekhne
12 years ago
Should i add that variable, anywhere?
I am starting kalarm as a local host, not being the owner of the kde session.
On a terminal, that user gets 'permission denied' to
.kde/share/apps/kalarmd/calendar.ics
Actually, the kalarmd directory does not exist at all.
.
Finally message pops up:
"Failure to create menus
(perhaps kalarmui.rc missing or corrupted)"
Any ideas?
thank you
--
Pol
Report
djarvie
12 years ago
The error creating menus is because you installed into /usr/local instead of into the KDE installation directory (presumably /usr). Configuration files (such as the menu definition) are still being taken from the KDE installation instead of from /usr/local. If you install into some other directory such as /usr/local, you need at the very least to have /usr/local as the first entry in $KDEDIRS when the KDE session starts. If you want things to work properly, I'd definitely recommend installing into the normal KDE directory unless you really know what you're doing.
Report
bumphead
14 years ago
.....
checking for libjpeg... -ljpeg
checking for perl... /usr/bin/perl
checking for Qt... configure: error: Qt (>= Qt 3.0 and < 4.0) (headers and libraries) not found. Please check your installation!
For more details about this problem, look at the end of config.log.
in 2.6.18-1.2257.fc5
i have the following packages installed:
qt-3.3.7-0.1.fc5
qt4-x11-4.2.2-1.fc5
qt4-4.2.2-1.fc5
qt4-devel-4.2.2-1.fc5
any idea ? thanks.
bumphead
Report
djarvie
14 years ago
Report
gohanz
14 years ago
http://www.slacky.it/
http://www.slacky.it/index.php?option=com_remository&Itemid=29&func=fileinfo&id=1015
Report
gohanz
14 years ago
http://www.slacky.it/
http://www.slacky.it/index.php?option=com_remository&Itemid=1&func=fileinfo&filecatid=1033&parent=category
Report
djarvie
14 years ago
Report
gohanz
14 years ago
Report
djarvie
14 years ago
Report
GreatBunzinni
14 years ago
Report
djarvie
14 years ago
That's a summary of the differences. Use whichever is best for your particular needs.
Report