On 2014-12-28 15:04 (+0100), Norbert Nemec wrote:
I am currently trying to get inkscape running with gtk3/OSX-native. After quite a bit of struggling, I got everything compiled and executable. When I run inkscape, however, I get tons of assertions, the window looks terrible, is just barely responsive and completely unusable. The info on the web is not very conclusive, so I wonder:
Can't confirm with local inkscape trunk builds (I have bin compiling Inkscape trunk with experimental GTK3 on OS X 10.7.5 about since the time this is actually possible via configure option. Of the current local trunk builds (updated about once a week) with GTK+/X11 3.4.3, GTK+/Quartz 3.6.4, GTK+/X11 3.14.6 and GTK+/Quartz 3.14.6 (besides the regular GTK2 builds), not one exposes the issues you briefly described (to the point of being "completely unusable"). OTOH I would not have recommended experimental GTK3 builds for regular usage at this stage either (but they are more than "completely unusable" here, at least).
Minor detail: I never installed an unstable GTK3 release (or GTK+ from git master), and don't know the state of Inkscape trunk compiled and running with GTK+/Quartz 3.15.3 or master.
Independent of the used backend and platform, experimental GTK3 builds have still plenty of issues - a few have already been reported in the bug tracker: https://bugs.launchpad.net/inkscape/+bugs?field.tag=gtk3
- is inkscape OSX/native generally still in such a bad state or did I
maybe not build it correctly?
Can't really tell (no information about how you compiled trunk with experimental GTK3 on your Mac).
Based on my own limited experience, Inkscape packages compiled with GTK2/Quartz are not in _such_ a bad state in general (at least based on the user feedback for builds based on the 'osxmenu' branch [1]) - they aren't at release quality either though (Inkscape stable and trunk branches lack any OS X-specific integration code for the Quartz backend, and the updated macosx packaging scripts are still focused on creating an application bundle with GTK2/X11-based builds).
- is anyone working on this actively?
Inkscape trunk with GTK3 and Quartz backend specifically? Not that I am aware of.
- what is the state of inkscape/gtk3 in general?
- What are the areas that require work to improve the situation?
Perhaps, I could help out?
Inkscape with GTK3 in general is experimental and not "done" yet (yes, it compiles, but it seems to need a lot more work). This is no different for Inkscape with GTK3/Quartz on OS X. The official GTK+ version for Inkscape (stable, upcoming 0.91 and trunk) is still GTK2 at the moment, and AFAIK won't change in the near future.
Generally, I used to use inkscape quite heavily several years ago on Linux and absolutely loved it. Today, I am forced to use OSX for work and would sometimes love to have inkscape available for some quick drawing task. The usability of the inkscape/gtk2/XQuark on OSX, however, has always put me off using inkscape altogether (booting Linux for every occasional quick drawing is just not an option). I would really love to see this situation improve.
Too bad - you seem to dismiss any other option than GTK+/Quartz 3 for OS X. If this isn't quite true, you might want to give newer GTK2/X11-based app bundles a test, or even one with GTK2/Quartz. Links to downloads (OS X 10.7 or later) can be found on the download page at inkscape.org (0.91pre3, 0.91+devel)[2], and on my launchpad profile page [1] (including the experimental 'osxmenu' branch).
We also started an attempt to track osx packaging status in the wiki [3].
Regards, V
[1] https://code.launchpad.net/~suv-lp [2] http://inkscape.org/en/download/ [3] http://wiki.inkscape.org/wiki/index.php/Notes_on_Packaging_for_OS_X