From kde-core-devel Sat Jul 23 10:32:46 2011 From: Dodji Seketeli Date: Sat, 23 Jul 2011 10:32:46 +0000 To: kde-core-devel Subject: Re: Formal complaint concerning the use of the name "System Settings" Message-Id: X-MARC-Message: https://marc.info/?l=kde-core-devel&m=131141745932446 Denis Washington a écrit: > Am 23.07.2011 11:54, schrieb Giovanni Campagna: >> Il giorno sab, 23/07/2011 alle 11.27 +0200, Dodji Seketeli ha scritto: >>> Matthias Clasen a écrit: >>> >>>> I don't think Shauns proposal addresses the issue, really. >>> >>> Why? Do you have an example that would show where Shaun's proposal >>> falls short? >> >> You have two .desktop files, matching the same application, so it is >> possible gnome-shell, unity or kde could pick the wrong one when >> matching desktop files to windows (unless you tweak Exec to pass >> --class, but that fails again with single-instance applications) > > But one of them is hidden via [Not]OnlyShowIn. There should be code in > all desktop's .destkop file matchers to prefer the files tailored to > the respective environment, and if not, it is easy enough to add. Exactly. > I think everyone here agrees that this more a less a temporary measure > and that other long-term solutions such as better cross-desktop > settings integration is in order. I couldn't agree more. Giovanni Campagna a écrit: [please don't CC me in your replies. I am subscribed to at lease one of the lists in the To: field] >> > If you want an app to be usable in different environments, then there >> > are some good solutions: >> > - make sure the app is self-contained and manages all of its settings itself >> > - make your app smart enough to pick up the relevant settings from the >> > different environments you want to support >> > >> > And there are bad solutions, including: >> > - making the app drag along half of its original environment, via dependencies >> >> You don't say why these would better address the issue "here and now" in >> comparison with what Shaun is proposing. > > You get to configure your apps once for both Gtk and Qt apps, which is > better for the user and makes the system more consistent > In particular, I underline "Gtk and Qt": you don't write GNOME apps, and > you don't write KDE apps, you write Gtk and Qt (or Qt+kdelibs) apps, and > then the toolkits adapts themselves to the environment. If you can write > a Qt+kdelibs app that work on windows or mac os x, you can make it work > out of the box in GNOME, without dragging in the entire workspace. You forgot the "here and now" part in my question. You just can't do what Mathias is proposing /quickly/ enough. It would seem to me that we need a stop gap measure now, while we carefully think about something more streamlined and future proof to be crafted later. -- Dodji