From qubes-devel Sun Apr 02 21:41:46 2017 From: Joanna Rutkowska Date: Sun, 02 Apr 2017 21:41:46 +0000 To: qubes-devel Subject: Re: [qubes-devel] Re: Preferred framework for graphical stuff? Message-Id: <20170402214146.GA1228 () work-mutt> X-MARC-Message: https://marc.info/?l=qubes-devel&m=149116931201502 -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On Sun, Apr 02, 2017 at 02:39:28PM -0400, Jean-Philippe Ouellet wrote: > On Mon, Nov 21, 2016 at 11:13 PM, Marek Marczykowski-G=C3=B3recki > wrote: > > -----BEGIN PGP SIGNED MESSAGE----- > > Hash: SHA256 > > > > On Mon, Nov 21, 2016 at 10:57:25PM -0500, Jean-Philippe Ouellet wrote: > >> On Mon, Nov 21, 2016 at 10:14 PM, Marek Marczykowski-G=C3=B3recki > >> wrote: > >> > Generally yes, especially the part about choosing GTK ;) > >> > >> Noted. > >> > >> > Since then we've moved to default Xfce, and GTK will be more consist= ent here. > >> > >> Are you saying that Xfce as default is the long term plan now? > >> > >> Or saying that there will be more consistency between {GTK in Xfce vs. > >> GTK in Gnome} than {Qt in Xfce vs. Qt in Gnome}? > >> > >> I don't understand. > > > > Both Gnome and Xfce use GTK widgets, so GUI parts done in GTK (vs Qt) > > are more consistent with the rest of desktop environment. >=20 > [1] has made me give some more thought to this. Yes, GTK is the > natural choice for things wishing to be first-class citizens in Gnome, > but this may not be the strongest consideration long-term. >=20 > Moving to Gnome has stagnated, and is a very low priority [2]. >=20 > With the planned disaggregation of the GUI into its own domain [3], > iteration in the desktop experience of Qubes becomes much easier, and > I think it's quite reasonable to consider that Gnome may not be the > only final target. >=20 > I think it is also worthwhile to consider the difference in experience > between Qt in primarily-not-Qt environments, vs. GTK in > primarily-not-GTK environments. On other non-linux platforms, Qt is > much better integrated into the native desktop UX than GTK. This is at > least true on Windows and OS X, and even Genode has native support for > Qt which continues to improve. This may may sound irrelevant now, but > I think is less so post-GuiVM. >=20 > FWIW it seems that peoples' complaints about the current Qt > qubes-manager in Xfce have nothing to do with it being Qt instead of > GTK. >=20 > I'd also like to bring attention to some relevant 3rd party > discussions on this: [4] >=20 > I believe that limiting the inputs to this decision to "Gnome means > GTK, we plan to eventually target Gnome, therefore let's use GTK" may > be short-sighted. >=20 > Thoughts? >=20 > [1]: https://groups.google.com/d/msg/qubes-devel/jDHiZ9nhzIc/5DIRzcOUCwAJ > [2]: https://github.com/QubesOS/qubes-issues/issues/1806#issuecomment-280= 281571 > [3]: https://github.com/QubesOS/qubes-issues/issues/833 > [4]: https://askubuntu.com/questions/281092/why-is-canonical-choosing-qt-= over-gtk-for-unitys-next-generation >=20 These are all good points, JP. But I think it's difficult and often counter-productive to try to over-generalize or make code over-portable "ju= st in case". So, I think that the choice of the GUI framework should be dictated primarily by the requirement to make our GUI stuff first-class citizens of whatever Desktop Environment we want to be the official one in the upcoming release. At this time we believe that for both 4.0 and 4.1 this will be Xfc= e4. The next criterion should be ease of development/integration with current c= ode. Perhaps for Qubes 5.x we will want to switch to some yet-unknown desktop environment, but then, chances are high, we will want to rewrite any GUI st= uff anyway. This is because the new environment might use different UX paradigm= s, or maybe in a few years time the general UX paradigm will change. So, ISTM, tr= ying to plan too much ahead (which framework/lang to use for GUI/UX), might ofte= n not be worth it. joanna. -----BEGIN PGP SIGNATURE----- iQIcBAEBCAAGBQJY4XAaAAoJEDOT2L8N3GcY7WMP/0RLgL7xxKjoSaKznPE0jiKy v8djdN4lEEhZEESg3Zc5H0LtTa/4ECfuThG5VqCEiCcry1IvzPhwInU8AH1JWoyn 6wRK0ogsy3tggC/90OHmJpKCJzaunD7XEUa5Gme7weDPTHWpbhnrh9UOEQzEJ4EH bzKbgnjxR8uuoj0xOeo32gFkN3xQ6Bu0LxmeiWBtVbORGd90E8b/M7dlq9WY2g0l Sj31ZMCSi6ugPrbW+EgCoLm/bqRMMQFKZBlVZEwF19/prrUUqxCmY9KAZbGFENMe MHSCAFAlXfAyiqA3xkZs8uaTLSq2WdK+jwaJqmk4rlBC9wlKOWLdldo413rT8Lvz TwHzSfLAVauxe1p2ej5HoNje8KOnwtnC52vIwaRuBOFr8x+oeQlRLZgPGUlxmYVn Xyt48CEis2bG18XuRgmN1f/QBw2F/FY0yQvawQgOlnJgpMc4tL5xjzrEvXHJSGxq bqwyn8NYAiWqjkZ1id11wLV8OyFe5iIi1rwUxZxBl8Y2wCaptnHzYTcHkTkQSy11 m5fh9BB8iohWyNMGCBSeXLTqoyO9AYjaHj4dKa37KF+oRzf/LOd2RZEx+Y+NVj3f mDv85+0/mAu4A3fmAVtDngyVdtEPCTbgnRzeLlTu8tnHNEI2/qAubCDUJbh7e7Sl Ez7Zu1x9heFBg/1wzaZD =3DfQYz -----END PGP SIGNATURE----- --=20 You received this message because you are subscribed to the Google Groups "= qubes-devel" group. To unsubscribe from this group and stop receiving emails from it, send an e= mail to qubes-devel+unsubscribe@googlegroups.com. To post to this group, send email to qubes-devel@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/= qubes-devel/20170402214146.GA1228%40work-mutt. For more options, visit https://groups.google.com/d/optout.