From: Namhyung Kim <namhyung.kim@lge.com>
To: Pekka Enberg <penberg@kernel.org>
Cc: Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Paul Mackerras <paulus@samba.org>, Ingo Molnar <mingo@redhat.com>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] perf ui/gtk: Use struct perf_error_ops
Date: Mon, 07 May 2012 16:40:19 +0900 [thread overview]
Message-ID: <874nrssal8.fsf@sejong.aot.lge.com> (raw)
In-Reply-To: <CAOJsxLEo32u8iYvQ+qeBX2YSKq=ftHs2jMdsKcCWWKO07XPGHg@mail.gmail.com> (Pekka Enberg's message of "Mon, 7 May 2012 10:17:41 +0300")
Hi,
On Mon, 7 May 2012 10:17:41 +0300, Pekka Enberg wrote:
> On Mon, May 7, 2012 at 9:03 AM, Namhyung Kim <namhyung.kim@lge.com> 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.
>>
>> Signed-off-by: Namhyung Kim <namhyung.kim@lge.com>
>
> I still don't like the dialog-based approach because it requires the
> *user* to respond. Just add a label to the GTK window and show the
> latest message there. If you want to make it even prettier, make the
> label clickable and open up a popup that shows all the warnings and
> errors in a separate window...
As I said before, most of calls to ui__warning/error are called just
before the main window is closed or critical enough to require user's
reponse - if not, it probably needs to use other API.
So I think it's OK for the current symantics of the API.
Thanks,
Namhyung
prev parent reply other threads:[~2012-05-07 7:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-07 6:03 [PATCH v2 1/2] perf ui: Introduce struct perf_error_ops Namhyung Kim
2012-05-07 6:03 ` [PATCH v2 2/2] perf ui/gtk: Use " Namhyung Kim
2012-05-07 7:17 ` Pekka Enberg
2012-05-07 7:40 ` Namhyung Kim [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=874nrssal8.fsf@sejong.aot.lge.com \
--to=namhyung.kim@lge.com \
--cc=a.p.zijlstra@chello.nl \
--cc=acme@ghostprotocols.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=paulus@samba.org \
--cc=penberg@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox