On Mon, Jan 5, 2015 at 5:57 PM, su_v <suv-sf@...58...> wrote:
On 2015-01-05 19:40 (+0100), Partha Bagchi wrote:
On Mon, Jan 5, 2015 at 9:05 AM, su_v <suv-sf@...58...> wrote:
On 2015-01-05 01:27 (+0100), Partha Bagchi wrote:
I compiled osxmenu (~suv's branch) using gtk3 and it looks good to me.
It was a little tricky since configure is not set to automatically do this
Inkscape with GTK3 is still at an experimental stage, hence it needs to be enabled intentionally (not automatically) by running configure with the corresponding option to enable it; for details see
$ ./configure --help | grep -A 1 gtk3
Yes I am aware of using --enable-gtk3-experimental during configure. Is that what you mean? You cannot build with gtk3 without this. Anyway, building with simply gtk3 does not enable any OSX menu features. You are left with a build that is similar to an XQuartz build.
I have just pushed a change to the osxmenu branch (r12890) to support compiling the branch with experimental GTK3 and gtk-mac-integration (if installed for gtk3) with these two configure flags (there should be no further changes required):
$ ./configure --enable-gtk3-experimental --enable-macintegration
I'm still convinced that Inkscape GTK3 OS X ports should _not_ use the external library 'gtk-mac-integration' for the global menubar and other features (and that instead Inkscape should be refactored so that the application can make use of the new built-in features of GTK3 for such integration tasks (on all supported gtk+ targets)).
Regards, V
We're totally aligned on this. However, John Rall's comment about gtk3 (https://wiki.gnome.org/Projects/GTK+/OSX/Integration) says, "Gtk+-3.4 added built-in quartz menu integration without documentation."
I don't know if the documentation has improved or not, though on the Mac I am using 3.14.6 and not the 3.15.x branch because of the new dependence on xlib!
Thanks, Partha