On Wed, Jul 29, 2015 at 02:07:50PM +0200, Matěj Cepl wrote:
On 2015-07-29, 10:47 GMT, Michael Schwendt wrote:
>> As I have thought for some time, I think we should have a team to keep
>> packages and make migrations like gtk2 to gkt3, libgnome2, pyorbit,
>> gnome-python2, pyhton2 to python3 , qt3 etc etc
>
> Wishful thinking. Porting from gtk2 to gtk3 is non-trivial or not even
> feasible in all cases (without dropping some features/implementations).
> Some developers are unhappy with gtk3. Others switch to Qt.
I would say that the transition from Gtk2 to Gtk3 was pretty
much a disaster especially in terms of the 3rd part software.
FWIW I found the port of Gtk3 pretty straightforward for
my Entangle application and find it quite alot nicer to work
with than Gtk2 in general, so has been a big plus overall.
I would *not* suggest that Fedora maintainers do any such
porting work though, as maintaining such a fork from upstream
would be seriously painful. Leave any porting work to the
upstream community to decide to do, or not.
* GIMP of all programs (original software for which Gtk was
created) is still Gtk2.
The GTK3 port is on GIMP's roadmap for their 3.0 release
series, but they need to get their port to gegl finished
before that
http://wiki.gimp.org/wiki/Roadmap
* Actually, I have hard time to imagine which large 3rd party
projects did switch from Gtk2 to Gtk3.
As an alternative to random FUD, here's some actual data
# dnf repoquery --whatrequires 'libgtk-3.so.0()(64bit)'
...plenty of significant apps/projects using Gtk3 there,
not least of all evolution, totem, evince, gnumeric,
ephinany, emacs
Regards,
Daniel
--
|:
http://berrange.com -o-
http://www.flickr.com/photos/dberrange/ :|
|:
http://libvirt.org -o-
http://virt-manager.org :|
|:
http://autobuild.org -o-
http://search.cpan.org/~danberr/ :|
|:
http://entangle-photo.org -o-
http://live.gnome.org/gtk-vnc :|