I guess I'm curious: why would this break apps? If your apps were relying on a specific user setting to show/hide icons, wasn't it technically broken already? There was no guarantee of the value of the setting.
It seems that reducing the amount of user configurations an app developer would have to test in is a great idea for all. On Wed, Oct 9, 2013 at 2:09 PM, Erick Pérez Castellanos <eric...@gnome.org>wrote: > People keep raising this issue (both on list and on IRC) and I think > there's a good reason for it. > > And people will keep doing it, until they get proper answers. > > As an application developer why I found troubling about this particular > removal is: > > First: the fact that no-one has explained the reasons behind it. Certainly > we can guess the thing has to do with Wayland port but yet there's no > comment in those commits explaining the reasons behind it. > > Second: The workaround being settings the option in every widget of an > application is not a friendly towards app developers. > Right now, in a moment where new widgets come into Gtk+, the *Getting > Started* section appeared in the docs and there's this new attention to the > developer story with Gtk+ (and others), that doesn't seem very friendly at > all. > > -- > Art is the most intense mode of individualism that the world has known > Oscar Wilde > > > _______________________________________________ > gtk-devel-list mailing list > gtk-devel-list@gnome.org > https://mail.gnome.org/mailman/listinfo/gtk-devel-list > > -- Jasper
_______________________________________________ gtk-devel-list mailing list gtk-devel-list@gnome.org https://mail.gnome.org/mailman/listinfo/gtk-devel-list
