On the OSX debate... a few years ago I would not have cared about OSX native versions at all, but it's true that Apple products have been getting
more popularin recent years.
But, can't there be a dedicated OS X team as opposed to forcing the core team to dedicate itself to it? Apple products aren't exactly cheap, and how many systems does one have to force all developers to use?
Maybe Inkscape could send an announcement on the website asking for an OS X team, something in the lines of "As some of you know, Inkscape currently lacks a native OS X build. However, as Apple products have become more popular, more people are also asking for a native version of Inkscape. However, not all the developers use OS X, so if you are a
developer familiar with OS X, we welcome you to join the Inkscape team to help produce native OS X builds."
I'm willing to bet that if people are actually aware that Inkscape is looking for sure a team, you'll get a few responses offering to help.
I admit, I already use Windows and Linux, and I'm not personally interested in OS X. I'm much more interested in features such as Pablo Trabajos' transformation anchors blueprint, layer masks (especially since unlike raster programs, you can't just lock visible pixels), and maybe a few more layer composite modes like overlay. Powerstroke of course, but that's happily in the works. :)
(on the other hand... how many people want to use Inkscape on touchscreen devices? I'm not familiar with this area, so forgive me if there are actually a lot of them)
On Mon, Feb 13, 2012 at 7:24 AM, Valerie wrote:
Maybe Inkscape could send an announcement on the website asking for an OS X team, something in the lines of "As some of you know, Inkscape currently lacks a native OS X build. However, as Apple products have become more popular, more people are also asking for a native version of Inkscape. However, not all the developers use OS X, so if you are a developer familiar with OS X, we welcome you to join the Inkscape team to help produce native OS X builds."
Noted, thanks :)
However, do we have an up to date information on state of affiars with native GTK+ builds?
raster programs, you can't just lock visible pixels), and maybe a few more layer composite modes like overlay.
More blending/compositing options will be available in SVG2.
http://dev.w3.org/SVG/modules/compositing/master/Overview.html
Alexandre Prokoudine http://libregraphicsworld.org
On Feb 12, 2012, at 8:54 PM, Alexandre Prokoudine wrote:
On Mon, Feb 13, 2012 at 7:24 AM, Valerie wrote:
Maybe Inkscape could send an announcement on the website asking for an OS X team, something in the lines of "As some of you know, Inkscape currently lacks a native OS X build. However, as Apple products have become more popular, more people are also asking for a native version of Inkscape. However, not all the developers use OS X, so if you are a developer familiar with OS X, we welcome you to join the Inkscape team to help produce native OS X builds."
Noted, thanks :)
However, do we have an up to date information on state of affiars with native GTK+ builds?
More progress picked up on GTK+ itself at the end of last October. I've started trying to actually build it native myself in the last few weeks, but hit some issues with Pango. Once I get such things cleared, I'll be able to push needed fixes upstream with GTK+ itself.
Personally I think it's looking good that native OSX GTK might wind up giving us fewer total bugs than we see with the recent combinations of X11 and OSX.
On Mon, Feb 13, 2012 at 9:13 AM, Jon Cruz wrote:
Maybe Inkscape could send an announcement on the website asking for an OS X team, something in the lines of "As some of you know, Inkscape currently lacks a native OS X build. However, as Apple products have become more popular, more people are also asking for a native version of Inkscape. However, not all the developers use OS X, so if you are a developer familiar with OS X, we welcome you to join the Inkscape team to help produce native OS X builds."
Noted, thanks :)
However, do we have an up to date information on state of affiars with native GTK+ builds?
More progress picked up on GTK+ itself at the end of last October. I've started trying to actually build it native myself in the last few weeks, but hit some issues with Pango. Once I get such things cleared, I'll be able to push needed fixes upstream with GTK+ itself.
Personally I think it's looking good that native OSX GTK might wind up giving us fewer total bugs than we see with the recent combinations of X11 and OSX.
Are you telling me that I should link from the news item to this mail of yours instead of some wiki page?
Alexandre Prokoudine http://libregraphicsworld.org
On 13/02/2012 05:54, Alexandre Prokoudine wrote:
On Mon, Feb 13, 2012 at 7:24 AM, Valerie wrote:
Maybe Inkscape could send an announcement on the website asking for an OS X team, something in the lines of "As some of you know, Inkscape currently lacks a native OS X build. However, as Apple products have become more popular, more people are also asking for a native version of Inkscape. However, not all the developers use OS X, so if you are a developer familiar with OS X, we welcome you to join the Inkscape team to help produce native OS X builds."
Noted, thanks :)
However, do we have an up to date information on state of affiars with native GTK+ builds?
The bit-rotten and partially broken menubar integration code has been removed from trunk and the 0.48.x branch. Both branches now build out-of-the-box with GTK+/X11 or GTK+/Quartz backend (depending on how the rest of the dependencies was configured).
Inkscape built with the Quartz backend of gtk2 has still several user interface issues to be addressed in Inkscape's code (AFAICT): no global menubar integration for now, no Mac-alike keyboard shortcuts, no function keys either, slower startup time, slight delays in drawing updates on-canvas. OTOH the many crashes (e.g. when trying to save a new drawing or open a second dialog window) caused by the outdated broken code (ige-mac-menu.*) are gone now.
Major drawback of the "native" builds for a graphics application like Inkscape (or MyPaint or GIMP): gtk2/quartz (upstream) does not offer support for tablets beyond simple drawing device (no pressure sensitivity, etc.).
There is a blueprint for new packaging routines for Quartz builds, but that's still WIP and needs to have some details (like bundling the required python modules) addressed.
Notes: above comments are based on using MacPorts for the dependencies, and on my own experience with creating local builds of trunk with the Quartz-backend of gtk2 (32bit, Leopard) as well as with the X11-backend (Leopard, Lion). Possibly Jon has plans to move to jhbuild-based builds entirely for the Quartz-backend - personally I have not tried this build system [1] yet nor have I seen any packaging scripts or build instructions for that on the list here or the Inkscape wiki.
~suv
[1] http://live.gnome.org/GTK%2B/OSX/#Building.2C_Bundling.2C_and_Integrating
participants (4)
-
Alexandre Prokoudine -
Jon Cruz -
Valerie -
~suv