https://bugs.kde.org/show_bug.cgi?id=452264
Christian Wolf <christianlu...@web.de> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |christianlu...@web.de
--- Comment #25 from Christian Wolf <christianlu...@web.de> ---
I was surprised by this regression as well as I updated my Archlinux machine. I
have read the comments with this report and see it slightly different: For me,
distinguishing between a task (fixed appointment) and a ToDo/task (rough time
estimation) is not that strict. The extremes are a fixed appointment and a
strategic document. Between them, there is a (linear, analogous)
space/gradient. The different approaches mentioned here are falling within this
gradient.
I confirm the statements in #16 and #18 are true. These types of delays are
valid and I can confirm. I want to add other points additionally:
1. I use a central Nextcloud server to sync tasks/appointments between phone
and laptop. So, for me it is essential that any solution is compatible with the
webdav-based appointments/tasks.
2. When driving in the car, I often get (good?) ideas. I want to fix them in a
quick manner. Normally, I do not have the time to decide if this is better a
task or an appointment. It's more like adding an appointment "Call Mom, mobile
app" to remind me that I need to call her and ask if I need to install a
certain app on her phone (just a dumb example). I will put a reminder (default
15min) after I arrived and most probably will be back on the computer. There I
can process further and call her.
3. When coming to my laptop, I am typically greeted by a bunch of notifications
that are informing me of whatever I need to do now. With the old korac I was
able to process the tasks in "my" order. Some could be dismissed directly
(already done). Others need more caring. One trick to get this done fast was to
delay all still-to-be-cared-of notifications for 1-2 minutes and then dismiss
all altogether. This was typically much faster than 1 on 1 dismissing.
4. I might be able to adjust to thinking if it is a hard deadline or not, most
of my appointments are rather tasks instead of appointments. Explaining the
concept to my parents or my girlfriend would seem rather complex. I do not know
if I can get them used to the difference.
5. Speaking boldly: What would be the benefit of differentiating between
appointments and tasks? The restrictions imposed by the UI to appointments hold
true for tasks, are they not?
6. If you put a hamburger menu for appointments/tasks in the UI, you could
think of an option to shift the event/task due time instead of delaying the
notification. That might be useful as it will propagate to all synced devices.
Eventually, I will have more comments, that it for now :-)
Christian
--
You are receiving this mail because:
You are watching all bug changes.
