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

List:       kde-usability
Subject:    Re: relevantive - korganizer
From:       Simon Edwards <simon () simonzone ! com>
Date:       2003-08-14 22:27:34
[Download RAW message or body]

On Thursday 14 August 2003 23:54, Aaron J. Seigo wrote:
> On Thursday 14 August 2003 03:38, Reinhold Kainhofer wrote:
> > > That's sounds cool.
> >
> > No, because the  line edit is there so that people can also just type in 
or
> > paste the date easily. If you want to display the date using localized
> > strings (i.e. 14. August 2003), you run into all kind of trouble parsing
> > the dates.

It's a tricky problem. Concerning reading dates, there is little doubt that:

Sun, 16 August 2003

is the clearest and less prone to error format. (The US Army studied this 
years ago, they even tried using roman numerals in places, ouch.) But it's a 
tricky input format. I guess ideally you should be able enter dates in 
whatever format you like, korganiser would then parse and format the date, 
giving immediate feedback as to what the machine understood the date to be.

Parsing of some kind might be unavoidable. Splitting dates into tidy fields is 
good for data validation, but is a major PITA for people who need to enter 
stuff.

> there's already all kinds of trouble parsing the dates:
> 
>   http://bugs.kde.org/show_bug.cgi?id=50625
> 
> i suppose we shouldn't make it any harder ;-) would it be possible to 
include 
> a simple RO label in the localized format next to the editable combobox?

perhaps,

> > > My concern is that normal people may not clearly distinguish between
> > > Dates and Times.
> >
> > But in the view it makes are really big difference if the item has a time
> > associated or not!

I'm not trying to eliminate it or anything, I'm just saying that currently the 
checkbox is a bit backward and the text might need improving. (Backward in 
the sense of having switch in a room to "turn the darkness on" instead of 
turning the light out.)

> > >> > * The "Play Sound" and "Run Program" stuff should be a bit clearer.
> > >> > Although we're a bit cramped for space in that area.
> >
> > BTW, an alarm can only display a message or it can play a sound or it can
> > run  a program. Currently the check buttons do not indicate that, but the
> > actions are exclusive, there can only be one. (IIRC their precedence is 
run
> > program, then play sound, and if none of these is set, its action is
> > display message).
> 
> ah, so it should be radio buttons then...

This just isn't going to fit in my design. The sound and program parts really 
need to looks something like:


(*) Play sound: [linux_pronouciation.wav_______] [Choose...]
( ) Run program:[______________________________] [Choose...]

showing what is currently entered.

cheers,

-- 
Simon Edwards             | Guarddog Firewall
simon@simonzone.com       | http://www.simonzone.com/software/
Nijmegen, The Netherlands | "ZooTV? You made the right choice."

_______________________________________________
kde-usability mailing list
kde-usability@mail.kde.org
http://mail.kde.org/mailman/listinfo/kde-usability
[prev in list] [next in list] [prev in thread] [next in thread]