9 Feb
2014
9 Feb
'14
9:14 p.m.
Hi,
1. I'd find it much more efficient, if the tasks would be shown in edit
mode always.
This way changes to a task could be typed in immediately w/o hitting an
"edit" button first
and the save button would just save and not return to a read-only view.
2. even more efficient would be an automated saving of the task changes
so that you don't have to hit a save button any more.
So as soon as anything is changed in a task it should be saved
automatically to the caldav server.
This way, the tasks interface woulnd't have save and revert buttons any
more (with the obvious disadvantage that undo wouldn't be possible any
more).
a) what's the opinion of others about these suggestions?
b) would it be hard to implement at least 1.?
thanks and regards,
--
Johannes
9 Feb
9 Feb
10:18 p.m.
Hi,
On 09 Feb 2014, at 22:14, Dr. Johannes Zellner <johannes(a)zellner.org> wrote:
1. I'd find it much more efficient, if the tasks
would be shown in edit mode always.
This way changes to a task could be typed in immediately w/o hitting an "edit"
button first
and the save button would just save and not return to a read-only view.
2. even more efficient would be an automated saving of the task changes so that you
don't have to hit a save button any more.
So as soon as anything is changed in a task it should be saved automatically to the
caldav server.
This way, the tasks interface woulnd't have save and revert buttons any more (with
the obvious disadvantage that undo wouldn't be possible any more).
a) what's the opinion of others about these suggestions?
b) would it be hard to implement at least 1.?
I do not think that any of these changes is a good idea because:
- we use both CalDavZAP/CardDavMATE in corporate environment and I really don't want
a ton of support request e-mails related to "randomly" changed data
- I want identical user experience in CalDavZAP and CalDavMATE (because the integrated
version of both clients is coming ... /we already use it/)
- without the "view" mode we need to detect whether the user changed something
in the interface => and this is not easy task because we need to listen on a ton of
keyboard/mouse events (+ major touch interface related problems)
JM
p.s.: my todo list contains an entry "allow change the task status directly in the
task list (without clicking to the editor)", but there are lot of more important
entries before that item ...
3283
days inactive
3283
days old
1 comments
2 participants
participants (2)
-
Dr. Johannes Zellner -
Ján Máté