[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-pim
Subject:    Re: [Kde-pim] entering events in korganizer sucks
From:       Ingo =?iso-8859-15?q?Kl=F6cker?= <kloecker () kde ! org>
Date:       2012-03-15 22:16:32
Message-ID: 201203152316.32921 () thufir ! ingo-kloecker ! de
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


On Thursday 15 March 2012, Georg C. F. Greve wrote:
> On Wednesday 14 March 2012 22.13:34 Ingo Klöcker wrote:
> > Hmm. I have to admit that I like the way Outlook 2007 handles this
> > much better. You select the timeslot and then type the summary
> > immediately into the calendar without any annoying dialog popping
> > up.
> 
> Well, some web interfaces allow to do just that, but what they do is
> they visualize that a new event is being created here and show a
> prompt within the calendar that allows direct editing.
> 
> But what I am saying is that if the application does not provide any
> kind of feedback on what the user could be doing or is expected to
> do, there is definitely room for improvement, e.g. what is the use
> case for selecting a slot in the calendar without creating a new
> event? (current behaviour)
> 
> Or: How do I select a slot that is within existing events (which were
> events of other people, or non-blocking items in the calendar)?

Outlook 2007 leaves a bit of space next to existing events to allow for 
this. IIRC, Outlook 2003 didn't do this. I'm pretty sure that Microsoft 
did perform extensive usabilitity testing for Outlook to find and fix 
such problems.


> Perhaps at the next KDE PIM sprint when I believe stability will be
> resolved we can get Björn to come back and then do a long session on
> how such things could / should work?

+1


Regards,
Ingo

["signature.asc" (application/pgp-signature)]

_______________________________________________
KDE PIM mailing list kde-pim@kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/

[prev in list] [next in list] [prev in thread] [next in thread]