Re: [Denemo-devel] Building Denemo with --enable-gtk2

[Richard Shann]

On Tue, 2015-11-24 at 23:50 -0600, Jeremiah Benham wrote:
> I
> On Nov 24, 2015 10:52 AM, "Richard Shann" <address@hidden>
> wrote:
> >
> > On my new Debian Jessie system I can build for Gtk3 but when I try
> > configuring for a gtk2 build I get this:
> >
[...]
> That is set too low obviously. We can compile against any version of
> evince as far as I know. I think you may need to roll your own it you
> insist upon that.

Well, Andreas has just emailed to say that "However, evince 3 depends on
GTK 3, which makes no sense to use in a GTK 2 build."

So I think we are coming even more quickly to the crunch time - I have
just put in a fix that means you can do without the tool tips on menu
items - you press f1 while hovering to get the context-sensitive help,
but this doesn't work for the explanations about the playback controls
etc which are now lost for users of Gtk>3.10

> >
> > Any help appreciated - we are going to have to work with Gtk2 more I
> > think, as it is stable while Gtk3 is becoming ususable.
> 
> Ok. Should we sign up for summer Google of code.  We can propose a
> migration to QT. I am half joking. 
yes - GSOC is only useful for a smallish task requiring specialist
knowledge that the "student" can bring - otherwise it is a drain on our
resources not a gain.

> I love the look and feel of gtk but QT is already on mobile platforms.
> This is why you can now get musescore for Android or Apple platforms.

This is an area I know very little about. I assumed that doing something
as complex as creating a music score on a mobile device was a
non-starter. But your comment about creating small music exercises while
commuting to work has got me wondering.
The problem that will arise is that I don't have a mobile device (words
like Android have quite a different meaning to me) and so can't help see
the way forward here. I do see that the Gtk team are adapting the API to
target those devices and causing problems for the older ones.

Richard