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

List:       kde-usability
Subject:    RE: Stuff I will be doing
From:       "Jonathan Bacon" <j.bacon () delta ! wlv ! ac ! uk>
Date:       2001-07-30 8:35:48
[Download RAW message or body]

In terms of coherent recommendations of reports, I think we need to take
reports and test data from a variety of places, and write periodical
reports on the usability of an object in KDE. For example if we have a
variety of reports on the usage of kicker, we need someone to read this
data and write a summary of usability issues and items.

It may be an idea to have a maintainer for writing a report for each
part of KDE. So we can have Kicker maintainer.

I will start a new thread to discuss this.

	Jono

-----Original Message-----
From: JP S-C [mailto:jp_sc@yahoo.com]
Sent: 27 July 2001 19:55
To: kde-usability@master.kde.org
Subject: Re: Stuff I will be doing


Jonathan Bacon wrote:
> ...
>  - Creating a reports area where people who have done usability tests
> can submit HTML reports to be placed on the site. It would be nice to
> have an annotations tool also for these reports.
>  - Developing the question API -> porting over the existing (limited!)
> API to the new framework
> 
> As for question tests, these should not be random but well developed
> tests based around what we expect to acheive in each study. I also
plan
> on developing an icon testing testbed but that may be down the line a
> bit.
> 
> Later we could do with a usability reports database, buts I don't
really
> think we want a load of old usability reports that never get purged.
> 
> Meanwhile, could people who have submitted reports on areas of KDE
that
> need work (such as the K Start button and the Ximian GNOME comparison
> report) please develop a report that I could load into the site. We
> could do with developing a formal look and feel for these reports, and
> maybe an online form for submitting them. If someone wants to develop
> this look and feel that would be great. :-)
> 
>         Jono

How are we going to ensure that all these reports come to together into
one coherent reccomendation?
Furthermore, isn't it possible that some of these reports might turn
into one developer's UI dislikes, which sort of defeats the point of
having "a study"?  I would think it might make more sense to first
design an overarching set of things we want to study, how we want to
study them, guidlines for conduct and presentation of reports, and then
divide them up and start a "Study To-Do List"?  Otherwise, couldn't we
run into problems when one study's reccomendations conflict with another
study that is done much later and seperately in a different fashion? 
This could be very frustrating to developers, who might follow one
study's reccomendations and change the UI's a bunch and then have
another study coming out reccomend something different.

I also have a dumb question :-)  What do you mean by "question API"? 
Are they questions or a way to write questions or a database?

Just some thoughts (and questions :-)

--JP


_________________________________________________________

Do You Yahoo!?

Get your free @yahoo.com address at http://mail.yahoo.com



_______________________________________________
kde-usability mailing list
kde-usability@master.kde.org
http://master.kde.org/mailman/listinfo/kde-usability
_______________________________________________
kde-usability mailing list
kde-usability@master.kde.org
http://master.kde.org/mailman/listinfo/kde-usability

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