From: "Kim, Dongwon" <dongwon.kim@intel.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: <qemu-devel@nongnu.org>
Subject: Re: [RFC PATCH v2 0/2] ui/gtk: Introduce new param - Connectors
Date: Wed, 12 Jun 2024 16:33:56 -0700 [thread overview]
Message-ID: <0fe76150-c347-40df-8d69-18a5d132d8bc@intel.com> (raw)
In-Reply-To: <CAJ+F1CLAJTZLHKa9_zVo=-GLRw8JHnzJT=G4fdLLsaS1sK2HUg@mail.gmail.com>
On 6/11/2024 11:42 PM, Marc-André Lureau wrote:
> Hi
>
> On Tue, Jun 11, 2024 at 10:28 PM Kim, Dongwon <dongwon.kim@intel.com
> <mailto:dongwon.kim@intel.com>> wrote:
>
> Hi Marc-André,
>
> On 6/5/2024 12:26 AM, Marc-André Lureau wrote:
> > Hi
> >
> > On Tue, Jun 4, 2024 at 9:59 PM Kim, Dongwon
> <dongwon.kim@intel.com <mailto:dongwon.kim@intel.com>
> > <mailto:dongwon.kim@intel.com <mailto:dongwon.kim@intel.com>>> wrote:
>
> > Xorg may not be going away soon, but it's used less and less. As
> one of
> > the developers, I am no longer running/testing it for a long time. I
> > wish we would just drop its support tbh.
>
> There are features offered by Xorg that are not offered by Wayland
> compositors and again, we have customers that rely on these features.
> One of them is the ability to position the window via
> gtk_window_set_position(). There are strong arguments
> made on either side when it comes to window positioning:
> https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/247 <https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/247>
>
> Until there is a way to do this with Wayland compositors, we have to
> unfortunately rely on Gnome + Xorg.
>
>
> It's a smaller and smaller number of users. The potential/future users
> are greater if we focus on Wayland.
Right, but until Gtk + Wayland offers the same feature parity and
customization as that of Gtk + Xorg, there will be distros/users that
will keep it alive.
>
> Fwiw, GNOME (and RHEL) is set to drop Xorg support
> (https://gitlab.gnome.org/GNOME/gnome-session/-/merge_requests/98
> <https://gitlab.gnome.org/GNOME/gnome-session/-/merge_requests/98>)
Doesn't look like it is going to happen anytime soon given the massive
pushback.
>
> Btw, there is a similar monitor-mapping functionality implemented in
> virt-viewer/remote-viewer:
> https://www.mankier.com/1/virt-viewer#Configuration
> <https://www.mankier.com/1/virt-viewer#Configuration>. Is this something
> that those users could use instead?
It looks a bit similar and interesting but one difference is that our
feature uses monitor labels such as DP-1, HDMI-2 which is a bit more
intuitive. And, the other key difference is that our feature includes
"hotplug" functionality where a Guest display/window is deeply tied to a
physical monitor to make it appear to the guest that it is dealing with
a real physical monitor.
In other words, when the physical monitor is unplugged, the associated
guest display/window gets destroyed/hidden and gets recreated/shown when
the monitor is hotplugged again.
>
>
> --
> Marc-André Lureau
next prev parent reply other threads:[~2024-06-12 23:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-31 18:58 [RFC PATCH v2 0/2] ui/gtk: Introduce new param - Connectors dongwon.kim
2024-05-31 18:58 ` [RFC PATCH v2 1/2] ui/gtk: Factor out tab window creation into a separate dongwon.kim
2024-05-31 18:58 ` [PATCH RFC v2 2/2] ui/gtk: Add a new parameter to assign connectors/monitors dongwon.kim
2024-06-04 10:37 ` [RFC PATCH v2 0/2] ui/gtk: Introduce new param - Connectors Marc-André Lureau
2024-06-04 17:59 ` Kim, Dongwon
2024-06-05 7:26 ` Marc-André Lureau
2024-06-11 18:28 ` Kim, Dongwon
2024-06-12 6:42 ` Marc-André Lureau
2024-06-12 23:33 ` Kim, Dongwon [this message]
2024-06-13 6:56 ` Marc-André Lureau
2024-06-13 17:08 ` Kim, Dongwon
2024-06-14 8:41 ` Marc-André Lureau
2024-06-14 17:40 ` Kim, Dongwon
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=0fe76150-c347-40df-8d69-18a5d132d8bc@intel.com \
--to=dongwon.kim@intel.com \
--cc=marcandre.lureau@gmail.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).