Linux Perf Users
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Matt Turner" <mattst88@gmail.com>
Cc: linux-perf-users@vger.kernel.org
Subject: Re: [PATCH v8 1/3] tools: port perf ui from GTK 2 to GTK 4
Date: Wed, 09 Sep 2026 03:06:14 +0000	[thread overview]
Message-ID: <20260909030614.E84551F00A3A@smtp.kernel.org> (raw)
In-Reply-To: <20260908-perf-gtk2-v8-1-e90d5d155f0d@gmail.com>

> Port straight to GTK 4 rather than GTK 3, since GTK 4 is where new
> development happens and GTK 3 is old itself now.
> 
> GTK 4 drops GtkContainer, GdkScreen, and the gtk_main()/
> gtk_dialog_run() family perf's GTK UI relied on. Containers get
> per-widget setters (gtk_box_append() and friends), monitor geometry
> comes from GdkMonitor instead of GdkScreen, and the main and
> error-dialog loops become explicit GMainLoops quit from the
> "close-request" and "response" signals. Widgets are visible by default
> now, so gtk_widget_show_all()/set_no_show_all() go away, and the
> remaining gtk_widget_show()/gtk_widget_hide() calls become
> gtk_widget_set_visible() (with a small wrapper where "response" needs
> to pass gtk_widget_hide() as a callback, since it no longer exists as
> a plain function).
> 
> [ ... ]
> and the check treats deprecation warnings as errors.
> HAVE_GTK_INFO_BAR_SUPPORT and its statusbar-only fallback go away; the
> info bar is now built unconditionally.
> 
> Signed-off-by: Matt Turner <mattst88@gmail.com>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260908-perf-gtk2-v8-0-e90d5d155f0d@gmail.com?part=1


  reply	other threads:[~2026-09-09  3:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-09  2:50 [PATCH v8 0/3] perf tools: port UI from GTK2 to GTK4 Matt Turner
2026-09-09  2:50 ` [PATCH v8 1/3] tools: port perf ui from GTK 2 to GTK 4 Matt Turner
2026-09-09  3:06   ` sashiko-bot [this message]
2026-09-09  2:50 ` [PATCH v8 2/3] perf tools: make the GTK4 report browser actually loadable at runtime Matt Turner
2026-09-09  3:01   ` sashiko-bot
2026-09-09  2:50 ` [PATCH v8 3/3] perf tools gtk: fix two hierarchy-view stack buffer overflows Matt Turner
2026-09-09  3:10   ` sashiko-bot
2026-09-09 11:13 ` [PATCH v8 0/3] perf tools: port UI from GTK2 to GTK4 Arnaldo Carvalho de Melo
2026-09-09 11:25   ` Arnaldo Carvalho de Melo
2026-09-09 11:29     ` Arnaldo Carvalho de Melo
2026-09-09 11:35       ` Arnaldo Carvalho de Melo
2026-09-09 11:43         ` Arnaldo Carvalho de Melo
2026-09-09 11:52           ` Arnaldo Carvalho de Melo
2026-09-09 20:02             ` Arnaldo Carvalho de Melo

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=20260909030614.E84551F00A3A@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-perf-users@vger.kernel.org \
    --cc=mattst88@gmail.com \
    --cc=sashiko-reviews@lists.linux.dev \
    /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