Re: [PATCH 7/7] perf ui/gtk: Use struct perf_error_ops

From: Namhyung Kim
Date: Mon May 07 2012 - 04:27:28 EST


Hi,

On Mon, 7 May 2012 10:10:51 +0200, Ingo Molnar wrote:
> * Namhyung Kim <namhyung.kim@xxxxxxx> wrote:
>
>> Hi,
>>
>> On Mon, 30 Apr 2012 09:31:28 +0300 (EEST), Pekka Enberg wrote:
>> > On Mon, 30 Apr 2012, Namhyung Kim wrote:
>> >> Define and use perf_gtk_eops to provide a GTK2 message
>> >> dialog for error reporting. To do that, we need global
>> >> main_window variable for tracking UI state.
>> >>
>> > I think this is an usability glitch waiting to happen - especially so if
>> > you use it for warnings. There's no reason to require the user to react to
>> > warning messages in the GUI because there's absolutely nothing they can do
>> > about them.
>> >
>> > I guess we could do something like the "ui helpline" thing used by the
>> > newt front-end if we really wanted to.
>> >
>> > Pekka
>>
>> I did quick grep on ui__warning and found that most of its
>> users are trying to show the messages before exiting. I think
>> some (at least) of them can be converted to ui__error(). And
>> as existing implementation (TUI) already requires user input
>> for this, I thought it's ok.
>>
>> But I agreed with you that ui__warning should not be used for
>> showing non-critical messages and converted to helpline-style
>> ones.
>
> If they are in essence ui__error() already then please convert
> them to ui__error() instead of perpetuating the mistake - don't
> force annoying pop-ups for warnings that may or may not be
> fatal. Spurious pop-ups are sad and people hate them.
>

Ok, will do that in another patch (series). So you mean ui__warning
should not be a pop-up dialog, right?

Thanks,
Namhyung
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/