#50: ABRT GUI rework ---------------------------------+------------------------------------------ Reporter: zprikryl | Owner: Type: usability assessment | Status: new Priority: major | Milestone: Version: | Keywords: ---------------------------------+------------------------------------------ Hi, since we are "command line" users, we aren't sure about how GUI is designed. Can anybody tak a look at it? Basically, there are two windows.
First window includes a list of bugs with basic information like application name, package name, ... An user has two options. Either report a crash or delete a crash. If the user wants to report a crash, he chooses some crash by clicking and then click on the icon in the icon panel, after a while a second windows is displayed. If he wants to delete a crash, then he click on another icon.
Second window includes a list of detailed information. Some information the user can not change (like linux kernel version), some information he can change (like backtrace). When data have binary form (possibly large amount of data) the user can decide if he wants to include then in a report (by clicking on a checkbutton on left side). The same situation is when data have text form and text is large.
#50: ABRT GUI rework ---------------------------------+------------------------------------------ Reporter: zprikryl | Owner: duffy Type: usability assessment | Status: new Priority: major | Component: Artwork Severity: Quick & Easy | Resolution: Keywords: | ---------------------------------+------------------------------------------ Changes (by duffy):
* owner: => duffy * component: => Artwork * severity: => Quick & Easy
#50: ABRT GUI rework ---------------------------------+------------------------------------------ Reporter: zprikryl | Owner: duffy Type: usability assessment | Status: new Priority: major | Component: Artwork Severity: Moderately Involved | Resolution: Keywords: | ---------------------------------+------------------------------------------ Changes (by duffy):
* severity: Quick & Easy => Moderately Involved
#50: ABRT GUI rework ---------------------------------+------------------------------------------ Reporter: zprikryl | Owner: duffy Type: usability assessment | Status: new Priority: major | Component: Interaction Design / Usability Severity: Moderately Involved | Resolution: Keywords: | ---------------------------------+------------------------------------------ Changes (by duffy):
* component: Artwork => Interaction Design / Usability
#50: ABRT GUI rework ---------------------------------+------------------------------------------ Reporter: zprikryl | Owner: duffy Type: usability assessment | Status: new Priority: major | Component: Interaction Design / Usability Severity: Moderately Involved | Resolution: Keywords: | ---------------------------------+------------------------------------------ Comment (by duffy):
Hi!
So I'm trying to get abrt running on my F11 system but it just doesn't load. I tried to install it from the rawhide repo but it won't install because of a weird rpm error "rpmlib(PayloadIsXz) is needed by abrt- libs-0.0.7.1-1.fc12.x86_64"
I would like to get a feel for how the app works right now, any ideas on how I could run it?
Other than that I have some specific questions:
- How is it launched? It is launched from a desktop menu primarily? - Does it have an applet? - Does it pop-up a dialog during an application crash? - How does it interact with Bug Buddy? - What kind of user information is being collected to enable the bug report? Does the user need a Bugzilla user id / password? Does the user need to fill anything out or is the intention that just the backtrace gets sent and the user doesn't need to input anything?
Are there any specific applications you're trying to model it against? E.g., I think the kernel oops reporting tool is nice, because it almost never gets in my way, it just does its job and doesn't need to be touched or configured, it just works. Rather than have a separate GUI with a separate menu item for this, you might want to consider building a preferences capplet for it for the system menu, and just letting the users modify whatever information is there (email address, bugzilla log, whatever) but have sane defaults, and maybe have a tab where they can look up the status of the bugs they already reported (I wish that kernel oops had this.)
Let me know what you think.
#50: ABRT GUI rework ---------------------------------+------------------------------------------ Reporter: zprikryl | Owner: duffy Type: usability assessment | Status: new Priority: major | Component: Interaction Design / Usability Severity: Moderately Involved | Resolution: Keywords: | ---------------------------------+------------------------------------------ Comment (by jmoskovc):
hi, the version in F11 repository is pretty old (I'll update it ASAP), but if you want to try it, you can use this yum repo file http://jmoskovc.fedorapeople.org/abrt.repo and install the latest packages.
How is it launched? It is launched from a desktop menu primarily?
- from menu - or by clicking on applet
Does it have an applet?
- yes
Does it pop-up a dialog during an application crash?
- it pops-up the notify bubble
How does it interact with Bug Buddy?
- it doesn't
What kind of user information is being collected to enable the bug
report? - user needs to fill in the bugzilla login+password
Does the user need to fill anything out or is the intention that just
the backtrace gets sent and the user doesn't need to input anything? - it's intended to gather the information automatically, but user can change/add some information
Are there any specific applications you're trying to model it against?
- not really, we took some ideas from Apport, but only for applet
The kerneloops
- this approach wouldn't work with bugzilla as it needs at least the login info which doesn't have any defaults
Rather than have a separate GUI with a separate menu item for this
- I thought about this, but then applet would have to be visible all the time, but it's not that big problem.
Have a nice day, Jirka
#50: ABRT GUI rework ---------------------------------+------------------------------------------ Reporter: zprikryl | Owner: duffy Type: usability assessment | Status: new Priority: major | Component: Interaction Design / Usability Severity: Moderately Involved | Resolution: Keywords: | ---------------------------------+------------------------------------------ Changes (by jmoskovc):
* cc: jmoskovc@redhat.com (added)
#50: ABRT GUI rework ---------------------------------+------------------------------------------ Reporter: zprikryl | Owner: duffy Type: usability assessment | Status: new Priority: major | Component: Interaction Design / Usability Severity: Moderately Involved | Resolution: Keywords: triaged | ---------------------------------+------------------------------------------ Changes (by duffy):
* keywords: => triaged
Comment:
Triaged 6 Apr 2010.
I am actively working with Jirka on this project. The latest mockups are here: https://fedoraproject.org/wiki/Design/ABRT_UI/UI_Suggestions_Mar_2010
#50: ABRT GUI rework ---------------------------------+------------------------------------------ Reporter: zprikryl | Owner: duffy Type: usability assessment | Status: closed Priority: major | Component: Interaction Design / Usability Severity: Moderately Involved | Resolution: fixed Keywords: | ---------------------------------+------------------------------------------ Changes (by nightmoves):
* cc: jmoskovc@redhat.com (removed) * keywords: triaged => * status: new => closed * resolution: => fixed
Comment:
Spoke with kirkb and decided we close this since #180 is open.
design-team-tickets@lists.fedoraproject.org