Launchpad Entry:
https://blueprints.launchpad.net/inkscape/+spec/fillet-tool

== Summary ==
The filleting tool will allow the user to replace the cusp of a corner on a path, with a rounding arc of specified radius. This is rather simple to the way we can round off the corners rectangles, but for arbitrary geometry.

Note that this proposed tool will only work on corners in individual paths - not on the intersections of the strokes of separate objects.

== Release Note ==

== Rationale ==
A fillet/chamfer tool is useful for technical drawings where fillets and chamfers are needed often, and smoothing corners in artwork.

== Design ==
=== User Interface ===
In terms of implementation, the filleting tool must be implemented as a first class citizen along with the rest of the toolbox - having a tool commands toolbar, a cursor, status messages etc., just like other tools. In terms of the UI for activating the tool - this could be added as another icon in the toolbox, but it might be better to hide the tool away in a well chosen location (discuss), so as not to clutter the toolbox with a new tool that is really very specialist.

To fillet a corner, the user will activate the tool, then click on the cusp point with the mouse. It might be possible to add a button in the tool commands bar that fillets all the corners in a shape.

An edit box with spinner will be placed in the tool commands bar so that the user can choose the radius for the fillet.

It might be helpful (discuss) to give the choice between placing a full circle object into the corner, a tangential arc object of the fillet, or actually filleting the corner with an arc which will modify the parent path to replace the cusp.

This tool could give the option to chamfer the corner - where instead smoothing the corner with an arc, the corner is smoothed with a straight line - simply snipping the tip off.

A good starting point for this tool would be the code from the node editor tool, because it already has UI code for selecting of nodes in a path. Code from this tool can be used, to fillet when the user clicks on a point.

=== Back End ===
The illustration below shows the steps involved in filleting the corner of a path:

[[Image:Fillet.png]]

Filleting a corner is a 3-step process. First, the centre point for the arc must be calculated (X and Y in fig 1 and fig 2a). Second, the arc's sweep must be calculated so that it merges with the parent path at the tagents (fig 2b). Third, the point of the corner must be snipped off, and the arc welded on (fig 2c).

All shapes must be converted to paths before filleting can occur.

Finding point X is mathematically trivial. Finding Y is very much harder, and will require a numerical solution to a set of simultaneous equations. Note that there could potentially be more than one possible solution (as shown in fig 2a), so the closest solution to the cusp along the the length of bezier should be selected.

== TODO ==

== Discussion ==

SpecFilletChamfer

2008-02-05T18:14:43Z

Joelholdsworth: /* Design */

Launchpad Entry:
https://blueprints.launchpad.net/inkscape/+spec/fillet-tool

== Summary ==
The filleting tool will allow the user to replace the cusp of a corner on a path, with a rounding arc of specified radius. This is rather simple to the way we can round off the corners rectangles, but for arbitrary geometry.

Note that this proposed tool will only work on corners in individual paths - not on the intersections of the strokes of separate objects.

== Release Note ==

== Rationale ==
A fillet/chamfer tool is useful for technical drawings where fillets and chamfers are needed often, and smoothing corners in artwork.

== Design ==
=== User Interface ===
In terms of implementation, the filleting tool must be implemented as a first class citizen along with the rest of the toolbox - having a tool commands toolbar, a cursor, status messages etc., just like other tools. In terms of the UI for activating the tool - this could be added as another icon in the toolbox, but it might be better to hide the tool away in a well chosen location (discuss), so as not to clutter the toolbox with a new tool that is really very specialist.

To fillet a corner, the user will activate the tool, then click on the cusp point with the mouse. It might be possible to add a button in the tool commands bar that fillets all the corners in a shape.

An edit box with spinner will be placed in the tool commands bar so that the user can choose the radius for the fillet.

It might be helpful (discuss) to give the choice between placing a full circle object into the corner, a tangential arc object of the fillet, or actually filleting the corner with an arc which will modify the parent path to replace the cusp.

This tool could give the option to chamfer the corner - where instead smoothing the corner with an arc, the corner is smoothed with a straight line - simply snipping the tip off.

A good starting point for this tool would be the code from the node editor tool, because it already has UI code for selecting of nodes in a path. Code from this tool can be used, to fillet when the user clicks on a point.

=== Back End ===
The illustration below shows the steps involved in filleting the corner of a path:

[[Image:Fillet.png]]

Filleting a corner is a 3-step process. First, the centre point for the arc must be calculated (X and Y in fig 1 and fig 2a). Second, the arc's sweep must be calculated so that it merges with the parent path at the tagents (fig 2b). Third, the point of the corner must be snipped off, and the arc welded on (fig 2c).

All shapes must be converted to paths before filleting can occur.

Finding point X is mathematically trivial. Finding Y is very much harder, and will require a numerical solution to a set of simultaneous equations. Note that there could potentially be more than one possible solution (as shown in fig 2a), so the closest solution to the cusp along the the length of bezier should be selected.

== TODO ==

* Flesh this specification out in more detail

== Discussion ==

SpecFilletChamfer

2008-02-02T20:05:31Z

Joelholdsworth: /* Rationale */

SpecFilletChamfer

2008-02-02T20:04:09Z

Joelholdsworth: /* Design */

SpecFilletChamfer

2008-02-02T20:01:28Z

Joelholdsworth: /* Design */

2008-01-31T19:30:25Z

Joelholdsworth: New page: Lanchpad Entry: https://blueprints.launchpad.net/inkscape/+spec/parametric-function-plotter == Summary == Create a new extension similar to the function plotter which plots parametric for...

INX extension descriptor format

2008-01-31T18:49:33Z

Joelholdsworth: /* See Also */

== Introduction ==

In order for Inkscape to make use of an external script or program, you must describe that script to inkscape using an INX file. See the inkscape share directory for examples. The INX file allows the author to:
* label strings for translation
* define parameters
* chain extensions
* etc
Be sure to read through the INX files that come with Inkscape. Nothing beats a working example.

== Localisation of extensions ==

To allow localisation of strings in extension for Inkscape, some xml tags have to be adapted to variant readable by intltool. It means that tags or parametres has to have "_" prepended to their name, e.g. <_name>name of extension</_name>

Also the path to the extension has to be included in POTFILES.in file to tell intltool where to look for translatable content.

