On Tue, Nov 13, 2012 at 4:00 AM,
<frogr-list-request gnome org> wrote:
Send frogr-list mailing list submissions to
frogr-list gnome org
To subscribe or unsubscribe via the World Wide Web, visit
https://mail.gnome.org/mailman/listinfo/frogr-list
or, via email, send a message with subject or body 'help' to
frogr-list-request gnome org
You can reach the person managing the list at
frogr-list-owner gnome org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of frogr-list digest..."
Today's Topics:
1. About frogr 0.8 and removing support for GTK+ 2
(Mario Sanchez Prada)
----------------------------------------------------------------------
Message: 1
Date: Tue, 13 Nov 2012 10:17:18 +0100
From: Mario Sanchez Prada <msanchez gnome org>
To: frogr-list gnome org
Subject: About frogr 0.8 and removing support for GTK+ 2
Message-ID: <1352798238.1939.150.camel@zoiberg>
Content-Type: text/plain; charset="UTF-8"
Hi all,
I have been working a bit lately in the next release of frogr and, among
some other stuff, I've currently added the following things, to be out
with the 0.8 release:
- Better handling and reporting of errors in the 'after
upload operations' (e.g. adding to sets, setting license...)
- Support for uploading videos with frogr (requires gstreamer)
- Support for saving the current state into a "project file"
so you can load it later and continue working (WARNING: this
specific feature has not been heavily tested yet)
Now, I'd like to add a last new feature to frogr 0.8 which is migrating
to GMenu to use the global menu in environments supporting that, like
GNOME Shell, while at the same time simplifying the Mac OS X specific
code. This requires to migrate first to GTKApplication, though, and
depend on GTK+ 3.4 for that specific feature.
The thing is that we are already in GNOME 3.6 and heading towards 3.8
and so I'm considering to do a big change and require GTK+ >= 3.4 from
now on (now it's GTK+ >= 2.16).
Why? Well, mainly because of the following reasons:
- There's specific code in frogr for GTK < 2.24, then for
2.24 <= GTK < 3.0 and then for GTK >= 3.0. And if we port
to GMenu, we would add a new "GTK >= 3.4" step to maintain.
- There's code for Mac OS X, specific to the creation of the
global menu, that could be removed with GTK >= 3.4, which
comes already with support for that (thanks to GMenu).
- GTK+ 3.4 is already in Debian testing (which will soon be
stable) and in the latest Ubuntu LTS, which are the distros
I normally look at when considering raising the version of
the dependencies, as long as in any modern distro.
So that's why I think moving to GTK+ >= 3.4 would be a good move, even
if it is a big jump from 2.16: it would help writing new features while
dropping a lot of conditional code and, at the same time, it would
probably be not a problem for most of the users of frogr, who I assume
would be using a modern enough GNU/Linux distribution.
What do you think?
Mario
------------------------------
_______________________________________________
frogr-list mailing list
frogr-list gnome org
https://mail.gnome.org/mailman/listinfo/frogr-list
End of frogr-list Digest, Vol 10, Issue 1
*****************************************
