While documenting KOrganizer incident dialogs, I was bugged about some small details. In the spirit of doing something about it instead of complaining, created some mockups to express these ideas.
I noticed that you can't select the resource to save the event in the dialog. It seems an important feature to me. Also, the incident description is buried in the end of the dialog. It is hard to know it is even the place to write the description, as there is no label. Here is the original image (correction: this is not the original image, this is a previous mockup. The original image does not have a "Description:" label above the details edit box):
[image:1155]
I moved the description up, and added the resource drop-down at the bottom. Nothing too fancy. The result is here:
[image:1156]
I know that from a task-oriented perspective, adding a description is probably a less common task than setting the time, so the time may deserve to be above the description. But then again, the user can (and should, because it is easier) create the event directly on the calendar main view, so the time is already set. And having where to set the calendar / resource to save the incident avoids displaying that pop up for every incident you save (when you have more than one resource available.
Now to the Attendees tab: the Address Book should be the main source of address right? But here on this dialog, where can you find access to the Address Book? There, at the bottom, hidden under the name "Select Adressees...".
[image:1157]
Since adding by hand one by one of the attendees does not seems to be the most practical way to fill the list, here is a mockup with the address book button renamed and moved up:
[image:1158]
That's all for the moment, but there is more to come.
Syndicate Blogs
Quality and Usability
Some of this stuff has actually already been covered by the usability team; seems the quality team is expanding its coverage
I'll just comment that adding a combobox for the resource implies the user can change it at any time. Not really something that is usefull and in various cases also unwanted (read only resources, for example).
In fact, I'm not even sure why it is a problem to select resource before adding to it; its not like you are going to be adding events most of the time you use korganizer.
I would like to ask you to join the people at the openusability.org site. As I doubt the developers will use your work published on a blog, which doesn't really work great for bouncing ideas between us, and all that.