NativeUIMacOsX

2010-03-24T09:20:37Z

Bugmenot2: Replaces links to imendo

During a discussion on the Developer's mailing list, it was pointed out that there was a consensus that the Inkscape project should create a Mac OS (Quartz) product using [http://live.gnome.org/GTK%2B/OSX Gtk+ for OSX].

== Dependencies ==
=== glib ===

=== [http://git.or.cz/ git] ===
You will need a working git to check out the Cairo sources. You can download a [http://kernel.org/pub/software/scm/git/git-1.3.2.tar.bz2 current snapshot], which compiles and runs flawlessly. There is a [http://pdb.finkproject.org/pdb/package.php/git git fink package] which Tiger users might prefer.

=== [http://www.cairographics.org/ Cairo] ===
At the time of writing, Gtk+ needs version 1.1.6 or later which is more recent than the [http://cairographics.org/releases/ latest unstable release] and more recent by far than the [http://pdb.finkproject.org/pdb/package.php/cairo-shlibs cairo package in fink]. As the build instructions do state, the only practical way of obtaining a suitable Cairo is to use the development sources available from the [http://cairographics.org/download#head-d5e2030369f7e642e430ae50d9ad3dc7981b5a4f git repository].

Here is a suggested configuration:
<code>../configure '--enable-debug=yes' '--prefix=/panther-quartz' 'CXXFLAGS=-fmessage-length=0' 'CFLAGS=-fmessage-length=0' '--enable-quartz' '--enable-atsui'</code>

When the script has run, it will produce a lengthy report which should resemble:<pre>cairo will be compiled with the following surface backends:
image: yes (always builtin)
Xlib: yes
Quartz: yes
XCB: no (disabled, use --enable-xcb to enable)
Win32: no (the Microsoft Windows backend requires a Win32 platform)
PostScript: yes
PDF: yes
SVG: yes
glitz: no (disabled, use --enable-glitz to enable)
BeOS: no (disabled, use --enable-beos to enable)
DirectFB: no (disabled, use --enable-directfb to enable)

the following font backends:
FreeType: yes
Win32: no (the Microsoft Windows backend requires a Win32 platform)
ATSUI: yes

the following features:
PNG functions: yes

and the following debug options:
gcov support: no
test surfaces: no

using CFLAGS:
-I/sw/include/libpng12 -I/usr/X11R6/include -I/sw/lib/freetype219/include/freetype2 -I/sw/include/libxml2 -I/sw/include -Wall -Wpointer-arith -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs -fno-strict-aliasing

*** The Quartz backend is still under active development and
*** is included in this release only as a preview. It does not
*** fully work yet and incompatible changes may yet be made
*** to Quartz-backend specific API.

*** The ATSUI backend is still under active development and
*** is included in this release only as a preview. It does not
*** fully work yet and incompatible changes may yet be made
*** to ATSUI-backend specific API.
</pre>
=== [http://www.pango.org/ Pango] ===
The stated requirement is for version 1.9.0, and I have successfully used the 1.9.1 snapshot. The [http://pdb.finkproject.org/pdb/package.php/pango1-xft2-ft219 pango fink package] is version 1.10.1, and I suggest that you don't use this (since we want to compile our own pango with pangocairo support), and instead use a snapshot later than 1.10.1, to avoid confusion.

Here is a suggested configuration:<code>../configure '--prefix=/panther-quartz' 'CFLAGS=-fmessage-length=0' 'CPPFLAGS=-fmessage-length=0' 'CXXFLAGS=-fmessage-length=0' '--enable-debug=yes'</code>

Note that the configure script will pick up the existence of Cairo without further ado.

In particular, note that when the configure script has finished, it reports which backends it will use, ''videlicet''<pre>configuration:
backends: FreeType X Xft Cairo</pre>

If you don't see Cairo in that list, then it is time to polish up your autoconf debugging skills. See [http://www.ddj.com/184402060 GNU Autoconf]

=== atk ===

== Known Issues ==

[[Category:Developer Discussion]]

PowerStroke

2010-03-24T05:21:04Z

Bugmenot2: /* Comments */

= Power stroke =

The proposed power stroke LPE is as follow:

[[Image:Power-stroke-1.png]]

== Functionality ==

This LPE allows a modulated stroke from manually entered values.

Further development could allow direct width reading from a pressure-enabled device.

== Workflow ==

The user simply creates the line, it might for example be based on an outline.

Then the user applies the LPE to his shape, it overrides the normal stroke rendering and allows custom line width at different nodes of the path.

Only the stroke-width property of the path is overridden, the rest of the stroke properties keep working as usual, when relevant.

== GUI ==

Se image above. User selects a nodes or a set of nodes and affects values to those. When a node is selected, you can see what its value is by the change in values in the number entry or by the state of the push button.

Additionally, hovering over a node could show the value of a node. Graphical feedback could even possibly set different icons for nodes that are set and others that are interpolated.

Perhaps Alt+drag a node to change the thickness?

A combination of a metakey and the scroll wheel would be intuitive as well (with status bar message stating you can do that, of course). -- [[jegHegy]]

= Comments =

== By JohanE ==
This is very well doable, but would require a new "Nodepath" implementation that enables writing special values (preferably a struct) per node. There is already something like this, the "nodetypes" attribute, but it is too restrictive. Expanding this would enable this effect, and opens up many other possibilities. Nice idea !

== By Pajarico ==
I'm thinking this tool could allow the user to copy a path or an object or group of objects to any node in a path. Which is similar to what you're proposing, only this doesn't use interpolation between adjacent nodes, it just places an element on a specific node (or nodes if you have several selected).

I'm not sure if it is better to open a separate blueprint or not. --Pajarico, [[User:Pajarico|Pajarico]] 22:36, 21 June 2008 (UTC)

== By rubikcube ==
You might want to have a look at how [http://www.synfig.org synfig] handles varying width for paths. Paths are called "Blines" there, the relevant feature is explained shortly at the bottom of [http://synfig.org/Creating_Shapes one of its manual pages]. --[[User:Rubikcube|Rubikcube]] 17:26, 3 September 2008 (UTC)

== By Klesus ==
In concept I've been thinking of this for a long time, so I'm hopeful that this possibly could be expanded to allow control of other things than stroke width like say, stroke color, opacity and perhaps even blur(!) although I doubt blur is something that would be impossible to implement.
Just my 2 cents.

Inkscape Wiki - User contributions [en]

NativeUIMacOsX

PowerStroke