abrt.git/src/Gui/CReporterAssistant.py, branch 1.1.11

Be more polite with user

2010-07-14T10:51:01+00:00

Signed-off-by: Denys Vlasenko

GUI: allow sending crashes without rating

2010-07-12T20:19:00+00:00

- some crashes (koopses, python) doesn't require rating, because
  their backtrace is always good, so we don't rate them and GUI
  should treat them as the rating was good

From: Jiri Moskovcak

GUI: fixed package name in warning message when the packge is kernel rhbz#612191

2010-07-12T15:26:27+00:00

Author: Jiri Moskovcak

String updates

2010-07-12T11:43:30+00:00

GUI: fixed problem with no gkeyring and just one reporter enabled rhbz#612457

2010-07-08T11:37:25+00:00

GUI: don't die if crash info doesn't contain bt

2010-06-30T15:36:35+00:00

- and of course don't let user to report a bug without bt if the reporter
  plugin requires it

GUI: don't try to use action plugins as reporters

2010-06-22T21:06:47+00:00

- action plugins can be specified in AnalyzerActionsAndReporters,
  but those are run automatically when user press "report" and gui
  shouldn't show them in reporter selector

GUI: skip the plugin selection, if it's not needed

2010-06-16T13:24:11+00:00

- if there's only one reporter, then we can skip the first
  page in the wizard
- the page is skipped only if the plugin options are properly configured

minor gui fixes

2010-06-16T12:35:37+00:00

- made the report results selectable, center the wrong settings dialog

GUI: don't require the rating for all reporters

2010-06-16T09:07:09+00:00

- some reporters (logger, RHTSupport) doesn't require a good
  backtrace (so far only bz does) so gui shouldn't force user
  to have a good backtrace everytime