Bug 195017 - Integrate korganizer, alarm and timer with clock plasmoid
Summary: Integrate korganizer, alarm and timer with clock plasmoid
Status: RESOLVED DUPLICATE of bug 46262
Alias: None
Product: plasma4
Classification: Unmaintained
Component: widget-clock (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR wishlist
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-02 21:09 UTC by Kamil Neczaj
Modified: 2011-04-21 10:46 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kamil Neczaj 2009-06-02 21:09:57 UTC
Version:            (using KDE 4.2.3)
OS:                Linux
Installed from:    Unlisted Binary Package

Now there is korganizer icon in systray, which is responsible for reminding about planned tasks, but there is also clock with calendar as plasmoid near the systray. Both applets are related to time organisation, so it would be nice to integrate them. Nice feature would be adding task by double click on date in the calendar in clock plasmoid or right-clicking on clock and choosing 'Add task'. Another really usable thing would be an option to set alarm on certain time with possibility to repeat it regularly, for example on Monday 19:00. Also possibility to set kitchen-timer would be great. For example you heat milk, so you go to kitchen put it on cooker and return to computer. You want to prevent milk from over boiling so you right-click on the clock, choose 'set timer' and type 5min. Your live gets easier! ;) All notifications could be displayed using common kde notifications system with optional sound.
Comment 1 bdbrot 2011-04-20 22:02:40 UTC
and a possibility to link the calendar with a calendar-file from lightning, korganizer, yahoo, google, e.g. an show dates at the calendar-top (like the holydays currently)
Comment 2 John Layt 2011-04-21 10:46:02 UTC

*** This bug has been marked as a duplicate of bug 46262 ***