Synfig Studio :: Documentation - User contributions [en]

Releases/Artwork

2009-08-25T15:15:50Z

Yaco:

Be sure to generate all this SVG at images with the same size and extension as their appear in they original page.

== Version 0.61.09 ==
<gallery>
Image:MainBanner-06109-en.jpg|Proposal 1 - [http://www.synfig.org/images/9/95/MainBanner-06109-en.svg SVG]
Image:MainBanner-06109-en-small.jpg|Proposal 1 - small
Image:MainBanner-06109-en-2.jpg|Proposal 2
</gallery>

== Version 0.61.08 ==
<gallery>
Image:Challenge-button-1.png|[http://synfig.org/images/2/22/Challenge-button-1.svg Editable version]
Image:News.png|[http://synfig.org/images/8/8d/News.svg Editable version]
Image:Movies.png|Not yet :(
Image:Complete_features.png|[http://synfig.org/images/4/4f/Complete_features.svg Editable version]
Image:MainBanner-06108-en.jpg|[http://synfig.org/images/a/a9/MainBanner-06108-en.svg Editable version]
Image:BackgroundRed-06108.png|Red background
Image:BackgroundBlue-06108.png|Blue background
Image:Square06108.png|Smallest version used in the French version
</gallery>

2008-10-09T07:01:05Z

Yaco:

<gallery>
Image:splash-06109.png|0.61.09 by '''Yaco''' & '''Genete''' (Source file)
Image:splash-06108.png|0.61.08 by '''Rore''' ([https://synfig.svn.sourceforge.net/svnroot/synfig/synfig-studio/trunk/images/splash_screen.sif Source file])
Image:splash-06101.png|0.61.01 by '''Darco''' ([https://synfig.svn.sourceforge.net/svnroot/synfig/synfig-studio/trunk/images/splash_screen-0.61.07.sif Source file])
</gallery>

File:Splash-06108.png

2008-10-09T06:59:24Z

Yaco:

2008-06-20T12:59:37Z

Yaco:

Doc:Svg2synfig

2008-06-09T13:23:31Z

Yaco: /* Usage */

== Option 1 ==
This uses an XSLT 2.0 stylesheet to transform SVG XML to Synfig XML.
=== Objective ===
Turn an SVG image into a Synfig file for import. First posted in the forums: http://synfig.org/forums/viewtopic.php?t=30
=== Prerequisites ===
# Make sure a Java runtime environment is installed.
# Get a recent version of the SAXON XSLT processor for Java from http://saxon.sourceforge.net/. Recommended version: Saxon-SA 9.0 (saxonsa9-0-0-2j.zip).
# Extract the SAXON package to a folder of your choice. As an example we're going to use d:\saxon in the following. The folder will contain several JAR files.
# Create the file d:\saxon\svg2synfig.xsl with the content provided at the bottom of this document ([[#svg2synfig.xsl]]).
==== Optional Prerequites for Windows ====
If you don't want to use the command line, create a batch file d:\saxon\svg2synfig.bat with this content:
@java -jar %0\..\saxon9.jar -xsl:%0\..\svg2synfig.xsl %1 > %0\..\synfig.sif
@pause
=== Transforming an SVG into a Synfig File ===
==== Windows Batch File ====
# Just drop the SVG file onto svg2synfig.bat.
==== Command line ====
# Change directory to d:\saxon.
# Enter the following command (replace your_input.svg by the path of the SVG file):
java -jar saxon9.jar -xsl:svg2synfig.xsl your_input.svg > synfig.sif
=== Result ===
If the conversion has been successful, the result will be written to the file d:\saxon\synfig.sif.
You can open this file in Synfig.
=== Limitations ===
* Doesn't seem to work with SaxonB (FOSS version)
* Compressed SVG (svgz) must be uncompressed first.
* Only SVG path objects are supported. Try converting all objects to paths.
* Only a subset of path elements is supported. Try to modify all path nodes to have split tangents, and all path segments to be curves.
* Sophisticated coloring (e. g. gradients) is not supported.
* Only basic transformations are supported.
* Fill and outline on the same object is not supported.
=== svg2synfig.xsl ===
<pre><nowiki>
<xsl:stylesheet version="2.0" exclude-result-prefixes="#all"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:svg="http://www.w3.org/2000/svg"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:math="http://exslt.org/math">
<xsl:output method="xml" indent="yes" encoding="UTF-8"/>

<xsl:template match="/">
<xsl:apply-templates/>
</xsl:template>

<xsl:template match="svg:svg">
<xsl:variable name="width" select="math:units_to_px(@width)"/>
<xsl:variable name="height" select="math:units_to_px(@height)"/>
<xsl:variable name="has_view_box" select="matches(@viewBox, '(\d+\s){3}\d+')"/>
<canvas version="0.2" id="{@id}"
width="{if ($has_view_box) then replace(@viewBox, '(\d+)\s(\d+)\s(\d+)\s(\d+)', '$3') else $width}"
height="{if ($has_view_box) then replace(@viewBox, '(\d+)\s(\d+)\s(\d+)\s(\d+)', '$4') else $height}"
view-box="{if ($has_view_box) then @viewBox else concat('0 0 ', $width, ' ', $height)}">
<xsl:apply-templates select="svg:g|svg:svg|svg:path"/>
</canvas>
</xsl:template>

<xsl:template match="svg:g">
<layer type="PasteCanvas" active="true" version="0.1" desc="{@id}">
<param name="canvas">
<canvas>
<xsl:apply-templates/>
</canvas>
</param>
</layer>
</xsl:template>

<xsl:template match="svg:path">
<xsl:variable name="style">
<xsl:for-each select="ancestor-or-self::*">
<xsl:sort select="position()" data-type="number" order="descending"/>
<xsl:value-of select="concat(@style, ';fill:', @fill, ';stroke:', @stroke, ';stroke-width:', @stroke-width, ';')"/>
</xsl:for-each>
</xsl:variable>
<xsl:variable name="self" select="."/>
<xsl:variable name="is_fill" select="not(matches(replace($style, 'fill:[^n;][^o].*', ''), 'fill:none'))"/>
<xsl:analyze-string select="@d" regex="m[^z]+(z|$)" flags="i">
<xsl:matching-substring>
<layer type="{if ($is_fill) then 'region' else 'outline'}" version="0.1" desc="{$self/@id}">
<xsl:call-template name="style-to-color">
<xsl:with-param name="style" select="replace(replace($style, ':none.*', ''), if ($is_fill) then '.*fill:([^;]+).*' else '.*stroke:([^;]+).*', '$1')"/>
</xsl:call-template>
<xsl:if test="not ($is_fill)">
<xsl:call-template name="style-to-width">
<xsl:with-param name="style" select="replace($style, '.*stroke-width:([^;]+).*', '$1')"/>
</xsl:call-template>
</xsl:if>
<param name="bline">
<bline type="bline_point" loop="{matches(., 'z', 'i')}">
<xsl:call-template name="path-to-bline">
<xsl:with-param name="path" select="."/>
<xsl:with-param name="node" select="$self" tunnel="yes"/>
</xsl:call-template>
</bline>
</param>
</layer>
</xsl:matching-substring>
</xsl:analyze-string>
</xsl:template>

<xsl:template name="path-to-bline">
<xsl:param name="path"/>
<xsl:variable name="stripped" select="replace(replace(translate($path, ',', ' '), '(\d)-', '$1 -'), '\s*([a-z]+)\s*', '$1', 'i')"/>
<xsl:variable name="closed" select="if (matches($stripped, 'z', 'i')) then $stripped else replace($stripped, 'm([-\d.]+\s[-\d.]+).*$', '$0l$1z', 'i')"/>
<xsl:variable name="tmp" select="replace($closed, '([-\d.]+\s[-\d.]+)l([-\d.]+\s[-\d.]+)', '$1c$1 $2 $2', 'i')"/>
<xsl:variable name="curve" select="replace($tmp, '([-\d.]+\s[-\d.]+)l([-\d.]+\s[-\d.]+)', '$1c$1 $2 $2', 'i')"/>
<xsl:analyze-string select="$curve" regex="\s([-\d.]+\s[-\d.]+)\s[-\d.]+\s[-\d.]+z" flags="i">
<xsl:matching-substring>
<xsl:analyze-string select="concat(regex-group(1), $curve)" regex="([-\d.]+)\s([-\d.]+)[m\s]([-\d.]+)\s([-\d.]+)c([-\d.]+)\s([-\d.]+)" flags="i">
<xsl:matching-substring>
<xsl:call-template name="node-to-bline-point">
<xsl:with-param name="c1_x" select="regex-group(1)"/>
<xsl:with-param name="c1_y" select="regex-group(2)"/>
<xsl:with-param name="x" select="regex-group(3)"/>
<xsl:with-param name="y" select="regex-group(4)"/>
<xsl:with-param name="c2_x" select="regex-group(5)"/>
<xsl:with-param name="c2_y" select="regex-group(6)"/>
</xsl:call-template>
</xsl:matching-substring>
</xsl:analyze-string>
</xsl:matching-substring>
</xsl:analyze-string>
</xsl:template>

<xsl:template name="node-to-bline-point">
<xsl:param name="x"/>
<xsl:param name="y"/>
<xsl:param name="c1_x"/>
<xsl:param name="c1_y"/>
<xsl:param name="c2_x"/>
<xsl:param name="c2_y"/>
<xsl:param name="node" tunnel="yes"/>
<xsl:variable name="transform">
<xsl:for-each select="$node/ancestor-or-self::*/@transform">
<xsl:value-of select="."/>
</xsl:for-each>
</xsl:variable>
<xsl:variable name="t" select="math:resolve_transform($transform)"/>
<xsl:variable name="transformed_x" select="$t[5] + $t[1] * xs:float($x) + $t[3] * xs:float($y)"/>
<xsl:variable name="transformed_y" select="$t[6] + $t[2] * xs:float($x) + $t[4] * xs:float($y)"/>
<xsl:variable name="transformed_c1_x" select="$t[5] + $t[1] * xs:float($c1_x) + $t[3] * xs:float($c1_y)"/>
<xsl:variable name="transformed_c1_y" select="$t[6]+ $t[2] * xs:float($c1_x) + $t[4] * xs:float($c1_y)"/>
<xsl:variable name="transformed_c2_x" select="$t[5] + $t[1] * xs:float($c2_x) + $t[3] * xs:float($c2_y)"/>
<xsl:variable name="transformed_c2_y" select="$t[6]+ $t[2] * xs:float($c2_x) + $t[4] * xs:float($c2_y)"/>
<entry>
<composite type="bline_point">
<point>
<vector>
<x><xsl:value-of select="$transformed_x"/></x>
<y><xsl:value-of select="$transformed_y"/></y>
</vector>
</point>
<width>
<real value="1"/>
</width>
<origin>
<real value="0.5"/>
</origin>
<split>
<bool value="true"/>
</split>
<t1>
<xsl:call-template name="vector-pair-to-radial">
<xsl:with-param name="origin-x" select="$transformed_c1_x"/>
<xsl:with-param name="origin-y" select="$transformed_c1_y"/>
<xsl:with-param name="x" select="$transformed_x"/>
<xsl:with-param name="y" select="$transformed_y"/>
</xsl:call-template>
</t1>
<t2>
<xsl:call-template name="vector-pair-to-radial">
<xsl:with-param name="origin-x" select="$transformed_x"/>
<xsl:with-param name="origin-y" select="$transformed_y"/>
<xsl:with-param name="x" select="$transformed_c2_x"/>
<xsl:with-param name="y" select="$transformed_c2_y"/>
</xsl:call-template>
</t2>
</composite>
</entry>
</xsl:template>

<xsl:template name="vector-pair-to-radial">
<xsl:param name="x"/>
<xsl:param name="y"/>
<xsl:param name="origin-x"/>
<xsl:param name="origin-y"/>
<xsl:variable name="dx" select="xs:float($x) - xs:float($origin-x)"/>
<xsl:variable name="dy" select="xs:float($y) - xs:float($origin-y)"/>
<xsl:variable name="d" select="math:sqrt($dx * $dx + $dy * $dy)"/>
<xsl:variable name="angle" select="math:atan2($dy, $dx)"/>
<radial_composite type="vector">
<radius>
<real value="{$d * 3}"/>
</radius>
<theta>
<angle value="{$angle * 57.295779513082320876798154814105}"/>
</theta>
</radial_composite>
</xsl:template>

<xsl:template name="style-to-width">
<xsl:param name="style"/>
<xsl:if test="matches($style, '^\d')">
<param name="width">
<real value="{math:units_to_px($style)}"/>
</param>
</xsl:if>
</xsl:template>

<xsl:template name="style-to-color">
<xsl:param name="style"/>
<xsl:if test="matches($style, '#')">
<xsl:analyze-string select="concat($style, ';')" regex="#([\da-f]{{2}})([\da-f]{{2}})([\da-f]{{2}});">
<xsl:matching-substring>
<param name="color">
<color>
<r><xsl:value-of select="math:hex_to_color(regex-group(1))"/></r>
<g><xsl:value-of select="math:hex_to_color(regex-group(2))"/></g>
<b><xsl:value-of select="math:hex_to_color(regex-group(3))"/></b>
<a><xsl:value-of select="if (matches($style, 'fill-opacity:')) then math:power(xs:float(replace($style, '.*fill-opacity:([-\d.]+).*', '$1')), 1 div 2.2) else 1"/></a>
</color>
</param>
</xsl:matching-substring>
</xsl:analyze-string>
</xsl:if>
<xsl:if test="matches($style, 'rgb')">
<xsl:analyze-string select="concat($style, ';')" regex="rgb[(\s]+([-\d.]+)[,\s]+([-\d.]+)[,\s]+([-\d.]+)[\s)]+;">
<xsl:matching-substring>
<param name="color">
<color>
<r><xsl:value-of select="math:power(xs:float(regex-group(1)) div 255, 2.2)"/></r>
<g><xsl:value-of select="math:power(xs:float(regex-group(2)) div 255, 2.2)"/></g>
<b><xsl:value-of select="math:power(xs:float(regex-group(3)) div 255, 2.2)"/></b>
<a>1</a>
</color>
</param>
</xsl:matching-substring>
</xsl:analyze-string>
</xsl:if>
<xsl:if test="matches($style, 'url')">
<param name="color">
<color><r>0.5</r><g>0.5</g><b>0.5</b><a>0.5</a> </color>
</param>
</xsl:if>
</xsl:template>

<xsl:function name="math:resolve_transform">
<xsl:param name="transform"/>
<xsl:variable name="stripped" select="replace(replace($transform, 'translate$', 'X(1,0,0,1,'), 'matrix', 'X')"/>
<xsl:analyze-string select="concat('X(1,0,0,1,0,0)', $stripped)" regex="(.*)X\((-?[\d.]+),(-?[\d.]+),(-?[\d.]+),(-?[\d.]+),(-?[\d.]+),(-?[\d.]+)$[^X]*X$(-?[\d.]+),(-?[\d.]+),(-?[\d.]+),(-?[\d.]+),(-?[\d.]+),(-?[\d.]+)$.*">
<xsl:non-matching-substring>
<xsl:sequence select="(1,0,0,1,0,0)"/>
</xsl:non-matching-substring>
<xsl:matching-substring>
<xsl:variable name="a2" select="xs:float(regex-group(8))"/>
<xsl:variable name="b2" select="xs:float(regex-group(9))"/>
<xsl:variable name="c2" select="xs:float(regex-group(10))"/>
<xsl:variable name="d2" select="xs:float(regex-group(11))"/>
<xsl:variable name="e2" select="xs:float(regex-group(12))"/>
<xsl:variable name="f2" select="xs:float(regex-group(13))"/>
<xsl:variable name="a1" select="xs:float(regex-group(2))"/>
<xsl:variable name="b1" select="xs:float(regex-group(3))"/>
<xsl:variable name="c1" select="xs:float(regex-group(4))"/>
<xsl:variable name="d1" select="xs:float(regex-group(5))"/>
<xsl:variable name="e1" select="xs:float(regex-group(6))"/>
<xsl:variable name="f1" select="xs:float(regex-group(7))"/>
<xsl:variable name="p" select="($a1*$a2+$c1*$b2,$b1*$a2+$d1*$b2,$a1*$c2+$c1*$d2,$b1*$c2+$d1*$d2,$a1*$e2+$c1*$f2+$e1,$b1*$e2+$d1*$f2+$f1)"/>
<xsl:variable name="remainder" select="replace(regex-group(1), 'X$1,0,0,1,0,0$', '')"/>
<xsl:choose>
<xsl:when test="matches($remainder, 'X')">
<xsl:variable name="recursion" select="concat($remainder, 'X(', $p[1], ',', $p[2], ',', $p[3], ',', $p[4], ',', $p[5], ',', $p[6], ')')"/>
<xsl:sequence select="math:resolve_transform($recursion)"/>
</xsl:when>
<xsl:otherwise>
<xsl:sequence select="$p"/>
</xsl:otherwise>
</xsl:choose>
</xsl:matching-substring>
</xsl:analyze-string>
</xsl:function>

<xsl:function name="math:hex_to_color" as="xs:float">
<xsl:param name="hex"/>
<xsl:value-of select="math:power(xs:float(string-length(substring-before('0123456789abcdef', substring($hex,1,1))) * 16 + string-length(substring-before('0123456789abcdef', substring($hex,2,1)))) div 255, 2.2)"/>
</xsl:function>

<xsl:function name="math:units_to_px" as="xs:float">
<xsl:param name="size"/>
<xsl:analyze-string select="$size" regex="^([-\d.]+)([a-z%]*)$">
<xsl:matching-substring>
<xsl:variable name="factor">
<xsl:choose>
<xsl:when test="regex-group(2) = 'pt'">1.25</xsl:when>
<xsl:when test="regex-group(2) = 'em'">16</xsl:when>
<xsl:when test="regex-group(2) = 'mm'">3.54</xsl:when>
<xsl:when test="regex-group(2) = 'pc'">15</xsl:when>
<xsl:when test="regex-group(2) = 'cm'">35.43</xsl:when>
<xsl:when test="regex-group(2) = 'in'">90</xsl:when>
<xsl:otherwise>1</xsl:otherwise>
</xsl:choose>
</xsl:variable>
<xsl:value-of select="xs:float($factor) * xs:float(regex-group(1))"/>
</xsl:matching-substring>
</xsl:analyze-string>
</xsl:function>
</xsl:stylesheet>
</nowiki></pre>

== Option 2 ==

This is a C program by akagogo that uses libxml to convert SVG to Synfig format.

http://none.carlos.googlepages.com/svgtosif.zip

=== Installation ===

Just make the usual '''./configure && make && sudo make install'''

=== Usage ===

The SVG files needs to be inside a folder called '''data'''. You have to run the command from the parent directory, but just using the name file as the command argument. So if:

* You are in folder "/example" you have to create a folder called "/example/data" and put the file "file.svg" there.
* Now you execute '''svgtosif file.svg''' when you got "/example" as your current working directory.

As you can see, this is really not to friendly. To quickly fix the problem, use the following bash script:

#!/bin/bash
mkdir data
cp "$1" data/
/usr/local/bin/svgtosif "$1"
NAME=`echo "$1" | cut -d "." -f 1`
cp "data/$NAME.sif" .
rm data/*
rmdir data
echo "Conversion complete!"

Put those lines in a file named "svg2sif" (name it as you want, but avoid using "svgtosif") and put it in a PATH directory (suggest /usr/bin). Then:
chmod +x /usr/bin/svg2sif

Thats all. Now use:
svg2sif <file.svg>

and you will get a .sif file in the same folder you are working in.

Doc:Svg2synfig

2008-06-09T13:22:14Z

Yaco: /* Option 2 */

== Option 1 ==
This uses an XSLT 2.0 stylesheet to transform SVG XML to Synfig XML.
=== Objective ===
Turn an SVG image into a Synfig file for import. First posted in the forums: http://synfig.org/forums/viewtopic.php?t=30
=== Prerequisites ===
# Make sure a Java runtime environment is installed.
# Get a recent version of the SAXON XSLT processor for Java from http://saxon.sourceforge.net/. Recommended version: Saxon-SA 9.0 (saxonsa9-0-0-2j.zip).
# Extract the SAXON package to a folder of your choice. As an example we're going to use d:\saxon in the following. The folder will contain several JAR files.
# Create the file d:\saxon\svg2synfig.xsl with the content provided at the bottom of this document ([[#svg2synfig.xsl]]).
==== Optional Prerequites for Windows ====
If you don't want to use the command line, create a batch file d:\saxon\svg2synfig.bat with this content:
@java -jar %0\..\saxon9.jar -xsl:%0\..\svg2synfig.xsl %1 > %0\..\synfig.sif
@pause
=== Transforming an SVG into a Synfig File ===
==== Windows Batch File ====
# Just drop the SVG file onto svg2synfig.bat.
==== Command line ====
# Change directory to d:\saxon.
# Enter the following command (replace your_input.svg by the path of the SVG file):
java -jar saxon9.jar -xsl:svg2synfig.xsl your_input.svg > synfig.sif
=== Result ===
If the conversion has been successful, the result will be written to the file d:\saxon\synfig.sif.
You can open this file in Synfig.
=== Limitations ===
* Doesn't seem to work with SaxonB (FOSS version)
* Compressed SVG (svgz) must be uncompressed first.
* Only SVG path objects are supported. Try converting all objects to paths.
* Only a subset of path elements is supported. Try to modify all path nodes to have split tangents, and all path segments to be curves.
* Sophisticated coloring (e. g. gradients) is not supported.
* Only basic transformations are supported.
* Fill and outline on the same object is not supported.
=== svg2synfig.xsl ===
<pre><nowiki>
<xsl:stylesheet version="2.0" exclude-result-prefixes="#all"
xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
xmlns:svg="http://www.w3.org/2000/svg"
xmlns:xs="http://www.w3.org/2001/XMLSchema"
xmlns:math="http://exslt.org/math">
<xsl:output method="xml" indent="yes" encoding="UTF-8"/>

<xsl:template match="/">
<xsl:apply-templates/>
</xsl:template>

<xsl:template match="svg:svg">
<xsl:variable name="width" select="math:units_to_px(@width)"/>
<xsl:variable name="height" select="math:units_to_px(@height)"/>
<xsl:variable name="has_view_box" select="matches(@viewBox, '(\d+\s){3}\d+')"/>
<canvas version="0.2" id="{@id}"
width="{if ($has_view_box) then replace(@viewBox, '(\d+)\s(\d+)\s(\d+)\s(\d+)', '$3') else $width}"
height="{if ($has_view_box) then replace(@viewBox, '(\d+)\s(\d+)\s(\d+)\s(\d+)', '$4') else $height}"
view-box="{if ($has_view_box) then @viewBox else concat('0 0 ', $width, ' ', $height)}">
<xsl:apply-templates select="svg:g|svg:svg|svg:path"/>
</canvas>
</xsl:template>

<xsl:template match="svg:g">
<layer type="PasteCanvas" active="true" version="0.1" desc="{@id}">
<param name="canvas">
<canvas>
<xsl:apply-templates/>
</canvas>
</param>
</layer>
</xsl:template>

<xsl:template match="svg:path">
<xsl:variable name="style">
<xsl:for-each select="ancestor-or-self::*">
<xsl:sort select="position()" data-type="number" order="descending"/>
<xsl:value-of select="concat(@style, ';fill:', @fill, ';stroke:', @stroke, ';stroke-width:', @stroke-width, ';')"/>
</xsl:for-each>
</xsl:variable>
<xsl:variable name="self" select="."/>
<xsl:variable name="is_fill" select="not(matches(replace($style, 'fill:[^n;][^o].*', ''), 'fill:none'))"/>
<xsl:analyze-string select="@d" regex="m[^z]+(z|$)" flags="i">
<xsl:matching-substring>
<layer type="{if ($is_fill) then 'region' else 'outline'}" version="0.1" desc="{$self/@id}">
<xsl:call-template name="style-to-color">
<xsl:with-param name="style" select="replace(replace($style, ':none.*', ''), if ($is_fill) then '.*fill:([^;]+).*' else '.*stroke:([^;]+).*', '$1')"/>
</xsl:call-template>
<xsl:if test="not ($is_fill)">
<xsl:call-template name="style-to-width">
<xsl:with-param name="style" select="replace($style, '.*stroke-width:([^;]+).*', '$1')"/>
</xsl:call-template>
</xsl:if>
<param name="bline">
<bline type="bline_point" loop="{matches(., 'z', 'i')}">
<xsl:call-template name="path-to-bline">
<xsl:with-param name="path" select="."/>
<xsl:with-param name="node" select="$self" tunnel="yes"/>
</xsl:call-template>
</bline>
</param>
</layer>
</xsl:matching-substring>
</xsl:analyze-string>
</xsl:template>

<xsl:template name="path-to-bline">
<xsl:param name="path"/>
<xsl:variable name="stripped" select="replace(replace(translate($path, ',', ' '), '(\d)-', '$1 -'), '\s*([a-z]+)\s*', '$1', 'i')"/>
<xsl:variable name="closed" select="if (matches($stripped, 'z', 'i')) then $stripped else replace($stripped, 'm([-\d.]+\s[-\d.]+).*$', '$0l$1z', 'i')"/>
<xsl:variable name="tmp" select="replace($closed, '([-\d.]+\s[-\d.]+)l([-\d.]+\s[-\d.]+)', '$1c$1 $2 $2', 'i')"/>
<xsl:variable name="curve" select="replace($tmp, '([-\d.]+\s[-\d.]+)l([-\d.]+\s[-\d.]+)', '$1c$1 $2 $2', 'i')"/>
<xsl:analyze-string select="$curve" regex="\s([-\d.]+\s[-\d.]+)\s[-\d.]+\s[-\d.]+z" flags="i">
<xsl:matching-substring>
<xsl:analyze-string select="concat(regex-group(1), $curve)" regex="([-\d.]+)\s([-\d.]+)[m\s]([-\d.]+)\s([-\d.]+)c([-\d.]+)\s([-\d.]+)" flags="i">
<xsl:matching-substring>
<xsl:call-template name="node-to-bline-point">
<xsl:with-param name="c1_x" select="regex-group(1)"/>
<xsl:with-param name="c1_y" select="regex-group(2)"/>
<xsl:with-param name="x" select="regex-group(3)"/>
<xsl:with-param name="y" select="regex-group(4)"/>
<xsl:with-param name="c2_x" select="regex-group(5)"/>
<xsl:with-param name="c2_y" select="regex-group(6)"/>
</xsl:call-template>
</xsl:matching-substring>
</xsl:analyze-string>
</xsl:matching-substring>
</xsl:analyze-string>
</xsl:template>

<xsl:template name="node-to-bline-point">
<xsl:param name="x"/>
<xsl:param name="y"/>
<xsl:param name="c1_x"/>
<xsl:param name="c1_y"/>
<xsl:param name="c2_x"/>
<xsl:param name="c2_y"/>
<xsl:param name="node" tunnel="yes"/>
<xsl:variable name="transform">
<xsl:for-each select="$node/ancestor-or-self::*/@transform">
<xsl:value-of select="."/>
</xsl:for-each>
</xsl:variable>
<xsl:variable name="t" select="math:resolve_transform($transform)"/>
<xsl:variable name="transformed_x" select="$t[5] + $t[1] * xs:float($x) + $t[3] * xs:float($y)"/>
<xsl:variable name="transformed_y" select="$t[6] + $t[2] * xs:float($x) + $t[4] * xs:float($y)"/>
<xsl:variable name="transformed_c1_x" select="$t[5] + $t[1] * xs:float($c1_x) + $t[3] * xs:float($c1_y)"/>
<xsl:variable name="transformed_c1_y" select="$t[6]+ $t[2] * xs:float($c1_x) + $t[4] * xs:float($c1_y)"/>
<xsl:variable name="transformed_c2_x" select="$t[5] + $t[1] * xs:float($c2_x) + $t[3] * xs:float($c2_y)"/>
<xsl:variable name="transformed_c2_y" select="$t[6]+ $t[2] * xs:float($c2_x) + $t[4] * xs:float($c2_y)"/>
<entry>
<composite type="bline_point">
<point>
<vector>
<x><xsl:value-of select="$transformed_x"/></x>
<y><xsl:value-of select="$transformed_y"/></y>
</vector>
</point>
<width>
<real value="1"/>
</width>
<origin>
<real value="0.5"/>
</origin>
<split>
<bool value="true"/>
</split>
<t1>
<xsl:call-template name="vector-pair-to-radial">
<xsl:with-param name="origin-x" select="$transformed_c1_x"/>
<xsl:with-param name="origin-y" select="$transformed_c1_y"/>
<xsl:with-param name="x" select="$transformed_x"/>
<xsl:with-param name="y" select="$transformed_y"/>
</xsl:call-template>
</t1>
<t2>
<xsl:call-template name="vector-pair-to-radial">
<xsl:with-param name="origin-x" select="$transformed_x"/>
<xsl:with-param name="origin-y" select="$transformed_y"/>
<xsl:with-param name="x" select="$transformed_c2_x"/>
<xsl:with-param name="y" select="$transformed_c2_y"/>
</xsl:call-template>
</t2>
</composite>
</entry>
</xsl:template>

<xsl:template name="vector-pair-to-radial">
<xsl:param name="x"/>
<xsl:param name="y"/>
<xsl:param name="origin-x"/>
<xsl:param name="origin-y"/>
<xsl:variable name="dx" select="xs:float($x) - xs:float($origin-x)"/>
<xsl:variable name="dy" select="xs:float($y) - xs:float($origin-y)"/>
<xsl:variable name="d" select="math:sqrt($dx * $dx + $dy * $dy)"/>
<xsl:variable name="angle" select="math:atan2($dy, $dx)"/>
<radial_composite type="vector">
<radius>
<real value="{$d * 3}"/>
</radius>
<theta>
<angle value="{$angle * 57.295779513082320876798154814105}"/>
</theta>
</radial_composite>
</xsl:template>

<xsl:template name="style-to-width">
<xsl:param name="style"/>
<xsl:if test="matches($style, '^\d')">
<param name="width">
<real value="{math:units_to_px($style)}"/>
</param>
</xsl:if>
</xsl:template>

<xsl:template name="style-to-color">
<xsl:param name="style"/>
<xsl:if test="matches($style, '#')">
<xsl:analyze-string select="concat($style, ';')" regex="#([\da-f]{{2}})([\da-f]{{2}})([\da-f]{{2}});">
<xsl:matching-substring>
<param name="color">
<color>
<r><xsl:value-of select="math:hex_to_color(regex-group(1))"/></r>
<g><xsl:value-of select="math:hex_to_color(regex-group(2))"/></g>
<b><xsl:value-of select="math:hex_to_color(regex-group(3))"/></b>
<a><xsl:value-of select="if (matches($style, 'fill-opacity:')) then math:power(xs:float(replace($style, '.*fill-opacity:([-\d.]+).*', '$1')), 1 div 2.2) else 1"/></a>
</color>
</param>
</xsl:matching-substring>
</xsl:analyze-string>
</xsl:if>
<xsl:if test="matches($style, 'rgb')">
<xsl:analyze-string select="concat($style, ';')" regex="rgb[(\s]+([-\d.]+)[,\s]+([-\d.]+)[,\s]+([-\d.]+)[\s)]+;">
<xsl:matching-substring>
<param name="color">
<color>
<r><xsl:value-of select="math:power(xs:float(regex-group(1)) div 255, 2.2)"/></r>
<g><xsl:value-of select="math:power(xs:float(regex-group(2)) div 255, 2.2)"/></g>
<b><xsl:value-of select="math:power(xs:float(regex-group(3)) div 255, 2.2)"/></b>
<a>1</a>
</color>
</param>
</xsl:matching-substring>
</xsl:analyze-string>
</xsl:if>
<xsl:if test="matches($style, 'url')">
<param name="color">
<color><r>0.5</r><g>0.5</g><b>0.5</b><a>0.5</a> </color>
</param>
</xsl:if>
</xsl:template>

<xsl:function name="math:resolve_transform">
<xsl:param name="transform"/>
<xsl:variable name="stripped" select="replace(replace($transform, 'translate$', 'X(1,0,0,1,'), 'matrix', 'X')"/>
<xsl:analyze-string select="concat('X(1,0,0,1,0,0)', $stripped)" regex="(.*)X\((-?[\d.]+),(-?[\d.]+),(-?[\d.]+),(-?[\d.]+),(-?[\d.]+),(-?[\d.]+)$[^X]*X$(-?[\d.]+),(-?[\d.]+),(-?[\d.]+),(-?[\d.]+),(-?[\d.]+),(-?[\d.]+)$.*">
<xsl:non-matching-substring>
<xsl:sequence select="(1,0,0,1,0,0)"/>
</xsl:non-matching-substring>
<xsl:matching-substring>
<xsl:variable name="a2" select="xs:float(regex-group(8))"/>
<xsl:variable name="b2" select="xs:float(regex-group(9))"/>
<xsl:variable name="c2" select="xs:float(regex-group(10))"/>
<xsl:variable name="d2" select="xs:float(regex-group(11))"/>
<xsl:variable name="e2" select="xs:float(regex-group(12))"/>
<xsl:variable name="f2" select="xs:float(regex-group(13))"/>
<xsl:variable name="a1" select="xs:float(regex-group(2))"/>
<xsl:variable name="b1" select="xs:float(regex-group(3))"/>
<xsl:variable name="c1" select="xs:float(regex-group(4))"/>
<xsl:variable name="d1" select="xs:float(regex-group(5))"/>
<xsl:variable name="e1" select="xs:float(regex-group(6))"/>
<xsl:variable name="f1" select="xs:float(regex-group(7))"/>
<xsl:variable name="p" select="($a1*$a2+$c1*$b2,$b1*$a2+$d1*$b2,$a1*$c2+$c1*$d2,$b1*$c2+$d1*$d2,$a1*$e2+$c1*$f2+$e1,$b1*$e2+$d1*$f2+$f1)"/>
<xsl:variable name="remainder" select="replace(regex-group(1), 'X$1,0,0,1,0,0$', '')"/>
<xsl:choose>
<xsl:when test="matches($remainder, 'X')">
<xsl:variable name="recursion" select="concat($remainder, 'X(', $p[1], ',', $p[2], ',', $p[3], ',', $p[4], ',', $p[5], ',', $p[6], ')')"/>
<xsl:sequence select="math:resolve_transform($recursion)"/>
</xsl:when>
<xsl:otherwise>
<xsl:sequence select="$p"/>
</xsl:otherwise>
</xsl:choose>
</xsl:matching-substring>
</xsl:analyze-string>
</xsl:function>

<xsl:function name="math:hex_to_color" as="xs:float">
<xsl:param name="hex"/>
<xsl:value-of select="math:power(xs:float(string-length(substring-before('0123456789abcdef', substring($hex,1,1))) * 16 + string-length(substring-before('0123456789abcdef', substring($hex,2,1)))) div 255, 2.2)"/>
</xsl:function>

<xsl:function name="math:units_to_px" as="xs:float">
<xsl:param name="size"/>
<xsl:analyze-string select="$size" regex="^([-\d.]+)([a-z%]*)$">
<xsl:matching-substring>
<xsl:variable name="factor">
<xsl:choose>
<xsl:when test="regex-group(2) = 'pt'">1.25</xsl:when>
<xsl:when test="regex-group(2) = 'em'">16</xsl:when>
<xsl:when test="regex-group(2) = 'mm'">3.54</xsl:when>
<xsl:when test="regex-group(2) = 'pc'">15</xsl:when>
<xsl:when test="regex-group(2) = 'cm'">35.43</xsl:when>
<xsl:when test="regex-group(2) = 'in'">90</xsl:when>
<xsl:otherwise>1</xsl:otherwise>
</xsl:choose>
</xsl:variable>
<xsl:value-of select="xs:float($factor) * xs:float(regex-group(1))"/>
</xsl:matching-substring>
</xsl:analyze-string>
</xsl:function>
</xsl:stylesheet>
</nowiki></pre>

== Option 2 ==

This is a C program by akagogo that uses libxml to convert SVG to Synfig format.

http://none.carlos.googlepages.com/svgtosif.zip

=== Installation ===

Just make the usual '''./configure && make && sudo make install'''

=== Usage ===

The SVG files needs to be inside a folder called '''data'''. You have to run the command from the parent directory, but just using the name file as the command argument. So if:

* You are in folder "/example" you have to create a folder called "/example/data" and put the file "file.svg" there.
* Now you execute '''svgtosif file.svg''' when you got "/example" as your current working directory.

As you can see, this is really not to friendly. To quickly fix the problem, use the following bash script:

#!/bin/bash
mkdir data
cp "$1" data/
/usr/local/bin/svgtosif "$1"
NAME=`echo "$1" | cut -d "." -f 1`
cp "data/$NAME.sif" .
rm data/*
rmdir data
echo "Conversion complete!"

Put those lines in a file named "svg2sif" (name it as you want) and put it in a PATH directory (suggest /usr/bin). Then:
chmod +x /usr/bin/svg2sif

Thats all. Now use:
svg2sif <file.svg>

and you will get a .sif file in the same folder you are working in.

File:Screenshot-Linux-06108-2030-1.jpg

2008-06-04T22:29:41Z

Yaco:

Screenshots

2008-06-04T22:27:48Z

Yaco: /* Community */

== Voria ==

Screenshots from when synfig was a proprietary product developed by [[History|Voria Studios]].

{|
|-
| align="center"|
[[image:linuxscreenshot.png|320 px|Linux screenshot]]

Linux

| align="center"|
[[image:Synfig-MacOSX.png|320 px|Mac OSX]]

Mac OSX
|}

== Community ==
;Add your favourite synfig screenshot here!

[[Image:Screenshot-Linux-06108-2030-1.jpg|320px]]

Synfig 0.61.08 (2030) running in ArchLinux GNU/Linux distribution, in a KDE desktop.

[[Image:Vista_screenshot.png|320 px|Vista]]

Microsoft Windows Vista Ultimate Screenshot
(With Task Manager showing 'Set Affinity' option. Set it to single CPU for best results)

[[Image:XPScreenshot.jpg|320 px|XP]]

Here is a synfig screenshot in Windows XP exporting the Voria logo.

Dev:Wish list

2008-06-04T16:31:52Z

Yaco: /* Allow select the origin of rotation when using the Rotate Tool */

'''''Warning''''': We need more people working on the code if we are going to be able to achieve all the feature requests.

Got a great idea for a new feature? Just add it here, or on the [http://sourceforge.net/tracker/?group_id=144022&atid=757419 feature requests tracker]. Before you do, please check the [http://svn.voria.com/code/ETL/trunk/TODO etl], [http://svn.voria.com/code/synfig-core/trunk/TODO synfig] and [http://svn.voria.com/code/synfig-studio/trunk/TODO synfigstudio] TODO files for similar ideas. Please add a rating of how essential this feature is to your workflow according to the following scale:

#"Well, it might be nifty. To someone."
#"I probably would make use this"
#"It's not essential, but I'd really like to have this at my disposal."
#"Synfig would be soooo much better with this change"
#"I can't/won't use Synfig without it!"

== Wishes ==

===Smart linking of tangents===
[4] As described in [[Sewing BLines]], when linking red tangent to yellow they are placed opposite against each other. This is normal from the program's point of view, but not normal for new users. Even more, to avoid this effect user needs to made some complex steps (see [[Sewing BLines#Solution]]). It takes a lot of time if we vahe lot of verticles to sew their tangents.

Suggestion:
* When linking tangents with the same color, program should act as usual.
* When linking tangents with different color program should automaticaly add Convert->Scale (-1) to avoid their opposite placement.
To allow linking two tangents in opposite position, I suggest to add a new menu option for tangents "Link Opposite". When linking two tangents with this option:
* When linking tangents with the different color, program should act as it acts now - no additional converts added.
* When linking tangents with the same color program should automaticaly add Convert->Scale (-1) to plcae them opposite against each other.

--[[User:Zelgadis|Zelgadis]]

===Movement blur effect===
To make the motion most realistic for movies, it should be possible to activate in the render dialog the option to smear the border of all objects, which move faster than a given value. For example, if a ball gets shot over the canvas/rendering-screen with speed over 50 px/frame it should have a blurry streak attached. This effect could be applied only at rendering time as an after-effect. --[[User:SvH|SvH]] 09:50, 28 May 2008 (EDT)

:There is a [[Motion Blur Layer]] that you can apply to the entire document or to the layers you want. It allows to turn the blur effect on and off during animation. I think it is more flexible that your proposal. [[User:Genete|Genete]] 10:13, 28 May 2008 (EDT)

===Morph sets===
This feature is similar to some other suggestions below, just with another way to approach. In animations are many movements, which can be put in some kind of library, to make use of at a later time. For example, movements to animate the key moments of a mouth, sampling syllables. For vector graphics, it should be possible to define some key points, which move just a small amount of space, to form another syllable. These syllables in this example, should be stored in a drop down list, to be able to select them for the key time on the timeline.
A morph-set for walking-left-to-right is different from a morph-set for a mounth, which has as options a,e,i,o,u,bah-disgust,happy-smile. The morph-set has to be stored as vector coordinates in a relative way(offset), e.g. X1=+212,+34;X2=-56,-23;X3=+3,-88;

To make use of the morph-set for the mouth, you have to define first, which vector points in your drawn mouth, correspond to the key-points of your morph-set. X1, X2, X3, Xn

--[[User:SvH|SvH]] 06:53, 27 May 2008 (EDT)

===Render time approximation===
Synfigstudio should get a button in the render dialog, which calculates the total render time for the actual settings (frames per second, length of the film, resolution, output format) It should testrender 1 picture, when the amount of total frames is below 1000. Over 1000 frames, it should testrender 10 pictures for more precise calculation.

--[[User:SvH|SvH]] 12:49, 22 May 2008 (EDT)

===Smartrendering===
I have made 25,000 small png-pictures with my 800Mhz computer in about 45 minutes. Synfigstudio did calculate each single frame of it. Nothing changed in this picture, so it does only need to get written to disk for the amount of pictures, until the next change (animation) has an effect on the output picture. This should save time for bigger projects with thousands of pictures. With smartrendering it is also possible to predict the total amound of space in Megabytes (Mibibytes) of the final render of the movie. It should calculate how much it needs and see, if enough space is free on the harddisk before the rendering get started.

--[[User:SvH|SvH]] 12:49, 22 May 2008 (EDT)

=== get_color method in text and radial blur ===

[5] Without get_color method distorion produces artifacts
[http://sourceforge.net/tracker/index.php?func=detail&aid=1831355&group_id=144022&atid=757416 bug 1831355]. So I would like to get this problem fixed before doing something else. --[[User:AkhIL|AkhIL]] 22:41, 1 May 2008 (EDT)

=== Full functional of group dialog ===

[5] Group dialog is broken now [http://sourceforge.net/tracker/index.php?func=detail&aid=1796833&group_id=144022&atid=757416 bug 1796833]. So we should get old features work right before making new one. --[[User:AkhIL|AkhIL]] 22:41, 1 May 2008 (EDT)

=== import/export .swf files ===

very important productivity feature

=== import/export .svg frames sequence, and/or .svg animations ===

very important productivity feature

=== a realtime .sif synchronized text window ===

just like the xml editor of Inkscape, or the html editor in Dreamweaver (this is hugelly useful for productivity)

I thinks scripting API can be implement in this way. For example you make XML DOM like implementation for python which alows to change DOM tree from python code and see chenges in canvas. By this way you can implement import/export scripts. Automation scripts. And a lot of different things. Even synchronization of animation between blender and synfig. --[[User:AkhIL|AkhIL]] 23:10, 26 April 2008 (EDT)

=== choosing colour from gimp/inkscape palettes ===

very useful when you need some colour comformity of what you're doing

=== Good high-level documentation of the source code ===

(2) It'd be nice if a newbie could quickly navigate around the source code. The best thing to do would be to add top-level comments in each file, explaining what that file does, a README.TXT in each directory, explaining what's in that directory. This would be pretty fast and easy to do, and make it much easier for new programmers to join.

Time permitting, it would also be good to document on a high level what the data structures are, but that's harder, since those tend to evolve, and it is often difficult to keep in sync. It would also be useful to document what individual functions do (just a one-liner high-level description), but that also takes more time.
: There is a page link in the wiki that connect to the [http://www.synfig.com/doc Synfig API Documentation]. I think this link should be highlighted to be more accessible for newbies contributors and mature developers (the link was found [[Releases/DeveloperPreview#Support | here]]). --[[User:Genete|Genete]] 10:02, 11 December 2007 (EST)

=== Mathematical functions to animate ===
(2/4) If you want to make a waving flag, it would be handful a sine function, tuned with random correctors, for example.
: -This should generate waypoints each 1, 2, 4 frames or any other step at artist's wish.
: -When applying a function you can add it to current values, add it to 1st frame values or simply override old values. Perhaps other options (such multiplication) would be fine, too. Something like texture editor in [http://www.artofillusion.org Art of Illusion], perhaps.
Perhaps it would be useful reusing the [http://www.gnu.org/software/octave/ Octave] source code to parse mathematical expressions.
I have rated this wish with a '2' because undoubtly many users will not be familiar to mathematical concepts, but for those who will be, I'd rate it with a 4. It would be possible to make a ball describing a parabolic moving in no time.
[[User:ajotatxe|ajotatxe]] 20 November 2007
: dooglus can probably chime in better than I here (see his example of balls on mathematical paths at http://uk.youtube.com/watch?v=YTpSfUthuVE ), but I believe that this is already possible. Synfig does support a variety of mathematical transforms for parameters, although the way you do this is by no means intuitive. (You might also want to check out the preambletaffy.sifz example for an easier approach to a waving flag. I know you were just using that as an example, but for the record...) [[User:Pxegeek|Pxegeek]] 00:58, 21 November 2007 (EST)

: I'd also rate it with a (4) (and updated the rating accordingly), not for this special case, but to make many workarounds much easier. Simulating [Parabolic Shot|free fall], for example, would be a lot easier with real formulas. I don't know, though how easy it will be to implement, maybe waiting for a scripting interface to be implemented is better than hacking this feature in an ad-hoc manner. --[[User:Rubikcube|Rubikcube]] 16:38, 29 February 2008 (EST)

=== Warning about editing bizarre things in animate editing mode ===
(3.5) It seems to have little sense animate certain things like Blend Method or Type of Feather. It would be very nice that the program asked comfirmation if you change these attributes in animate editing mode. If you do want to, you would have three options: "Yes, never ask", "Yes, never ask for this attribute", "No". I guess that internally, this attributes has integer type (or something like that) and the attributes that you normally want to animate, float type, so I think that this feature is relatively easy to implement. My English is not very good, so please feel free to fix this post.
[[User:ajotatxe|ajotatxe]] 20 November 2007

=== Bones with FK & IK + grouping of objects into folders ===

(1) Bones cane move specific vector assigned to them or the bones can have envelopes that move the vectors within their field of influence, much Like Anime Studio/Moho does. It's quite a time saving process of animating. Objects created can be saved into separate groups or folders using the same system as Anime Studio/Moho -Shadowphoenix 27/8/2007

=== Animated sketch ===

(1) it would be great, if the tool Sketch was animatable (for example, in a form of a special sketch-layer). --Zelgadis 2007-06-14

=== Duck for Amount value in Zoom layer ===

(2) It would be nice if Amount value in Zoom layer was controlled by additional duck. --[[User:Zelgadis|Zelgadis]] 02:49, 29 December 2007 (EST)
: I found that I can better use Warp layer instead of Zoom to change size. But it'd be nice to have Amount duck for Zoom layer anyway...
:: The Amount parameter works exponentially; each time you add 1 to the Amount, the image is zoomed by a further factor of e (= 2.71828 or so). Would a duck be any use if it just controlled the value of Amount in a linear way?
:: Workarounds include: export Amount, select it in the children dialog. Whatever's selected in the children dialog shows a duck. You can adjust it using that duck.
:: Also, if you use a Stretch layer, convert the Amount to Composite, export the X-Axis and connect it to the Y-Axis, then you have a duck-controllable fixed-aspect zoom. -- [[User:Dooglus|dooglus]] 15:32, 15 January 2008 (EST)
::: Yeah I found this workaround, but it's to much actions - i prefer better use Warp or Stretch layers. Why not the link Amount duck and Amount value with logarithmic function? ;) --[[User:Zelgadis|Zelgadis]] 10:33, 17 January 2008 (EST)

=== Automatic colour palette optimisation ===

(0) it would be nice to use libcontrast [http://david.navi.cx/blog/?p=132] [http://david.navi.cx/blog/?p=94] [http://david.navi.cx/blog/?p=99] [http://svn.gnome.org/svn/xchat-gnome/trunk/src/libcontrast/] to automatically adjust selected or all the palette items for best visual contrast. It would also be interesting to have a layer that uses this code to filter the image.

=== Arbitrary Color Channels ===

— The ability for the user to create any number of custom channels for various purposes.

=== Autorecover History ===

— It would be great if autorecover could also recover the associated history of a file in the event of a crash.

=== Layer Convert ===

<strike>(4)</strike> (2) — The original intent of this feature request has been solved and documented - [[How_do_I#Fill_an_outline.3F|How do I....Fill an Outline?]] - but it would still be nice to have a way to convert one sort of path layer to another. ''(Downgraded to level 2) [[User:SnapSilverlight|Snap]] 12:32, 17 Jan 2006 (PST)''

=== Vector fill bucket ===

(3) — Like the traditional bitmap fill, but this fills the area clicked out to the nearest boundary paths with a region of that area, set to the foreground color (it actually would create a new [[Region Layer|region layer]]). <p>Alternatively, a single-duck layer object, that performs a simple bitmap fill from its (animatable) location, with its stored color value. (This second approach is similar to the behavior of one of Softimage's TOONZ[http://www.google.com/search?q=softimage+TOONZ]'s tools)</p><p>If this is implemented, it will probably be necessary to change the existing "fill" tool's name and icon to a "color injector" (hypodermic needle / turkey injector icon) tool, as that's closer to describing what it does.

*Inkscape has a very innvative version of this tool. Maybe you can just grab the code from there and integrate it in synfig? --[[User:SvH|SvH]] 01:37, 14 May 2008 (EDT)

=== [[redraw tool]] ===

(4-5) — Intutive reshaping of path-based layers. See link.

=== [http://developer.gnome.org/projects/gup/hig/ Gnome HIG Compliance] ===

— This should solve all complaints about the layout, without requiring Synfig to be "just like program (x)". See [[UI Reloaded]] for progress on this.

=== Feedback for [[Smooth Move Tool]] ===

(3) — This tool does what a lot of folks are looking for, warping selected ducks in a "soft" fashion. But it's not very obvious what sort of effect it will have, from the tool's interface. It needs some sort of momentary center-of-action and radius indicator at the very least. Perhaps an "influence gradient" overlaid on the canvas once Synfig's core is sped up?

=== Networkability ===

(2) — Like Inkscape's "inkboard" feature (using Jabber), or Blender's Verse server [http://www.blender.org/modules/verse/index.php], or OpenCanvas's Networking option. This should probably farm off all the networking stuff to the telepathy framework so that synfig doesn't have to deal with all the account/etc issues.

=== Intuitive tangent modification ===

(3) — (BBQ Pulled Duck) Inkscape has this for still handles - basically, grab a section of the spline between handles, and pull it around, the program automatically alters the tangent handles to match. What would be really neat is if you could do the same for temporal handles - be able to grab the spline between keyframes, and yank it around, and have Synfig automatically adjust the key interpolation to match. Not sure exactly what the workflow in the UI would be for this, however.

-Agreed; blender does this with its IPO curves, and it's a really efficient way to work.

=== Plugin API ===

(1) — Would be nice to enable additional functionality to be added to the program without it necessarily needing to be in the Synfig source tree. ''According to the Synfig 0.61.01 roadmap on [http://deepdarc.com/ deepdarc.com], there is a plugin API already implemented. So instead, this may be a [[Wiki Wish List|Wiki Wish]] for documentation, depending on how much has already been completed. [[User:SnapSilverlight|Snap]] 19:57, 13 Jan 2006 (PST)

=== Python support ===

(1) of some sort will no doubt be demanded by the userbase eventually, for studio-specific automation of tasks, noncompiled plugins, etc. I ([[User:Snap|SnapSilverlight]]) don't have any particular use for it at the moment, tho'.

I suuose to join this request with [[Wish_list#a_realtime_.sif_synchronized_text_window]]. We can implement python access to XML DOM and write XML Editor in python. --[[User:AkhIL|AkhIL]] 06:54, 30 April 2008 (EDT)

=== mod_synfig ===

(1) — For Apache. Render .sif to some format like png/mng on access.

=== synfig nsplugin ===

(1) — Let Mozilla and Mozilla-based view synfig files in-browser.

=== Align function ===

(3) — Align objects at a common border (as in Inkscape)

=== Improved SVG import ===

(4) — Currently, all importing an SVG does is render it in ImageMagick. What I want is the ability to import the SVG document so that all the shapes, etc. of the SVG document show up as their equivilant synfig layers - i.e. if I had put them there myself. I'm trying to write a patch for this but the codebase is mostly undocumented. [[User:KMeist|KMeist]] 16:38, 25 Feb 2006 (PST)

[[svg2synfig]] could be incorporated using an open source XSLT processor. --[[User:Dmd|Dmd]] 13:34, 26 January 2008 (EST)

=== Gradient Paint Tool ===

How about a tool that can 'paint' a gradient object. For example the options would be width and gradient type, one would make a stroke with the tool and the gradient would be automatically applied inside of the outline (set by width). This would save the trouble of having to the all the encapsulation stuff. (Actually any tool that makes creating gradient one step would be good).--[[User:Triclops|Triclops]] 09:52, 9 Aug 2006 (PDT)

=== Bone Animation Tools ===

Bone system with inverse kinematics, very important for quick animation. You put bones on a drawed man and you can animate him like a puppet. I'm using that in Moho (lost marble product).--[[User:Ziolive|ziolive]] 23 Aug 2006
*I would find this very useful too. I think it is called '''rigging'''(4/5) --[[User:SvH|SvH]] 01:33, 14 May 2008 (EDT)

=== AVI Backgrounds ===
Is there any way I can add an avi as a background so I could add facial expressions to a stop-motion animated figure. [zotz here, I was thinking DV background or extra timeline. I would like to mix animations with live footage. rating (3/4)]

=== Character tool on Tool Options Dialog ===

I want to use the as a character generator for a TV show. By using chroma key hide the background. Even better interface to a video overlay card with Alpha blending.

=== Collect for Publication ===

(3/4) - (zotz) Menu item, functionality that would collect alll files referenced in a sif and place them all in a tgz for sending elsewhere or publishing anumations in source form.

=== Object Library ===

(3/4) - (zotz) Haven't thought this all through yet, but synfig could come with a library of categotrised "objects" with a copyleft license (GPL? CC BY-SA?) An animation clip art type deal.
**I'd suggest this should be public domain and distributed by openclipart.org -- --[[User:PaulWise|pabs]]

=== Flash Export ===

(3/4) Well, might just be me but if there was a posiblity to export in .swf or .fla, I think the project might become a lot more popular.[[User:Conceit|Conceit]]

(4/5) I wholeheartedly agree. I would definitely use synfig more if this feature were added and it would most definitely increase popularity. [[User:cdj05a|cdj05a]]

=== Single window ===

Depending on individual desktop setups, single window is sometimes preferable to many windows. Can we have a single-window option?

Also, even with many windows, Windows-users especially might find it better if all the windows only appeared as a single one on the taskbar.

=== Line width tool ===
(4) It will be good to have a tool for easy changing line width. There was a such tool in earlier versions, but it's not usable. I'm often use variable line width, when drawing in synfig, so it is important for me. -- [[User:Zelgadis|Zelgadis]] 2007-09-09

: It is [[FAQ#Where did the polygon, draw, sketch, and width tools go?|still available]]. Also, you can turn on the width ducks, using Alt-5. -- [[User:Dooglus|dooglus]] 12:18, 9 October 2007 (EDT)

:: It is available, but I never was able to figure out how it works. Alt-5 works, but it is hard to set width to zero, for example. -- [[User:Zelgadis|Zelgadis]] 2007-09-10

::: Are you wanting something that works on one vertex at a time? Or all the vertices in an area? Apparently the width tool was designed to work on a bunch of vertices at once. I didn't figure out how it works though, either. -- [[User:Dooglus|dooglus]] 16:57, 10 October 2007 (EDT)

:::: Width tool is surely a mystery. :) I'm waiting for something that works on one vertex at time. I liked the way as width was changed in Moho (Anime Studio now) - there was a special width tool and holding left mouse button on the vertex and moving cursor left decreasing width value, moving right - increasing. Maybe it make sense to rework Width tool in such way. -- [[User:Zelgadis|Zelgadis]] 2007-09-13

::In my opinion the use of a seperate device like a joystick could help. You draw the line with the mouse and with the other hand, you push/pull the joystick to change the linewith in realtime. --[[User:SvH|SvH]] 05:25, 30 May 2008 (EDT)

=== Export Wizard ===

(2/4) Conversion and export to other file formats (mpg, avi, flash formats, others, and the synfig format) with a step by step wizard for choosing format and place of saving. Similar to Gimp's saving of .png files but for movie/video type files. --
[[User:Hiddenghost|hiddenghost]]

=== Using Synfig as a portable app ===

(3) This isn't really a feature request (though it could be) but I was wondering if synfig could be used as a portable application (as in www.portableapps.com). Does the windows install require registry access? i really want to use Synfig at work, but I'm reluctant to install it just in case it leave footprints in the regisitry or something, and it would be sweet to use it on my travels as well. Only thing is, I can't test it out at home because I am using Linux.
See also: http://portableapps.com/node/5761
[[User:Zenoscope|zenoscope]]

This isn't currently possible without modifying the source code. That has been on my TODO list for ages [[User:PaulWise|pabs]] 01:17, 26 October 2007 (EDT)

=== Allow organize child valuenodes in an hierarchy ===
(3-2) And allow maintain the organization once the file is saved. At the moment they are reordered in alphabetical order which is useless and annoying.

=== Triangle sliders to be always visible ===
(3) I would like that the triangle sliders from [[Colors Dialog]] and [[Gradient Editor Dialog]] were visible whatever color or channel you're editing. Some times when the color or channel is to bright or light the slider is difficult to distinguish. --[[User:Genete|Genete]] 14:30, 29 October 2007 (EDT)

=== XICC support ===

It would be cool if synfigstudio had support for [http://burtonini.com/blog/computers/xicc XICC].

=== Area to Edit ===

An option like blender - select area to update would be nice, so the only part of the image that updates when you add or change something is in the selected area

ie. when working on a complex composition, studio doesn't know, when I tweak a tiny part of the composition, that only that part needs redrawing, so it redraws the whole thing. It would be good if there was some way of telling it which part to focus on. -- [[User:Dooglus|dooglus]] 04:02, 3 February 2008 (EST)

=== Histograms ===

01:23 * AkhIL wish to have histograms and luma/color scope like [http://mac.softpedia.com/progScreenshots/Avid-Xpress-DV-Screenshot-14207.html] in synfig

I've looked at those pictures but don't know what they're showing. Can you describe what those scopes are doing, and what the histograms display? ie. what are the X and Y axes of the histograms? -- [[User:Dooglus|dooglus]] 04:07, 3 February 2008 (EST)

First look this description in blender wiki [http://wiki.blender.org/index.php/Manual/VSE_Modes]

Ok There is four things.
* Upper left is Lumascope (Luma Waveform in blender). X-Axis represents image's X-Axys. Y-Axis is average luminescence of column of pixels.
* Upper right is Chromascope (Chroma Vectorscope in blender). Just look description on blender wiki.
* Lower left is like Lumascope but for each channel
* Lower right is histograms. X is luminescence and Y is count of pixels with such luminiscence.

=== Sound Layer ===

(4) It would be a very good improvement if the sound system were implemented into synfig in [[Sound Layer | this]] way. --[[User:Genete|Genete]] 07:46, 8 February 2008 (EST)

=== Rearrange the view of waypoints for Canvas param ===
As reported in [http://sourceforge.net/tracker/index.php?func=detail&aid=1888858&group_id=144022&atid=757416 Bug #1888858] waypoints are not displayed for canvas switch events.
I suggest to rearrange waypoints display according to [[Media:Canvas_prop.png|this scheme]].

=== Width weigths ===
Is it possible to add "weigths" for widths? ^_^ I.e. width changes not all the way along the segment. Maybe something like a duck on bline which indicates the region where the width of current vertex isn't changed.
[[Media:width-proposal.png|Illustration here.]]

More ideas around this concept in [http://dooglus.rincevent.net/synfig/logs/2008/%23synfig-2008-04-16.log this conversation]. Although the log of that day is very interesting the lines related to this idea are from 22:38 to 23:43. [[User:Genete|Genete]] 17:51, 16 April 2008 (EDT)

=== Improved Colour Dialog ===
How easy is it to stick in a colour square/wheel? Messing with sliders is somewhat obstructive.

=== Insert Waypoints ===
A button to create a waypoint for every selected duck, in its current position. Moving each duck up a bit and down again quickly gets tedious.
:If the duck in question has already a waypoint then you don't need to move it to create a new waypoint. Just select the corresponding parameter in your child list panel and select 'Add Waypoint' from the right click context menu over the parameter. No need to have the duck selected. If you want to freeze the entire bline just do that over the Bline Point List. [[User:Genete|Genete]] 07:48, 29 April 2008 (EDT)
::Yes, but it would be nice to have opportunity to add waypoint to parameer which not have any ducks yet (i.e. non-animated parameter). --[[User:Zelgadis|Zelgadis]] 08:33, 29 April 2008 (EDT)

=== Automatically split tangeants ===

Holding shift while moving tangeant ducks should automatically split them. They can be rejoined if necessary through the context menu as they are now.

=== A way to link params without exporting ===
I need a way to link params with different names without exporting. It is possible to achive by manualy editing of sif file. But inposible by gui. I will be nice to have linking by drag-n-drop. Or just by selecting reference param, pushing copy button, selecting another param and bushing link button. ---[[User:AkhIL|AkhIL]] 21:47, 30 May 2008 (EDT)

=== Allow select the origin of rotation when using the Rotate Tool ===

It can be initially set to the geometrical center of the selected ducks or the gravity center depending of the selected checkboxes in the tool options panel. Later the user could move it before perform the rotation operation. It is a waste of time to rotate and translate the ducks every time a rotation manipulation is done. ---[[User:Genete|Genete]] 12:16, 4 June 2008 (EDT)

:I was adding this request at the same time than you Genete :-). Here is an example of how this issue is solved in Inkscape:

:[[Image:rotate-tool-inkscape.png|center]]

:---[[User:Yaco|Yaco]]

File:Rotate-tool-inkscape.png

2008-06-04T16:30:56Z

Yaco:

Dev:Wish list

2008-06-04T16:30:01Z

Yaco: /* Allow select the origin of rotation when using the Rotate Tool */

Keyboard Shortcuts

2008-05-08T16:58:57Z

Yaco: /* Hotkeys Visual Guide */

Here is a list of some of the keyboard sortcuts you currently have at your disposal. These are the defaults. There is a way to customize these, but it is currently not intuitive. Basically you need to edit the accelrc file in your synfig settings directory.

{| border="1" cellspacing="0" align="center" width="80%"
|'''Keystroke'''||'''Description'''
|-
| <Control>-A || Select all ducks
|-
| <Shift><Control>-A || Select all layers
|-
| <Control>-C || Copy currently selected layer(s) and put them in the clipboard
|-
| <Control>-D || Deselect all ducks
|-
| <Shift><Control>-D || Deselect all layers
|-
| <Control>-G || Toggle grid show
|-
| <Control>-I || Import image
|-
| <Control>-L || Toggle grid snap
|-
| <Control>-N || New composition (since r1386)
|-
| <Control>-O || Open composition (since r1386)
|-
| <Alt>-O || Toggle onion skin (since r1525 - it was Control-O until r1386)
|-
| <Control>-P || Play the current animation in the WorkArea
|-
| <Control>-Q || Quit Synfig Studio
|-
| <Control>-R || Redo
|-
| <Control>-S || Save
|-
| <Control>-V || Paste the layer(s) from the clipboard above the currently selected layer
|-
| <Control>-W || Closes the current animation document.
|-
| <Control>-X || Cut currently selected layer(s) and put them in the clipboard
|-
| <Control>-Z || Undo
|-
| <Control>-` || Toggle low/high-resolution (defaults to low resolution)
|-
| <Control>-0...9 || Change the current rendering quality (lower is better, but 0==10)
|-
| <Alt>-1 || Toggle display of "Position" ducks
|-
| <Alt>-2 || Toggle display of "Vertex" ducks
|-
| <Alt>-3 || Toggle display of "Tangent" ducks
|-
| <Alt>-4 || Toggle display of "Radius" ducks
|-
| <Alt>-5 || Toggle display of "Width" ducks (DEFAULTS TO OFF)
|-
| <Alt>-6 || Toggle display of "Angle" ducks
|-
| <Control>-'-' || Zoom out of canvas (spacial zoom)
|-
| <Control>-'=' || Zoom in on canvas (spacial zoom)
|-
| <Control>-<Shift>-Z || Zoom canvas to 100% (spacial zoom)
|-
| <Control>-'_' || Zoom out of timeline (temporal zoom)
|-
| <Control>-'+' || Zoom in on timeline (temporal zoom)
|-
| <Control>-',' || Move backward one frame
|-
| <Control>-'.' || Move forward one frame (be careful - can step past the end of an animation; fixed in svn r452)
|-
| <Control>-'<' || Move backward one second
|-
| <Control>-'>' || Move forward one second
|-
| <Control>-'[' || Move backward to previous [[Keyframe|keyframe]]
|-
| <Control>-']' || Move forward to next keyframe
|-
| Home || Jump to beginning of timeline (broken; fixed in svn r451)
|-
| End || Jump to end of timeline (broken; fixed in svn r451)
|-
| <Control>-'(' || Decrease workarea pixel size
|-
| <Control>-')' || Increase workarea pixel size
|-
| <Control>-<Alt>-'(' || Decrease 'amount' of selected layer
|-
| <Control>-<Alt>-')' || Increase 'amount' of selected layer
|-
| <Shift>-PgUp || Raise currently selected layers
|-
| <Shift>-PgDn || Lower currently selected layers
|-
| <Alt>-A || Select 'normal' tool
|-
| <Alt>-V || Select 'smooth move' tool (shortcut added in svn r548)
|-
| <Alt>-S || Select 'scale' tool (shortcut changed in svn r1985)
|-
| <Alt>-T || Select 'rotate' tool (shortcut changed in svn r1985)
|-
| <Alt>-M || Select 'mirror' tool (shortcut added in svn r548)
|-
| <Alt>-C || Select 'circle' tool (shortcut added in svn r548)
|-
| <Alt>-R || Select 'rectangle' tool (shortcut added in svn r548)
|-
| <Alt>-Q || Select 'star' tool (tool and shortcut added in svn r1983)
|-
| <Alt>-G || Select 'gradient' tool
|-
| <Alt>-P || Select 'polygon' tool (shortcut added in svn r548)
|-
| <Alt>-B || Select 'bline' tool
|-
| <Alt>-X || Select 'text' tool (tool and shortcut added in svn r1959)
|-
| <Alt>-F || Select 'fill' tool
|-
| <Alt>-E || Select 'eyedrop' tool
|-
| <Alt>-Z || Select 'zoom' tool
|-
| <Alt>-D || Select 'draw' tool (shortcut changed in svn r2009)
|-
| <Alt>-K || Select 'sketch' tool (shortcut added in svn r548)
|-
| <Alt>-W || Select 'width' tool (shortcut changed in svn r2009)
|-
| F8 || Canvas Properties
|-
| F9 || Render
|-
| F11 || Preview
|-
| F12 || Canvas Options (Grid size, etc.)
|-
| <Escape> || Stop (stop what? not sure...)
|-
| <Delete> || Deletes the currently selected canvas. (CAREFUL! There is currently a bug which makes this work in just about any context! ie: if you are editing a parameter and press the delete key, it will delete the layer! this can be easily undone, but just keep it in mind)
|-
| <Cursor Key> || Nudge the currently selected duck(s) one pixel in the given direction
|-
| <Shift>-<Cursor Key> || Nudge the currently selected duck(s) ten pixels in the given direction
|-
|}

== Hotkeys Visual Guide ==
A good way to learn all this shorcuts is putting them in front of your eyes all the time. Because of that, we bring to you a beatiful "Hotkeys Visual Guide" that you can use as a poster.

<gallery>
Image:hotkeys-visual-guide-SVN2011.png|PNG Version - SVN2011
</gallery>

We offer you two print sizes (both in PDF):
* [http://synfig.org/images/c/cd/Hotkeys-visual-guide-SVN2011-A4.pdf A4 Version]
* [A3 Version]

And these are the source files in SVG format:
* [http://synfig.org/images/e/e1/Hotkeys-visual-guide-SVN2011-A4.svg A4 Version]
* [http://synfig.org/images/c/c2/Hotkeys-visual-guide-SVN2011-A3.svg A3 Version]

Give us your [[Talk:Keyboard_Shortcuts|feedback and comments]].

File:Hotkeys-visual-guide-SVN2011-A3.svg

2008-05-08T16:58:19Z

Yaco:

Keyboard Shortcuts

2008-05-08T16:53:13Z

Yaco: /* Hotkeys Visual Guide */

Here is a list of some of the keyboard sortcuts you currently have at your disposal. These are the defaults. There is a way to customize these, but it is currently not intuitive. Basically you need to edit the accelrc file in your synfig settings directory.

{| border="1" cellspacing="0" align="center" width="80%"
|'''Keystroke'''||'''Description'''
|-
| <Control>-A || Select all ducks
|-
| <Shift><Control>-A || Select all layers
|-
| <Control>-C || Copy currently selected layer(s) and put them in the clipboard
|-
| <Control>-D || Deselect all ducks
|-
| <Shift><Control>-D || Deselect all layers
|-
| <Control>-G || Toggle grid show
|-
| <Control>-I || Import image
|-
| <Control>-L || Toggle grid snap
|-
| <Control>-N || New composition (since r1386)
|-
| <Control>-O || Open composition (since r1386)
|-
| <Alt>-O || Toggle onion skin (since r1525 - it was Control-O until r1386)
|-
| <Control>-P || Play the current animation in the WorkArea
|-
| <Control>-Q || Quit Synfig Studio
|-
| <Control>-R || Redo
|-
| <Control>-S || Save
|-
| <Control>-V || Paste the layer(s) from the clipboard above the currently selected layer
|-
| <Control>-W || Closes the current animation document.
|-
| <Control>-X || Cut currently selected layer(s) and put them in the clipboard
|-
| <Control>-Z || Undo
|-
| <Control>-` || Toggle low/high-resolution (defaults to low resolution)
|-
| <Control>-0...9 || Change the current rendering quality (lower is better, but 0==10)
|-
| <Alt>-1 || Toggle display of "Position" ducks
|-
| <Alt>-2 || Toggle display of "Vertex" ducks
|-
| <Alt>-3 || Toggle display of "Tangent" ducks
|-
| <Alt>-4 || Toggle display of "Radius" ducks
|-
| <Alt>-5 || Toggle display of "Width" ducks (DEFAULTS TO OFF)
|-
| <Alt>-6 || Toggle display of "Angle" ducks
|-
| <Control>-'-' || Zoom out of canvas (spacial zoom)
|-
| <Control>-'=' || Zoom in on canvas (spacial zoom)
|-
| <Control>-<Shift>-Z || Zoom canvas to 100% (spacial zoom)
|-
| <Control>-'_' || Zoom out of timeline (temporal zoom)
|-
| <Control>-'+' || Zoom in on timeline (temporal zoom)
|-
| <Control>-',' || Move backward one frame
|-
| <Control>-'.' || Move forward one frame (be careful - can step past the end of an animation; fixed in svn r452)
|-
| <Control>-'<' || Move backward one second
|-
| <Control>-'>' || Move forward one second
|-
| <Control>-'[' || Move backward to previous [[Keyframe|keyframe]]
|-
| <Control>-']' || Move forward to next keyframe
|-
| Home || Jump to beginning of timeline (broken; fixed in svn r451)
|-
| End || Jump to end of timeline (broken; fixed in svn r451)
|-
| <Control>-'(' || Decrease workarea pixel size
|-
| <Control>-')' || Increase workarea pixel size
|-
| <Control>-<Alt>-'(' || Decrease 'amount' of selected layer
|-
| <Control>-<Alt>-')' || Increase 'amount' of selected layer
|-
| <Shift>-PgUp || Raise currently selected layers
|-
| <Shift>-PgDn || Lower currently selected layers
|-
| <Alt>-A || Select 'normal' tool
|-
| <Alt>-V || Select 'smooth move' tool (shortcut added in svn r548)
|-
| <Alt>-S || Select 'scale' tool (shortcut changed in svn r1985)
|-
| <Alt>-T || Select 'rotate' tool (shortcut changed in svn r1985)
|-
| <Alt>-M || Select 'mirror' tool (shortcut added in svn r548)
|-
| <Alt>-C || Select 'circle' tool (shortcut added in svn r548)
|-
| <Alt>-R || Select 'rectangle' tool (shortcut added in svn r548)
|-
| <Alt>-Q || Select 'star' tool (tool and shortcut added in svn r1983)
|-
| <Alt>-G || Select 'gradient' tool
|-
| <Alt>-P || Select 'polygon' tool (shortcut added in svn r548)
|-
| <Alt>-B || Select 'bline' tool
|-
| <Alt>-X || Select 'text' tool (tool and shortcut added in svn r1959)
|-
| <Alt>-F || Select 'fill' tool
|-
| <Alt>-E || Select 'eyedrop' tool
|-
| <Alt>-Z || Select 'zoom' tool
|-
| <Alt>-D || Select 'draw' tool (shortcut changed in svn r2009)
|-
| <Alt>-K || Select 'sketch' tool (shortcut added in svn r548)
|-
| <Alt>-W || Select 'width' tool (shortcut changed in svn r2009)
|-
| F8 || Canvas Properties
|-
| F9 || Render
|-
| F11 || Preview
|-
| F12 || Canvas Options (Grid size, etc.)
|-
| <Escape> || Stop (stop what? not sure...)
|-
| <Delete> || Deletes the currently selected canvas. (CAREFUL! There is currently a bug which makes this work in just about any context! ie: if you are editing a parameter and press the delete key, it will delete the layer! this can be easily undone, but just keep it in mind)
|-
| <Cursor Key> || Nudge the currently selected duck(s) one pixel in the given direction
|-
| <Shift>-<Cursor Key> || Nudge the currently selected duck(s) ten pixels in the given direction
|-
|}

== Hotkeys Visual Guide ==
A good way to learn all this shorcuts is putting them in front of your eyes all the time. Because of that, we bring to you a beatiful "Hotkeys Visual Guide" that you can use as a poster.

<gallery>
Image:hotkeys-visual-guide-SVN2011.png|PNG Version - SVN2011
</gallery>

We offer you two print sizes (both in PDF):
* [http://synfig.org/images/c/cd/Hotkeys-visual-guide-SVN2011-A4.pdf A4 Version]
* [A3 Version]

And these are the source files in SVG format:
* [http://synfig.org/images/e/e1/Hotkeys-visual-guide-SVN2011-A4.svg A4 Version]
* [A3 Version]

Give us your [[Talk:Keyboard_Shortcuts|feedback and comments]].

File:Hotkeys-visual-guide-SVN2011-A4.svg

2008-05-08T16:50:48Z

Yaco:

File:Hotkeys-visual-guide-SVN2011-A4.pdf

2008-05-08T16:50:35Z

Yaco:

Test zone

2008-05-01T07:45:01Z

Yaco: New page: == Test #1 == * Uploader: Yaco * Problem: Make a BLine with 2 nodes and the try to move the second one. It will crash. * File: http://synfig.org/images/7/73/Testzone-test-1.sifz

== Test #1 ==
* Uploader: Yaco
* Problem: Make a BLine with 2 nodes and the try to move the second one. It will crash.
* File: http://synfig.org/images/7/73/Testzone-test-1.sifz

File:Testzone-test-1.sifz

2008-05-01T07:44:22Z

Yaco:

Dev:Bugs

2008-05-01T07:42:13Z

Yaco:

There are several bug trackers for synfig and synfig packages:

* [http://sourceforge.net/tracker/?group_id=144022 Synfig]: [http://sourceforge.net/tracker/?group_id=144022&atid=757416 bugs] [http://sourceforge.net/tracker/?group_id=144022&atid=757419 enhancements] [http://sourceforge.net/tracker/?group_id=144022&atid=757418 patches] [http://sourceforge.net/tracker/?group_id=144022&atid=757417 support]
* [http://www.debian.org Debian]: [http://bugs.debian.org/src:etl etl] [http://bugs.debian.org/src:synfig synfig] [http://bugs.debian.org/src:synfigstudio synfigstudio]
* [http://www.ubuntu.com Ubuntu]: [http://launchpad.net/distros/ubuntu/+source/etl/+bugs etl] [http://launchpad.net/distros/ubuntu/+source/synfig/+bugs synfig] [http://launchpad.net/distros/ubuntu/+source/synfigstudio/+bugs synfigstudio]
* [http://support.zenwalk.org/ Zenwalk]
* [http://fink.sf.net Fink]: [http://sf.net/tracker/?atid=117203&group_id=17203&summary_keyword=etl etl] [http://sf.net/tracker/?atid=117203&group_id=17203&summary_keyword=synfig synfig] [http://sf.net/tracker/?atid=117203&group_id=17203&summary_keyword=synfigstudio synfigstudio]

* '''[[Test zone]]''' - Where we upload buggy files

2008-04-10T21:57:06Z

Yaco: /* Hotkeys Visual Guide */

Here is a list of some of the keyboard sortcuts you currently have at your disposal. These are the defaults. There is a way to customize these, but it is currently not intuitive. Basically you need to edit the accelrc file in your synfig settings directory.

{| border="1" cellspacing="0" align="center" width="80%"
|'''Keystroke'''||'''Description'''
|-
| <Control>-A || Select all ducks
|-
| <Shift><Control>-A || Select all layers
|-
| <Control>-C || Copy currently selected layer(s) and put them in the clipboard
|-
| <Control>-D || Deselect all ducks
|-
| <Shift><Control>-D || Deselect all layers
|-
| <Control>-G || Toggle grid show
|-
| <Control>-I || Import image
|-
| <Control>-L || Toggle grid snap
|-
| <Control>-N || New composition (since r1386)
|-
| <Control>-O || Open composition (since r1386)
|-
| <Alt>-O || Toggle onion skin (since r1525 - it was Control-O until r1386)
|-
| <Control>-P || Play the current animation in the WorkArea
|-
| <Control>-Q || Quit Synfig Studio
|-
| <Control>-R || Redo
|-
| <Control>-S || Save
|-
| <Control>-V || Paste the layer(s) from the clipboard above the currently selected layer
|-
| <Control>-W || Closes the current animation document.
|-
| <Control>-X || Cut currently selected layer(s) and put them in the clipboard
|-
| <Control>-Z || Undo
|-
| <Control>-` || Toggle low/high-resolution (defaults to low resolution)
|-
| <Control>-0...9 || Change the current rendering quality (lower is better, but 0==10)
|-
| <Alt>-1 || Toggle display of "Position" ducks
|-
| <Alt>-2 || Toggle display of "Vertex" ducks
|-
| <Alt>-3 || Toggle display of "Tangent" ducks
|-
| <Alt>-4 || Toggle display of "Radius" ducks
|-
| <Alt>-5 || Toggle display of "Width" ducks (DEFAULTS TO OFF)
|-
| <Alt>-6 || Toggle display of "Angle" ducks
|-
| <Control>-'-' || Zoom out of canvas (spacial zoom)
|-
| <Control>-'=' || Zoom in on canvas (spacial zoom)
|-
| <Control>-<Shift>-Z || Zoom canvas to 100% (spacial zoom)
|-
| <Control>-'_' || Zoom out of timeline (temporal zoom)
|-
| <Control>-'+' || Zoom in on timeline (temporal zoom)
|-
| <Control>-',' || Move backward one frame
|-
| <Control>-'.' || Move forward one frame (be careful - can step past the end of an animation; fixed in svn r452)
|-
| <Control>-'<' || Move backward one second
|-
| <Control>-'>' || Move forward one second
|-
| <Control>-'[' || Move backward to previous [[Keyframe|keyframe]]
|-
| <Control>-']' || Move forward to next keyframe
|-
| Home || Jump to beginning of timeline (broken; fixed in svn r451)
|-
| End || Jump to end of timeline (broken; fixed in svn r451)
|-
| <Control>-'(' || Decrease workarea pixel size
|-
| <Control>-')' || Increase workarea pixel size
|-
| <Control>-<Alt>-'(' || Decrease 'amount' of selected layer
|-
| <Control>-<Alt>-')' || Increase 'amount' of selected layer
|-
| <Shift>-PgUp || Raise currently selected layers
|-
| <Shift>-PgDn || Lower currently selected layers
|-
| <Alt>-A || Select 'normal' tool
|-
| <Alt>-V || Select 'smooth move' tool (shortcut added in svn r548)
|-
| <Alt>-S || Select 'scale' tool (shortcut changed in svn r1985)
|-
| <Alt>-T || Select 'rotate' tool (shortcut changed in svn r1985)
|-
| <Alt>-M || Select 'mirror' tool (shortcut added in svn r548)
|-
| <Alt>-C || Select 'circle' tool (shortcut added in svn r548)
|-
| <Alt>-R || Select 'rectangle' tool (shortcut added in svn r548)
|-
| <Alt>-Q || Select 'star' tool (tool and shortcut added in svn r1983)
|-
| <Alt>-G || Select 'gradient' tool
|-
| <Alt>-P || Select 'polygon' tool (shortcut added in svn r548)
|-
| <Alt>-B || Select 'bline' tool
|-
| <Alt>-X || Select 'text' tool (tool and shortcut added in svn r1959)
|-
| <Alt>-F || Select 'fill' tool
|-
| <Alt>-E || Select 'eyedrop' tool
|-
| <Alt>-Z || Select 'zoom' tool
|-
| <Alt>-D || Select 'draw' tool (shortcut changed in svn r2009)
|-
| <Alt>-K || Select 'sketch' tool (shortcut added in svn r548)
|-
| <Alt>-W || Select 'width' tool (shortcut changed in svn r2009)
|-
| F8 || Canvas Properties
|-
| F9 || Render
|-
| F11 || Preview
|-
| F12 || Canvas Options (Grid size, etc.)
|-
| <Escape> || Stop (stop what? not sure...)
|-
| <Delete> || Deletes the currently selected canvas. (CAREFUL! There is currently a bug which makes this work in just about any context! ie: if you are editing a parameter and press the delete key, it will delete the layer! this can be easily undone, but just keep it in mind)
|-
| <Cursor Key> || Nudge the currently selected duck(s) one pixel in the given direction
|-
| <Shift>-<Cursor Key> || Nudge the currently selected duck(s) ten pixels in the given direction
|-
|}

== Hotkeys Visual Guide ==
A good way to learn all this shorcuts is putting them in front of your eyes all the time. Because of that, we bring to you a beatiful "Hotkeys Visual Guide" that you can use as a poster.

<gallery>
Image:hotkeys-visual-guide-SVN2008.png|PNG Version
</gallery>

We offer you two print sizes (both in PDF):
* [http://synfig.org/images/b/b0/Hotkeys-visual-guide-a4-SVN2008.pdf A4 Version]
* [A3 Version]

And these are the source files in SVG format:
* [http://synfig.org/images/1/1a/Hotkeys-visual-guide-a4-SVN2008.svg A4 Version]
* [http://synfig.org/images/f/f6/Hotkeys-visual-guide-a3-SVN2008.svg A3 Version]

Give us your [[Talk:Keyboard_Shortcuts|feedback and comments]].