Usefull information, before this section gets fully updated, can be found at [http://gould.cx/ted/blog/Translating_Custom_XML Ted's blog].

== Example ==
More example INX files are available in the Inkscape distribution or in the Inkscape [http://inkscape.svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/share/extensions/|SVN repository].

<pre>
<inkscape-extension>
<_name>{Friendly Extension Name}</_name>
<id>{org.domain.sub-domain.extension-name}</id>
<dependency type="executable" location="[extensions|path|plugins|{location}]">program.ext</dependency>
<param name="tab" type="notebook">
<page name="controls" _gui-text="Controls">
<param name="{argumentName}" type="[int|float|string|boolean|description]" min="{number}" max="{number}"
_gui-text="{Friendly Argument Name}">{default value}</param>
</page>
<page name="help" _gui-text="Help">
<param name="help_text" type="description">{Friendly Extension Help}</param>
</page>
</param>
<effect>
<object-type>[all|{element type}]</object-type>
<effects-menu>
<submenu _name="{Extension Group Name}"/>
</effects-menu>
</effect>
<script>
<command reldir="extensions" interpreter="[python|perl|ruby|bash|{some other}]">program.ext</command>
</script>
</inkscape-extension>
</pre>

== DTD ==

<!ELEMENT inkscape-extension (name, id, dependency*, param*,(input|output|effect),(script|plugin))>
<!ELEMENT input (extension, mimetype, filetype, filetypetooltip, output_extension?)>
<!ELEMENT output (extension, mimetype, filetype, filetypetooltip, dataloss?)>
<!ELEMENT effect (object-type)>
<!ELEMENT script (command, helper_extension*, check*)>
<!ELEMENT plugin (name)>
<!ELEMENT name (#PCDATA)>
<!ELEMENT id (#PCDATA)>
<!ELEMENT item (#PCDATA)>
<!ELEMENT dependency (#PCDATA)>
<!ELEMENT param (#PCDATA, page*, item*)>
<!ELEMENT page (#PCDATA, param*)>
<!ELEMENT extension (#PCDATA)>
<!ELEMENT mimetype (#PCDATA)>
<!ELEMENT filetype (#PCDATA)>
<!ELEMENT filetooltip (#PCDATA)>
<!ELEMENT object-type (#PCDATA)>
<!ELEMENT command (#PCDATA)>
<!ELEMENT check (#PCDATA)>
<!ELEMENT dataloss (#PCDATA)>
<!ELEMENT helper_extension (#PCDATA)>
<!ELEMENT output_extension (#PCDATA)>

<!ATTLIST check reldir (absolute|path|extensions|plugins) #REQUIRED>
<!ATTLIST command reldir (absolute|path|extensions|plugins) #REQUIRED>
<!ATTLIST command interpreter CDATA #REQUIRED>
<!ATTLIST dependency type (executable|extension) #REQUIRED>
<!ATTLIST dependency location (absolute|path|extensions|plugins) #IMPLIED>
<!ATTLIST dependency description CDATA #IMPLIED>
<!ATTLIST page name CDATA #REQUIRED>
<!ATTLIST page gui-text CDATA #IMPLIED>
<!ATTLIST param name CDATA #REQUIRED>
<!ATTLIST param type (int|float|string|boolean|enum|notebook|description) #REQUIRED>
<!ATTLIST param min CDATA #IMPLIED>
<!ATTLIST param max CDATA #IMPLIED>
<!ATTLIST param precision CDATA #IMPLIED>
<!ATTLIST param gui-text CDATA #IMPLIED>
<!ATTLIST submenu name CDATA #REQUIRED>

== See Also ==
*[[ScriptingHOWTO]]

[[Category:Developer Documentation]]
[[Category:Help Wanted]]
[[Category:Extensions]]

SpecRicherExtensionParameters

2008-01-25T10:41:18Z

Joelholdsworth: /* Design */

Lanchpad Entry:
https://blueprints.launchpad.net/inkscape/+spec/richer-extension-parameters

== Summary ==

Suggestions include:
#Colour Selector
#Angle Selector
#On-Canvas Selection of X/Y Points
#On-Canvas Selection of Objects (a la Live Path Effects)
#Random Seed Selector (a la Live Path Effects)
#File Selector Dialog

== Release Note ==

== Rationale ==

== Design ==
Suggestions include:
=== Colour Selector ===
Could we use the same control as in Document Properties dialog? with the choice for alpha, or no alpha?

=== Angle Selector ===
An option for the angle selector would be the one proposed for GIMP [http://gimp-brainstorm.blogspot.com/2007/12/angle-widget-for-motion-blur.html here] (circle with a radial arrow that can be dragged around).
=== On-Canvas Selection of X/Y Points ===
=== On-Canvas Selection of Objects (a. la Live Path Effects) ===
=== Random Seed Selector (a la Live Path Effects) ===
=== File Selector Dialog ===

== TODO ==

* Flesh this specification out in more detail

== Discussion ==

SpecRicherExtensionParameters

2008-01-25T10:40:56Z

Joelholdsworth: /* Summary */

Lanchpad Entry:
https://blueprints.launchpad.net/inkscape/+spec/richer-extension-parameters

== Summary ==

Suggestions include:
#Colour Selector
#Angle Selector
#On-Canvas Selection of X/Y Points
#On-Canvas Selection of Objects (a la Live Path Effects)
#Random Seed Selector (a la Live Path Effects)
#File Selector Dialog

== Release Note ==

== Rationale ==

== Design ==
Suggestions include:
=== Colour Selector ===
Could we use the same control as in Document Properties dialog? with the choice for alpha, or no alpha?

=== Angle Selector ===
An option for the angle selector would be the one proposed for GIMP [http://gimp-brainstorm.blogspot.com/2007/12/angle-widget-for-motion-blur.html here] (circle with a radial arrow that can be dragged around).
=== On-Canvas Selection of X/Y Points ===
=== On-Canvas Selection of Objects (a. la Live Path Effects) ===
=== File Selector Dialog ===

== TODO ==

* Flesh this specification out in more detail

== Discussion ==

SpecRicherExtensionParameters

2008-01-16T21:24:58Z

Joelholdsworth: /* Colour Selector */

Lanchpad Entry:
https://blueprints.launchpad.net/inkscape/+spec/richer-extension-parameters

== Summary ==

Suggestions include:
#Colour Selector
#Angle Selector
#On-Canvas Selection of X/Y Points
#On-Canvas Selection of Objects (a. la Live Path Effects)
#File Selector Dialog

== Release Note ==

== Rationale ==

== Design ==
Suggestions include:
=== Colour Selector ===
Could we use the same control as in Document Properties dialog? with the choice for alpha, or no alpha?

=== Angle Selector ===
An option for the angle selector would be the one proposed for GIMP [http://gimp-brainstorm.blogspot.com/2007/12/angle-widget-for-motion-blur.html here] (circle with a radial arrow that can be dragged around).
=== On-Canvas Selection of X/Y Points ===
=== On-Canvas Selection of Objects (a. la Live Path Effects) ===
=== File Selector Dialog ===

== TODO ==

* Flesh this specification out in more detail

== Discussion ==

SpecRicherExtensionParameters

2008-01-16T19:27:30Z

Joelholdsworth: /* Summary */

Release notes/0.46

2007-08-08T22:40:25Z

Joelholdsworth: /* Even more improvements */

=Inkscape 0.46=
'''(not released yet)'''

Major things in this release:

* Paintbucket tool

* Tweak tool

* 3D box tool

* LPEs

* native PDF and AI import

* new SVG filters and UI

* full on-canvas gradient editing

* engraver's toolbox

* touch selection

* command line access to verbs

* snapping made usable

=Speed and interactivity=

* In this version, Inkscape starts using the [http://www.cairographics.org cairo] library for rendering. It is now used for '''outline mode''' display which, thanks to using cairo and other optimizations, redraws '''faster by about 25%'''. More impressive are memory savings: thanks to cairo, in outline mode Inkscape now takes only about '''50% of the memory''' used by 0.45 for the same file.

* '''Smart redraw directionality:''' With complex images and/or on slow computers, you may have noticed that Inkscape redraws the screen image in horizontal strips, and these strips are painted sequentially top to bottom. Now this direction is automatically changed based on where your mouse cursor is. In particular, if mouse is closer to the bottom of the area to redraw, strips will be painted in the bottom-to-top order. This significantly improves the responsiveness and interactivity in some situations. For example, when you are node-editing the bottom part of a complex path, the entire path needs to be redrawn on each change, but now this redraw starts from the bottom and therefore the you see the effect of your changes at once - i.e. while screen redraw may still lag behind your mouse movement, this lag is less noticeable.

* '''Faster blur''' for exporting and high quality on-screen rendering: Inkscape now uses an IIR (Infinite Impulse Response) filter for blurring with large radius. This greatly improves the speed of blur redraw at high zooms or in high-resolution export (or simply with very large blur radius). On the other hand, the results are an approximation to a true Gaussian blur, so a drawing may look slightly different from the mathematically precise blur (usually the differences are far from visible, though). This code is mainly based on: ''Recursive Gaussian Derivative Filters'' by L.J. van Vliet, I.T. Young and P.W. Verbeek (see the source code for more detailed references).

* '''Moving the cursor around''' in a file with large and complex paths has become much snappier and more responsive. Previously, in extreme cases Inkscape could freeze for seconds while catching up with the mouse cursor; such delays are now eliminated.

* Several improvements make '''canvas panning and scrolling''' smoother and more interactive in complex slow-rendering documents:

:* When panning by the middle mouse button, Inkscape no longer attempts to redraw the canvas while your mouse button is pressed. Any redrawing only happens after you release the mouse. As a result, the newly revealed parts of the canvas are somewhat more "dirty" but the '''panning is smoother than before''', with few if any "hiccups".

:* Previously, if you start panning with middle button while Inkscape is still redrawing screen in a complex drawing, panning sometimes completely failed or moved canvas just a little step. Now it is '''guaranteed to pan the canvas all the way''' from mouse-press point to mouse-release point in any case, even if sometimes it fails to show the intermediate positions.

:* When pressing and holding Ctrl+arrows to scroll canvas, Inkscape normally accelerates scrolling so that each next scrolling step is bigger than the previous. Previously, in complex drawings this acceleration sometimes got interrupted, which made scrolling annoyingly bumpy and slow. Now this is fixed so that '''scrolling is smoothly accelerated''' even in a slow-rendering document.

:* The default '''starting speed and acceleration''' of Ctrl+arrows scrolling are slightly increased. (They are both settable in Preferences.)

=Tools=

==Paint Bucket tool==

The new Paint Bucket tool works exactly as you would expect: click in any area bounded on all sides and it will '''fill it with color'''. Being a vector tool, however, Inkscape's Paint Bucket just creates a new ''path'' that "fills in" the area in which you clicked.

It is important to note that the tool is '''perceptual''', not geometric. That is, when looking for the boundaries around the point you clicked, it takes for such boundaries any ''visible'' color changes. This means that filling will stop at gradients, blurs, and even the color boundaries in imported bitmaps, but will ignore any paths or other objects that are fully (or almost) transparent or for any other reason do not stand out from the background. In short, it will work exactly as if you were filling a rasterized version of your image in a bitmap editor like Photoshop or GIMP - but will give you a vector object to work with.

For example, now you can scan a pencil sketch, import the bitmap into Inkscape, and quickly fill all its cells with colors even without tracing the bitmap first. This is a very convenient and interactive way of digitizing your paper drawings, making the '''traditional bitmap tracing unnecessary''' in many cases.

Internally, the tool works by performing a bitmap-based flood fill on a rendered version of the visible canvas, then tracing the resulting fill using [[potrace]] and placing the traced path into the document.

It places the rendered path onto the current layer, so you can have a layer on top (for example, "Inks") and select the layer below ("Colors") and do the fills so that they always appear below the Inks.

The '''resolution''' of the bitmap image used to perform the trace is dependent upon your '''current zoom level''' -- the more zoomed in to an area that you are, the higher the resolution of the bitmap-based flood fill. So, if you are got a fill that is too imprecise, has rough corners, or don't go into small nooks and appendices where it is supposed to go, just undo, zoom in closer and repeat filling from the same point. Conversely, if the fill leaks out through a small gap, zoom out to make the gap less visible and fill again.

Like all object-creating tools, the Paint Bucket may use the '''last-set style''' for the objects it creates (this is the default), or it can use its own '''fixed style'''. You can switch between these modes on this tool's page in Inkscape Preferences (Ctrl+Shift+P).

In the tool's '''Controls bar''':

* '''Tolerance''' (set in per cent units) controls how large must be color difference at a point (compared to the initial click point) to stop the fill. Zero tolerance means only the area of strictly the same color will be filled; the larger the tolerance, the easier it will be for the fill to leak into adjacent different-color areas. The default value is 10%.

* You can control the amount of '''inset/outset''' to be applied to the created fill path. Setting a positive outset causes fill paths to be larger than the filled bitmap area (good for eliminating anti-aliasing errors), while setting a negative outset causes the path to be smaller. This works the same as the Outset and Inset path commands.

* Paint Bucket's perceptual fill can use either all visible colors or specific color '''channels'''. You can restrict the fill algorithm to the following channels:
** Red
** Green
** Blue
** Hue
** Saturation
** Lightness
** Alpha

* An '''auto gap''' setting. When enabled, Paint Bucket will try to close any gaps in the area boundaries that would normally cause the fill to spill out of the desired area. There are four settings to auto gap:
** None
** Small (fill gaps up to 2 pixels in size)
** Medium (4 pixels)
** Large (6 pixels)

* A '''style swatch''' on the far right of the bar shows the style that will be used for the next fill object you create.

The tool's '''shortcuts''' are:

* '''Single click''' performs filling from the click point.

* '''Shift+click''' performs filling from the click point and then unions the resulting path with the selected path. This way, if your first attempt did not fill in all of the desired area, you can Shift+click the remaining corner to fill it in separately and combine the result with the result of the previous fill.

* '''Ctrl+click''' on an object simply changes that object's fill to the current fill color of the tool, and '''Shift+Ctrl+click''' changes the stroke to the current stroke color.

* '''Click and drag''' performs filling from '''all of the points''' that you pass while dragging (you will see your path visualized by a red line). From each point, the fill spreads to the neighbors with the colors similar to that point - in other words, it's like clicking with this tool at each point of the drag path and unioning the results. This lets you easily fill an area occupied by a gradient or blur - just drag from the darkest to the lightest points in the area you want to fill.

* '''Alt+click and drag''' works similarly to simple drag, except from each point of the drag path, the fill spreads to the neighbors (if any) with the colors similar to the ''initial point'' (the point where you started the drag). This lets you fill a series of similarly-colored yet separated areas (for example, multiple cells in a cartoon) by starting the drag in one of those areas, and alt+dragging the tool through all the other areas.

==Tweak tool==

The Tweak tool is an exciting new way to edit paths. Unlike the Node tool, you don't need to worry about where the nodes of a path are and how to manipulate them to obtain the shape you want. Instead, you just act on any part of a path using the tool's "brush" in order to bend, twist, or stretch that part, and the path will respond smoothly and naturally regardless of where its nodes lie. While not very useful for technical applications such as schemes or diagrams, this tool will be indispensable for artistic uses of Inkscape - cartoons, drawings, sketches, anime, etc. This new functionality is somewhat similar to the "Pucker", "Bloat", and other similar tools in the latest versions of Adobe Illustrator, except that in Inkscape it works softer and is easier to
control.

The area of the tool's action (its "brush") is visualized as an orange-colored circular
outline centered at your mouse pointer. However, that area actually has no sharp
boundaries; the power of the tool's action falls off gradually, following a smooth
bell-shaped profile. This makes the tool act softly and smoothly, and the paths respond
as if they are made of soft jelly.

The tool will work on any number of selected objects; for example, you can select all
(Ctrl+A) and "smear" your entire drawing by Push. If applied to a shape or text, the
tool converts them to paths automatically. You can also apply it to groups of
objects. If you're trying to use it without anything selected, it will remind you to
select some objects by a statusbar message.

===Width===

The width of the tool's brush can be changed by the '''Width''' control in the tool's
controls bar above the canvas (in the range from 1 to 100). You can also change width by
'''Left''' and '''Right''' arrow keys (same as in the Calligraphy tool) at any time (including
during action). Also like in Calligraphy tool, the visible width of the brush is
independent of zoom; simply zooming in or out is often easier than adjusting the width
if you want to cover a smaller or larger area of the drawing.

===Force===

The next control is '''Force''' which adjusts the power of the action (in the range from
1 to 100). You can also change width by '''Up''' and '''Down''' arrow keys at any time
(including during action).

Think of it as the force of pressure you apply to the paths you tweak. If you have a
pressure-sensitive tablet and your "Use pressure" button on the right-hand end of the
controls bar is on, then the force will also depend on how hard you actually press your
pen into your tablet, changing in the range from zero to whatever you set in the Force
control. If all you have is a mouse, then the force will be constant but still settable
by the Force control. The force of the effect also depends on zoom (or in other words,
it stays the same when measured by screen pixels, same as when you move and object by
Alt+arrow keys).

===Fidelity===

Any tweaking of a path slightly distorts the entire path, including even those parts
that you didn't touch. These distortions are similar to those that a Simplify command
produces. The '''Fidelity''' value (also in the range from 1 to 100, default is 50)
allows you to control the amount of these distortions. With a higher fidelity, the
distortions are less noticeable, but the path may end up having a lot of nodes which
blows up the SVG size and slows down Inkscape.

The best value of Fidelity depends on the nature of your artwork. If you're sculpting an
amorphous blob, you can do with low fidelity of about 20. If, however, you are pushing
or blowing a text string (as a single path) and want the letters outside the distorted
area to remain crisp and clean, you will need to raise fidelity to 80 or more.

===Modes===

There are currently four modes in the Tweak tool: '''Push''', '''Melt''', '''Blow''',
and '''Roughen'''.

* This default mode of the tool, '''Push''', simply displaces the part of the path under the cursor in the direction of the drag. The path behaves like soft jelly, bending and bulging smoothly and naturally. It's an easy way to produce various irregular, lifelike, handmade-looking shapes starting from something as simple as an ellipse or a calligraphic stroke. For parallel-stroke hatching (engraving) done in the Calligraphy tool, pushing is an easy way to bend, pinch, or curve the entire hatching uniformly.

* The '''Melt and Blow''' are two opposite modes that move each point of a path in a direction perpendicular to the path's surface at the point, either inwards (Melt) or outwards (Blow). This is similar to the Inset and Outset commands, except that the Tweak tool can act on a part of a path instead of the whole path.

:For example, the visible lightness/darkness of an engraving hatching may not exactly correspond to your artistic intention. Also, the ends of strokes are often far from ideal - they may be too blunt or have unsightly bends or blobs. This is where the Tweak tool may help. Select all the strokes in a hatching pattern and apply a light Melt action where you want the lines to become thinner (and the hatching to become lighter), up until total disappearance. If you press hard, melting works as an eraser, so you can easily clean the strokes' ends in a hatching to making them thin, sharp, and uniform. Conversely, applying Blow makes strokes wider (i.e. the hatching becomes darker).

:Of course, melting and blowing are useful not only for calligraphic strokes. Same as with Push, with Melt and Blow you can '''sculpt''' any path, spawning smooth treacle-like appendages with Blowing and carving holes with Melting. Unlike the "node sculpting" mode in the Node tool, however, this does not require adding new nodes to the shape or selecting any nodes.

* The '''Roughen''' mode does exactly this: roughens the edge of the path without changing its overall shape. Slight roughening simply makes the edge crooked and uneven; strong roughening tears and explodes the edge into random blobs and splotches. Note that this operation, especially with high Fidelity, adds a lot of nodes which increases the size of your SVG document and may slow down Inkscape considerably. In particular, pushing/melting/blowing of a roughened path becomes much slower and more difficult, so it's recommended to finalize the overall shape of a path first and roughen it, if necessary, only as the final step.

===Keyboard shortcuts===

* '''W''', '''Alt+F2''': switch to the Tweak tool

* '''Shift+P''': switch to the Push mode

* '''Shift+M''': switch to the Melt mode

* '''Shift+B''': switch to the Blow mode

* '''Shift+R''': switch to the Roughen mode

* '''Left, Right, Home, End''': change width

* '''Up, Down''': change force

* '''mouse drag''': act on selected path in the current mode

* '''Ctrl+mouse drag''': temporarily switch to Melt (while Ctrl is down)

* '''Shift+Ctrl+mouse drag''': temporarily switch to Blow (while Shift+Ctrl is down)

===Known problems===

Known problems with the Tweak tool:

# it is rather slow;
# it quickly eats memory; and
# it is sometimes buggy - thin calligraphic strokes may suddenly disappear or change their shape drastically as you're melting or blowing them.

For (3), it helps to increase Fidelity. Also, you can undo the bad change and try again with less pressure on the pen - if you do your thinning in several light touches instead of one heavy press, usually you will be able to get the desired result without the buggy behavior.

Also, sometimes after roughening, further tweaking of a path becomes impossible with this diagnostic:

WARNING **: Shape error in ConvertToShape: directedEulerian(a) == false

All these problems stem from the livarot library that we use for geometric manipulation of paths. Fortunately, livarot is scheduled for replacement by lib2geom, a new library now in development, so hopefully these issues will be addressed then.

==3D Box tool==

Inkscape is a two-dimensional drawing tool. However, very often it is used to draw three-dimensional objects. The new '''3D box tool''' helps you create such 3D drawings by automating the most common operation: creating a three-dimensional box in a given perspective. The tool automatically ensures that all sides of the box lie on the corresponding perspective lines. We're not going to compete with Blender - but even simple things can go a long way.

Currently in the 3D box tool you can:

* draw a 3D box by dragging on canvas (use Shift+dragging without releasing the mouse button to extrude in z direction)

* adjust any of its 3 dimensions by handles

* adjust the vanishing points of a perspective by dragging them across the canvas (see below) or toggling their states; all boxes sharing this perspective are transformed accordingly

In SVG, a 3D box is represented as a '''group''' (svg:g) with a special extension attribute (in inkscape namespace); this group contains the 6 quadrilateral '''paths''' representing the sides of the box. Only the 3D box tool treats this object as a box; for all other tools it is just a group, so you can select any of the paths by Ctrl+click, apply any style to it, delete it, etc. You can of course transform the entire box or any face in it using Selector or Node tools.

When several boxes are selected, all vanishing points of their associated perspectives are shown on the canvas. If vanishing points of different perspectives coincide, they are combined in a single "dragger". Moving this dragger moves all the vanishing points simultaneously and transforms the associated boxes accordingly. Note that some non-selected boxes may also be reshaped if their perspectives share the same vanishing point. Pressing Shift while moving the dragger can be used to only transform the selected boxes, separating their perspectives from the non-selected ones'. On the other hand, when a vanishing point being dragged comes close enough to another one, both snap together and are combined in a single dragger.

===Keyboard shortcuts===

* '''X''', '''Alt+F4''': switch to the 3D box tool

* '''L''': toggle visibility of perspective lines

* '''A''': when perspective lines are visible, toggle between "all lines" and "only lines connected to front corners" (this can help to avoid visual clutter)

[max]

==Gradient Tool==
Stops in gradients can be added, deleted, and edited on-canvas now.
*Stops can be added by '''double clicking''' or by '''Ctrl+Alt+Click''' on the gradient line.
*Stops can be deleted by '''Ctrl+Alt+Click''' on a stop or by the '''Del''' key for all the selected stop(s).
:*When you delete an end stop, the nearest intermediate stop becomes the new end stop of the gradient (without moving - i.e., the gradient span becomes shorter).
:*When you delete an end stop and there are no intermediate stops, the object will be painted with a solid fill taken from the color & opacity of the remaining stop.
*More than one stop can be selected at a time by '''Shift+click'''.
:*Can be moved together if next to each other.
:*Can be deleted at the same time.
:*When you have one of the '''gradient handles selected''', its style (color and opacity) is reflected by the selected style indicator (left of the statusbar) and the Fill&Stroke dialog. Previously, opacity of a gradient handle was reflected as fill-opacity and stroke-opacity; now it is reflected as '''master opacity''' (the "O:" spinbutton in the selected style indicator, the "Master opacity" slider in Fill&Stroke). This makes it much easier to view and change opacity of gradient handles using only the selected style indicator in the statusbar.
:*When multiple gradient stops are selected, the selected style indicator (in the statusbar) displays and controls the averaged color and opacity of the selected stops.
*If the selected object(s) have gradient in fill or stroke, the '''selected style indicator''' in the bottom-left corner of the editing window now displays a '''live gradient preview''' prefixed by '''R''' or '''L''' to indicate Radial or Linear gradients (instead of displaying "L Gradient" or "R Gradient" text labels as before). Also, this and other similar widget now use italic font face to indicate <i>None</i> and bold to indicate <b>Unset</b>.
* When copy/pasting or duplicating an object with gradient, it now automatically gets a '''copy''' of the original gradient, so modifying it does not affect the source object's gradient anymore (before, you had to press the Duplicate button on the Gradient controls bar for this).

==Calligraphy tool: Engraver's Toolbox ==

Several new features were added to the Calligraphic pen to make
Inkscape capable of the ancient art of '''line
engraving'''. Traditional engraving is a very labour-intensive
process, and while for a long time it was the only practical way
of reproducing lifelike images in black-and-white print, about a
century ago it was almost completely displaced by automatic
halftone screens. However, line engravings have their
characteristic charm, and there's no reason not to try to
resurrect this art form with the help of Inkscape.

A brief visual guide to the new functionality can be seen on
these screenshots:

http://inkscape.org/screenshots/gallery/inkscape-0.46-engraving1.png

http://inkscape.org/screenshots/gallery/inkscape-0.46-engraving2.png

===Tracking a guide path with Ctrl===

One of the most common operations in line engraving is
'''hatching''' (or sometimes ''cross-hatching'' when several
hatching grids cross): filling a space with many parallel
straight or variously curved lines (usually of varying width to
represent a gradual shading). You could try to achieve a similar
effect with e.g. path interpolation (blending), but it is rather
cumbersome and limited; manual drawing of hatch lines, on the
other hand, is tedious and nearly impossible to do
uniformly. Now Inkscape provides "assisted hatching" by
'''tracking a guide path''', allowing you to hatch quickly and
uniformly and at the same time giving you sufficient manual
control over the process.

Here's how to do this. First, select the '''guide path''' that
you will track. It may be another calligraphic stroke, any path
or shape, or even a letter of a text object. Then switch to
Calligraphic pen, select the desired parameters (line width,
angle, fixation etc.) and, before starting to draw, press
Ctrl. You will see a gray '''track circle''' centered at your
mouse pointer and touching the closest point on the selected
guide path. (If you have no guide path selected, a statusbar
message will tell you to select it.)

Now move your mouse close to the guide path, so that the track
circle radius is equal to the desired spacing of your hatch
pattern, and start drawing along the guide path. At that moment,
the radius of the circle gets locked; now the circle slides
along the guide path - and the actual stroke is drawn by the
center of the tracking circle, ''not'' by your mouse point. As
a result, you are getting a smooth stroke going parallel to the
guide path and always at the same distance from it.

When the stroke is ready, release your mouse button (or lift
your tablet pen) but '''do not let go of the Ctrl key''' because
as long as you have it pressed, the tool remembers the hatch
spacing you set when you started drawing. Now, you have just
created a new stroke and, as usual with Inkscape tools, it gets
selected instead of what was selected before. In our case, this
means that the newly drawn stroke itself becomes the new guide
path. Next, you can draw a second stroke along the first one,
then a third one along the second, etc. Eventually you can fill
any desired space with uniform hatching.

Alternatively, if you uncheck "Select new path" in the Calligraphy tool preferences, newly created strokes will not be selected, so your original guide path will be kept selected. In this mode, Inkscape will increase the tracking distance after each created stroke so that you can create uniformly spaced hatching by tracking a single guide path.

The attachment to the guide path is not absolute. If you stray
your mouse pointer far enough from the guide path, you will be
able to tear it off (the track circle turns from green to red)
and move freely. This is intentional; this feature allows you,
for example, to continue drawing a stroke past the end of a
guide stroke, thus making your hatching cover a wider area than
the initial guide path. Special care is taken to make such
tearing off as smooth as possible and to suppress violent jerks,
but this is not always possible; the general advice is to not
try to hatch too fast. If jerking and unintended tearoffs still
bother you, try increasing the Mass parameter.

Also, special code is in place to prevent flipovers - accidental
jumps to the other side of the guide path. Brief flipovers are
suppressed, but if you intentionally go over to the other side
and stay there, eventually Inkscape will obey and your tracking
stroke will also flip over to follow you.

Tracking a guide also allows some slight feedback by gradually
changing the tracking distance in response to your drawing
behavior. Thus, if you're consistently trying to draw closer or
farther from the guide than the current tracking distance, the
distance will correspondingly decrease or increase, so you will
get a hatching that is slightly spacing in or out. (The effect
is very slight, however, so as not to become a nuisance.) Also,
note that since tracking follows the edge of the stroke, strokes
of varying width (such as those tracing background, see below)
will result in gradual bending of the hatching pattern as you
proceed.

===Tracing background by stroke width===

There is a new toggle button on the Calligraphy tool's controls
bar, '''Trace background'''. When on, the width of your pen
depends on the lightness of the background under the stroke in
each point, so that white translates into the minimum stoke
width (1) and black translates to the maximum (which is set by the
Width parameter). This can work alone or in combination with
pressure sensitivity, depending on whether the "Use pressure" button
is also toggled.

This feature allows you to not only hatch over an imported
bitmap image or any drawing, but to do so automatically
reproducing the highlights and shades of the background with
your strokes becoming lighter and heavier as needed.

===Misc features===

* For consistency with other drawing tools, drawing with '''Shift''' in Calligraphy tool automatically '''unions''' the newly created stroke with whatever paths were selected (and selects the result). Thus, you can do a series of overlapping Shift+strokes to create one unioned path object instead of separate objects as before.

* To facilitate changing the Width parameter, the Home/End keys in Calligraphy tool switch you to the minimum (1) and maximum (100) width, correspondingly. (This is in addition to the Left/Right arrow keys that change Width by 1; remember also that you can press Alt+X, type any width, and press Enter.)

==Selector==

* A new selection mode is available: '''selecting by touch'''. In this mode, you draw a freehand path across the objects; when you release mouse button, all objects that are touched by this path get selected. This mode is very convenient in situations where you need to select objects so intermingled that selecting them by the rectangular rubberband is too difficult and so numerous that click-selecting them one by one is too tedious.

:To activate selecting by touch, whenever you are drawing a rubberband rectangle, just press '''Alt''' to switch it to the touch mode. The rectangle will disappear and a red ''touch path'' will be shown instead. When dragging from an empty space, you can press '''Alt''' first and then start to drag to get the touch mode (note that your selection must be empty, otherwise Alt+dragging will move the selected objects instead). To start a touch selection from a point over an object, or to add to existing selection by touching, press '''Shift+Alt''' and then start to drag.

* Previously, the only way to switch selection from scale mode to rotate mode or back was to click on it, which was rather inconvenient when the selected object is in a group or under other objects. Now you can switch modes with keyboard as well by pressing '''Shift+S''' in Selector tool.

* Draging the '''scale handles with Alt''' now scales selection by an integer factor, i.e. up to '''2''', '''3''', '''4''', etc. times the original size or down to '''1/2'''. '''1/3''', '''1/4''', etc. of the original size (in any of the two dimensions independently). This replaces the old and rarely used "slow" scaling mode with Alt.

* '''Horizontal/vertical flipping''': So far, flipping a selection made it flip within its bounding box, so that the latter remained fixed. In the move/scale mode of the selector tool, this behaviour remains unchanged. However, in rotate/shear mode flipping now happens about an (imaginary) vertical/horizontal axis through the rotation center. This is very handy, since the latter can be freely dragged around and snaps to all kinds of objects if desired.

==Node tool==
[sculpt profiles - bbyak]

* If any of the nodes in the currently selected path is mouseovered, then horizontal/vertical flipping ('H' and 'V' keys), stepwise rotation ('[' and ']' keys) and scaling ('<' and '>' keys) now all use this specific node as center/axis. If there is no mouseovered node, the center of the bounding box is used instead (as is currently the case unconditionally). Nodes that are covered by one of their handles are also detected as mouseovered.

* [helper path display - johan]

==Text tool==
* [text toolbar - deadchip?]
* If text contains a tref element, the text tool's behavior may not be as expected. Please see [[#The tref Element]]

=SVG=

==The tref Element==

Inkscape can now correctly open files with '''tref''' elements, and new tref elements can be created manually in the XML editor.

The actual character data contained in a text element can either be embedded directly, or it can be the character content of an element referenced by a '''tref'''.

While the textual content from the referenced element will be stripped of any markup before being used by the '''tref''', the '''tref''' element can itself have the same attributes as a '''tspan'''. In fact, when rendered, it is as though the '''tref''' element is replaced by a '''tspan''' with the same attributes, and the referenced character data is embedded in that '''tspan'''.

The property '''xlink:href''' is used to refer to another element whose character data will be used. Any element can be referred to except an ancestor of the '''tref'''. When any of the text contained in the referred element changes, the '''tref''' will immediately be updated to display the new data.

Existing tref elements can be converted into tspan elements with '''Edit > Clone > Unlink Clone'''. If more than one '''tref''' is contained within a selection, all '''trefs''' will be converted into '''tspans'''. All attributes applied to the '''tref''' will be retained in the new '''tspan'''.

A '''tref''' element can be mixed with any other elements allowed to be contained by a text element.

The cloned character data rendered by the '''tref''' may not be edited, but any characters surrounding it can be changed. Styles cannot be applied to a subset of the cloned characters, but if all are selected, a style can be applied to the '''tref'''.

=Filters=

==New filters supported==

* The '''feBlend''' filter primitive gives us image blending modes, like in many image manipulation programs. These modes are screen, multiply, darken and lighten. There's a caveat, though: when blending an object against an semi-transparent background, the background will be accumulated twice, resulting in thicker objects under the bounding box of blended object. This is a limitation of current version of SVG format, not a bug in Inkscape.

* The '''feOffset''' filter primitive offsets the image by an user-defined amount. For example, this is useful for drop shadows, as the shadow has to be in a slightly different position than the actual object.

[[Filter Effects]]

==Filters UI==

* New dialog for creating and modifying filter effects ('''Object>Filter Effects...''')
* The list at the left of the dialog displays all filters currently in the document.
** New filters can be added with the '''Add''' button beneath the list
** Right-clicking a filter for the pop-up menu allows duplicating or removing a filter.
** Double-clicking a filter will apply it to all selected objects
** A black dot is placed next to whatever filter is applied to the selected objects. If more than one filter is in use by selected objects, an unfilled dot is used instead.
* The second list, at the left of the dialog, displays the '''filter primitives''' that are contained within the currently-selected filter.
** New primitives can be added by selecting the primitive type from the combo box beneath the list, and then pressing the '''Add''' button.
** Right-clicking a primitive for the pop-up menu allows duplicating or removing a primitive.
** Primitives can be rearranged by clicking and dragging any filter in the list.
** When a filter is selected, the '''Settings''' group at the bottom of the dialog will change to display the attributes available for that primitive. Changing a setting results in an immediate update to the document.
** The "in" and "in2" attributes for filters that support them are not shown in the '''Settings''' group. These input connections are displayed graphically in the list, under the '''Connections''' column.
*** Inputs for a particular filter are displayed as triangles. Depending on the primitive type, there may be one or two inputs (or more for Merge primitives.) Connections can be created by clicking on a triangle and dragging.
*** There are six standard input types that can be used for any primitive input; Source Graphic, Source Alpha, Background Image, Background Alpha, Fill Paint, and Stroke Paint. These are displayed vertically on the far right of the list. Click and drag from an input triangle to one of the standard inputs to connect them.
*** Primitives can also be connected to other primitives by clicking an input triangle and dragging upwards to another primitive. A primitive can only be connected to one higher up the list.
*** Single-clicking on an input triangle will unset it, returning it to the default. If it is on a Merge primitive, the input will be deleted.
*** Merge inputs have an empty input at the end. Dragging a connection from this input will add a new input to the primitive.

=Live path effects=

'''Live path effects''' (not to be confused with extension effects or SVG filters) are a new way to non-destructively modify path and shape objects. LPEs only affect the path of an object and not its style. The original path is preserved and can be edited directly, and the LPEs applied to it will be updated.

Live path effects were developed as part of the GSoC 2007.

[johan]

=Extension effects=

== Live preview ==

* '''Live preview of effects''': Using the async behavior (see below), as soon as the parameters dialog for an effect is shown, the script is executed in the background and the screen updates as soon as it's finished. This can result is seemingly faster execution if no parameters are changed. If some parameters are adjusted, the script is restarted. This allows you to see immediately the effects of any parameter change without pressing the OK button on the effect's dialog.

* '''Spawn Glib API''': Scripting extension have been moved to the Glib spawn API to ensure that parameters and variables aren't interpreted by a shell. This also means that scripting extensions are executed in a separate process asynchronously allowing the GTK main loop to continue to execute.

* '''Progress dialog''': While an extension is working on a document, a small dialog is shown allowing the user to cancel the execution.

== New and improved effects ==

* The new '''Render > Barcode''' extension creates a [http://en.wikipedia.org/wiki/Barcode barcode]. Supported types include EAN13, EAN8, UPC-A, UPC-E, UPC-5, Code39, Code39Ext, Code93, Code128, and RM4SCC.

* The new '''Render > Gear''' extension creates a [http://en.wikipedia.org/wiki/Gear mechanical gear] given the number of teeth, the circular pitch (in px units), and the pressure angle.

* The new '''Render > [[Spirograph]]''' extension creates intricate mathematical curves akin to the classic [http://en.wikipedia.org/wiki/Spirograph mechanical Spirograph toy] (see [http://wiki.inkscape.org/wiki/images/Spirograph_Samples.svg samples]).

* A group of new effects in the '''Text''' submenu performs various case conversions on selected text objects: converting to UPPERCASE, lowercase, Sentence case, Title Case, as well as flipping case (switching uppercase to lowercase and vice versa) and rANdoMiZInG cAse. If no texts are selected, the effect works on all texts in the document.

* Another effect in the Text submenu, '''Replace text''', performs search-and-replace on the selected text objects or (if nothing is selected) on all texts in the document. Searching is case sensitive. You can use this effect to globally delete all occurrences of some text fragment by replacing it with empty string. Conversely, if you search for an empty string and replace it with some string, this string will be inserted after every character of your text; for example, you can space out a text by replacing in it an empty string with a single space.

* A new effect, '''Replace color''' in the Color submenu, simply replaces one RRGGBB-specified color to another within selection or, if there's no selection, in the entire document. As with other effects in that submenu, the replacement affects fill, stroke, and gradient colors, but not colors of bitmaps.

*The '''Whirl''' extension uses the center of view as the center of whirl, so you don't have to enter the center coordinates numerically.

*The '''Render > Grid''' extension has got an extended range of grid spacings, from 0.1 to 1000 px.

*The '''Render > Function Plotter''' extension can now plot using polar coordinates.

== New Python XML library ==

* All Python effects are switched from the old and unmaintained PyXML library to the new powerful [http://codespeak.net/lxml/ lxml] library.

=Snapping=

* In addition to all other snapping modes and techniques, snapping has been implemented or improved in many tools and contexts:

:* Drawing of new '''shapes''' (such as rectangles or ellipses) snaps to grid/guides/objects.

:* '''Handles''' of existing objects and gradient handles snap.

:* '''Skewing''' objects in Selector snaps.

:* Snapping to objects works for '''images''' and '''clones''' (not only paths/shapes as before).

:* Snapping of '''text baselines''' works again.

:* When moved in Selector, an object optionally snaps with its '''rotation axis''' (which is by default in the geometric center of its bounding box, but can be arbitrarily moved and its position is remembered for every object).

:Other snapping fixes and improvements include:

:* The snapping preferences dialog has been restyled to make it more intuitive

:* Snapping distance is now set in screen pixels and is therefore independent of zoom.

:* Snapping to bounding boxes has been added

:* Snapping of objects has been made more clean, by only snapping bounding box corners to bounding boxes, and nodes to other nodes and paths.

:* The bug where "node-to-node" snapping caused jerky movement of nodes is fixed.

:* The aspect ratio is correctly preserved while scaling objects with snapping turned on.

:* All four bounding box corners now snap instead of only the lower-left and upper-right as before.

:* Snapping while uniformly scaling has been improved.

* The confusing "Default transformations origin" option is removed. Now Inkscape always uses the opposite edge of the object's bounding box as the transformation origin (though the bounding box itself can now be different, see next item).

* A new preference option has been added to specify the kind of '''bounding box''' to be used for transforming objects (see Inkscape Preferences, Tools, Selector). You can choose between the '''visual bounding box''' (which takes into account the stroke width, markers, and blur margins; this is the default behavior) or '''geometric bounding box''' (which encloses only the path itself, disregarding stroke width).

=Grids=

* a new tab in the document properties dialog, solely meant for grids; the former grid/guide tab is now solely for guides. I envision a list of guides there in the future, for easier deletion of guides etc.
* more than one grid can be active at the same time, although i am having trouble in finding a usefull case for this
* multiple views on the same document share the same grids, but the grid can be turned off for each view separately. For example: one could have an overview view without grid enabled. Duplicate that window and zoom in on some detail; then grids can be shown only for that view, and snapping will only happen in those views for which grids are enabled. (sorry i am not able to explain more clearly)
* grid information is now stored in SVG as a child of sodipodi:namedview. Can someone please make an extension that converts an old grid definition to the new format?
* axonometric grid (not yet snapping)
* dots instead of lines

From developer perspective:

* implementation of new grids is much easier now; subclassing CanvasGrid and adding an entry in the is enough. Have a peek at how the rectangular grid is implemented (CanvasXYGrid).
* note that there is no longer "the grid", there might be several grids active now!

[Future plans (i will not be working on this soon, due to GSoC Live effects!):
** possibility of enabling not all but a selection of grids for a view. Eg. when there are 4 grids defined in the document, only enable grid2 for a certain view.
** new grids!
** better snapping mechanism to enable snapping to intersections of guides&grids and grids&grids.

A side effect of removal of old gridcode: apparantly the origin of the desktop rules used to be set to the origin of the grid. I find this strange: specifying a grid origin of (2,2) would have me think the origin would be at ruler location (2,2) instead of (0,0) as it is in 0.45.1.
I have commented the grid-origin correction to the ruler range, because now there is not a single grid anymore to correct it for. Isn't there a control somewhere to define the documents origin? Now the ruler origin is set to (0,0) -- johan]

=Bitmap export=

* '''Batch export''': The Bitmap Export dialog (Ctrl+Shift+E) got a new checkbox, ''Batch export all selected objects''. This checkbox is available when two or more objects are selected. If it is checked, instead of exporting selection as a whole, Inkscape exports each selected object separately into its own PNG file. This uses each object's export hints (i.e. export filename and DPI) if they are remembered from a previous export; otherwise, the filename is created from the object ID and the DPI is 90 pixels per inch. '''Caution:''' Unlike regular export, batch export overwrites all existing PNG files without warning.

:This makes it possible to implement all kinds of '''image slicing''' and automated export scenarios. For example, if you are working on a web site design, you can create a separate "export" layer. In that layer, "slice" your web page image into separate areas by creating invisible rectangles with no fill and no stroke. Select each rectangle (by Tab/Shift+Tab, or by switching to Outline mode where even an invisible rectangle can be selected by clicking on its outline) and export it into the corresponding filename (which gets saved as that object's export hint). After that, if you do any changes to your graphics, it's very easy to reexport all the slices: just switch to the "export" layer, select all in that layer (Ctrl+A), and export with the ''Batch export selected objects'' checkbox on.

* '''Hide all except selected''': A new checkbox allows you to hide in the exported image everything except selected object(s).

* The Export dialog automatically appends the '''.png''' extension to the export filename you specify.

=Import/Export=

* [libpoppler PDF/AI import - miklos]

:* '''Implemented features''': The libpoppler based import extension can import shapes, text, clippaths and non-masked/masked images from PDF documents. It supports tiling patterns (XStep and YStep attributes are ignored), axial and radial gradients (only those made up of sampled functions). Currently it will only import the first page of the opened document.

:* '''Text editing tips''': Any text imported from PDF or AI has each letter's precise place on the page ''fixed''. While this preserves the exact appearance (e.g. justification of text blocks) of the imported document, it makes editing such text difficult: deleting text fails to contract the text line and inserting text fails to expand it, i.e. typed letters overlay the existing letters. (However, you still can replace a letter with another letter of about the same width, although you may need to kern it into place with Alt+arrows.)

::To work around this, select the text object you want to edit and use '''Text > Remove manual kerns''' command. This will remove the exact positioning information, so if the text block was justified it will lose justification, but instead you will be able to edit it as usual.

::Note that there is a way to select even a single line in a text block. For this, open the XML editor, expand the <svg:text> tree branch corresponding to your text, and select any of the <svg:tspan> objects under it. Now you can remove manual kerns from this line only. After you finish editing the line, you can manually justify it back, for example by adding spaces, manual kerns (Alt+arrows), or by adjusting letterspacing (select the whole line and use Alt+> or Alt+<).

* '''[if enabled! - mental]''' A new cairo-based PDF exporter has been added to Inkscape. Inkscape 0.46 can export shapes, strokes, transparency, gradients, patterns, text, and images correctly to cairo. While clipping paths and masks are known to be faulty or missing. cairo will write a PDF with vector graphics when possible and fall back to raster graphics when needed. What can be exported as vectors and how much of the image will be rasterized when the fallback kicks in depends on your version of cairo. cairo version 1.2 with the pdf backend compiled in is the minimum requirement for any cairo-based PDF exports.

* [cairo ps export - adib]

* [new wpg lib - ted gould]

=Command line=

Several new command line options are added that make Inkscape even more scriptable and automatable than before.

* --verb-list will list all the Verb IDs and their names in Inkscape. This makes writing your own menus and hotkeys much easier as you can easily find out what the choices are.

* --verb followed by a verb ID allows you to specify a verb to be called on every document opened by Inkscape initially from the command line.

* --select followed by a node ID will allow you to add a node to the list of selected objects.

These options can be used, for example, for performance testing. You could do something like this:

$ time inkscape --verb=FileClose my_complex_file.svg

to measure the time it takes to load and display the file.

Of course, with the ability to select objects, it can be much more useful than
that. You can call extension effects, or any other verb, then FileSave and
FileClose to automate all kinds of operations on your drawings.

=UI=

== [toolbars - [[JonCruz]]] ==

[calligraphy: menus, tooltips; star; ...]

Switched to stock GTK+ toolbars.

Extra magic secret sauce added.

== [filedialogs - [[JonCruz]]] ==

== Print dialog integration ==

* '''Print Dialog''': The GTK Unix Print Dialog has been hooked up! From the dialog, you can select any of the Postscript-capable printers known to your system and configure them as with any other GTK application.

== Saving window geometry globally ==

Previously, window geometry (size and position of document windows) could only be saved into the document (so that each document stored its own window geometry). Now, a new option is added to save the geometry of the last used window to the preferences and apply this geometry to all new windows. Thus, with the "Save geometry to preferences" option enabled, new windows will open with the shape of the most recent previous window. This mode also remembers and restores the maximized/fullscreen state (unlike geometry saved to documents).

== New ways to scroll and zoom ==

* You can now enable Space+mouse drag to pan canvas, as it does in Adobe Illustrator. This mode is enabled by the '''Left mouse button pans when Space is pressed''' checkbox in the Scrolling tab of the Inksape Preferences dialog. By default it is off and pressing the spacebar key switches you to Selector and back, as it always did in Inkscape.

* By default, rotating the mouse wheel scrolls the canvas vertically and Ctrl+wheel zooms in and out. Now, if you turn on the '''Mouse wheel zooms by default''' checkbox in the Scrolling tab of the Inksape Preferences dialog, this behavior is reversed: mouse wheel zooms without Ctrl and scrolls with Ctrl. This new mode should be familiar for users of AutoCAD and CorelDraw.

* In the Zoom tool, right mouse button always zooms out instead of calling the context menu (which is rather useless in this tool anyway).

=Even more improvements=

* '''Gnome VFS Improvements''': Gnome VFS Non-Local files are now usable through all of our file choosers in Open, Save and Export. This compile-time option allowed people to open any Gnome-VFS-based URI from the command-line in the past, but not non-local resources (WebDAV, SFTP, etc) and this now allows for all the lovely possibilities Gnome-VFS provides.

* In previous versions, Inkscape didn't allow you to '''group a single object.''' Yet in some cases, this operation is useful (for example, to blur the clipped edged of an object, or apply more than one clippath/mask to an object). Now this limitation is removed; just select any single object and group it to get a single-object group.

* The somewhat cryptic "F:" and "S:" labels in the selected style indicator (at the left end of the statusbar) and in tool's style swatches are now spelled out as '''Fill:''' and '''Stroke:'''. We believe this makes the interface, even if less space-efficient, a bit more friendly for newbies.

* The '''style swatches''' at the right end of object-creating tools' control bars now open the Preferences page of the corresponding tool when clicked. Also, now these swatches display a tooltip explaining its purpose (e.g. "Style of new rectangles", "Style of new calligraphic strokes", etc.)

* After dragging a curve segment in Node tool, Inkscape no longer selects the two adjacent nodes if they were not selected before.

* The '''Tile Clones''' dialog now uses the object's defined '''rotation axis''' (which can be freely moved by Selector tool and which is saved separately for each object) for all rotations (including both symmetry rotations and the Rotation tab rotations), scales, and flips. This renders unnecessary the previous workarounds where you had to group an object with another transparent object to affect how it's rotated by the clone tiler.

* In '''Pencil''' and '''Calligraphic''' tools, pressing '''Esc''' or '''Ctrl+Z''' while drawing cancels the currently drawn path or stroke. When not drawing, these keys work as before (Esc deselects, Ctrl+Z undoes last action). (This is the same behavior as in the Pen tool where it was introduced in a previous version.)

* A set of new verbs has been added to allow the user to easily '''unlock all locked objects''' or '''unhide all hidden objects'''. There are two variants one that operates on the current layer and its children and one that operates globally. While searching for hidden or locked object descendants of locked layers are ignored.

* Several more '''rotation snapping increments''' are available in the Steps tab of the Inkscape Preferences dialog: 36, 22.5, 18, 12, and 0.5 degrees.

* The list of folder shortcuts in the '''Open''' dialog includes the folder with Inkscape's SVG '''examples''' for easy access. Similarly, the '''Save''' dialog has a shortcut for the user's own '''templates''' dialog making it easy to save the current document as a template (if saved as <code>default.svg</code>, it will be loaded every time you run Inkscape or create new document with Ctrl+N; with any other name, it will be added to the File > New submenu).

* The file dialogs now have the inkscape desktop window set correctly as their parent window.

* For time-intensive operations such as Paint Bucket and Simplify, the system's busy wait cursor is displayed to indicate to the user that Inkscape is actively working, and not frozen.

* [statusbar updates: save, ...]

* Several improvements in '''inkview''': busy cursor is shown while loading file, the button window stays on top and responds to keyboard shortcuts; several memleaks stopped and bugs fixed. The "slideshow mode" of the main inkscape application (-s or --slideshow command line option) is removed; use inkview instead.

* In Document Metadata dialog, updated Creative Commons Licenses to version 3.0.

* In addition to Shift+click, right clicking on a colour swatch now also sets the stroke colour.

=Notable bugfixes=

These are bugfixes compared to 0.45.1; for a list of fixes in 0.45.1 compared to 0.45, see [[ReleaseNotes045|0.45.1 release notes]]

* The '''sodipodi:docbase''' attribute is no longer added to the root <svg> element. This attribute used to keep the latest directory that the document was saved to, and thus represented a mild privacy violation (i.e., by sharing your Inkscape SVG files you allowed others to have a peek into your directory structure). Note, however, that Inkscape does not remove this attribute from old documents it opens; if you want you can remove it yourself. Inkscape just no longer creates this attribute in new documents.

* Inkscape now properly quotes <code>font-family</code> values and therefore can use fonts with various nonalphanumeric characters in their names, which previously failed.

* If you have saved documents with a previous version of Inkscape which used '''right-to-left text''' (e.g. Arabic, Hebrew) then the paragraph alignment of non-flowed text has been reversed in this release. This is due to a bug in previous versions - the new behaviour is compliant with the SVG specification and compatible with other editors and viewers. To correct your images, simply reverse the paragraph alignment by selecting the text and clicking the appropriate button on the toolbar.

* A large family of bugs was exterminated where an object's style could only refer other objects (such as gradients, patterns, and filters) that come after it in the document. Now any objects can be referenced from a style regardless of their place in the document. This fixed the disappearance of gradients/patterns/filters after you undo an effect, as well as lots of assorted crashes and misrenderings (mostly on non-Inkscape SVG files).

* '''Stock markers''' now appear in the "recently used markers" section of the marker selector dropdowns in the Fill & Stroke dialog. Before, any markers with stock id's (including markers modified by the user) were hidden, making it difficult to work with modified stock markers.

* A regression in 0.45 caused crashes when undo or redo was attempted before the previous action could complete (e.g. pressing ctrl+z while you are still drawing a rectangle). This is now fixed.

* Previously, if there was a single invalid property in a <code>style</code> attribute, the entire attribute was discarded, i.e. the object lost all styling. Now Inkscape's behavior is more compliant to the CSS specification: it ignores only the invalid property but reads in all the rest.

* Several bugs are fixed in searching for linked images. Now moving SVG documents with their associated images to a different place or a different machine should work more reliably.

* Master opacity did not apply to stroke markers as it should; fixed.

* Creative Commons Public Domain Declaration URI points to right location now.

* Text objects didn't display the pattern editing handles; fixed.

= Previous releases =

* [[ReleaseNotes045]]
* [[ReleaseNotes044]]
* [[ReleaseNotes043]]
* [[ReleaseNotes042]]
* [[ReleaseNotes041]]
* [[ReleaseNotes040]]
* [[ReleaseNotes039]]
* [[ReleaseNotes038]]
* [[ReleaseNotes037]]
* [[ReleaseNotes036]]
* [[ReleaseNotes035]]

[[Category:Marketing]]

Using Eclipse

2007-07-01T20:16:46Z

Joelholdsworth: /* TortoiseSVN */

Eclipse is a popular development tool used primarily with Java; however, with the CDT plugin, C/C++ development can also be done. This page will help you set up Eclipse for coding, building, and debugging Inkscape.

= Eclipse on Windows =

Running Eclipse provides a relatively easy and familiar way to work with Inkscape code on Windows. This section will explain how to make it happen.

'''Note:''' Some of these instructions may be applicable to development on Mac or Linux. Feel free to refactor them if you are adding information for those platforms.

== Initial Setup ==

First, if you don't have Eclipse, [http://www.eclipse.org/downloads/ get it]. Check out the [http://help.eclipse.org/help32/index.jsp online help] if needed.

Next, you need to set up the necessary add-ons. Most important is the [http://www.eclipse.org/cdt/downloads.php CDT plug-in] which facilitates C/C++ development. You may also wish to add [http://subclipse.tigris.org/install.html Subclipse] for SVN access within Eclipse. Alternatively, many Windows users prefer to use [http://tortoisesvn.net/downloads TortoiseSVN], which works with Windows Explorer.

Finally, follow the instructions on the [[Win32Port]] page under the heading '''Inkscape under Windows'''.

== Creating a Project ==

=== Subclipse ===

The next step is to get the source code ready for use in Eclipse. Check [[WorkingWithSVN | here]] for general instructions for working with SVN; in this section, the aim is to show how to check out the code using Subclipse.

In Eclipse, we want the SVN perspective to be open. Click '''Window > Open Perspective > Other'''. Choose '''SVN Repository Exploring''' and click ok.

[[Image:Eclipse-01.png]]

In the '''SVN Repository''' tab, right click and choose '''New > Repository Location...'''.

[[Image:Eclipse-02.png]]

In the '''Location Url:''' box, paste the link https://svn.sourceforge.net/svnroot/inkscape/inkscape/trunk and click finish. This location will now show in the '''SVN Repository''' tab. You can expand the tree to see what is on the server.

Now right click the location name (which is really just the link given above), and click '''Checkout...'''. Choose '''Check out as a project configured using the New Project Wizard''' and the revision you want (probably Head), and click '''Finish'''.

In the New Project window that appears, choose '''C++ Project''' in Eclipse Europa (or in Callisto '''Standard Make C++ Project''') and click '''Next'''.

[[Image:Eclipse-Europa-ProjectType.png]]

Give your project a name such as InkscapeSVN. Uncheck the '''Use default location''' box so you can provide a better project location outside of your workspace, such as C:\InkscapeSVN. Select '''Executable (XL C/C++)''' as the project type, and '''XL C/C++ Tool Chain''' as the the Toolchain (this will not be necessary in Callisto (or before?) as this has been already been specified by selecting '''Standard Make C++ Project'''). Click '''Finish'''.

[[Image:Eclipse-Europa-CppProjectType.png]]

The source code will now be checked out - this may take a while. You will also now have a project in the '''C/C++ Perspective''' with whatever name you provided earlier.

=== TortoiseSVN ===

To use TortoiseSVN instead of Subclipse to check out your project, open a Windows Explorer instance. Right click anywhere outside of an existing SVN tree and choose '''SVN Checkout...'''. Specify the link given above and the destination directory.

To get a project in Eclipse, go to the '''C/C++ Perspective'''.

In Eclipse Europa select '''File > New > C++ Project'''. Choose a project type of '''Executable (XL C/C++)'''.

In Eclipse Calisto right click in the '''C/C++ Projects''' tab, and choose '''New > Project...''' and in the window choose '''Standard Make C++ Project.'''

Give the project a name, and uncheck the '''Use default location''' box. You must give the location that you checked the code out into here.

At this point, you will be able to use TortoiseSVN or Subclipse within Eclipse to control the source.

== Building ==

Be sure you have the btool built and ready to go, as outlined on the [[Win32Port]] page. You can build Inkscape from the command line or initiate it from within Eclipse, which will capture the output for you.

To set up Eclipse to do this, make sure you are in the '''C/C++ Perspective''' and that your project is open. Right click on the project name and click '''Properties'''. Click on '''Builders'''. Uncheck any builders that are there since we will be using the custom btool. Click '''New...''' and select '''Program'''.

[[Image:Eclipse-04.png]]

In the '''Main''' tab, browse the workspace for the location of the btool.exe file. Browse the workspace again to set the working directory to the main project directory.

[[Image:Eclipse-05.png]]

Now go to the '''Environment Tab''' and add a new variable called path. Add the same thing that appears in your mingenv.bat file here.

[[Image:Eclipse-06.png]]

[[Image:Eclipse-07.png]]

Click on '''C/C++ Project Paths''' and then the tab '''Path Containers'''. Click '''Add...''', choose '''Discovered scanner configuration container''', '''Next''', '''Discovered Paths''', and '''Finish'''.

Now go to '''C/C++ Include Paths and Symbols'''. Click '''Add Contributed''' and choose the '''Discovered scanner configuration container''', then '''Discovered Paths'''. Then click '''Add External Include Path''' and add the path to your GTK folder (probably something like c:\gtk210).

[[Image:Eclipse-08.png]]

You should now be able to use the '''Project > Build All''' command, capturing the output onto Eclipse's console.

== Debugging ==

You need to make a couple of changes to the build.xml file and do a clean rebuild. First, add -g to the flags section:

<flags>
-Wall -O3
-mms-bitfields
'''-g'''
</flags>

Then avoid stripping symbol information from the exe by changing this line
strip="'''true'''" symfile="${build}/inkscape.dbg"
with this one
strip="'''false'''" symfile="${build}/inkscape.dbg"

Now you need to create a debugging instance in Eclipse. Click '''Run > Debug...'''. Click on '''C/C++ Local Application''' and then click the new button. Give the launch configuration a logical name such as Inkscape Debug.

These screenshots show you the values you have to change in each tab. Nothing else needs to change.

[[Image:Eclipse-09.png]]

[[Image:Eclipse-10.png]]

Now you can launch this new configuration and debug away!

(Don't worry about funny warnings about files or folders not existing - it doesn't seem to affect the use of the debugger. However, if you know how to fix it, please replace this comment with instructions.)

[[Category:Developer Documentation]]

Using Eclipse

2007-07-01T20:10:41Z

Joelholdsworth: /* Creating a Project */

Eclipse is a popular development tool used primarily with Java; however, with the CDT plugin, C/C++ development can also be done. This page will help you set up Eclipse for coding, building, and debugging Inkscape.

= Eclipse on Windows =

Running Eclipse provides a relatively easy and familiar way to work with Inkscape code on Windows. This section will explain how to make it happen.

'''Note:''' Some of these instructions may be applicable to development on Mac or Linux. Feel free to refactor them if you are adding information for those platforms.

== Initial Setup ==

First, if you don't have Eclipse, [http://www.eclipse.org/downloads/ get it]. Check out the [http://help.eclipse.org/help32/index.jsp online help] if needed.

Next, you need to set up the necessary add-ons. Most important is the [http://www.eclipse.org/cdt/downloads.php CDT plug-in] which facilitates C/C++ development. You may also wish to add [http://subclipse.tigris.org/install.html Subclipse] for SVN access within Eclipse. Alternatively, many Windows users prefer to use [http://tortoisesvn.net/downloads TortoiseSVN], which works with Windows Explorer.

Finally, follow the instructions on the [[Win32Port]] page under the heading '''Inkscape under Windows'''.

== Creating a Project ==

=== Subclipse ===

The next step is to get the source code ready for use in Eclipse. Check [[WorkingWithSVN | here]] for general instructions for working with SVN; in this section, the aim is to show how to check out the code using Subclipse.

In Eclipse, we want the SVN perspective to be open. Click '''Window > Open Perspective > Other'''. Choose '''SVN Repository Exploring''' and click ok.

[[Image:Eclipse-01.png]]

In the '''SVN Repository''' tab, right click and choose '''New > Repository Location...'''.

[[Image:Eclipse-02.png]]

In the '''Location Url:''' box, paste the link https://svn.sourceforge.net/svnroot/inkscape/inkscape/trunk and click finish. This location will now show in the '''SVN Repository''' tab. You can expand the tree to see what is on the server.

Now right click the location name (which is really just the link given above), and click '''Checkout...'''. Choose '''Check out as a project configured using the New Project Wizard''' and the revision you want (probably Head), and click '''Finish'''.

In the New Project window that appears, choose '''C++ Project''' in Eclipse Europa (or in Callisto '''Standard Make C++ Project''') and click '''Next'''.

[[Image:Eclipse-Europa-ProjectType.png]]

Give your project a name such as InkscapeSVN. Uncheck the '''Use default location''' box so you can provide a better project location outside of your workspace, such as C:\InkscapeSVN. Select '''Executable (XL C/C++)''' as the project type, and '''XL C/C++ Tool Chain''' as the the Toolchain (this will not be necessary in Callisto (or before?) as this has been already been specified by selecting '''Standard Make C++ Project'''). Click '''Finish'''.

[[Image:Eclipse-Europa-CppProjectType.png]]

The source code will now be checked out - this may take a while. You will also now have a project in the '''C/C++ Perspective''' with whatever name you provided earlier.

=== TortoiseSVN ===

To use TortoiseSVN instead of Subclipse to check out your project, open a Windows Explorer instance. Right click anywhere outside of an existing SVN tree and choose '''SVN Checkout...'''. Specify the link given above and the destination directory.

To get a project in Eclipse, go to the '''C/C++ Perspective'''. Right click in the '''C/C++ Projects''' tab, and choose '''New > Project...''' and in the window choose '''Standard Make C++ Project.''' Give the project a name, and uncheck the '''Use default location''' box. You must give the location that you checked the code out into here.

At this point, you will be able to use TortoiseSVN or Subclipse within Eclipse to control the source.

== Building ==

Be sure you have the btool built and ready to go, as outlined on the [[Win32Port]] page. You can build Inkscape from the command line or initiate it from within Eclipse, which will capture the output for you.

To set up Eclipse to do this, make sure you are in the '''C/C++ Perspective''' and that your project is open. Right click on the project name and click '''Properties'''. Click on '''Builders'''. Uncheck any builders that are there since we will be using the custom btool. Click '''New...''' and select '''Program'''.

[[Image:Eclipse-04.png]]

In the '''Main''' tab, browse the workspace for the location of the btool.exe file. Browse the workspace again to set the working directory to the main project directory.

[[Image:Eclipse-05.png]]

Now go to the '''Environment Tab''' and add a new variable called path. Add the same thing that appears in your mingenv.bat file here.

[[Image:Eclipse-06.png]]

[[Image:Eclipse-07.png]]

Click on '''C/C++ Project Paths''' and then the tab '''Path Containers'''. Click '''Add...''', choose '''Discovered scanner configuration container''', '''Next''', '''Discovered Paths''', and '''Finish'''.

Now go to '''C/C++ Include Paths and Symbols'''. Click '''Add Contributed''' and choose the '''Discovered scanner configuration container''', then '''Discovered Paths'''. Then click '''Add External Include Path''' and add the path to your GTK folder (probably something like c:\gtk210).

[[Image:Eclipse-08.png]]

You should now be able to use the '''Project > Build All''' command, capturing the output onto Eclipse's console.

== Debugging ==

You need to make a couple of changes to the build.xml file and do a clean rebuild. First, add -g to the flags section:

<flags>
-Wall -O3
-mms-bitfields
'''-g'''
</flags>

Then avoid stripping symbol information from the exe by changing this line
strip="'''true'''" symfile="${build}/inkscape.dbg"
with this one
strip="'''false'''" symfile="${build}/inkscape.dbg"

Now you need to create a debugging instance in Eclipse. Click '''Run > Debug...'''. Click on '''C/C++ Local Application''' and then click the new button. Give the launch configuration a logical name such as Inkscape Debug.

These screenshots show you the values you have to change in each tab. Nothing else needs to change.

[[Image:Eclipse-09.png]]

[[Image:Eclipse-10.png]]

Now you can launch this new configuration and debug away!

(Don't worry about funny warnings about files or folders not existing - it doesn't seem to affect the use of the debugger. However, if you know how to fix it, please replace this comment with instructions.)

[[Category:Developer Documentation]]

Using Eclipse

2007-07-01T18:19:02Z

Joelholdsworth: /* Subclipse */

Eclipse is a popular development tool used primarily with Java; however, with the CDT plugin, C/C++ development can also be done. This page will help you set up Eclipse for coding, building, and debugging Inkscape.

= Eclipse on Windows =

Running Eclipse provides a relatively easy and familiar way to work with Inkscape code on Windows. This section will explain how to make it happen.

'''Note:''' Some of these instructions may be applicable to development on Mac or Linux. Feel free to refactor them if you are adding information for those platforms.

== Initial Setup ==

First, if you don't have Eclipse, [http://www.eclipse.org/downloads/ get it]. Check out the [http://help.eclipse.org/help32/index.jsp online help] if needed.

Next, you need to set up the necessary add-ons. Most important is the [http://www.eclipse.org/cdt/downloads.php CDT plug-in] which facilitates C/C++ development. You may also wish to add [http://subclipse.tigris.org/install.html Subclipse] for SVN access within Eclipse. Alternatively, many Windows users prefer to use [http://tortoisesvn.net/downloads TortoiseSVN], which works with Windows Explorer.

Finally, follow the instructions on the [[Win32Port]] page under the heading '''Inkscape under Windows'''.

== Creating a Project ==

=== Subclipse ===

The next step is to get the source code ready for use in Eclipse. Check [[WorkingWithSVN | here]] for general instructions for working with SVN; in this section, the aim is to show how to check out the code using Subclipse.

In Eclipse, we want the SVN perspective to be open. Click '''Window > Open Perspective > Other'''. Choose '''SVN Repository Exploring''' and click ok.

[[Image:Eclipse-01.png]]

In the '''SVN Repository''' tab, right click and choose '''New > Repository Location...'''.

[[Image:Eclipse-02.png]]

In the '''Location Url:''' box, paste the link https://svn.sourceforge.net/svnroot/inkscape/inkscape/trunk and click finish. This location will now show in the '''SVN Repository''' tab. You can expand the tree to see what is on the server.

Now right click the location name (which is really just the link given above), and click '''Checkout...'''. Choose '''Check out as a project configured using the New Project Wizard''' and the revision you want (probably Head), and click '''Finish'''.

[[Image:Eclipse-Europa-ProjectType.png]]

In the New Project window that appears, choose '''C++ Project''' in Eclipse Europa (or in Callisto '''Standard Make C++ Project''') and click '''Next'''.

[[Image:Eclipse-Europa-CppProjectType.png]]

Give your project a name such as InkscapeSVN. Uncheck the '''Use default location''' box so you can provide a better project location outside of your workspace, such as C:\InkscapeSVN. Select '''Executable (XL C/C++)''' as the project type, and '''XL C/C++ Tool Chain''' as the the Toolchain (this will not be necessary in Callisto (or before?) as this has been already been specified by selecting '''Standard Make C++ Project'''). Click '''Finish'''. The source code will now be checked out - this may take a while. You will also now have a project in the '''C/C++ Perspective''' with whatever name you provided earlier.

=== TortoiseSVN ===

To use TortoiseSVN instead of Subclipse to check out your project, open a Windows Explorer instance. Right click anywhere outside of an existing SVN tree and choose '''SVN Checkout...'''. Specify the link given above and the destination directory.

To get a project in Eclipse, go to the '''C/C++ Perspective'''. Right click in the '''C/C++ Projects''' tab, and choose '''New > Project...''' and in the window choose '''Standard Make C++ Project.''' Give the project a name, and uncheck the '''Use default location''' box. You must give the location that you checked the code out into here.

At this point, you will be able to use TortoiseSVN or Subclipse within Eclipse to control the source.

== Building ==

Be sure you have the btool built and ready to go, as outlined on the [[Win32Port]] page. You can build Inkscape from the command line or initiate it from within Eclipse, which will capture the output for you.

To set up Eclipse to do this, make sure you are in the '''C/C++ Perspective''' and that your project is open. Right click on the project name and click '''Properties'''. Click on '''Builders'''. Uncheck any builders that are there since we will be using the custom btool. Click '''New...''' and select '''Program'''.

[[Image:Eclipse-04.png]]

In the '''Main''' tab, browse the workspace for the location of the btool.exe file. Browse the workspace again to set the working directory to the main project directory.

[[Image:Eclipse-05.png]]

Now go to the '''Environment Tab''' and add a new variable called path. Add the same thing that appears in your mingenv.bat file here.

[[Image:Eclipse-06.png]]

[[Image:Eclipse-07.png]]

Click on '''C/C++ Project Paths''' and then the tab '''Path Containers'''. Click '''Add...''', choose '''Discovered scanner configuration container''', '''Next''', '''Discovered Paths''', and '''Finish'''.

Now go to '''C/C++ Include Paths and Symbols'''. Click '''Add Contributed''' and choose the '''Discovered scanner configuration container''', then '''Discovered Paths'''. Then click '''Add External Include Path''' and add the path to your GTK folder (probably something like c:\gtk210).

[[Image:Eclipse-08.png]]

You should now be able to use the '''Project > Build All''' command, capturing the output onto Eclipse's console.

== Debugging ==

You need to make a couple of changes to the build.xml file and do a clean rebuild. First, add -g to the flags section:

<flags>
-Wall -O3
-mms-bitfields
'''-g'''
</flags>

Then avoid stripping symbol information from the exe by changing this line
strip="'''true'''" symfile="${build}/inkscape.dbg"
with this one
strip="'''false'''" symfile="${build}/inkscape.dbg"

Now you need to create a debugging instance in Eclipse. Click '''Run > Debug...'''. Click on '''C/C++ Local Application''' and then click the new button. Give the launch configuration a logical name such as Inkscape Debug.

These screenshots show you the values you have to change in each tab. Nothing else needs to change.

[[Image:Eclipse-09.png]]

[[Image:Eclipse-10.png]]

Now you can launch this new configuration and debug away!

(Don't worry about funny warnings about files or folders not existing - it doesn't seem to affect the use of the debugger. However, if you know how to fix it, please replace this comment with instructions.)

[[Category:Developer Documentation]]

File:Eclipse-Europa-CppProjectType.png

2007-07-01T18:18:37Z

Joelholdsworth:

2007-06-23T17:39:54Z

Joelholdsworth: Samples of the output of the spirograph extension

Samples of the output of the spirograph extension

Spirograph

2007-06-23T17:38:18Z

Joelholdsworth: Created

The spirograph extension is a script which will generate Epitrochoid and Hypotrochoid in the same way as the Spirograph toy does.