Inkscape Wiki - User contributions [en]

User talk:Kris

2017-08-24T13:59:57Z

Kris: /* Compiling Inkscape on Windows with MSYS2 */

{| align="center" cellpadding="10" style="border:4px DeepSkyBlue solid;background-color: Aquamarine; width:300px;border-radius: 25px;"
|-
|
|-
| align="center" | It's better to ask than to say nothing. :-)
|-
|
|}

== Compiling Inkscape on Windows with MSYS2 ==

Hi Kris,

I just reverted [[Special:Diff/106786|your change]] in the mentioned article.

It should not be necessary to set any environment variables if you use the proper MinGW shell for building Inkscape (that's one of the nice things of MSYS2 builds compared to our previous devlibs builds). Did you try to build in cmd.exe? As a matter of fact the file "msysenv.sh" will likely go away as part of our "root-dir tidying" efforts unless people are still actively using it (which they probably should not).

Let me know if I missed something or you need help with the MSYS2 build!

--[[User:Eduard|Eduard]] ([[User talk:Eduard|talk]]) 15:34, 23 August 2017 (UTC)
:I am still not able to successfully compile with the new system. If I remember well I'm stuck with the "cmake -G Ninja .." phase, so after a years break, I did not manage to setup the new system and contribute to translating and source code checks with cppcheck.
::> I just reverted [[Special:Diff/106786|your change]] in the mentioned article.
:That's fine. Though it comes as a surprise to have a script for setting the variables. :-)
:Regards, [[User:Kris|Kris]] ([[User talk:Kris|talk]]) 13:59, 24 August 2017 (UTC)

Compiling Inkscape on Windows with MSYS2

2017-08-19T14:53:15Z

Kris: /* Building Inkscape with MSYS2 */

This page explains how to compile Inkscape on Windows using [http://www.msys2.org/ '''MSYS2'''].

MSYS2 does not only offer a convenient build environment for compiling Inkscape but also provides all necessary build tools and dependencies making it extremely simple to get started with Inkscape development.

== Installing MSYS2 ==

To set-up MSYS2 and download the necessary dependencies only two steps are required:
* '''Step 1''' — Install MSYS2
** Download the installer from the [http://www.msys2.org/ MSYS2 homepage]. Start the installation and follow the instructions on screen.
**After installation finished start an MSYS2 MSYS shell (you can work with the one launched by the installer, use the "MSYS2 MSYS" shortcut in the start menu or launch "msys2.exe" in the installation directory).
**Execute the command <code>pacman -Syu</code>. This will start a full system upgrade and ensure that you have the latest versions of all core libraries (repeat this step until no new updates are found).
* '''Step 2''' — Download dependencies
** Start an MSYS2 MinGW shell (use the "MSYS2 MinGW 32/64-bit" shortcut in the start menu or launch "mingw32/64.exe" in the installation directory). Choose the shell in this step (32-bit or 64-bit) according to whether you want to build a 32-bit or 64-bit version of Inkscape later.
** Execute the script [https://gitlab.com/inkscape/inkscape/blob/master/buildtools/msys2installdeps.sh msys2installdeps.sh] by either copy-and-pasting it into the console or by downloading it and (after changing to the folder containing the file) typing <code>./msys2installdeps.sh</code>. If you already have a copy of the Inkscape source it should also be included in the "buildtools" folder.
Step 2 will take some time to complete (approx. 10 minutes depending on the speed of your internet connection and the load of the download servers), so relax and get a cup of coffee...

== Obtaining Inkscape Source ==

''Note: For general instructions on how to use Git see [[Working with Git]].''

As MSYS2 provides the revision control software Git you do not need to download it separately. Simply open the MSYS2 MinGW shell and run the command
<pre>git clone https://gitlab.com/inkscape/inkscape.git master</pre>
This creates a folder called "master" in the current working directory (usually the home folder located at "C:\msys64\home\Your_Username" or similar) in which the so-called clone of the source repository is created.

== Building Inkscape with MSYS2 ==

To compile Inkscape open the MSYS2 MinGW shell (remember to use the correct shell, i.e. 32-bit or 64-bit, matching the dependencies you downloaded above and the version of Inkscape you want to build).

Then execute the following commands:
<pre>
# change to the directory containing your Inkscape source checkout (has to be adjusted to match your system)
cd master

#run de msysenv.sh script to set the required environment parameters
./msysenv.sh

# create a directory for the build (could also be another folder, but we'll assume 'build' being used for the rest of the article)
mkdir build
cd build

# create build files with CMake (we generate rules for "Ninja" as it's significantly faster then "MinGW Makefiles" which uses mingw32-make)
# note the source path '..' (which in this case is the parent directory) and should always point to the root folder of your copy of the Inkscape source
cmake -G Ninja ..

# start the compilation
ninja

# install compiled files and all dependencies required to run Inkscape into the folder 'build/inkscape/'
ninja install

# The last two steps can be combined (i.e. run 'ninja install' immediately) if you want to save time in future, as the "install" target also includes the default target
</pre>

'''''That's it!''''' 
Afterwards you should have a complete binary distribution of Inkscape in the folder "build/inkscape/" that can be run on any Windows machine.

Google Summer of Code

2014-02-24T19:32:06Z

Kris: /* Better SVG standard coverage */

= Welcome to Inkscape! =

For quite a few years Inkscape has been successfully participating in [http://code.google.com/soc/ Google Summer of Code].

GSoC is a program where Google funds the development of specific features in open source software by university students. You don't need to be a Computer Science student to apply. Features to be developed are picked by Inkscape administrators from the pool of proposals submitted by students.

We've mentored about half a dozen students a year since GSoC started. Many students enjoyed their work and continue to be involved; perhaps your mentor will be a past GSoC student! We have a high rate of acceptance of student code into the core codebase. Indeed, GSoC projects have been a key source of some of Inkscape's best features in the past several releases.

If you are interested in joining us this summer, it is time to get your proposal ready. You can choose a proposal from our list of suggestions or come up with one of your own. In either either case, you must give us a detailed outline of what you plan to do. It is highly recommended that you discuss your idea as early as possible with Inkscape developers. They not only can give you guidance as you flesh out your proposal but ultimately you must convince them that you can do the work planned in the time allotted.

= Student Applications =

* Google program information:
** [https://www.google-melange.com/gsoc/homepage/google/gsoc2014 Home page].
** Summer of Code Application form.

* Inkscape-specific information:
** [[SOC Application Template]].
** [[Roadmap | Inkscape Roadmap]] - to see our overall objectives.
** [[SOC Writing Project Proposals]] - some guidelines for proposals.
** [[SOC Selection Criteria]] - how we rate applications.

'''Student Applications for GSoC 2014 must be submitted to the GSoC site by 19:00 UTC on March 21st 2014.'''

= The "two patches" rule =

We require two patches from each potential GSoC student, before accepting the student for GSoC participation (it is the same requirement as for obtaining rights to commit changes to the Bazaar code repository).
The reason for this requirement is that you can show us that you have succeeded in building Inkscape on your PC, and that you have understood a little piece of Inkscape's code and are able to improve it.
Inkscape is a large project, and you really should not try to understand all the code. Many (all?) developers know only parts of the program code!
You can join our [http://inkscape.org/discussion.php jabber/IRC] channel and ask developers for help.

== Suggested "easy" bug fixes or improvements ==

To get you started on Inkscape development, you can find (probably) easy-to-fix bugs or small improvements that require very little knowledge of the whole program by searching our [https://bugs.launchpad.net/inkscape bug-tracker] for bugs tagged with 'easy-fix'.

= Performance Evaluation =

GSoC has two formal evaluation points, at the ''mid-term'' and at the end. These evaluations determine if you receive the stipend from Google. In order to receive a pass for the evaluations you will need to show adequate progress toward your project's goals.

To help you meet your goals and so that your mentor can better evaluate your progress you need to:

* Have frequent, public discussions of your progress. (Don't rely on just your mentor for advice.)
* Have a public Inkscape branch for your code to which you commit regularly.
* Give weekly status reports.

For the final pass, you will normally be required to merge your code into Inkscape trunk.

Remember: ''we want you to succeed!''

= Suggested Ideas =

Please note that your project proposal must be realistic: if you promise too much, we will most likely think you have not understood at all what it is about and will reject your proposal.

== Generic ideas ==

* Font editing and creation features, e.g. [https://blueprints.launchpad.net/inkscape/+spec/designing-svg-fonts-using-styles designing SVG fonts using styles]
* [https://blueprints.launchpad.net/inkscape/+spec/kidscape-project kidscape] - Condensed version of Inkscape aimed at young kids and small form factor devices
* [https://blueprints.launchpad.net/inkscape/+spec/cutter-control Cutter control] - Enable Inkscape's use with vinyl cutters.

== Import/export projects ==

* Importing of 3D scene files in 16 file formats using [http://assimp.sourceforge.net/ Open Asset Import Library]
* [https://blueprints.launchpad.net/inkscape/+spec/xar-to-svg-converter xar-to-svg converter] - Converter for Xara Xtreme to Inkscape
* [https://blueprints.launchpad.net/inkscape/+spec/kml-svg-translation KML SVG translation] - For use of Inkscape with Google Earth or Maps

== Internal work & performance improvements ==

* Improve startup time and initialization performance (a.o. improving font cache).
* Continue C++ification (including more use of the gtkmm-framework as well as well as string classes (std::string and glib::ustring) in favor of C-strings).
* Improving 2Geom where necessary (e.g. '''boolops''' and '''python bindings''').
* [https://blueprints.launchpad.net/inkscape/+spec/icc-for-cairo ICC Color Management for cairo outputs] - Would allow Inkscape to produce CMYK PDFs and PSs with Cairo.
* [http://wiki.inkscape.org/wiki/index.php/TextRework Text layout rewrite]: Move flow-text into Inkscape name space. Add support for hyphenation, paragraph indentation, underlining, etc.


== Better SVG standard coverage ==

* Full SVG viewbox support
* [[multipage | Multiple Page support]]
* Improve SVG compliance. [http://tavmjong.free.fr/INKSCAPE/W3C_SVG_1.1F2/harness/htmlInkscapeApproved/index.html Current status of W3C test suite compliance].
* Implement SVG 2.0 (and related) items such as:
** Vector Effects (non-destructive boolean-ops would be a good start)
** Marker color matching stroke
** [http://www.w3.org/TR/SVGMobile12/single-page.html#painting-SolidColorElement Solid-color support] (Named colors, would deprecate the single-stop gradient approach we currently use)
** [http://www.w3.org/TR/css3-color/ CSS3 color support]
** CSS3 2d transforms (duplicates current attributes)
** [http://www.w3.org/Graphics/SVG/WG/wiki/Proposals/Stroke_position Stroke position]
** [http://www.w3.org/Graphics/SVG/WG/wiki/Proposals/Stroke_dash_adjustment Stroke dash adjustment]
Note: Some of the above items are somewhat low hanging fruit and would need a few of them to make a good proposal, others alone are worthy of a full GSoC project.

== Improve Inkscape SVG for use on Web ==

A proposal should fix most if not all of these problems:

* Fix "plain" SVG to not remove <script> section, etc.
* Add option to set viewbox attribute to Document Properties.
* Easily add/edit hyperlinks.
* Better CSS support.
* Option to add title to SVG (searchability and accessibility).
* Remove XML prolog/DOCTYPE.
* Move sodipodi namespace items to Inkscape namespace.

== Live Path Effects related ==

* [https://blueprints.launchpad.net/inkscape/+spec/lpe-blueprint More Live Path Effects] - There is a lengthy list of ideas to choose from here.

== Tools and shapes related ==

* Multi shape editing - ability to edit more than 1 shape (like ellipse or star) at once, with extra features like resizing rectangles by dragging their edges.
* [https://blueprints.launchpad.net/inkscape/+spec/transformation-anchors Transformation Anchors]
* Further development of [http://generalpicture.com/svg/shapeopera.html Shape Opera], a simple Javascript framework for morphing Inkscape PATH shapes.
* Extend the Symbols dialog to include generic objects.
* [https://blueprints.launchpad.net/inkscape/+spec/inkscape-connectors Connector tool improvements] - Expose new libavoid functionality: orthogonal routing, connector ports, curved connectors. (Mentor: Michael Wybrow)
* [https://blueprints.launchpad.net/inkscape/+spec/fillet-tool Fillet/Chamfer tool]
* Move Mesh gradients to Inkscape name space with appropriate editing interface and export fallback. Note, Inkscape trunk has an experimental implementation based on the proposed mesh syntax for SVG 2.

Please do not feel limited to the above ideas - some of our best contributions have been unique ideas that students had in mind from other sources!

For more ideas, please see https://blueprints.launchpad.net/inkscape/

= Successful SOC Projects from Previous Years =
* 2005
** Connectors
** Inkboard
** [http://www.openclipart.org/ Open Clip Art Library (OCAL)] Interface
** DXF Import / Export
* [[Google Summer of Code 2006|2006]]
** Support for SVG Filters
** Filter Effects
** PDF export
** Inkboard Protocol Spec / Lib Conversion
* [[Google Summer of Code 2007|2007]]
** Text Style Improvements
** PDF import
** Live Path Effects
** 3D Box Tool
** UI for SVG Filter Effects
** Raster Functionality
** Importing from, and Exporting to, a remote ccHost instance
* [[Google Summer of Code 2008|2008]]
** SVG Fonts support
** 2Geom refactoring project - port most geometry code to 2Geom
** lib2geom: interactive applications showing off the power of lib2geom
** Tech drawing abilities
** A test suite
* 2009
** [[GSoC 2009 Node Tool Rewrite|Node tool rewrite]]
** D-Bus scripting API
** Connector tool improvements
** ICC/CMYK workflow
* 2010
** Cairo-based rendering
** C++ification of SP Layer
* 2011
** Rendering caching
** Javascript support improvements
** CSS support improvements
* 2012
** Usibility Improvements for Guides
** [[Tiling tool|On-canvas support for Tessellations]]
** Creating python bindings for lib2geom
* [[Google Summer of Code 2013|2013]]
** Recolor Tool
** Improved Units Support
** Electronics CAD Support
** New From Templates Dialog
** New Raster to Vector Algorithm
[[Category:Developer Documentation]]

Google Summer of Code

2014-02-24T19:31:29Z

Kris: /* Internal work & performance improvements */

= Welcome to Inkscape! =

For quite a few years Inkscape has been successfully participating in [http://code.google.com/soc/ Google Summer of Code].

GSoC is a program where Google funds the development of specific features in open source software by university students. You don't need to be a Computer Science student to apply. Features to be developed are picked by Inkscape administrators from the pool of proposals submitted by students.

We've mentored about half a dozen students a year since GSoC started. Many students enjoyed their work and continue to be involved; perhaps your mentor will be a past GSoC student! We have a high rate of acceptance of student code into the core codebase. Indeed, GSoC projects have been a key source of some of Inkscape's best features in the past several releases.

If you are interested in joining us this summer, it is time to get your proposal ready. You can choose a proposal from our list of suggestions or come up with one of your own. In either either case, you must give us a detailed outline of what you plan to do. It is highly recommended that you discuss your idea as early as possible with Inkscape developers. They not only can give you guidance as you flesh out your proposal but ultimately you must convince them that you can do the work planned in the time allotted.

= Student Applications =

* Google program information:
** [https://www.google-melange.com/gsoc/homepage/google/gsoc2014 Home page].
** Summer of Code Application form.

* Inkscape-specific information:
** [[SOC Application Template]].
** [[Roadmap | Inkscape Roadmap]] - to see our overall objectives.
** [[SOC Writing Project Proposals]] - some guidelines for proposals.
** [[SOC Selection Criteria]] - how we rate applications.

'''Student Applications for GSoC 2014 must be submitted to the GSoC site by 19:00 UTC on March 21st 2014.'''

= The "two patches" rule =

We require two patches from each potential GSoC student, before accepting the student for GSoC participation (it is the same requirement as for obtaining rights to commit changes to the Bazaar code repository).
The reason for this requirement is that you can show us that you have succeeded in building Inkscape on your PC, and that you have understood a little piece of Inkscape's code and are able to improve it.
Inkscape is a large project, and you really should not try to understand all the code. Many (all?) developers know only parts of the program code!
You can join our [http://inkscape.org/discussion.php jabber/IRC] channel and ask developers for help.

== Suggested "easy" bug fixes or improvements ==

To get you started on Inkscape development, you can find (probably) easy-to-fix bugs or small improvements that require very little knowledge of the whole program by searching our [https://bugs.launchpad.net/inkscape bug-tracker] for bugs tagged with 'easy-fix'.

= Performance Evaluation =

GSoC has two formal evaluation points, at the ''mid-term'' and at the end. These evaluations determine if you receive the stipend from Google. In order to receive a pass for the evaluations you will need to show adequate progress toward your project's goals.

To help you meet your goals and so that your mentor can better evaluate your progress you need to:

* Have frequent, public discussions of your progress. (Don't rely on just your mentor for advice.)
* Have a public Inkscape branch for your code to which you commit regularly.
* Give weekly status reports.

For the final pass, you will normally be required to merge your code into Inkscape trunk.

Remember: ''we want you to succeed!''

= Suggested Ideas =

Please note that your project proposal must be realistic: if you promise too much, we will most likely think you have not understood at all what it is about and will reject your proposal.

== Generic ideas ==

* Font editing and creation features, e.g. [https://blueprints.launchpad.net/inkscape/+spec/designing-svg-fonts-using-styles designing SVG fonts using styles]
* [https://blueprints.launchpad.net/inkscape/+spec/kidscape-project kidscape] - Condensed version of Inkscape aimed at young kids and small form factor devices
* [https://blueprints.launchpad.net/inkscape/+spec/cutter-control Cutter control] - Enable Inkscape's use with vinyl cutters.

== Import/export projects ==

* Importing of 3D scene files in 16 file formats using [http://assimp.sourceforge.net/ Open Asset Import Library]
* [https://blueprints.launchpad.net/inkscape/+spec/xar-to-svg-converter xar-to-svg converter] - Converter for Xara Xtreme to Inkscape
* [https://blueprints.launchpad.net/inkscape/+spec/kml-svg-translation KML SVG translation] - For use of Inkscape with Google Earth or Maps

== Internal work & performance improvements ==

* Improve startup time and initialization performance (a.o. improving font cache).
* Continue C++ification (including more use of the gtkmm-framework as well as well as string classes (std::string and glib::ustring) in favor of C-strings).
* Improving 2Geom where necessary (e.g. '''boolops''' and '''python bindings''').
* [https://blueprints.launchpad.net/inkscape/+spec/icc-for-cairo ICC Color Management for cairo outputs] - Would allow Inkscape to produce CMYK PDFs and PSs with Cairo.
* [http://wiki.inkscape.org/wiki/index.php/TextRework Text layout rewrite]: Move flow-text into Inkscape name space. Add support for hyphenation, paragraph indentation, underlining, etc.


== Better SVG standard coverage ==

* Full SVG viewbox support
* [[multipage | Multiple Page support]]
* Improve SVG compliance. [http://tavmjong.free.fr/INKSCAPE/W3C_SVG_1.1F2/harness/htmlInkscapeApproved/index.html Current status of W3C test suite compliance].
* Implement SVG 2.0 (and related) items such as:
** Vector Effects (non-destructive boolean-ops would be a good start)
** Marker color matching stroke
** [http://www.w3.org/TR/SVGMobile12/single-page.html#painting-SolidColorElement Solid-color support] (Named colors, would deprecate the single-stop gradient approach we currently use)
** [http://www.w3.org/TR/css3-color/ CSS3 color support]
** CSS3 2d transforms (duplicates current attributes)
** [http://www.w3.org/Graphics/SVG/WG/wiki/Proposals/Stroke_position Stroke position]
** [http://www.w3.org/Graphics/SVG/WG/wiki/Proposals/Stroke_dash_adjustment Stroke dash adjustment]
Note: Some of the above items are somwhat low hanging fruit and would need a few of them to make a good proposal, others alone are worthy of a full GSoC project.

== Improve Inkscape SVG for use on Web ==

A proposal should fix most if not all of these problems:

* Fix "plain" SVG to not remove <script> section, etc.
* Add option to set viewbox attribute to Document Properties.
* Easily add/edit hyperlinks.
* Better CSS support.
* Option to add title to SVG (searchability and accessibility).
* Remove XML prolog/DOCTYPE.
* Move sodipodi namespace items to Inkscape namespace.

== Live Path Effects related ==

* [https://blueprints.launchpad.net/inkscape/+spec/lpe-blueprint More Live Path Effects] - There is a lengthy list of ideas to choose from here.

== Tools and shapes related ==

* Multi shape editing - ability to edit more than 1 shape (like ellipse or star) at once, with extra features like resizing rectangles by dragging their edges.
* [https://blueprints.launchpad.net/inkscape/+spec/transformation-anchors Transformation Anchors]
* Further development of [http://generalpicture.com/svg/shapeopera.html Shape Opera], a simple Javascript framework for morphing Inkscape PATH shapes.
* Extend the Symbols dialog to include generic objects.
* [https://blueprints.launchpad.net/inkscape/+spec/inkscape-connectors Connector tool improvements] - Expose new libavoid functionality: orthogonal routing, connector ports, curved connectors. (Mentor: Michael Wybrow)
* [https://blueprints.launchpad.net/inkscape/+spec/fillet-tool Fillet/Chamfer tool]
* Move Mesh gradients to Inkscape name space with appropriate editing interface and export fallback. Note, Inkscape trunk has an experimental implementation based on the proposed mesh syntax for SVG 2.

Please do not feel limited to the above ideas - some of our best contributions have been unique ideas that students had in mind from other sources!

For more ideas, please see https://blueprints.launchpad.net/inkscape/

= Successful SOC Projects from Previous Years =
* 2005
** Connectors
** Inkboard
** [http://www.openclipart.org/ Open Clip Art Library (OCAL)] Interface
** DXF Import / Export
* [[Google Summer of Code 2006|2006]]
** Support for SVG Filters
** Filter Effects
** PDF export
** Inkboard Protocol Spec / Lib Conversion
* [[Google Summer of Code 2007|2007]]
** Text Style Improvements
** PDF import
** Live Path Effects
** 3D Box Tool
** UI for SVG Filter Effects
** Raster Functionality
** Importing from, and Exporting to, a remote ccHost instance
* [[Google Summer of Code 2008|2008]]
** SVG Fonts support
** 2Geom refactoring project - port most geometry code to 2Geom
** lib2geom: interactive applications showing off the power of lib2geom
** Tech drawing abilities
** A test suite
* 2009
** [[GSoC 2009 Node Tool Rewrite|Node tool rewrite]]
** D-Bus scripting API
** Connector tool improvements
** ICC/CMYK workflow
* 2010
** Cairo-based rendering
** C++ification of SP Layer
* 2011
** Rendering caching
** Javascript support improvements
** CSS support improvements
* 2012
** Usibility Improvements for Guides
** [[Tiling tool|On-canvas support for Tessellations]]
** Creating python bindings for lib2geom
* [[Google Summer of Code 2013|2013]]
** Recolor Tool
** Improved Units Support
** Electronics CAD Support
** New From Templates Dialog
** New Raster to Vector Algorithm
[[Category:Developer Documentation]]

Google Summer of Code

2014-02-24T19:30:32Z

Kris: /* Internal work & performance improvements */ was not this already done?

= Welcome to Inkscape! =

For quite a few years Inkscape has been successfully participating in [http://code.google.com/soc/ Google Summer of Code].

GSoC is a program where Google funds the development of specific features in open source software by university students. You don't need to be a Computer Science student to apply. Features to be developed are picked by Inkscape administrators from the pool of proposals submitted by students.

We've mentored about half a dozen students a year since GSoC started. Many students enjoyed their work and continue to be involved; perhaps your mentor will be a past GSoC student! We have a high rate of acceptance of student code into the core codebase. Indeed, GSoC projects have been a key source of some of Inkscape's best features in the past several releases.

If you are interested in joining us this summer, it is time to get your proposal ready. You can choose a proposal from our list of suggestions or come up with one of your own. In either either case, you must give us a detailed outline of what you plan to do. It is highly recommended that you discuss your idea as early as possible with Inkscape developers. They not only can give you guidance as you flesh out your proposal but ultimately you must convince them that you can do the work planned in the time allotted.

= Student Applications =

* Google program information:
** [https://www.google-melange.com/gsoc/homepage/google/gsoc2014 Home page].
** Summer of Code Application form.

* Inkscape-specific information:
** [[SOC Application Template]].
** [[Roadmap | Inkscape Roadmap]] - to see our overall objectives.
** [[SOC Writing Project Proposals]] - some guidelines for proposals.
** [[SOC Selection Criteria]] - how we rate applications.

'''Student Applications for GSoC 2014 must be submitted to the GSoC site by 19:00 UTC on March 21st 2014.'''

= The "two patches" rule =

We require two patches from each potential GSoC student, before accepting the student for GSoC participation (it is the same requirement as for obtaining rights to commit changes to the Bazaar code repository).
The reason for this requirement is that you can show us that you have succeeded in building Inkscape on your PC, and that you have understood a little piece of Inkscape's code and are able to improve it.
Inkscape is a large project, and you really should not try to understand all the code. Many (all?) developers know only parts of the program code!
You can join our [http://inkscape.org/discussion.php jabber/IRC] channel and ask developers for help.

== Suggested "easy" bug fixes or improvements ==

To get you started on Inkscape development, you can find (probably) easy-to-fix bugs or small improvements that require very little knowledge of the whole program by searching our [https://bugs.launchpad.net/inkscape bug-tracker] for bugs tagged with 'easy-fix'.

= Performance Evaluation =

GSoC has two formal evaluation points, at the ''mid-term'' and at the end. These evaluations determine if you receive the stipend from Google. In order to receive a pass for the evaluations you will need to show adequate progress toward your project's goals.

To help you meet your goals and so that your mentor can better evaluate your progress you need to:

* Have frequent, public discussions of your progress. (Don't rely on just your mentor for advice.)
* Have a public Inkscape branch for your code to which you commit regularly.
* Give weekly status reports.

For the final pass, you will normally be required to merge your code into Inkscape trunk.

Remember: ''we want you to succeed!''

= Suggested Ideas =

Please note that your project proposal must be realistic: if you promise too much, we will most likely think you have not understood at all what it is about and will reject your proposal.

== Generic ideas ==

* Font editing and creation features, e.g. [https://blueprints.launchpad.net/inkscape/+spec/designing-svg-fonts-using-styles designing SVG fonts using styles]
* [https://blueprints.launchpad.net/inkscape/+spec/kidscape-project kidscape] - Condensed version of Inkscape aimed at young kids and small form factor devices
* [https://blueprints.launchpad.net/inkscape/+spec/cutter-control Cutter control] - Enable Inkscape's use with vinyl cutters.

== Import/export projects ==

* Importing of 3D scene files in 16 file formats using [http://assimp.sourceforge.net/ Open Asset Import Library]
* [https://blueprints.launchpad.net/inkscape/+spec/xar-to-svg-converter xar-to-svg converter] - Converter for Xara Xtreme to Inkscape
* [https://blueprints.launchpad.net/inkscape/+spec/kml-svg-translation KML SVG translation] - For use of Inkscape with Google Earth or Maps

== Internal work & performance improvements ==

* Improve startup time and initialization performance.
* Continue C++ification (including more use of the gtkmm-framework as well as well as string classes (std::string and glib::ustring) in favor of C-strings).
* Improving 2Geom where necessary (e.g. '''boolops''' and '''python bindings''').
* [https://blueprints.launchpad.net/inkscape/+spec/icc-for-cairo ICC Color Management for cairo outputs] - Would allow Inkscape to produce CMYK PDFs and PSs with Cairo.
* [http://wiki.inkscape.org/wiki/index.php/TextRework Text layout rewrite]: Move flow-text into Inkscape name space. Add support for hyphenation, paragraph indentation, underlining, etc.


== Better SVG standard coverage ==

* Full SVG viewbox support
* [[multipage | Multiple Page support]]
* Improve SVG compliance. [http://tavmjong.free.fr/INKSCAPE/W3C_SVG_1.1F2/harness/htmlInkscapeApproved/index.html Current status of W3C test suite compliance].
* Implement SVG 2.0 (and related) items such as:
** Vector Effects (non-destructive boolean-ops would be a good start)
** Marker color matching stroke
** [http://www.w3.org/TR/SVGMobile12/single-page.html#painting-SolidColorElement Solid-color support] (Named colors, would deprecate the single-stop gradient approach we currently use)
** [http://www.w3.org/TR/css3-color/ CSS3 color support]
** CSS3 2d transforms (duplicates current attributes)
** [http://www.w3.org/Graphics/SVG/WG/wiki/Proposals/Stroke_position Stroke position]
** [http://www.w3.org/Graphics/SVG/WG/wiki/Proposals/Stroke_dash_adjustment Stroke dash adjustment]
Note: Some of the above items are somwhat low hanging fruit and would need a few of them to make a good proposal, others alone are worthy of a full GSoC project.

== Improve Inkscape SVG for use on Web ==

A proposal should fix most if not all of these problems:

* Fix "plain" SVG to not remove <script> section, etc.
* Add option to set viewbox attribute to Document Properties.
* Easily add/edit hyperlinks.
* Better CSS support.
* Option to add title to SVG (searchability and accessibility).
* Remove XML prolog/DOCTYPE.
* Move sodipodi namespace items to Inkscape namespace.

== Live Path Effects related ==

* [https://blueprints.launchpad.net/inkscape/+spec/lpe-blueprint More Live Path Effects] - There is a lengthy list of ideas to choose from here.

== Tools and shapes related ==

* Multi shape editing - ability to edit more than 1 shape (like ellipse or star) at once, with extra features like resizing rectangles by dragging their edges.
* [https://blueprints.launchpad.net/inkscape/+spec/transformation-anchors Transformation Anchors]
* Further development of [http://generalpicture.com/svg/shapeopera.html Shape Opera], a simple Javascript framework for morphing Inkscape PATH shapes.
* Extend the Symbols dialog to include generic objects.
* [https://blueprints.launchpad.net/inkscape/+spec/inkscape-connectors Connector tool improvements] - Expose new libavoid functionality: orthogonal routing, connector ports, curved connectors. (Mentor: Michael Wybrow)
* [https://blueprints.launchpad.net/inkscape/+spec/fillet-tool Fillet/Chamfer tool]
* Move Mesh gradients to Inkscape name space with appropriate editing interface and export fallback. Note, Inkscape trunk has an experimental implementation based on the proposed mesh syntax for SVG 2.

Please do not feel limited to the above ideas - some of our best contributions have been unique ideas that students had in mind from other sources!

For more ideas, please see https://blueprints.launchpad.net/inkscape/

= Successful SOC Projects from Previous Years =
* 2005
** Connectors
** Inkboard
** [http://www.openclipart.org/ Open Clip Art Library (OCAL)] Interface
** DXF Import / Export
* [[Google Summer of Code 2006|2006]]
** Support for SVG Filters
** Filter Effects
** PDF export
** Inkboard Protocol Spec / Lib Conversion
* [[Google Summer of Code 2007|2007]]
** Text Style Improvements
** PDF import
** Live Path Effects
** 3D Box Tool
** UI for SVG Filter Effects
** Raster Functionality
** Importing from, and Exporting to, a remote ccHost instance
* [[Google Summer of Code 2008|2008]]
** SVG Fonts support
** 2Geom refactoring project - port most geometry code to 2Geom
** lib2geom: interactive applications showing off the power of lib2geom
** Tech drawing abilities
** A test suite
* 2009
** [[GSoC 2009 Node Tool Rewrite|Node tool rewrite]]
** D-Bus scripting API
** Connector tool improvements
** ICC/CMYK workflow
* 2010
** Cairo-based rendering
** C++ification of SP Layer
* 2011
** Rendering caching
** Javascript support improvements
** CSS support improvements
* 2012
** Usibility Improvements for Guides
** [[Tiling tool|On-canvas support for Tessellations]]
** Creating python bindings for lib2geom
* [[Google Summer of Code 2013|2013]]
** Recolor Tool
** Improved Units Support
** Electronics CAD Support
** New From Templates Dialog
** New Raster to Vector Algorithm
[[Category:Developer Documentation]]

Google Summer of Code

2014-02-24T19:29:06Z

Kris: /* Internal work & performance improvements */

= Welcome to Inkscape! =

For quite a few years Inkscape has been successfully participating in [http://code.google.com/soc/ Google Summer of Code].

GSoC is a program where Google funds the development of specific features in open source software by university students. You don't need to be a Computer Science student to apply. Features to be developed are picked by Inkscape administrators from the pool of proposals submitted by students.

We've mentored about half a dozen students a year since GSoC started. Many students enjoyed their work and continue to be involved; perhaps your mentor will be a past GSoC student! We have a high rate of acceptance of student code into the core codebase. Indeed, GSoC projects have been a key source of some of Inkscape's best features in the past several releases.

If you are interested in joining us this summer, it is time to get your proposal ready. You can choose a proposal from our list of suggestions or come up with one of your own. In either either case, you must give us a detailed outline of what you plan to do. It is highly recommended that you discuss your idea as early as possible with Inkscape developers. They not only can give you guidance as you flesh out your proposal but ultimately you must convince them that you can do the work planned in the time allotted.

= Student Applications =

* Google program information:
** [https://www.google-melange.com/gsoc/homepage/google/gsoc2014 Home page].
** Summer of Code Application form.

* Inkscape-specific information:
** [[SOC Application Template]].
** [[Roadmap | Inkscape Roadmap]] - to see our overall objectives.
** [[SOC Writing Project Proposals]] - some guidelines for proposals.
** [[SOC Selection Criteria]] - how we rate applications.

'''Student Applications for GSoC 2014 must be submitted to the GSoC site by 19:00 UTC on March 21st 2014.'''

= The "two patches" rule =

We require two patches from each potential GSoC student, before accepting the student for GSoC participation (it is the same requirement as for obtaining rights to commit changes to the Bazaar code repository).
The reason for this requirement is that you can show us that you have succeeded in building Inkscape on your PC, and that you have understood a little piece of Inkscape's code and are able to improve it.
Inkscape is a large project, and you really should not try to understand all the code. Many (all?) developers know only parts of the program code!
You can join our [http://inkscape.org/discussion.php jabber/IRC] channel and ask developers for help.

== Suggested "easy" bug fixes or improvements ==

To get you started on Inkscape development, you can find (probably) easy-to-fix bugs or small improvements that require very little knowledge of the whole program by searching our [https://bugs.launchpad.net/inkscape bug-tracker] for bugs tagged with 'easy-fix'.

= Performance Evaluation =

GSoC has two formal evaluation points, at the ''mid-term'' and at the end. These evaluations determine if you receive the stipend from Google. In order to receive a pass for the evaluations you will need to show adequate progress toward your project's goals.

To help you meet your goals and so that your mentor can better evaluate your progress you need to:

* Have frequent, public discussions of your progress. (Don't rely on just your mentor for advice.)
* Have a public Inkscape branch for your code to which you commit regularly.
* Give weekly status reports.

For the final pass, you will normally be required to merge your code into Inkscape trunk.

Remember: ''we want you to succeed!''

= Suggested Ideas =

Please note that your project proposal must be realistic: if you promise too much, we will most likely think you have not understood at all what it is about and will reject your proposal.

== Generic ideas ==

* Font editing and creation features, e.g. [https://blueprints.launchpad.net/inkscape/+spec/designing-svg-fonts-using-styles designing SVG fonts using styles]
* [https://blueprints.launchpad.net/inkscape/+spec/kidscape-project kidscape] - Condensed version of Inkscape aimed at young kids and small form factor devices
* [https://blueprints.launchpad.net/inkscape/+spec/cutter-control Cutter control] - Enable Inkscape's use with vinyl cutters.

== Import/export projects ==

* Importing of 3D scene files in 16 file formats using [http://assimp.sourceforge.net/ Open Asset Import Library]
* [https://blueprints.launchpad.net/inkscape/+spec/xar-to-svg-converter xar-to-svg converter] - Converter for Xara Xtreme to Inkscape
* [https://blueprints.launchpad.net/inkscape/+spec/kml-svg-translation KML SVG translation] - For use of Inkscape with Google Earth or Maps

== Internal work & performance improvements ==

* Improve startup time and initialization performance.
* Continue C++ification (including more use of the gtkmm-framework as well as well as string classes (std::string and glib::ustring) in favor of C-strings).
* Improving 2Geom where necessary (e.g. '''boolops''' and '''python bindings''').
* [https://blueprints.launchpad.net/inkscape/+spec/icc-for-cairo ICC Color Management for cairo outputs] - Would allow Inkscape to produce CMYK PDFs and PSs with Cairo.
* [http://wiki.inkscape.org/wiki/index.php/TextRework Text layout rewrite]: Move flow-text into Inkscape name space. Add support for hyphenation, paragraph indentation, underlining, etc.
* Units (inch, cm, px): the codebase has 4 different pieces of code for handling units! Refactoring into *one*. Allow users to choose which unit to use by default.

== Better SVG standard coverage ==

* Full SVG viewbox support
* [[multipage | Multiple Page support]]
* Improve SVG compliance. [http://tavmjong.free.fr/INKSCAPE/W3C_SVG_1.1F2/harness/htmlInkscapeApproved/index.html Current status of W3C test suite compliance].
* Implement SVG 2.0 (and related) items such as:
** Vector Effects (non-destructive boolean-ops would be a good start)
** Marker color matching stroke
** [http://www.w3.org/TR/SVGMobile12/single-page.html#painting-SolidColorElement Solid-color support] (Named colors, would deprecate the single-stop gradient approach we currently use)
** [http://www.w3.org/TR/css3-color/ CSS3 color support]
** CSS3 2d transforms (duplicates current attributes)
** [http://www.w3.org/Graphics/SVG/WG/wiki/Proposals/Stroke_position Stroke position]
** [http://www.w3.org/Graphics/SVG/WG/wiki/Proposals/Stroke_dash_adjustment Stroke dash adjustment]
Note: Some of the above items are somwhat low hanging fruit and would need a few of them to make a good proposal, others alone are worthy of a full GSoC project.

== Improve Inkscape SVG for use on Web ==

A proposal should fix most if not all of these problems:

* Fix "plain" SVG to not remove <script> section, etc.
* Add option to set viewbox attribute to Document Properties.
* Easily add/edit hyperlinks.
* Better CSS support.
* Option to add title to SVG (searchability and accessibility).
* Remove XML prolog/DOCTYPE.
* Move sodipodi namespace items to Inkscape namespace.

== Live Path Effects related ==

* [https://blueprints.launchpad.net/inkscape/+spec/lpe-blueprint More Live Path Effects] - There is a lengthy list of ideas to choose from here.

== Tools and shapes related ==

* Multi shape editing - ability to edit more than 1 shape (like ellipse or star) at once, with extra features like resizing rectangles by dragging their edges.
* [https://blueprints.launchpad.net/inkscape/+spec/transformation-anchors Transformation Anchors]
* Further development of [http://generalpicture.com/svg/shapeopera.html Shape Opera], a simple Javascript framework for morphing Inkscape PATH shapes.
* Extend the Symbols dialog to include generic objects.
* [https://blueprints.launchpad.net/inkscape/+spec/inkscape-connectors Connector tool improvements] - Expose new libavoid functionality: orthogonal routing, connector ports, curved connectors. (Mentor: Michael Wybrow)
* [https://blueprints.launchpad.net/inkscape/+spec/fillet-tool Fillet/Chamfer tool]
* Move Mesh gradients to Inkscape name space with appropriate editing interface and export fallback. Note, Inkscape trunk has an experimental implementation based on the proposed mesh syntax for SVG 2.

Please do not feel limited to the above ideas - some of our best contributions have been unique ideas that students had in mind from other sources!

For more ideas, please see https://blueprints.launchpad.net/inkscape/

= Successful SOC Projects from Previous Years =
* 2005
** Connectors
** Inkboard
** [http://www.openclipart.org/ Open Clip Art Library (OCAL)] Interface
** DXF Import / Export
* [[Google Summer of Code 2006|2006]]
** Support for SVG Filters
** Filter Effects
** PDF export
** Inkboard Protocol Spec / Lib Conversion
* [[Google Summer of Code 2007|2007]]
** Text Style Improvements
** PDF import
** Live Path Effects
** 3D Box Tool
** UI for SVG Filter Effects
** Raster Functionality
** Importing from, and Exporting to, a remote ccHost instance
* [[Google Summer of Code 2008|2008]]
** SVG Fonts support
** 2Geom refactoring project - port most geometry code to 2Geom
** lib2geom: interactive applications showing off the power of lib2geom
** Tech drawing abilities
** A test suite
* 2009
** [[GSoC 2009 Node Tool Rewrite|Node tool rewrite]]
** D-Bus scripting API
** Connector tool improvements
** ICC/CMYK workflow
* 2010
** Cairo-based rendering
** C++ification of SP Layer
* 2011
** Rendering caching
** Javascript support improvements
** CSS support improvements
* 2012
** Usibility Improvements for Guides
** [[Tiling tool|On-canvas support for Tessellations]]
** Creating python bindings for lib2geom
* [[Google Summer of Code 2013|2013]]
** Recolor Tool
** Improved Units Support
** Electronics CAD Support
** New From Templates Dialog
** New Raster to Vector Algorithm
[[Category:Developer Documentation]]

Release notes/0.91

2012-09-20T20:48:24Z

Kris: /* New */

{{Other languages|en=Release_notes/0.49}}

==Inkscape 0.49==

'''(not released yet - [[AnnouncePlanning049]])'''

==Release highlights==

Released on '''d month year'''.

* Cairo rendering for display and PNG export
* OpenMP multithreading for all filters

==Rendering and performance==

Inkscape 0.49 includes a new renderer based on the Cairo library. This work was done during Google Summer of Code 2010 and 2011 projects.
* '''Improved performance.''' The new renderer is significantly faster on most drawings. Renderings of the most complex objects are automatically cached to improve responsiveness during editing.
* '''OpenMP multithreading for filters.''' Filters use all available processor cores for computation. This results in substantial speedups when editing drawings containing large filtered objects on multi-core systems.
* '''Substantial memory savings.''' Inkscape now uses less memory when opening complex drawings, in some cases using only 25% of the memory used by Inkscape 0.48. Larger files can now be opened.
* '''Responsiveness improvements.''' The rendering of the SVG drawing is now cached. This results in massive improvements in responsiveness of path highlights, object selection / deselection, and path editing in delayed update mode.
* '''Rendering bug fixes.''' Most of the rendering glitches in our bug tracker are no longer present in Inkscape 0.49. The following things now render correctly:
** Pattern fills (no more gaps between tiles, regardless of transformation)
** Stroke of transformed objects in patterns
** Patterns containing clipped objects
** Nested clipping paths
** Masked and clipped objects with large masks / clipping paths in Outline view
** Paths with wide strokes and long miters
** Fonts

==Tools==

=== Node tool ===
The Node tool's toolbar contains new buttons to insert new knots on the selected path segments' extreme values. Click the dropdown arrow next to the insert knots button.

=== Measurement tool ===
New.

=== Text tool ===
* Text size units is customizable (px,pt,pc,mm,cm,in,em), default is now pt
* Text toolbar shows full list of font style variants for that font
* Files with text in em units read correctly
* Font substitution warning dialog

=== Gradients ===
* Gradient toolbar enhanced to select and modify gradient stops, invert, repeat, and link gradients
* On-canvas gradient editing fixes - double clicking to create stops, correct focus on select
* Gradients sortable by color, name and usage in Fill/Stroke
* Gradients can be renamed in Fill/Stroke

== Dialogs, etc. ==

=== Align and distribute ===
* New "Exchange position of selected objects" feature. It adds three buttons in the Align and Distribute dialog (rearrange group) that exchange the positions of the selected objects: 1. according to the selection order, 2. according to the Z-order, and 3. clockwise.
* Keyboard shortcuts (Ctrl+Alt+Keypad numbers) for align operations

=== Find/Select ===

* It is now easier to select items which are not at the top of the Z-order: use Alt+mouse wheel scroll to cycle through all items that are stacked on top of each other at the location of the mouse pointer (use Shift+Alt+mouse wheel scroll to add to the existing selection). At present, groups are not honoured, i.e., only individual items within groups are considered.
* New Find/Replace dialog can operate on text or any attribute
* "Select Same" by Color/Style/Type added to main and context menu

=== Layers ===
* Drag and drop to reorder layers and create sublayers
* Show All / Hide All layers options in context menu

=== Transform ===
* Rotation of objects clockwise or counterclockwise

=== Markers ===
* Markers now take objects color

===Live Path Effects===

The object's Live Path Effects are now forked upon object duplication.

====PowerStroke====
Here a list of the current state. Note that this is very much work in progress and '''anything can change'''. I think this is the most efficient place of keeping track how the powerstroke LPE works.
* stroke knots are purple diamonds
* when first applied, 3 stroke knots are added one at start, one at end, one somewhere in the middle along the path.
* adding nodes: Ctrl+click purple knot
* deleting nodes: Ctrl+Alt+click purple knot
* "sort points" reorders the stroke knots according to where they lie along the path (where they are closest to the path), instead of keeping them in original order.
* start and end caps can be specified. The SVG cap types are available, as well as an extra type, "Zero width", that is identical to adding a width control knot at the start/end of the path with zero width.
* join type can be specified. In addition to the SVG join types, there are two new types:
** '''Extrapolated''': this extrapolates the contour of the stroked path to obtain a more natural looking miter join.
** '''Spiro''': rounds the join using a spiro curve (the '''rounded''' type rounds the curve using an elliptical arc).

[http://imgh.us/powerstroke-ell.png example screenshot]

====Clone original====
The Clone original LPE ignores the path data of the path it has been applied to; instead, it '''copies the original-d path data''', i.e. the path data before LPE calculation, from the path linked to by the Linked path parameter.

The Clone original LPE is made to be used in conjunction with powerstroke. Powerstroke creates a path with a variable stroke, but this path can then not be filled (because the fill is used as the stroke). To fill a powerstroked path, one must create a second path (dummy path), apply the Clone original LPE and link it to the powerstroked path. Because this second path clones the original path data before the Powerstroke LPE, it can be used to fill the powerstroked path.
To quickly create a dummy path and apply this effect, one can select the path to 'clone' and click the menu item '''Edit > Clone > Clone original path (LPE)'''.

Like for normal clones, pressing Shift+D, when the selected path has the Clone original LPE applied, selects the path referred to by the LPE.

Another very useful ability of the Clone original LPE is to create a clone with a different style than its referred path. To facilitate this, the LPE dialog will add the Clone original LPE when a clone is selected and the "+" button is pressed.

===Filters===
The new Custom predefined filters allow users to create predefined filters with custom parameters. See [[SpecCustomPredefinedFilters]].

==Import/Export==
* New Flash XML Graphics (FXG) export format.
* New Synfig Animation Studio (SIF) export format.
* XAML export improvements.
* Compressed SVG and media export extension improvements. New options: set an image directory in the zip file, and add a text file that lists the fonts used in the SVG document.
* New preference to allow users to always link, embed or ask when importing bitmaps.
* New preferences that allow the checking of SVG on input and/or export for invalid or not useful elements, attributes, and properties. Options control whether such items generate warnings (when Inkscape is run from the command line) or in removing such items.

===Gimp XCF improvements===
* The "Save Background" option allows users to choose if the page background is saved with each Gimp layer.
* The exported layers now use the label attribute or, if not set, the id attribute.
* New help tab.
* Some bugs and warnings fixed.

===PDF/EPS/PS + LaTeX===
* Added the possibility of scaling the image. The 'calc' package must be included in the preamble. Then the image can be scaled by defining '\svgscale' instead of '\svgwidth'.
* The font shape is now also exported. '\textit{}' for italic text, '\textbf{}' for bold text, and '\textsl{}' (slanted) for oblique text. It is important to note that '''Arial''' has an '''oblique''' font shape and not '''italic''', so the result in LaTeX will be '''slanted instead of italic'''. It is better to '''use another font''' in Inkscape when you want true italics.

==Extensions==
===New===
* The new guillotine extension is used for exporting png slices from a drawing. The slice rectangles are defined by adding horizontal and vertical guides within the canvas boundary, the canvas boundary serves as the outside of the sliced area.
* The new [http://en.wikipedia.org/wiki/G-code G-code] tools extension converts paths to G-code (using circular interpolation), makes offset paths and engraves sharp corners using cone cutters.
* New [http://en.wikipedia.org/wiki/QR_code QR code] generator.
* New isometric grid generator.
* New bitmap crop extension.
* New "Extract text" extension outputs the text elements of the document in a chosen order.
* New HSL adjust extension.

===Improvements===
* Number nodes. New parameters allowing users to choose the starting dot number and the numbering step between two nodes.
* Color Markers to Match Stroke extension improvements. The markers can now inherit the fill and stroke colors and alpha channels from the object, or be customized with color selectors in a separate tab.
* Optional sliders added on float and int extension parameters (full and minimal modes).
* Extension parameters values (''except attributes!'') can now be contextualized for translation (with msgctxt).

==User interface==

=== General ===
* Canvas background color can be set without exporting it (background transparency is only used for export but not the canvas).
* Guides visibility can be toggled by clicking the ruler

=== Menu/Access ===
* The interface elements are accessible through the keyboard with ALT+key in many more dialogs.
* "Text and Font", "Fill and Stroke", and "Check Spelling" dialogs are added to the text object context menu (right click).
* Menu items renamed - Edit->Preferences, Edit->Input Devices, File->Cleanup Document
* Checkboxes to indicated status of View->Grid/Guides/Snap/Color Management
* Group/Ungroup from the context menu

=== Dialogs ===
* Dialog status and position is remembered between sessions
* Most dialogs now dockable (including "Object properties", "Object attributes", "Text and Font", "Check spelling", "Export bitmap", "XML editor", "Find", and "Tiled clones")
* New preference to allow Windows users to choose between native and Gtk open/save dialog
* Preferences dialog cleanup
* Document Metadata dialog merged into Document Properties

===Simple calculations in spinboxes===
In most spinboxes (a spinbox is an entry field with up and down "spinbuttons" next to it) you can now write simple calculations. For example: "2 * 3", "50 + 100", or "((12 + 34) * (5 + 5) - 2) / 2".
Moreover, you can use units in entering values, like "2 + 2 cm". The result will be converted to the selected unit for the particular entry.

===Configurable Control Handles===

New preferences have been added to allow for the size of the on-canvas controls to be increased or decreased. The "Input Devices" section has been updated to control this.

==Translations==
* The ''Keyboard and mouse reference'' (inkscape-docs project) and color palettes' labels are now translatable.
* New UI translation in Latvian.
* New tutorial translations in Galician and Greek.
* New man pages in Chinese (zh_TW) Greek (el), Japanese (ja) and Slovak (sk), and updated French translation. ''[Galician (gl) and Polish (pl) in progress]''
* Man pages now use PO files for translation (inkscape-docs project).
* The tutorial generation system now fully supports RTL languages.

==SVG Support==

* The <tt>clip-rule</tt> property is now supported. No UI to set it exists at the moment, other than the XML editor.

== Snapping ==
* The snapping preferences and the snap toolbar have been reworked, both in the underlying code as well as in the GUI. This should make the snapping preferences easier to understand, easier to maintain, and make it easier to find and fix any remaining snapping bugs
* Inkscape now also snaps perpendicularly and tangentialy to paths, when creating paths in the pen tool, when dragging nodes, or when manipulating guides. Newly created guides (dragged off the ruler) will snap perpendicularly or tangentialy to any curve that is being snapped to. Two checkboxes have been added to the document properties dialog (on the snapping tab). Please note that snapping perpendicularly or tangetialy will not work in the selector tool when transforming an object or a selection of objects.
* Intersections of paths and guides can now be snapped to too
* Snapping has been implemented fully for transforming selections of multiple nodes in the node tool
* Snapping to text anchors and baselines has been implemented properly
* If one has chosen for only snapping the snap source closest to the mouse pointer, then the tab key can be used to cycle to the next closest snap source

==Notable bug fixes==
Notable bug fixes since last bug fix release ([[Release notes/0.48.3|0.48.3]]):
* Relative image paths are no longer stored as absolute (regression introduced with [[Release notes/0.47|0.47]]).
* Many rendering glitches were fixed.
* The rendering of the stroke on transformed objects now matches the SVG specification.
* Values entered in the numeric input boxes for the selector tool (X/Y/width/height) are much more accurately applied.

==Known issues==
* The Cairo library used in the new renderer does not implement downscaling, which causes large bitmaps to be pixelated on export. [https://bugs.launchpad.net/inkscape/+bug/804162]

==Previous releases==
* [[Release notes/0.48]] ([[Release notes/0.48.1 |0.48.1]], [[Release notes/0.48.2 | 0.48.2]], [[Release notes/0.48.3 | 0.48.3]])
* [[Release notes/0.47]]
* [[Release notes/0.46]]
* [[Release notes/0.45]]
* [[Release notes/0.44]]
* [[Release notes/0.43]]
* [[Release notes/0.42]]
* [[Release notes/0.41]]
* [[Release notes/0.40]]
* [[Release notes/0.39]]
* [[Release notes/0.38]]
* [[Release notes/0.37]]
* [[Release notes/0.36]]
* [[Release notes/0.35]]

[[Category:Marketing]]

Release notes/0.91

2012-09-09T16:00:29Z

Kris: typo

{{Other languages|en=Release_notes/0.49}}

==Inkscape 0.49==

'''(not released yet - [[AnnouncePlanning049]])'''

==Release highlights==

* Cairo rendering for display and PNG export
* OpenMP multithreading for all filters

==Rendering and performance==

Inkscape 0.49 includes a new renderer based on the Cairo library. This work was done during Google Summer of Code 2010 and 2011 projects.
* '''Improved performance.''' The new renderer is significantly faster on most drawings. Renderings of the most complex objects are automatically cached to improve responsiveness during editing.
* '''OpenMP multithreading for filters.''' Filters use all available processor cores for computation. This results in substantial speedups when editing drawings containing large filtered objects on multi-core systems.
* '''Substantial memory savings.''' Inkscape now uses less memory when opening complex drawings, in some cases using only 25% of the memory used by Inkscape 0.48. Larger files can now be opened.
* '''Responsiveness improvements.''' The rendering of the SVG drawing is now cached. This results in massive improvements in responsiveness of path highlights, object selection / deselection, and path editing in delayed update mode.
* '''Rendering bug fixes.''' Most of the rendering glitches in our bug tracker are no longer present in Inkscape 0.49. The following things now render correctly:
** Pattern fills (no more gaps between tiles, regardless of transformation)
** Stroke of transformed objects in patterns
** Patterns containing clipped objects
** Nested clipping paths
** Masked and clipped objects with large masks / clipping paths in Outline view
** Paths with wide strokes and long miters
** Fonts

==Tools==

=== Node tool ===
The Node tool's toolbar contains new buttons to insert new knots on the selected path segments' extreme values. Click the dropdown arrow next to the insert knots button.

=== Measurement tool ===
New.

=== Text tool ===
* Text size units is customizable (px,pt,pc,mm,cm,in,em), default is now pt
* Text toolbar shows full list of font style variants for that font
* Files with text in em units read correctly
* Font substitution warning dialog

=== Gradients ===
* Gradient toolbar enhanced to select and modify gradient stops, invert, repeat, and link gradients
* On-canvas gradient editing fixes - double clicking to create stops, correct focus on select
* Gradients sortable by color, name and usage in Fill/Stroke
* Gradients can be renamed in Fill/Stroke

== Dialogs, etc. ==

=== Align and distribute ===
* New "Exchange position of selected objects" feature. It adds three buttons in the Align and Distribute dialog (rearrange group) that exchange the positions of the selected objects: 1. according to the selection order, 2. according to the Z-order, and 3. clockwise.
* Keyboard shortcuts (Ctrl+Alt+Keypad numbers) for align operations

=== Find/Select ===

* It is now easier to select items which are not at the top of the Z-order: use Alt+mouse wheel scroll to cycle through all items that are stacked on top of each other at the location of the mouse pointer (use Shift+Alt+mouse wheel scroll to add to the existing selection). At present, groups are not honoured, i.e., only individual items within groups are considered.
* New Find/Replace dialog can operate on text or any attribute
* "Select Same" by Color/Style/Type added to main and context menu

=== Layers ===
* Drag and drop to reorder layers and create sublayers
* Show All / Hide All layers options in context menu

=== Transform ===
* Rotation of objects clockwise or counterclockwise

=== Markers ===
* Markers now take objects color

===Live Path Effects===

The object's Live Path Effects are now forked upon object duplication.

====PowerStroke====
Here a list of the current state. Note that this is very much work in progress and '''anything can change'''. I think this is the most efficient place of keeping track how the powerstroke LPE works.
* stroke knots are purple diamonds
* when first applied, 3 stroke knots are added one at start, one at end, one somewhere in the middle along the path.
* adding nodes: Ctrl+click purple knot
* deleting nodes: Ctrl+Alt+click purple knot
* "sort points" reorders the stroke knots according to where they lie along the path (where they are closest to the path), instead of keeping them in original order.
* start and end caps can be specified. The SVG cap types are available, as well as an extra type, "Zero width", that is identical to adding a width control knot at the start/end of the path with zero width.
* join type can be specified. In addition to the SVG join types, there are two new types:
** '''Extrapolated''': this extrapolates the contour of the stroked path to obtain a more natural looking miter join.
** '''Spiro''': rounds the join using a spiro curve (the '''rounded''' type rounds the curve using an elliptical arc).

[http://imgh.us/powerstroke-ell.png example screenshot]

====Clone original====
The Clone original LPE ignores the path data of the path it has been applied to; instead, it '''copies the original-d path data''', i.e. the path data before LPE calculation, from the path linked to by the Linked path parameter.

The Clone original LPE is made to be used in conjunction with powerstroke. Powerstroke creates a path with a variable stroke, but this path can then not be filled (because the fill is used as the stroke). To fill a powerstroked path, one must create a second path (dummy path), apply the Clone original LPE and link it to the powerstroked path. Because this second path clones the original path data before the Powerstroke LPE, it can be used to fill the powerstroked path.
To quickly create a dummy path and apply this effect, one can select the path to 'clone' and click the menu item '''Edit > Clone > Clone original path (LPE)'''.

Like for normal clones, pressing Shift+D, when the selected path has the Clone original LPE applied, selects the path referred to by the LPE.

Another very useful ability of the Clone original LPE is to create a clone with a different style than its referred path. To facilitate this, the LPE dialog will add the Clone original LPE when a clone is selected and the "+" button is pressed.

===Filters===
The new Custom predefined filters allow users to create predefined filters with custom parameters. See [[SpecCustomPredefinedFilters]].

==Import/Export==
* New Flash XML Graphics (FXG) export format.
* New Synfig Animation Studio (SIF) export format.
* XAML export improvements.
* Compressed SVG and media export extension improvements. New options: set an image directory in the zip file, and add a text file that lists the fonts used in the SVG document.
* New preference to allow users to always link, embed or ask when importing bitmaps.
* New preferences that allow the checking of SVG on input and/or export for invalid or not useful elements, attributes, and properties. Options control whether such items generate warnings (when Inkscape is run from the command line) or in removing such items.

===Gimp XCF improvements===
* The "Save Background" option allows users to choose if the page background is saved with each Gimp layer.
* The exported layers now use the label attribute or, if not set, the id attribute.
* New help tab.
* Some bugs and warnings fixed.

===PDF/EPS/PS + LaTeX===
* Added the possibility of scaling the image. The 'calc' package must be included in the preamble. Then the image can be scaled by defining '\svgscale' instead of '\svgwidth'.
* The font shape is now also exported. '\textit{}' for italic text, '\textbf{}' for bold text, and '\textsl{}' (slanted) for oblique text. It is important to note that '''Arial''' has an '''oblique''' font shape and not '''italic''', so the result in LaTeX will be '''slanted instead of italic'''. It is better to '''use another font''' in Inkscape when you want true italics.

==Extensions==
===New===
* The new guillotine extension is used for exporting png slices from a drawing. The slice rectangles are defined by adding horizontal and vertical guides within the canvas boundary, the canvas boundary serves as the outside of the sliced area.
* The new [http://en.wikipedia.org/wiki/G-code G-code] tools extension converts paths to G-code (using circular interpolation), makes offset paths and engraves sharp corners using cone cutters.
* New [http://en.wikipedia.org/wiki/QR_code QR code] generator
* New isometric grid generator
* New bitmap crop extension (Extensions>Bitmaps>Crop)
* New "Extract text" extension outputs the text elements of the document in a chosen order.

===Improvements===
* Number nodes. New parameters allowing users to choose the starting dot number and the numbering step between two nodes.
* Color Markers to Match Stroke extension improvements. The markers can now inherit the fill and stroke colors and alpha channels from the object, or be customized with color selectors in a separate tab.
* Optional sliders added on float and int extension parameters (full and minimal modes).
* Extension parameters values (''except attributes!'') can now be contextualized for translation (with msgctxt).

==User interface==

=== General ===
* Canvas background color can be set without exporting it (background transparency is only used for export but not the canvas).
* Guides visibility can be toggled by clicking the ruler

=== Menu/Access ===
* The interface elements are accessible through the keyboard with ALT+key in many more dialogs.
* "Text and Font", "Fill and Stroke", and "Check Spelling" dialogs are added to the text object context menu (right click).
* Menu items renamed - Edit->Preferences, Edit->Input Devices, File->Cleanup Document
* Checkboxes to indicated status of View->Grid/Guides/Snap/Color Management
* Group/Ungroup from the context menu

=== Dialogs ===
* Dialog status and position is remembered between sessions
* Most dialogs now dockable (including "Object properties", "Object attributes", "Text and Font", "Check spelling", "Export bitmap", "XML editor", "Find", and "Tiled clones")
* New preference to allow Windows users to choose between native and Gtk open/save dialog
* Preferences dialog cleanup
* Document Metadata dialog merged into Document Properties

===Simple calculations in spinboxes===
In most spinboxes (a spinbox is an entry field with up and down "spinbuttons" next to it) you can now write simple calculations. For example: "2 * 3", "50 + 100", or "((12 + 34) * (5 + 5) - 2) / 2".
Moreover, you can use units in entering values, like "2 + 2 cm". The result will be converted to the selected unit for the particular entry.

===Configurable Control Handles===

New preferences have been added to allow for the size of the on-canvas controls to be increased or decreased. The "Input Devices" section has been updated to control this.

==Translations==
* The ''Keyboard and mouse reference'' (inkscape-docs project) and color palettes' labels are now translatable.
* New UI translation in Latvian.
* New tutorial translations in Galician and Greek.
* New man pages in Chinese (zh_TW) Greek (el), Japanese (ja) and Slovak (sk), and updated French translation. ''[Galician (gl) and Polish (pl) in progress]''
* Man pages now use PO files for translation (inkscape-docs project).
* The tutorial generation system now fully supports RTL languages.

==SVG Support==

* The <tt>clip-rule</tt> property is now supported. No UI to set it exists at the moment, other than the XML editor.

== Snapping ==
* The snapping preferences and the snap toolbar have been reworked, both in the underlying code as well as in the GUI. This should make the snapping preferences easier to understand, easier to maintain, and make it easier to find and fix any remaining snapping bugs
* Inkscape now also snaps perpendicularly and tangentialy to paths, when creating paths in the pen tool, when dragging nodes, or when manipulating guides. Newly created guides (dragged off the ruler) will snap perpendicularly or tangentialy to any curve that is being snapped to. Two checkboxes have been added to the document properties dialog (on the snapping tab). Please note that snapping perpendicularly or tangetialy will not work in the selector tool when transforming an object or a selection of objects.
* Intersections of paths and guides can now be snapped to too
* Snapping has been implemented fully for transforming selections of multiple nodes in the node tool
* Snapping to text anchors and baselines has been implemented properly
* If one has chosen for only snapping the snap source closest to the mouse pointer, then the tab key can be used to cycle to the next closest snap source

==Notable bug fixes==
Notable bug fixes since last bug fix release ([[Release notes/0.48.3|0.48.3]]):
* Relative image paths are no longer stored as absolute (regression introduced with [[Release notes/0.47|0.47]]).
* Many rendering glitches were fixed.
* The rendering of the stroke on transformed objects now matches the SVG specification.
* Values entered in the numeric input boxes for the selector tool (X/Y/width/height) are much more accurately applied.

==Known issues==
* The Cairo library used in the new renderer does not implement downscaling, which causes large bitmaps to be pixelated on export. [https://bugs.launchpad.net/inkscape/+bug/804162]

==Previous releases==
* [[Release notes/0.48]] ([[Release notes/0.48.1 |0.48.1]], [[Release notes/0.48.2 | 0.48.2]], [[Release notes/0.48.3 | 0.48.3]])
* [[Release notes/0.47]]
* [[Release notes/0.46]]
* [[Release notes/0.45]]
* [[Release notes/0.44]]
* [[Release notes/0.43]]
* [[Release notes/0.42]]
* [[Release notes/0.41]]
* [[Release notes/0.40]]
* [[Release notes/0.39]]
* [[Release notes/0.38]]
* [[Release notes/0.37]]
* [[Release notes/0.36]]
* [[Release notes/0.35]]

[[Category:Marketing]]

Release notes/0.91

2012-08-27T20:50:50Z

Kris: /* Rendering and performance */ per bug 167076 [https://bugs.launchpad.net/inkscape/+bug/167076]

{{Other languages|en=Release_notes/0.49}}

==Inkscape 0.49==

'''(not released yet - [[AnnouncePlanning049]])'''

==Release highlights==

* Cairo rendering for display and PNG export
* OpenMP multithreading for all filters

==Rendering and performance==

Inkscape 0.49 includes a new renderer based on the Cairo library. This work was done during Google Summer of Code 2010 and 2011 projects.
* '''Improved performance.''' The new renderer is significantly faster on most drawings. Renderings of the most complex objects are automatically cached to improve responsiveness during editing.
* '''OpenMP multithreading for filters.''' Filters use all available processor cores for computation. This results in substantial speedups when editing drawings containing large filtered objects on multi-core systems.
* '''Substantial memory savings.''' Inkscape now uses less memory when opening complex drawings, in some cases using only 25% of the memory used by Inkscape 0.48. Larger files can now be opened.
* '''Responsiveness improvements.''' The rendering of the SVG drawing is now cached. This results in massive improvements in responsiveness of path highlights, object selection / deselection, and path editing in delayed update mode.
* '''Rendering bug fixes.''' Most of the rendering glitches in our bug tracker are no longer present in Inkscape 0.49. The following things now render correctly:
** Pattern fills (no more gaps between tiles, regardless of transformation)
** Stroke of transformed objects in patterns
** Patterns containing clipped objects
** Nested clipping paths
** Masked and clipped objects with large masks / clipping paths in Outline view
** Paths with wide strokes and long miters
** Fonts

==Tools==

=== Selector tool ===

It is now easier to select items which are not at the top of the Z-order: use Alt+mouse wheel scroll to cycle through all items that are stacked on top of each other at the location of the mouse pointer (use Shift+Alt+mouse wheel scroll to add to the existing selection). At present, groups are not honoured, i.e., only individual items within groups are considered.

=== Node tool ===
The Node tool's toolbar contains new buttons to insert new knots on the selected path segments' extreme values. Click the dropdown arrow next to the insert knots button.

=== Align and distribute dialog ===
New "Exchange position of selected objects" feature. It adds three buttons in the Align and Distribute dialog (rearrange group) that exchange the positions of the selected objects: 1. according to the selection order, 2. according to the Z-order, and 3. clockwise.

===Live Path Effects===

The object's Live Path Effects are now forked upon object duplication.

====PowerStroke====
Here a list of the current state. Note that this is very much work in progress and '''anything can change'''. I think this is the most efficient place of keeping track how the powerstroke LPE works.
* stroke knots are purple diamonds
* when first applied, 3 stroke knots are added one at start, one at end, one somewhere in the middle along the path.
* adding nodes: Ctrl+click purple knot
* deleting nodes: Ctrl+Alt+click purple knot
* "sort points" reorders the stroke knots according to where they lie along the path (where they are closest to the path), instead of keeping them in original order.
* start and end caps can be specified. The SVG cap types are available, as well as an extra type, "Zero width", that is identical to adding a width control knot at the start/end of the path with zero width.
* join type can be specified. In addition to the SVG join types, there are two new types:
** '''Extrapolated''': this extrapolates the contour of the stroked path to obtain a more natural looking miter join.
** '''Spiro''': rounds the join using a spiro curve (the '''rounded''' type rounds the curve using an elliptical arc).

[http://imgh.us/powerstroke-ell.png example screenshot]

====Clone original====
The Clone original LPE ignores the path data of the path it has been applied to; instead, it '''copies the original-d path data''', i.e. the path data before LPE calculation, from the path linked to by the Linked path parameter.

The Clone original LPE is made to be used in conjunction with powerstroke. Powerstroke creates a path with a variable stroke, but this path can then not be filled (because the fill is used as the stroke). To fill a powerstroked path, one must create a second path (dummy path), apply the Clone original LPE and link it to the powerstroked path. Because this second path clones the original path data before the Powerstroke LPE, it can be used to fill the powerstroked path.
To quickly create a dummy path and apply this effect, one can select the path to 'clone' and click the menu item '''Edit > Clone > Clone original path (LPE)'''.

Like for normal clones, pressing Shift+D, when the selected path has the Clone original LPE applied, selects the path referred to by the LPE.

Another very useful ability of the Clone original LPE is to create a clone with a different style than its referred path. To facilitate this, the LPE dialog will add the Clone original LPE when a clone is selected and the "+" button is pressed.

===Filters===
The new Custom predefined filters allow users to create predefined filters with custom parameters. See [[SpecCustomPredefinedFilters]].

==Import/Export==
* New Flash XML Graphics (FXG) export format.
* New Synfig Animation Studio (SIF) export format.
* XAML export improvements.
* Compressed SVG and media export extension improvements. New options: set an image directory in the zip file, and add a text file that lists the fonts used in the SVG document.
* New preference to allow users to always link, embed or ask when importing bitmaps.
* New preferences that allow the checking of SVG on input and/or export for invalid or not useful elements, attributes, and properties. Options control whether such items generate warnings (when Inkscape is run from the command line) or in removing such items.

===Gimp XCF improvements===
* The "Save Background" option allows users to choose if the page background is saved with each Gimp layer.
* The exported layers now use the label attribute or, if not set, the id attribute.
* New help tab.
* Some bugs and warnings fixed.

===PDF/EPS/PS + LaTeX===
* Added the possibility of scaling the image. The 'calc' package must be included in the preamble. Then the image can be scaled by defining '\svgscale' instead of '\svgwidth'.
* The font shape is now also exported. '\textit{}' for italic text, '\textbf{}' for bold text, and '\textsl{}' (slanted) for oblique text. It is important to note that '''Arial''' has an '''oblique''' font shape and not '''italic''', so the result in LaTeX will be '''slanted instead of italic'''. It is better to '''use another font''' in Inkscape when you want true italics.

==Extensions==
===New===
* The new guillotine extension is used for exporting png slices from a drawing. The slice rectangles are defined by adding horizontal and vertical guides within the canvas boundary, the canvas boundary serves as the outside of the sliced area.
* The new [http://en.wikipedia.org/wiki/G-code G-code] tools extension converts paths to G-code (using circular interpolation), makes offset paths and engraves sharp corners using cone cutters.
* New [http://en.wikipedia.org/wiki/QR_code QR code] generator
* New isometric grid generator
* New bitmap crop extension (Extensions>Bitmaps>Crop)
* New "Extract text" extension outputs the text elements of the document in a chosen order.

===Improvements===
* Number nodes. New parameters allowing users to choose the starting dot number and the numbering step between two nodes.
* Color Markers to Match Stroke extension improvements. The markers can now inherit the fill and stroke colors and alpha channels from the object, or be customized with color selectors in a separate tab.
* Optional sliders added on float and int extension parameters (full and minimal modes).
* Extension parameters values (''except attributes!'') can now be contextualized for translation (with msgctxt).

==User interface==
*The interface elements are accessible through the keyboard with ALT+key in many more dialogs.
*Ability to set the canvas background color without exporting it (background transparency is only used for export but not the canvas).
*Dialogs:
**The following dialogs are now also dockable: "Object properties", "Object attributes", "Text and Font", "Check spelling", "Export bitmap", "XML editor", "Find", and "Tiled clones".
**New preference to allow Windows users to choose between native and Gtk open/save dialog.
**Preferences dialog cleanup.
**Find dialog extended to search for and replace properties, fonts, styles, etc.
*Menus: "Text and Font", "Fill and Stroke", and "Check Spelling" dialogs are added to the text object context menu (right click).

===Simple calculations in spinboxes===
In most spinboxes (a spinbox is an entry field with up and down "spinbuttons" next to it) you can now write simple calculations. For example: "2 * 3", "50 + 100", or "((12 + 34) * (5 + 5) - 2) / 2".
Moreover, you can use units in entering values, like "2 + 2 cm". The result will be converted to the selected unit for the particular entry.

===Configurable Control Handles===

New preferences have been added to allow for the size of the on-canvas controls to be increased or decreased. The "Input Devices" section has been updated to control this.

==Translations==
* The ''Keyboard and mouse reference'' (inkscape-docs project) and color palettes' labels are now translatable.
* New UI translation in Latvian.
* New tutorial translations in Galician and Greek.
* New man pages in Chinese (zh_TW) Greek (el), Japanese (ja) and Slovak (sk), and updated French translation. ''[Galician (gl) and Polish (pl) in progress]''
* Man pages now use PO files for translation (inkscape-docs project).
* The tutorial generation system now fully supports RTL languages.

==SVG Support==

* The <tt>clip-rule</tt> property is now supported. No UI to set it exists at the moment, other than the XML editor.

== Snapping ==
* The snapping preferences and the snap toolbar have been reworked, both in the underlying code as well as in the GUI. This should make the snapping preferences easier to understand, easier to maintain, and make it easier to find and fix any remaining snapping bugs
* Inkscape now also snaps perpendicularly and tangentialy to paths, when creating paths in the pen tool, when dragging nodes, or when manipulating guides. Newly created guides (dragged off the ruler) will snap perpendicularly or tangentialy to any curve that is being snapped to. Two checkboxes have been added to the document properties dialog (on the snapping tab). Please note that snapping perpendicularly or tangetialy will not work in the selector tool when transforming an object or a selection of objects.
* Intersections of paths and guides can now be snapped to too
* Snapping has been implemented fully for transforming selections of multiple nodes in the node tool
* Snapping to text anchors and baselines has been implemented properly
* If one has chosen for only snapping the snap source closest to the mouse pointer, then the tab key can be used to cycle to the next closest snap source

==Notable bug fixes==
Notable bug fixes since last bug fix release ([[Release notes/0.48.3|0.48.3]]):
* Relative image paths are no longer stored as absolute (regression introduced with [[Release notes/0.47|0.47]]).
* Many rendering glitches were fixed.
* The rendering of the stroke on transformed objects now matches the SVG specification.
* Values entered in the numeric input boxes for the selector tool (X/Y/width/height) are much more accurately applied.

==Known issues==
* The Cairo library used in the new renderer does not implement downscaling, which causes large bitmaps to be pixelated on export. [https://bugs.launchpad.net/inkscape/+bug/804162]

==Previous releases==
* [[Release notes/0.48]] ([[Release notes/0.48.1 |0.48.1]], [[Release notes/0.48.2 | 0.48.2]], [[Release notes/0.48.3 | 0.48.3]])
* [[Release notes/0.47]]
* [[Release notes/0.46]]
* [[Release notes/0.45]]
* [[Release notes/0.44]]
* [[Release notes/0.43]]
* [[Release notes/0.42]]
* [[Release notes/0.41]]
* [[Release notes/0.40]]
* [[Release notes/0.39]]
* [[Release notes/0.38]]
* [[Release notes/0.37]]
* [[Release notes/0.36]]
* [[Release notes/0.35]]

[[Category:Marketing]]

JonPhillips

2012-08-18T08:10:04Z

Kris: linkfix

[http://www.rejon.org/ rejon.org]

Joined the project right after the initial announcement. His main interest is in promoting Inkscape and linking the project with larger goals through the cleaning up usability, bugs and the implementation of new ideas (mainly the extension system). He is taking a lead on the new clipart project with Ted, Bryce and some sodipodi developers. Tasks: planner, writer, administrative, website, help/tutorials, code cleanup, tester, some work on the codebase.

== TODO ==

=== Immediately ===

* icons?
* finish elements...
* fix and update xpms for cursors

=== Add system for modifying the cursor icon when a key is depressed. ===

=== Add History item to Help Menu ===

=== Clear out All Uses of XPMs ===

I'm trying to clear out all uses of XPMs and replacing them with SVGs.

=== Article (for 0.38) ===

I'm thinking that this could be in the form of questions asked of our community and developed answers on the wiki.

See Vector Aesthetics

=== [[PublicityInfo]] ===

Need to develop this section more.

=== External Preview ===

From an email from BULIA:
>If this functionality is in fact "Preview in Browser" then it is certainly>confusing which makes it useless in its current state but I think with>minor changes it could be made genuinely useful.Good idea to make this command an "External preview". Just store a command line with options in prefs, and when a preview is requested, save the current file and run the command on it.This seems to be similar to the task of running an external browser for help files - therefore, Jon, what would you say if I ask you to add this to your TODO?Right now, however, the "preview" is done by Inkscape itself, and is therefore useless. So I'm removing this command for now, until we have an external preview functionality.

=== Help System Overview ===

Bulia has intermediately developed the keyboard shorcuts SVG in the Help Menu. NJH and BULIA created a tutorial there as well. Eventually, we will need to integrate YELP[[/SCROLLKEEPER]] into the whole scheme.

=== Eyedropper Tool Enhancement ===

Add button to copy hex to clipboard in the secondary toolbar

=== Open URL ===

Already Inkscape can open URLs from commandline, one should be able to do this in the app.

=== Develop BIG PICTURE Section more ===

This includes talking with MRDOCS about the OPTO group and developing relationships with other projects. Also, the openswatch project should be pushed further still. I should really look more into SCRIBUS' development community and the docs that MRDOCS has written.

=== Tutorials and Practical Uses ===

(18:42:27) rejon: http://1acre.ucsd.edu/
(18:42:50) rejon: used inkscape to plan out colors (although all done in css)
(18:44:33) rejon: that would be a good section in our site: practical uses (could put web design testimonial)
(18:44:39) rejon: maybe a tutorial

=== Sort out and Clear out [[FeatureNotePad]] ===

=== Review and Sort [[NewFeatureProposals]] ===

=== Sort out and Clear out [[FeatureNotePad]] ===

=== [[Inkscape coverage|InkscapePresentations]] ===

[[Category:Developer]]

User talk:Kris

2012-08-09T19:57:10Z

Kris: Replaced content with "{| align="center" cellpadding="10" style="border:4px DeepSkyBlue solid;background-color: Aquamarine; width:300px;border-radius: 25px;" |- | |- | align="center" | It..."

User:Kris

2012-08-09T19:49:19Z

Kris: Created page with "I'm an occasional Inkscape user using Inkscape to adapt graphs and to create simple self explaining drawings to illustrate things such as experimental setups. For Inkscape de..."

I'm an occasional Inkscape user using Inkscape to adapt graphs and to create simple self explaining drawings to illustrate things such as experimental setups.

For Inkscape development involved with:
* UI and tutorial translation in Dutch
* cppcheck code checking
* UI consistency
* Bug management and from time to time fixing bugs

[[Category:Developer]]

MediaWiki:Spam-blacklist

2012-06-05T19:11:53Z

Kris:

# External URLs matching this list will be blocked when added to a page.
# This list affects only this wiki; refer also to the global blacklist.
# For documentation see http://www.mediawiki.org/wiki/Extension:SpamBlacklist
# <pre>
#
# Syntax is as follows:
# * Everything from a "#" character to the end of the line is a comment
# * Every non-blank line is a regex fragment which will only match hosts inside URLs

#</pre> 

\b24houressays\.com\b
\bcomeawn\.com\b
\bcross\-walks\.org\b
\ben\.astratranslations\.co\.uk\b
\bespinheira\.org\b
\bfindthisall\.com\b
\bgadgets\-rule\.com\b
\bgangstaa\.joinvps\.com\b
\bhaljava\.planet\.ee\b
\binforaise\.net\b
\bnewsouthblogs\.org\b
\bpara\.llel\.us\b
\bprisonersreachingout\.com\b
\bqlddm\.org\b
\bstudygroup\.feedtheyogi\.com\b
\bto27\.com\b
\bwiki\.galaxianfederation\.com\b
\bwiki\.php\-fusion.pl\b
\bwww\.accounting\-wiki\.com\b
\bwww\.chadharvey\.com\b
\bwww\.mycirclesonline\.com\b
\bwww\.poor2riches\.com\b
\bwww\.projectdelta\.me\b
\bwww\.scuoladuepuntozero\.tv\.it\b
coupon
dating\.
ebuysilver\.com\b
promocode
guildwars\.com\b
\btraccfilms\.co\.uk\b
\bwww\.sacslvuitton\.com\b
\bwww\.frlouisvmagasin\.com\b
\bwww\.monster\-beatsbydrestudio\.com\b
\bwww\.ganardinero\-facil\.info\b
\bwww\.noticiasinsolitas\.info\b
\bwww\.postres\-faciles\.info\b
\bwww\.tiradadeltarotgratis\.info\b
\bwww\.blanqueamientodentales\.info\b
\bwww.ganadineronavegando.com\b
\bwww\.ganardinero\-facil\.info\b
casino\.com\b
\bwww\.sizzlinghotspielen\.net\b
\bwww\.onlinecasinonederland\.net\b
\bposnation\.com\b
\bwww\.escortsnewcastle\.co\.uk\b
\bwww\.hostinginfinite\.com\b
\bwww\.freeitunescardcodes\.info\b
\bwww\.ucakbiletiplus\.com\b
\bwww\.belfitigisatisi\.com\b
\bwww\.antakyabiberizayiflama\.org\b
\bwww\.pozitifcallcenter\.com\b
\bwww\.africanmangotr\.net\b
\bwww\.Samandagbiberisatisi\.com\b
\bwww\.gobekeritmebandi\.com\b
\bwww\.ayakkabiplus\.com\b
\bwww\.acaizayiflama\.net\b
\bwww\.minoxidilsampuan\.com\b
\bwww\.kiloaldiricigainmax\.com\b
\bwww\.boyuzatici\.com\b
\bwww\.kiloaldirici\.com\.tr\b
\bwww\.eginayachts\.com\b
\bwww\.firmakurdu\.com\b
\bwww\.kiralikvosvos\.com\b
\bwww\.ownhost\.net\b
\bwww\.444vps\.com\.tr\b
\bwww\.asyadokum\.com\.tr\b
\bwww\.sinemaizleyelim\.com\b
\bwww\.zayiflamaonline\.com\b
\bwww\.zayiflamakemeri\.com\b
\bwww\.saunaesofman\.web\.tr\b
\bwww\.paydayloanscity\.co\.uk\b
\bwww\.santedentaire\.net\b
\bmetalpresswork\.com\b

Islint-implementation

2012-06-05T19:08:13Z

Kris: cat

{{DevDiscussion}}
linked from [http://wiki.inkscape.org/wiki/index.php/Islint islint]

== Wiki Notes Annotated ==

I don't agree with some of the assumptions in these notes. I suspect that that's because I have different use cases for SVG than the person who wrote them. Sometimes it's hard to be objective in these matters. It would be good to have developers from different disciplines take a look at this list in order to get a useful generic set of requirements.

'''''In italics is a copy of the '''Cleaning Operations''' list from the [http://wiki.inkscape.org/wiki/index.php/Save_Cleaned_SVG Save_Cleaned_SVG] page'''''

Notes are formatted like this. ''Status, difficulty, priority like this''.

=== Specify a limit to the precision of all positional elements. ===
''DONE v0.8''. Trimming precision was my first priority. precision can be set to -1 (off) or 0..9. islint gives an extra decimal to transformation floats, so if you set prec=1, a matrix will have values to two decimal places. This is to preserve a little sanity at a low cost should there be nested transforms.
=== Clean up XML Elements ===
* '''''Collapse multiple redundant groups'''''
''Not done, easy, low priority''.
* '''''Remove empty tags, such as defs or metadata.'''''
''Not done, easy, low priority''.
* '''''Remove id tags for elements not referenced'''''
''Not done, easy, low priority''. I like to have an id on everything. I usually want something more useful than path1234, but that requires either human intervention, or a targeted generator. I can add it as an option.
=== Clean up Definitions ===
''Not done, moderate, low priority''. Generally I think this section needs a bit of work. I don't use InkScape for gradients much, but I could. InkScape creates a lot of gradients and creates and references linear gradients when it needs a radial gradient. It is possible to do a lot of cleanup here.
* '''''Remove unused definitions'''''
* '''''Remove duplicate gradient stops'''''
* '''''Collapse duplicate gradient definitions'''''
* '''''Remove gradients that are only referenced by one other gradient'''''
=== Clean up CSS ===
islint implements inline CSS style sheets by parsing the style attributes (style=) into a table removing defaults, merging them, substituting class attributes, and finally, creating an inline style sheet. ''At the moment it does nothing with standalone XML attributes'' (stroke=, fill=) Currently I do not READ CSS tables or files for updating. This is a '''''HIGH PRIORITY''''' I like to use external CSS, it makes projects easy to adapt. ''If I can read in inline style sheets or external css files, I can carry along a naming convention in the style sheet.'' I need to know more about the InkScape plugin interface before I can implement separate CSS files. Perhaps a two stage operation? 1. profile the document, 2, save and reference the style sheet?
: So, I have implemented one method of styling, possibly the most difficult one. Certainly the one I find most useful. This is done in the first pass of the document, gathering up all the styling. Writing the styling is done dead last, after all other manipulations have completed.
: It would be easy to convert to all style attributes, or standalone XML attributes instead of an inline style sheet.

* '''''Remove Default values, i.e. opacity: 1;'''''
''DONE v0.8''.
* '''''Remove Not applicable values, i.e. opacity: 0; fill-color: #00000;'''''
Not sure what is meant here.
* '''''Convert RGB colours from RGB(r,g,b) to #RRGGBB format'''''
''Not done, easy, med priority''.

''DONE v0.8''. I convert everything to rgb(...) because I like it for programmability and the CSS DOM seems to like them.
* '''''Convert RGB colours from #RRGGBB to #RGB if possible'''''
''Not done, easy, med priority''.

=== Clean up paths ===
''DONE v0.8'' (my way) What isn't mentioned here, and is fully implemented in islint, is recovering, circles, ellipses, lines, polylines and polygons. islint parses 'd' attributes into path segments, analyzes them, converts if possible, else puts them back together being very stingy with white space. A large effort was put forth here, so the code is in good shape for further reduction operations on paths. The sodipodi namespace data makes it possible to recover circles and arcs.
* '''''Detect vertical/horizontal lines and replace.'''''
''Not done, easy, high priority''.
* '''''Eliminate empty path segments'''''
''Not done, easy, high priority''. I didn't know there were any.
* '''''Eliminate last segment in a polygon'''''
''Not done, easy, high priority''.
* '''''Collapse straight curves.'''''
''Not done, ???, med priority''.
* '''''Convert absolute path segments to relative ones.'''''
''Not done, easy, high priority''.
=== Process Transformations ===
Do not understand these first two points, process Beziers how? Collapse transforms how?
* '''''Process quadratic Bezier curves'''''
* '''''Collapse all group based transformations'''''
* '''''Convert known properties to element attributes'''''
If this means convert the css properties in style attributes to standalone XML attributes (fill=, stroke=), see ''[http://wiki.inkscape.org/wiki/index.php/Islint#Clean_up_CSS Clean up CSS]'' above.
* '''''css to element attributes'''''
see ''[http://wiki.inkscape.org/wiki/index.php/Islint#Clean_up_CSS Clean up CSS]'' above.

=== Output Standard SVG ===
''DONE v0.8''. islint removes all namespaces it has not been told to keep. It is possible to tell it to preserve foreign namespaces by adding them through an option. Currently only possible via the command line interface.
* '''''Remove inkscape namespace'''''
* '''''Remove sodipodi namespace'''''
* '''''Remove adobe namespace'''''
* '''''Use viewPort instead of document width/height'''''
''Not done, difficult, medium priority''. There many many ways to specify the document extent in SVG. Some analysis needs to be done before attempting to automate this.

== Implementation Notes ==

I'll keep track of what I do, am doing here. v0.8 is the version as of this writing.

=== CSS Styling v0.8 ===

Currently islint either creates inline CSS style sheets, or leaves styling alone. Only style attributes are processed.
* TODO:
** parse XML style attributes (stroke=, fill=)
** implement options for document styling:
*** CSS (inline or external)
*** style attributes
*** standalone XML attributes

--[[User:Tsingi|Tsingi]] 12:29, 24 September 2009 (UTC)

MediaWiki:Spam-blacklist

2012-06-04T13:19:15Z

Kris:

MediaWiki:Spam-blacklist

2012-06-04T13:11:16Z

Kris:

MediaWiki:Spam-blacklist

2012-06-04T13:08:40Z

Kris:

Release notes/0.91

2012-05-07T16:04:10Z

Kris: /* User interface */

==Inkscape 0.49==

'''(not released yet - [[AnnouncePlanning049]])'''

==Release highlights==

* Cairo rendering for display and PNG export
* OpenMP multithreading for all filters

==Rendering and performance==

Inkscape 0.49 includes a new renderer based on the Cairo library. This work was done during Google Summer of Code 2010 and 2011 projects.
* '''Improved performance.''' The new renderer is significantly faster on most drawings. Renderings of the most complex objects are automatically cached to improve responsiveness during editing.
* '''OpenMP multithreading for filters.''' Filters use all available processor cores for computation. This results in substantial speedups when editing drawings containing large filtered objects on multi-core systems.
* '''Substantial memory savings.''' Inkscape now uses less memory when opening complex drawings, in some cases using only 25% of the memory used by Inkscape 0.48. Larger files can now be opened.
* '''Responsiveness improvements.''' The rendering of the SVG drawing is now cached. This results in massive improvements in responsiveness of path highlights, object selection / deselection, and path editing in delayed update mode.
* '''Rendering bug fixes.''' Most of the rendering glitches in our bug tracker are no longer present in Inkscape 0.49. The following things now render correctly:
** Pattern fills (no more gaps between tiles, regardless of transformation)
** Stroke of transformed objects in patterns
** Patterns containing clipped objects
** Nested clipping paths
** Masked and clipped objects with large masks / clipping paths in Outline view
** Paths with wide strokes and long miters

==Tools==

=== Selector tool ===

It is now easier to select items which are not at the top of the Z-order: use Alt+mouse wheel scroll to cycle through all items that are stacked on top of each other at the location of the mouse pointer (use Shift+Alt+mouse wheel scroll to add to the existing selection). At present, groups are not honoured, i.e., only individual items within groups are considered.

=== Node tool ===
The Node tool's toolbar contains new buttons to insert new knots on the selected path segments' extreme values. Click the dropdown arrow next to the insert knots button.

=== Align and distribute dialog ===
New "Exchange position of selected objects" feature. It adds three buttons in the Align and Distribute dialog (rearrange group) that exchange the positions of the selected objects: 1. according to the selection order, 2. according to the Z-order, and 3. clockwise.

===Live Path Effects===

The object's Live Path Effects are now forked upon object duplication.

====PowerStroke====
Here a list of the current state. Note that this is very much work in progress and '''anything can change'''. I think this is the most efficient place of keeping track how the powerstroke LPE works.
* stroke knots are purple diamonds
* when first applied, 3 stroke knots are added one at start, one at end, one somewhere in the middle along the path.
* adding nodes: Ctrl+click purple knot
* deleting nodes: Ctrl+Alt+click purple knot
* "sort points" reorders the stroke knots according to where they lie along the path (where they are closest to the path), instead of keeping them in original order.
* start and end caps can be specified. The SVG cap types are available, as well as an extra type, "Zero width", that is identical to adding a width control knot at the start/end of the path with zero width.
* join type can be specified. In addition to the SVG join types, there are two new types:
** '''Extrapolated''': this extrapolates the contour of the stroked path to obtain a more natural looking miter join.
** '''Spiro''': rounds the join using a spiro curve (the '''rounded''' type rounds the curve using an elliptical arc).

[http://imgh.us/powerstroke-ell.png example screenshot]

====Clone original====
The Clone original LPE ignores the path data of the path it has been applied to; instead, it '''copies the original-d path data''', i.e. the path data before LPE calculation, from the path linked to by the Linked path parameter.

The Clone original LPE is made to be used in conjunction with powerstroke. Powerstroke creates a path with a variable stroke, but this path can then not be filled (because the fill is used as the stroke). To fill a powerstroked path, one must create a second path (dummy path), apply the Clone original LPE and link it to the powerstroked path. Because this second path clones the original path data before the Powerstroke LPE, it can be used to fill the powerstroked path.
To quickly create a dummy path and apply this effect, one can select the path to 'clone' and click the menu item '''Edit > Clone > Clone original path (LPE)'''.

Like for normal clones, pressing Shift+D, when the selected path has the Clone original LPE applied, selects the path referred to by the LPE.

Another very useful ability of the Clone original LPE is to create a clone with a different style than its referred path. To facilitate this, the LPE dialog will add the Clone original LPE when a clone is selected and the "+" button is pressed.

===Filters===
The new Custom predefined filters allow users to create predefined filters with custom parameters. See [[SpecCustomPredefinedFilters]].

==Import/Export==
* New Flash XML Graphics (FXG) export format.
* New Synfig Animation Studio (SIF) export format.
* XAML export improvements.
* Compressed SVG and media export extension improvements. New options: set an image directory in the zip file, and add a text file that lists the fonts used in the SVG document.
* New preference to allow users to always link, embed or ask when importing bitmaps.

===Gimp XCF improvements===
* The "Save Background" option allows users to choose if the page background is saved with each Gimp layer.
* The exported layers now use the label attribute or, if not set, the id attribute.
* New help tab.
* Some bugs and warnings fixed.

===PDF/EPS/PS + LaTeX===
* Added the possibility of scaling the image. The 'calc' package must be included in the preamble. Then the image can be scaled by defining '\svgscale' instead of '\svgwidth'.
* The font shape is now also exported. '\textit{}' for italic text, '\textbf{}' for bold text, and '\textsl{}' (slanted) for oblique text. It is important to note that '''Arial''' has an '''oblique''' font shape and not '''italic''', so the result in LaTeX will be '''slanted instead of italic'''. It is better to '''use another font''' in Inkscape when you want true italics.

==Extensions==
===New===
* The new guillotine extension is used for exporting png slices from a drawing. The slice rectangles are defined by adding horizontal and vertical guides within the canvas boundary, the canvas boundary serves as the outside of the sliced area.
* The new [http://en.wikipedia.org/wiki/G-code G-code] tools extension converts paths to G-code (using circular interpolation), makes offset paths and engraves sharp corners using cone cutters.
* New [http://en.wikipedia.org/wiki/QR_code QR code] generator
* New isometric grid generator
* New bitmap crop extension (Extensions>Bitmaps>Crop)
* New "Extract text" extension outputs the text elements of the document in a chosen order.

===Improvements===
* Number nodes. New parameters allowing users to choose the starting dot number and the numbering step between two nodes.
* Color Markers to Match Stroke extension improvements. The markers can now inherit the fill and stroke colors and alpha channels from the object, or be customized with color selectors in a separate tab.
* Optional sliders added on float and int extension parameters (full and minimal modes).
* Extension parameters values (''except attributes!'') can now be contextualized for translation (with msgctxt).

==User interface==
*The interface elements are accessible through the keyboard with ALT+key in many more dialogs.
*Ability to set the canvas background color without exporting it (background transparency is only used for export but not the canvas).
*Dialogs:
**The following dialogs are now also dockable: "Object properties", "Object attributes", "Text and Font", "Check spelling", "Export bitmap", "XML editor", "Find", and "Tiled clones".
**New preference to allow Windows users to choose between native and Gtk open/save dialog.
**Preferences dialog cleanup.
**Find dialog extended to search for and replace properties, fonts, styles, etc.
*Menus: "Text and Font", "Fill and Stroke", and "Check Spelling" dialogs are added to the text object context menu (right click).

===Simple calculations in spinboxes===
In most spinboxes (a spinbox is an entry field with up and down "spinbuttons" next to it) you can now write simple calculations. For example: "2 * 3", "50 + 100", or "((12 + 34) * (5 + 5) - 2) / 2".
Moreover, you can use units in entering values, like "2 + 2 cm". The result will be converted to the selected unit for the particular entry.

===Configurable Control Handles===

New preferences have been added to allow for the size of the on-canvas controls to be increased or decreased. The "Input Devices" section has been updated to control this.

==Translations==
* The ''Keyboard and mouse reference'' (inkscape-docs project) and color palettes' labels are now translatable.
* New UI translation in Latvian.
* New tutorial translations in Galician and Greek.
* New man pages in Chinese (zh_TW) Greek (el), Japanese (ja) and Slovak (sk), and updated French translation. ''[Galician (gl) and Polish (pl) in progress]''
* Man pages now use PO files for translation (inkscape-docs project).
* The tutorial generation system now fully supports RTL languages.

==SVG Support==

* The <tt>clip-rule</tt> property is now supported. No UI to set it exists at the moment, other than the XML editor.

== Snapping ==
* The snapping preferences and the snap toolbar have been reworked, both in the underlying code as well as in the GUI. This should make the snapping preferences easier to understand, easier to maintain, and make it easier to find and fix any remaining snapping bugs
* Inkscape now also snaps perpendicularly and tangentialy to paths, when creating paths in the pen tool, when dragging nodes, or when manipulating guides. Newly created guides (dragged off the ruler) will snap perpendicularly or tangentialy to any curve that is being snapped to. Two checkboxes have been added to the document properties dialog (on the snapping tab). Please note that snapping perpendicularly or tangetialy will not work in the selector tool when transforming an object or a selection of objects.
* Intersections of paths and guides can now be snapped to too
* Snapping has been implemented fully for transforming selections of multiple nodes in the node tool
* Snapping to text anchors and baselines has been implemented properly
* If one has chosen for only snapping the snap source closest to the mouse pointer, then the tab key can be used to cycle to the next closest snap source

==Notable bug fixes==
Notable bug fixes since last bug fix release ([[Release notes/0.48.3|0.48.3]]):
* Relative image paths are no longer stored as absolute (regression introduced with [[Release notes/0.47|0.47]]).
* Many rendering glitches were fixed.
* The rendering of the stroke on transformed objects now matches the SVG specification.
* Values entered in the numeric input boxes for the selector tool (X/Y/width/height) are much more accurately applied.

==Known issues==
* The Cairo library used in the new renderer does not implement downscaling, which causes large bitmaps to be pixelated on export. [https://bugs.launchpad.net/inkscape/+bug/804162]

==Previous releases==
* [[Release notes/0.48]] ([[Release notes/0.48.1 |0.48.1]], [[Release notes/0.48.2 | 0.48.2]], [[Release notes/0.48.3 | 0.48.3]])
* [[Release notes/0.47]]
* [[Release notes/0.46]]
* [[Release notes/0.45]]
* [[Release notes/0.44]]
* [[Release notes/0.43]]
* [[Release notes/0.42]]
* [[Release notes/0.41]]
* [[Release notes/0.40]]
* [[Release notes/0.39]]
* [[Release notes/0.38]]
* [[Release notes/0.37]]
* [[Release notes/0.36]]
* [[Release notes/0.35]]

[[Category:Marketing]]

User talk:Kris

2012-04-23T14:14:46Z

Kris: /* Suggestion to replace CAPTCHA module */

== Template to add a Category? ==
I'm still trying to master MediaWiki syntax, so when I see someone doing something different, I try to understand what they have done and, perhaps, why they are doing it.

You seem to have added Template:DevDiscussion merely to add Category:Developer Discussion to a wiki article. I don't understand the improvement a Template provides over merely directly placing the Category reference in the article. Can you help me understand, please?
[[User:NeoPhyte Rep|NeoPhyte Rep]] 15:11, 6 January 2012 (UTC)
:Hi Neophyte, there is actually not really a difference for average usage on the wiki and hence, should generally not be used for simple categorisation. There is only one advantage, namely when you want to "rename" a category. Renaming a category is not possible, it consist of duplicating the category page and moving the content in the new category before deleting the original category name. So if you have used a template, you can simply modify the template. I only did this for now as the wiki now needs some content update. I see different many different styles in naming pages, namely CamelCase, Each Word Capitalized, etc. So in case we want to uniformize, this first step might save some work later on. Regards, [[User:Kris|Kris]] 17:37, 6 January 2012 (UTC) PS: maybe on the developers discussion pages, it might be interesting to have an info box at the top saying this (and that is were a template would be really handy)
::Interesting technique. Thanks for the explanation. [[User:NeoPhyte Rep|NeoPhyte Rep]] 18:05, 6 January 2012 (UTC)

== Wiki maintenance ==
Kris, I've noticed that you're spending an inordinate amount of effort blocking accounts of spammers and deleting their handiwork. Most of them are, no doubt, new accounts, and it's a good bet that many of them are perpetrated by the same bad actors who are logging in with temporary IP addresses that change every time they reboot their ADSL modem. I recently encountered an interesting technique to cut down on this type of activity at the OpenOffice.org wiki. (Sorry, you'll need to find the URL yourself, because a half-baked script on this wiki puked when I tried to save this message with a link to the relevant page.) They've implemented a "cooling-off period" for new accounts and have completely blocked editing by anonymous users. Anyone can create an account, but one must wait '''four days''' before making the first edit. If someone has a legitimate reason to be here, they'll make a note of it and come back when the waiting time has expired, but it may be a significant deterrent to hit-and-run spammers. [[User:User8192|User8192]] 07:36, 2 December 2011 (UTC)
:Hi User8192, We are aware of this extension which allows to allows to hinder inappropriate behaviour at various levels. It should be enabled now or very soon (I do not know its status though). Regards, [[User:Kris|Kris]] 08:20, 3 December 2011 (UTC)

== New spam ==
I've been editing the wiki in the last couple of days and noticed new user accounts that have been used for the sole purpose of spamming. The accounts and their IP addresses should be blocked and all pages created by them should be deleted. Since I don't have administrator privileges on this wiki, I replaced the content in pages that I found with the word "SPAM" and put "SPAM" in the edit summary. [[User:User8192|User8192]] 19:24, 13 December 2011 (UTC)
*[[Special:Contributions/Gitukaff]]
*[[Special:Contributions/Colecris]]
*[[Special:Contributions/Restinve]]
*[[Special:Contributions/Betgclub9]]
*[[Special:Contributions/Fesulri]]
*[[Special:Contributions/Fidedian]]

*[[Special:Contributions/Annavict]] hasn't done anything yet, but it looks suspicious, as it was created at the same time as Colecris and Restinve.
*[[Special:Contributions/Holidaygclub]] also looks suspicious, but hasn't posted anything yet.
*[[Special:Contributions/Moonpav]] (added after initial post)
Unfortunately I can't give you admin permissions myself, but I have blocked most of those users for you. [[User:Legio noctis|Legio noctis]] 20:38, 14 December 2011 (UTC)

== Blocking spam (external links) ==

Hello. The pages [[MediaWiki:Spam-blacklist]] and [[MediaWiki:Spam-whitelist]] can help you in combating spam. Once a link is added to the blacklist, no one will be able to save it again on this wiki. These 2 pages are protected, so that ordinary users (like me) can't edit them.

For an usage example, see [http://en.wikipedia.org/wiki/MediaWiki:Spam-blacklist]. It's a list of regular expressions. The main thing you have to remember is that <code>.</code> represents a single character in the URL, while <code>\.</code> represents a dot in the URL. <code>\b</code> identifies a word boundary, i.e. the position between a word (a sequence of letters and/or digits) and a punctuation character. 
Can I help? I have experience with regular expressions, and I can write down them, given the links.

For example, you might add
<pre>\bgangstaa\.joinvps\.com\b</pre>
URL taken from [[Jobs The Outdoors‎|1]], [[Jobs In Dripping Springs‎|2]]

Also, I'm wondering why they're spamming non-existing domains.

(I have absolutely no idea of whom and where to write this to: ) The webmaster of this wiki might also consider to read the page [http://www.mediawiki.org/wiki/Manual:Combating_spam#SpamBlacklist "Combating spam"] in the MediaWiki manual. --[[User:Marko|Marko]] 16:42, 16 February 2012 (UTC)
:Thanks Marko, I knew of the existence of the blacklist, but did not think on it as one of the problems is really the creating of dozens and dozens of accounts from open proxies. This link to the manual is handy. I'll forward the link to the "IP address blacklists" section to the right person. Kind regards, [[User:Kris|Kris]] 20:11, 16 February 2012 (UTC)

== Suggestion to replace CAPTCHA module ==

Hi, I'd like to suggest replacing the simple MathCAPTCHA with QuestyCaptcha (it is a Mediawiki Extension). I have been successfully using it on a number of public wikis and with a good selection of questions it has immediately brought the number of spam accounts down to zero. Good questions and answers will be very easy for Inkscape users and even newcomers, but generally unsuitable for spambots (e.g. "The main color in the Inkscape logo is ..."). I've found that avoiding direct questions in favour of sentences to complete is better, but YMMV. I'm happy to help if needed --[[User:Steko|Steko]] 11:50, 21 April 2012 (UTC)
:Thanks I'll discuss it it with the website admins. [[User:Kris|Kris]] 14:14, 23 April 2012 (UTC)

Filter Effects

2012-04-09T07:33:08Z

Kris: /* general bugs */

Filter effects is a part of [http://www.w3.org/TR/SVG11/filters.html SVG specification]. It has been worked on in Inkscape as part of Googles Summer Of Code 2006 and 2007 and [http://www.coss.fi/web/coss/developers/summercode COSS's Kesäkoodi] 2007

For more info on this Kesäkoodi project, see [http://fedev.blogspot.com/ the project blog] or [http://cs.helsinki.fi/u/kiirala/kesakoodi/application.html the project plan].

User interface for filter effects was developed in GSoC 2007.

There exists a (still incomplete) set of filter effect tutorials aimed for end users at [http://fedev.blogspot.com/search/label/Filter%20Effects%20Tutorial fedev.blogspot.com]

For information about internal workings of filter effects renderer, please see page [[Filter effects internals]].

== What works in Inkscape 0.46 ==

While Inkscape 0.46 support for Filter Effects is still incomplete, it has a fairly good support for most features.

The big improvements compared to Inkscape 0.45 are
* The Filter Effects dialog, which allows for easy creation of new filter effects
* Filter primitives can be connected to each other to form complex filters
* Support for using background image as part of a filter effect
* Most filter primitives are now implemented, compared to one filter primitive in 0.45

Noteworthy things that don't work:
* Fill Paint and Stroke Paint input images do not work, even though they are usable in Filter Effects dialog. Any filter using these is likely to look different in future Inkscape versions, when the renderer is implemented.
* There's no GUI for setting the enable-background property. This property has to be set on some parent layer of filtered object to make Background Image and Background Alpha input images work.
* Filter primitive subregions do not work nor there is GUI for them. These are required for SVG compatibility and to make using feTile to make any sense.

=== Status of the filter primitives===
{| border="1"
! primitive
! renderer
! user interface
|-
! [http://www.w3.org/TR/SVG11/filters.html#feBlendElement feBlend]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feColorMatrixElement feColorMatrix]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feComponentTransferElement feComponentTransfer]
|style="background-color:#ffbbbb;"| '''Not implemented'''
|style="background-color:#dddddd;"| '''Disabled'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feCompositeElement feComposite]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feConvolveMatrixElement feConvolveMatrix]
|style="background-color:#ddffbb;"| '''Partial implementation'''
TODO:
*edgeMode behaviour
*produce resolution-independent results
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feDiffuseLightingElement feDiffuseLighting]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feDisplacementMapElement feDisplacementMap]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feFloodElement feFlood]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feGaussianBlurElement feGaussianBlur]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feImageElement feImage]
|style="background-color:#ddffbb;"| '''Partly implemented'''
* Only works on external images
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feMergeElement feMerge]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feMorphologyElement feMorphology]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feOffsetElement feOffset]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feSpecularLightingElement feSpecularLighting]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feTileElement feTile]
|style="background-color:#ddffbb;"| '''Partly Implemented'''
|style="background-color:#dddddd;"| '''Disabled'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feTurbulenceElement feTurbulence]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
|}

== What works in Inkscape 0.45 ==

Basic support for filter effects is included in 0.45 release. At the moment only gaussian blur is implemented, so while specifications define a bunch of other effects and some other programs can handle them, Inkscape cannot render them yet. Also, tools for editing other types of filters do not exist yet.

Gaussian blur can be applied to an object by using Blur slider in Fill and stroke dialog.

In Inkscape preferences dialog there is a setting controlling the filter rendering quality. Even low quality often produces good enough rendering quality, but it takes a lot less time to render. When exporting an image from Inkscape, the best quality is always used, regardless of this setting.

== Filter Effect support in trunk ==
=== Status of the filter primitives===
{| border="1"
! primitive
! renderer
! user interface
|-
! [http://www.w3.org/TR/SVG11/filters.html#feBlendElement feBlend]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feColorMatrixElement feColorMatrix]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feComponentTransferElement feComponentTransfer]
|style="background-color:#ffbbbb;"| '''Not implemented'''
|style="background-color:#ddffbb;"| '''Partially Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feCompositeElement feComposite]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feConvolveMatrixElement feConvolveMatrix]
|style="background-color:#ddffbb;"| '''Partial implementation'''
TODO:
*edgeMode behaviour
*produce resolution-independent results
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feDiffuseLightingElement feDiffuseLighting]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feDisplacementMapElement feDisplacementMap]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feFloodElement feFlood]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feGaussianBlurElement feGaussianBlur]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feImageElement feImage]
|style="background-color:#ddffbb;"| '''Partly implemented'''
* still doesnt work for other SVG elements. There is a [http://article.gmane.org/gmane.comp.graphics.inkscape.devel/24571 patch] being worked on.

|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feMergeElement feMerge]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feMorphologyElement feMorphology]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feOffsetElement feOffset]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feSpecularLightingElement feSpecularLighting]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feTileElement feTile]
|style="background-color:#ddffbb;"| '''Partly Implemented'''
|style="background-color:#dddddd;"| '''Needs some analysis'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feTurbulenceElement feTurbulence]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
|}

=== General bugs ===
UI
* Connecting a filter with itself, connect it to one of the reserved keywords.[https://bugs.launchpad.net/inkscape/+bug/168790]

Renderer
* StrokePaint and FillPaint input images are not supported. [https://bugs.launchpad.net/inkscape/+bug/168791]

* Result from filter is not cut to the shape of filter effects area. Note that filter effects area can be a rotated rectangle or parallelogram when viewed in display coordinates.

* There are many parts in filtering code marked with TODO. Many of these mark unhandled corner cases and places, where the filters generate almost but not quite correct results.

== Mockups of Filter editing and related dialogs ==

As of Inkscape 0.46 there exists a Filter Effects editor, highly similar to the one depicted here.

Presentation of new Fill and Stroke dialog where user can easily access most frequent actions like changing Blend modes, Blurring and Opacity of an object and select filter for an object or group of objects WITHOUT ability of accessing editing of the same.

[[Image:Fill_and_stroke.png]]

Changing of effect parameters and building sets of same can be done in specialized editor. Maybe next step in pushing ease of effect use further could be loading of contributed sets of effects and their parameters from file user had made himself or downloaded according to his preference from Effect library hosted somewhere on net (inkscape.org?!).

[[Image:Filter_edit_dialog.png]]

Possible benefits of this approach:

- '''Speed-ups''' - no need to redraw canvas for every single effect parameter tweaking

- '''Effect library''' - like noted above; SVG effects can be very hard to deal with for a designer/illustrator without technical background. This way developers can make a small set of commonly used effects like '''''drop shadow, outer/inner glow, etc'''''. Learning curve for such (I think targeted) user will be shorter because he/she will eventually catch up with internal way of dealing with effects by doing simple changes on occasion.

Another possible mock-up of the filters dialogue: http://wiki.inkscape.org/wiki/images/INKSCAPE_filters_dialogue.svg

-using extra windows to tweak effect parameters (its good for effects with 1 parameter, but most have at least 2. hmm)
[[Category:Developer_Documentation]]

Filter Effects

2012-04-09T07:31:46Z

Kris: lang

Filter effects is a part of [http://www.w3.org/TR/SVG11/filters.html SVG specification]. It has been worked on in Inkscape as part of Googles Summer Of Code 2006 and 2007 and [http://www.coss.fi/web/coss/developers/summercode COSS's Kesäkoodi] 2007

For more info on this Kesäkoodi project, see [http://fedev.blogspot.com/ the project blog] or [http://cs.helsinki.fi/u/kiirala/kesakoodi/application.html the project plan].

User interface for filter effects was developed in GSoC 2007.

There exists a (still incomplete) set of filter effect tutorials aimed for end users at [http://fedev.blogspot.com/search/label/Filter%20Effects%20Tutorial fedev.blogspot.com]

For information about internal workings of filter effects renderer, please see page [[Filter effects internals]].

== What works in Inkscape 0.46 ==

While Inkscape 0.46 support for Filter Effects is still incomplete, it has a fairly good support for most features.

The big improvements compared to Inkscape 0.45 are
* The Filter Effects dialog, which allows for easy creation of new filter effects
* Filter primitives can be connected to each other to form complex filters
* Support for using background image as part of a filter effect
* Most filter primitives are now implemented, compared to one filter primitive in 0.45

Noteworthy things that don't work:
* Fill Paint and Stroke Paint input images do not work, even though they are usable in Filter Effects dialog. Any filter using these is likely to look different in future Inkscape versions, when the renderer is implemented.
* There's no GUI for setting the enable-background property. This property has to be set on some parent layer of filtered object to make Background Image and Background Alpha input images work.
* Filter primitive subregions do not work nor there is GUI for them. These are required for SVG compatibility and to make using feTile to make any sense.

=== Status of the filter primitives===
{| border="1"
! primitive
! renderer
! user interface
|-
! [http://www.w3.org/TR/SVG11/filters.html#feBlendElement feBlend]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feColorMatrixElement feColorMatrix]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feComponentTransferElement feComponentTransfer]
|style="background-color:#ffbbbb;"| '''Not implemented'''
|style="background-color:#dddddd;"| '''Disabled'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feCompositeElement feComposite]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feConvolveMatrixElement feConvolveMatrix]
|style="background-color:#ddffbb;"| '''Partial implementation'''
TODO:
*edgeMode behaviour
*produce resolution-independent results
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feDiffuseLightingElement feDiffuseLighting]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feDisplacementMapElement feDisplacementMap]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feFloodElement feFlood]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feGaussianBlurElement feGaussianBlur]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feImageElement feImage]
|style="background-color:#ddffbb;"| '''Partly implemented'''
* Only works on external images
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feMergeElement feMerge]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feMorphologyElement feMorphology]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feOffsetElement feOffset]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feSpecularLightingElement feSpecularLighting]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feTileElement feTile]
|style="background-color:#ddffbb;"| '''Partly Implemented'''
|style="background-color:#dddddd;"| '''Disabled'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feTurbulenceElement feTurbulence]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
|}

== What works in Inkscape 0.45 ==

Basic support for filter effects is included in 0.45 release. At the moment only gaussian blur is implemented, so while specifications define a bunch of other effects and some other programs can handle them, Inkscape cannot render them yet. Also, tools for editing other types of filters do not exist yet.

Gaussian blur can be applied to an object by using Blur slider in Fill and stroke dialog.

In Inkscape preferences dialog there is a setting controlling the filter rendering quality. Even low quality often produces good enough rendering quality, but it takes a lot less time to render. When exporting an image from Inkscape, the best quality is always used, regardless of this setting.

== Filter Effect support in trunk ==
=== Status of the filter primitives===
{| border="1"
! primitive
! renderer
! user interface
|-
! [http://www.w3.org/TR/SVG11/filters.html#feBlendElement feBlend]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feColorMatrixElement feColorMatrix]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feComponentTransferElement feComponentTransfer]
|style="background-color:#ffbbbb;"| '''Not implemented'''
|style="background-color:#ddffbb;"| '''Partially Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feCompositeElement feComposite]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feConvolveMatrixElement feConvolveMatrix]
|style="background-color:#ddffbb;"| '''Partial implementation'''
TODO:
*edgeMode behaviour
*produce resolution-independent results
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feDiffuseLightingElement feDiffuseLighting]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feDisplacementMapElement feDisplacementMap]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feFloodElement feFlood]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feGaussianBlurElement feGaussianBlur]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feImageElement feImage]
|style="background-color:#ddffbb;"| '''Partly implemented'''
* still doesnt work for other SVG elements. There is a [http://article.gmane.org/gmane.comp.graphics.inkscape.devel/24571 patch] being worked on.

|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feMergeElement feMerge]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feMorphologyElement feMorphology]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feOffsetElement feOffset]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feSpecularLightingElement feSpecularLighting]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feTileElement feTile]
|style="background-color:#ddffbb;"| '''Partly Implemented'''
|style="background-color:#dddddd;"| '''Needs some analysis'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feTurbulenceElement feTurbulence]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
|}

=== general bugs ===
UI
* Connecting a Filter with itself, connect it to one of the reserved keywords.[https://bugs.launchpad.net/inkscape/+bug/168790]

Renderer
* StrokePaint and FillPaint input images are not supported. [https://bugs.launchpad.net/inkscape/+bug/168791]

* Result from filter is not cut to the shape of filter effects area. Note that filter effects area can be a rotated rectangle or parallelogram when viewed in display coordinates.

* There are many parts in filtering code marked with TODO. Many of these mark unhandled corner cases and places, where the filters generate almost but not quite correct results.

== Mockups of Filter editing and related dialogs ==

As of Inkscape 0.46 there exists a Filter Effects editor, highly similar to the one depicted here.

Presentation of new Fill and Stroke dialog where user can easily access most frequent actions like changing Blend modes, Blurring and Opacity of an object and select filter for an object or group of objects WITHOUT ability of accessing editing of the same.

[[Image:Fill_and_stroke.png]]

Changing of effect parameters and building sets of same can be done in specialized editor. Maybe next step in pushing ease of effect use further could be loading of contributed sets of effects and their parameters from file user had made himself or downloaded according to his preference from Effect library hosted somewhere on net (inkscape.org?!).

[[Image:Filter_edit_dialog.png]]

Possible benefits of this approach:

- '''Speed-ups''' - no need to redraw canvas for every single effect parameter tweaking

- '''Effect library''' - like noted above; SVG effects can be very hard to deal with for a designer/illustrator without technical background. This way developers can make a small set of commonly used effects like '''''drop shadow, outer/inner glow, etc'''''. Learning curve for such (I think targeted) user will be shorter because he/she will eventually catch up with internal way of dealing with effects by doing simple changes on occasion.

Another possible mock-up of the filters dialogue: http://wiki.inkscape.org/wiki/images/INKSCAPE_filters_dialogue.svg

-using extra windows to tweak effect parameters (its good for effects with 1 parameter, but most have at least 2. hmm)
[[Category:Developer_Documentation]]

Filter Effects

2012-04-09T07:31:21Z

Kris: lang

Filter effects is a part of [http://www.w3.org/TR/SVG11/filters.html SVG specification]. It has been worked on in Inkscape as part of Googles Summer Of Code 2006 and 2007 and [http://www.coss.fi/web/coss/developers/summercode COSS's Kesäkoodi] 2007

For more info on this Kesäkoodi project, see [http://fedev.blogspot.com/ the project blog] or [http://cs.helsinki.fi/u/kiirala/kesakoodi/application.html the project plan].

User interface for filter effects was developed in GSoC 2007.

There exists a (still incomplete) set of filter effects tutorials aimed for end users at [http://fedev.blogspot.com/search/label/Filter%20Effects%20Tutorial fedev.blogspot.com]

For information about internal workings of filter effects renderer, please see page [[Filter effects internals]].

== What works in Inkscape 0.46 ==

While Inkscape 0.46 support for Filter Effects is still incomplete, it has a fairly good support for most features.

The big improvements compared to Inkscape 0.45 are
* The Filter Effects dialog, which allows for easy creation of new filter effects
* Filter primitives can be connected to each other to form complex filters
* Support for using background image as part of a filter effect
* Most filter primitives are now implemented, compared to one filter primitive in 0.45

Noteworthy things that don't work:
* Fill Paint and Stroke Paint input images do not work, even though they are usable in Filter Effects dialog. Any filter using these is likely to look different in future Inkscape versions, when the renderer is implemented.
* There's no GUI for setting the enable-background property. This property has to be set on some parent layer of filtered object to make Background Image and Background Alpha input images work.
* Filter primitive subregions do not work nor there is GUI for them. These are required for SVG compatibility and to make using feTile to make any sense.

=== Status of the filter primitives===
{| border="1"
! primitive
! renderer
! user interface
|-
! [http://www.w3.org/TR/SVG11/filters.html#feBlendElement feBlend]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feColorMatrixElement feColorMatrix]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feComponentTransferElement feComponentTransfer]
|style="background-color:#ffbbbb;"| '''Not implemented'''
|style="background-color:#dddddd;"| '''Disabled'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feCompositeElement feComposite]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feConvolveMatrixElement feConvolveMatrix]
|style="background-color:#ddffbb;"| '''Partial implementation'''
TODO:
*edgeMode behaviour
*produce resolution-independent results
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feDiffuseLightingElement feDiffuseLighting]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feDisplacementMapElement feDisplacementMap]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feFloodElement feFlood]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feGaussianBlurElement feGaussianBlur]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feImageElement feImage]
|style="background-color:#ddffbb;"| '''Partly implemented'''
* Only works on external images
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feMergeElement feMerge]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feMorphologyElement feMorphology]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feOffsetElement feOffset]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feSpecularLightingElement feSpecularLighting]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feTileElement feTile]
|style="background-color:#ddffbb;"| '''Partly Implemented'''
|style="background-color:#dddddd;"| '''Disabled'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feTurbulenceElement feTurbulence]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
|}

== What works in Inkscape 0.45 ==

Basic support for filter effects is included in 0.45 release. At the moment only gaussian blur is implemented, so while specifications define a bunch of other effects and some other programs can handle them, Inkscape cannot render them yet. Also, tools for editing other types of filters do not exist yet.

Gaussian blur can be applied to an object by using Blur slider in Fill and stroke dialog.

In Inkscape preferences dialog there is a setting controlling the filter rendering quality. Even low quality often produces good enough rendering quality, but it takes a lot less time to render. When exporting an image from Inkscape, the best quality is always used, regardless of this setting.

== Filter Effect support in trunk ==
=== Status of the filter primitives===
{| border="1"
! primitive
! renderer
! user interface
|-
! [http://www.w3.org/TR/SVG11/filters.html#feBlendElement feBlend]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feColorMatrixElement feColorMatrix]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feComponentTransferElement feComponentTransfer]
|style="background-color:#ffbbbb;"| '''Not implemented'''
|style="background-color:#ddffbb;"| '''Partially Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feCompositeElement feComposite]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feConvolveMatrixElement feConvolveMatrix]
|style="background-color:#ddffbb;"| '''Partial implementation'''
TODO:
*edgeMode behaviour
*produce resolution-independent results
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feDiffuseLightingElement feDiffuseLighting]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feDisplacementMapElement feDisplacementMap]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feFloodElement feFlood]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feGaussianBlurElement feGaussianBlur]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feImageElement feImage]
|style="background-color:#ddffbb;"| '''Partly implemented'''
* still doesnt work for other SVG elements. There is a [http://article.gmane.org/gmane.comp.graphics.inkscape.devel/24571 patch] being worked on.

|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feMergeElement feMerge]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feMorphologyElement feMorphology]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feOffsetElement feOffset]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feSpecularLightingElement feSpecularLighting]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feTileElement feTile]
|style="background-color:#ddffbb;"| '''Partly Implemented'''
|style="background-color:#dddddd;"| '''Needs some analysis'''
|-
! [http://www.w3.org/TR/SVG11/filters.html#feTurbulenceElement feTurbulence]
|style="background-color:#aaffbb;"| '''Implemented'''
|style="background-color:#aaffbb;"| '''Implemented'''
|-
|}

=== general bugs ===
UI
* Connecting a Filter with itself, connect it to one of the reserved keywords.[https://bugs.launchpad.net/inkscape/+bug/168790]

Renderer
* StrokePaint and FillPaint input images are not supported. [https://bugs.launchpad.net/inkscape/+bug/168791]

* Result from filter is not cut to the shape of filter effects area. Note that filter effects area can be a rotated rectangle or parallelogram when viewed in display coordinates.

* There are many parts in filtering code marked with TODO. Many of these mark unhandled corner cases and places, where the filters generate almost but not quite correct results.

== Mockups of Filter editing and related dialogs ==

As of Inkscape 0.46 there exists a Filter Effects editor, highly similar to the one depicted here.

Presentation of new Fill and Stroke dialog where user can easily access most frequent actions like changing Blend modes, Blurring and Opacity of an object and select filter for an object or group of objects WITHOUT ability of accessing editing of the same.

[[Image:Fill_and_stroke.png]]

Changing of effect parameters and building sets of same can be done in specialized editor. Maybe next step in pushing ease of effect use further could be loading of contributed sets of effects and their parameters from file user had made himself or downloaded according to his preference from Effect library hosted somewhere on net (inkscape.org?!).

[[Image:Filter_edit_dialog.png]]

Possible benefits of this approach:

- '''Speed-ups''' - no need to redraw canvas for every single effect parameter tweaking

- '''Effect library''' - like noted above; SVG effects can be very hard to deal with for a designer/illustrator without technical background. This way developers can make a small set of commonly used effects like '''''drop shadow, outer/inner glow, etc'''''. Learning curve for such (I think targeted) user will be shorter because he/she will eventually catch up with internal way of dealing with effects by doing simple changes on occasion.

Another possible mock-up of the filters dialogue: http://wiki.inkscape.org/wiki/images/INKSCAPE_filters_dialogue.svg

-using extra windows to tweak effect parameters (its good for effects with 1 parameter, but most have at least 2. hmm)
[[Category:Developer_Documentation]]

Pre-installed gradients

2012-04-08T05:42:39Z

Kris: cat

I created some gradients to be compatible with latest Gimp.

[[File:Gradients.svg|thumb|Rendering may be problematic. Download and use in Inkscape]]

http://groups.yahoo.com/group/gimpi/files/Gradients/gimp-nevit-322-extra-gradients-20070117-for_gimp_2_3.zip

Those who start with Atmospheric
attempt to make Common Atmospheric Effects
done in 3D programs in GIMP at ease of
drawing a Gradient from bottom of image to top.

There are many Basic Gradient possibilities
that done for a quick visual reference and
easy of use. Their names start with Basic.

There are also a few modifications of original
Gimp Gradients like neons in new colors, and a
few unclassified new gradients that neither fit
in atmospheric nor basic.

These can either be included with Inkscape distribution package or IS extras...

Ps. sorry for long link. Wiki does not support zip uploads.

Nevit Dilmen

Copyright notice:

I, the author of this gradients, hereby publish it under the following license:
Permission is granted to copy, distribute and/or modify this
package under the terms of the GNU Free License,
Version 1.2 or any later version published by the
Free Software Foundation a copy of which can be found at
www.GNU.org

Most gradients are now available in SVG format. This is a special Inkscape file It includes hundreds of gradients. They can be accessed and used under gradient dialog of '''Fill and Stroke menu'''. You will see the available gradients under Fill & Stroke.
* [http://commons.wikimedia.org/wiki/File:Gradients.svg File:Gradients.svg]

[[Category:About Inkscape‏‎]]

== Main menus ==

=== Add an item to an existing menu ===

# Choose a short name and a place you want to put it (e.g. ''Paste as dummy...'' in ''Edit'' menu between ''Paste'' and ''Paste In Place'')
# Code its behaviour in a function somewhere or locate an existing one (e.g. ''sp_paste_as_dummy()'' in ''sp-dummy.cpp'' and ''sp-dummy.h'')
# Deduce a [[Verb]] name which looks like ''SP_VERB_ + menu name'' (e.g. ''SP_VERB_EDIT_PASTE_AS_DUMMY'')
# In [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head%3A/src/verbs.h src/verbs.h]
## Locate the big enum at the beginning
## Add the new Verb name in the enum at the right place (e.g. after ''SP_VERB_EDIT_PASTE'')
# In [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head%3A/src/verbs.cpp src/verbs.cpp]
## Locate ''_base_verbs[]'' creation
## Add a new item at the right place. With this add you will set its short name (e.g. ''Paste as dummy...''), description and icon (a GTK stock, an Inkscape icon or NULL)
## Locate the ''perform(...)'' function of the menu (e.g. locate ''EditVerb::perform(...)'')
## Add a new case to deal with your feature to call your function (e.g. to call ''sp_paste_as_dummy()'')
# In [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head%3A/src/menus-skeleton.h src/menus-skeleton.h]
## Locate ''menus_skeleton[]'' variable
## Edit its content to add your new feature at the right place
# Save all, compile and run, it should works.

=== Create a new menu ===

To be written.

== Context menu ==

See [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head%3A/src/interface.cpp src/interface.cpp] and [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head%3A/src/interface.h src/interface.h].

[[Category:Developer Documentation]]
[[Category:Needs Work]]

Tool Grouping and Interface suggestions

2012-04-02T16:38:54Z

Kris: cat

== Toolbar re-arrangement possibilities ==

As new tools are added, the current toolbar is getting rather long. Possible solutions include a combination of the following:
* Grouping tools
* Enabling hiding of some tools like in Gimp
* Double toolbars or moving the toolbar to the top (arguable)
* Enable “presets” bars.

=== Tool grouping ===

Tools such as rectangle, circle, star and spiral can be grouped into a Shapes tool for example.

Some possibilities:

# '''Clicking on the tool opens list of sub-tools '''
#* Pros: Straightforward grouping and access.
#* Cons: user has to click the tool to find the sub-tools needed.
# '''Sub-tools available as “modes” in the tool control bar '''
#* Pros: Top-level access.
#* Cons: Screen clutter.
#* Notes: Clutter can be reduced if the tool control bar is “dynamic”, i.e. options change depending on the sub-tool used.
# '''Sub-tools available as “drop-downs” in the tool control bar '''
#* This is what the “Shapes” option in Bezier and Freehand tools currently achieved.
#* Pros: You can add as many sub-tools as you want.
#* Cons: Difficult access.
#* Notes: Also requires “dynamic tool control bar” to avoid cluttering the tool control bar with sub-options.
# '''Sub-tools appear next to tool control bars '''
#* Pros: Because separate bars are involved, the tool control bar does not need to be dynamic, since they’re essentially separate tool control bars for separate tools.
#* Cons: Permanent sub-tool bar takes up permanent space.
# '''Tool mode vs sub-tool '''
Is it possible for a shortcut to link to a tool mode (for example, the "Circle" mode of a "Shape" tool), rather than the tool itself? If not, then some options should be made into independent sub-tools.

This limitation could be limited thanks to "Presets toolbars" however.

[http://postimage.org/image/qpwmume5p/ List of Tool grouping and subtool display options]

=== Presets bars ===

Presets bars could be accessed from an arrow in the toolbar, and either:
* Show the presets in place of the current toolbar (which remains available as a "default" mode)
* Open an independant floating dialogue, where you can add new tools via drag and drop

Default presets are available according to functions. Examples:
* Technical drawing: selection, technical drawing tools, text...
* Graphs: shapes (diagrams?), text, connectors
* Font design: guides, powerstroke, etc.

[http://postimage.org/image/w3vf263vx/ Tool presets for easy access to certain functions?]

=== Other toolbar size control methods ===

An option could exist to hide tools that are not commonly used.

Inkscape could also have two bars instead of one, though this doesn’t really solve the issue.

== Toolbar and sub-tools grouping ==

This describes a possible grouping of existing tools, as well as the addition of new tools and sub-tools.

* '''Select/transform '''
** Resize/Rotate
** Perspective deform
** Envelop Deform (includes “Envelop”?)

* '''Node '''
** Default
** Offset?
** Extrude?
** [https://blueprints.launchpad.net/inkscape/+spec/fillet-tool Fillet tool] ?
Offset and extrude will be new tools allowing the user to control offsets and extrusions on canvas. This could be useful for technical drawing.

* '''Tweak '''
** Object tweaks
** Node tweaks?
** Other tweaks?
(Breakdowns if users find the current interface too long?)

* '''Guides '''
** Point
** Axis
** Grid
** Circular/Angular
** Perspective
** Composition
See [https://blueprints.launchpad.net/inkscape/+spec/guides-improvement Guides improvement blueprint].

* '''Tiles and symmetries '''
** Symmetries
** Radial clones
** Tiling
** Clones along path

* '''2D Shape tool '''
** Line
** Rectangle
** Circle
** Star
** Spiral
See [https://blueprints.launchpad.net/inkscape/+spec/tech-drawing Tech drawing blueprint]. New tool: line, as well as new modes to be allowed for rectangles and circles, namely alternate means of construction by placing points on canvas.

* '''Technical drawing '''
** I'm not 100% what should be going in here, but where possible it could be integrated into existing tools (node, shapes) as modes and sub-tools?

* '''3D Shape tool '''
** 3D box
** Cylinder
** Sphere
** (etc.)

* '''Freehand tool '''
** Line shape: markers and line styles (dots etc.)
** Diagram connectors?
** Powerstroke shape: presets drop-down. Has two modes: normal and "with fill."
** Custom shape (LPE): shows width and repeat options from tool control. Grouped with Clipboard.
** Sketch (currently an LPE)

[http://postimage.org/image/v6tl71hr7/ Additions to the tool control bar for Freehand and Bezier sub-tools]

* '''Bezier tool '''
(see Freehand)

* '''Text tool '''
** Typing (main mode)
** Separate kerning mode? (for those with small screens?)
** Text-flow? (for flowing text onto paths or into objects)
** Text diagram? (some default text boxes for those making graphs or comics)

* '''Calligraphy, Ruler, Spray, Zoom, Eraser, Bucket, Gradient, Color Picker '''
** No change.

* '''Mesh Gradient'''
** New tool.

* '''Pattern tool'''
** (Rather than just make you choose from a drop-down, pattern tool allows you to generate and control some common patterns like stripes, dots etc.)

{{DevDiscussion}}

Clipboard

2012-04-02T16:38:27Z

Kris: cat

== What can I copy? ==

When copying, different scenari could appear (cf. [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head%3A/src/ui/clipboard.cpp void ClipboardManagerImpl::copy(SPDesktop *desktop)]):

* If Inkscape is in [[Gradient toolbar|Gradient mode]] and a gradient is selected, the selected gradient is copied
* If Inkscape is in [[Colorpicker toolbar|Color picker mode]], the color under the cursor is copied
* If Inkscape is in [[Text toolbar|Text mode]] and if a text is selected, the selected text is copied
* In all other cases, the objects selected are copied

== What can I paste? ==

=== Default behaviour ===

When pasting, the clipboard items will be scaned at a predefined order (cf. [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head%3A/src/ui/clipboard.cpp ClipboardManagerImpl::ClipboardManagerImpl()]) but the idea is to search data in the clipboard following this order:

* Inkscape SVG ressource
** image/x-inkscape-svg
* SVG ressource
** image/svg+xml
** image/svg+xml-compressed
* Others vector formats:
** PDF ressource
** Adobe Illustrator ressource

If no ressource is found, other formats are searched (cf. [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head%3A/src/ui/clipboard.cpp bool ClipboardManagerImpl::paste(SPDesktop *desktop, bool in_place)]):

* Windows users only: EMF ressource
* Image ressource
* Text string

=== Special behaviour ===

Those behaviours are accessible via keyboard shortcuts and/or menus:

* Paste path effect ([[Path menu]]) (cf. [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head%3A/src/ui/clipboard.cpp bool ClipboardManagerImpl::pastePathEffect(SPDesktop *desktop)])
* Paste size ([[Edit menu]]) (cf. [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head%3A/src/ui/clipboard.cpp bool ClipboardManagerImpl::pasteSize(SPDesktop *desktop, bool separately, bool apply_x, bool apply_y)])
* Paste style ([[Edit menu]]) (cf. [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head%3A/src/ui/clipboard.cpp bool ClipboardManagerImpl::pasteStyle(SPDesktop *desktop)])

== Developpers informations ==

=== How can I allow pasting a new SVG mimetype? ===

Nota: this section is underwriting and should be used with caution.

Default non-Inkscape SVG mimetype is ''image/svg+xml''. In order to deal with others non-Inkscape SVG mimetypes, do the following:

# In [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head%3A/src/ui/clipboard.cpp src/ui/clipboard.cpp]
## Locate ''ClipboardManagerImpl::ClipboardManagerImpl()''
## Just after the ''image/svg+xml'' mimetype, add a new line with your mimetype
## Locate ''ClipboardManagerimpl::_retrieveClipboard()''
## The goal here is to change the mimetype from yours to the default non-Inkscape SVG mimetype. Locate the ''if'' test which set the target to the default non-Inkscape SVG mimetype
## Add a new case in the ''if'' with your mimetype

=== Source files ===

* [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head%3A/src/ui/clipboard.cpp /src/ui/clipboard.cpp]
* [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head%3A/src/ui/clipboard.h /src/ui/clipboard.h]

{{DevDiscussion}}

== Add an item to an existing menu ==

# Choose a short name and a place you want to put it (e.g. ''Paste as dummy...'' in ''Edit'' menu between ''Paste'' and ''Paste In Place'')
# Code its behaviour in a function somewhere or locate an existing one (e.g. ''sp_paste_as_dummy()'' in ''sp-dummy.cpp'' and ''sp-dummy.h'')
# Deduce a [[Verb]] name which looks like ''SP_VERB_ + menu name'' (e.g. ''SP_VERB_EDIT_PASTE_AS_DUMMY'')
# In [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head%3A/src/verbs.h src/verbs.h]
## Locate the big enum at the beginning
## Add the new Verb name in the enum at the right place (e.g. after ''SP_VERB_EDIT_PASTE'')
# In [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head%3A/src/verbs.cpp src/verbs.cpp]
## Locate ''_base_verbs[]'' creation
## Add a new item at the right place. With this add you will set its short name (e.g. ''Paste as dummy...''), description and icon (a GTK stock, an Inkscape icon or NULL)
## Locate the ''perform(...)'' function of the menu (e.g. locate ''EditVerb::perform(...)'')
## Add a new case to deal with your feature to call your function (e.g. to call ''sp_paste_as_dummy()'')
# In [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head%3A/src/menus-skeleton.h src/menus-skeleton.h]
## Locate ''menus_skeleton[]'' variable
## Edit its content to add your new feature at the right place
# Save all, compile and run, it should works.

== Create a new menu ==

To be writed.

[[Category:Developer Documentation]]
[[Category:Needs Work]]

Tiling tool

2012-03-27T17:51:38Z

Kris: category

== Tiling tool ==
The current tiling interface is hard to use. The current Tiling Tool proposal attempts to resolve part of that issue through the use of on-canvas guides called “Tiles.” This feature also expands the tiling to radial tiling and line tiling (currently known as Pattern Along Path).
{| class="wikitable"
|+
! scope="col" width="180"| Type
! scope="col" width="700" | Description
|-
! Wallpaper tiling
| Allows users to use the 17 wallpaper types.
|-
! Radial tiling
|
* This is for radial designs, and allows both angular clones and radial clones.
* For angular clones, users can choose between simple rotation or symmetry + rotation.
* For radial clones, users can choose between same direction and alternating directions.
|-
! Path tiling
|
* Clones are generated along a path. This can be used to create a string of decorations, for repeating frills, for page borders etc.
* Users can choose from all 7 Frieze groups.
|}

== Terminology ==

* '''Tile:''' A tile is defined here a guide used to mark the boundaries of the base tiling, as well as define the tiling type. It defines the “unit” of the tiling. For example, it is a rectangle for a “P1: Simple translation” tiling. Tiles can be moved, rotated or scaled. In tile edit mode, the type of tile can be modified through the use of handles or from a drop-down list. When rendering a tiling, Inkscape automatically detects the type of tile being used to select the tiling type.
* '''Base pattern:''' Defined here as the pattern that needs to be repeated.
* '''Tiling tool:''' This tool. Used to render tilings.
* '''Render mode:''' The main mode of the tiling tool. From here you can create a new tile, and if you have a tile and based pattern selected, you can “render” the appropriate tiling.
* '''Tile edit mode:''' Double-clicking on a tile enters the tile edit mode. Double-clicking elsewhere leaves it. In tile edit mode, the toolbar changes to one appropriate for that tiling operation (wallpaper, radial or line tiling). Additional features proposed:
** '''Guides:''' In tiling mode, the user can add additional guides (points or lines) to help design their pattern. These additional guides are just visual references and don’t perform additional actions.
** '''Render frame:''' A render frame shows an outline of frames to render. Users can add or delete frames with the mouse. The whole frame can also be moved, rotated and resized.
* '''Tiling dialogue:''' A dialogue with additional options, behaving like an LPE dialogue. Users can also see the stacking of tilings from here.

== Tiling tool: Render mode ==

The toolbar looks like this:

[[File:Tiling_Tool_Render_Mode.png|GUI proposal for the Render mode of the Tiling tool]]
 

The tile creation process:
# Create a base pattern.
# From the tiling mode, add a “Tile.”
#* Edit the tile as needed. Double-clicking a tile enters a tile edit mode. Double-click elsewhere to exit.
#* Make additional changes to the base pattern as needed.
# Select a base pattern and a tile. Switch to tiling tool again.
#* Before selecting the base pattern and tile, copy a target to render over if needed.
#* Choose tiling options.
# Click render.

== Tile edit mode ==

To enter Tile Edit mode, double-click on a tile. Exit by double-clicking elsewhere. The tile can be moved, resized and rotated using just the Transform (F1) tool, just like how rectangles and ellipses can be edited outside of their respective tools.

[[File:Tiling_Tool_Tile_Edit_Mode.png|GUI proposal for the tile Edit mode for the Tiling Tool]]
 

Advanced users can then change the type of the base tile (example: from P1 to P2) in tile edit mode through the use of handles or drop-downs. These handles are not visible nor editable outside the tile edit mode (to avoid getting in the way).

{| class="wikitable"
|+
! scope="col" width="180"| Type
! scope="col" width="500" | Description
|-
! scope="row" | Wallpaper tiling
| These guides corresponds to the different wallpaper categories
|-
! scope="row" | Radial tiling
| These are to create radial patterns. They're basically arc segments with a direction.
|-
! scope="row" | Tiling along Path
| This is defined by a central axis, an attach point and 2 tile bounds. The central axis represents the path to which the tile will attach, basically a visual normal offset. The tile attaches to a specific node (say, the first node of the path) from the attach point, basically a visual tangential offset. The two bounds decide where the tile cuts off save for edge scenarios.
|}

Veronica made a nice list of tiles for wallpapers and corresponding output previews here:

[http://i.imgur.com/DMCvU.png Full list of wallpaper tiles and previews]

== Tiling modes ==

[[File:Tiling_Tool_modes.png|Render modes for the tiling tool proposal]]
 
There are 4 modes in the current proposal:
* Plain: this is a normal tiling
* Clip: through clipping, only the part within the tile is shown. This is to avoid overlapping.
* Fuse: a “join node” operation is then conducted on all the nodes in the output. If the user designed the tiles to be seamless, then the lines should join up to create a seamless output.
* Fuse cut: this is, in fact, a “cut” and “delete” operation followed by a “join nodes” operation. Inkscape will cut along certain lines and delete parts for “inner” tiles. This last mode allows the user to create seamless tiles with “edge” scenarios from a single base pattern:

== More explanations of the "fuse cut" mode ==

[[File:Tiling_cut_excess.png|Explanation of "Fuse cut" feature for tiling proposal]]
 

[[File:Tiling_interface_examples.png|More examples of the possible outputs for the “Fuse Cut” mode]]
 

== Dynamics ==

[[File:Tiling_Tool_Dynamics.png|GUI and presets for Dynamics presets for Tiling Tool proposal]]
 
Simple dynamics presets could be accessible from the tiling tool. A separate “Dynamics” panel corresponding to the current tiling operation pops up when choosing the Edit option. Major differences are:
* Vertical listing
* Checkbox next to every transformation type, so users can easily remove all of them while retaining some values.
* Radial Clones use Polar coordinates.
* Tiling along Path use orthogonal coordinates (normal and orthogonal).
* Users can save and use presets. This includes a "No dynamics" option.

== Target ==

[[File:Tiling_Tool_Targets.png|Possible "target" types for tiling tool proposal]]
 
"Target" determines where you render your tiling.

For wallpaper tiling:
* By numbers: A pop-up asks you to input the number of tiles to make (example: 3 x 5), or the size of a rectangular area to render over
* Render frame: See guide description. After adding a render frame, Inkscape will render tiles according to that frame.
* Over copied: If you have a copied object, Inkscape will render over the copy.
* Border to copy: easy page borders? Makes a border.
* Clip to copied: Same as above, except clipped to the target. Use for clothes etc.
* Pattern to copy: (if allowed by .svg standards) The tiling is converted to a pattern and applied to the copied object. This pattern can be manually adjusted with the Pattern edit tool.
* New pattern: (if allowed by .svg standards) A pop-asks asks you to name and save the new pattern for later use.
For radial tiling:
* By number: A pop-up asks you to input the number of radial and angular copies. You can choose to input by angle and by radial distance instead.
* Render frame: see render frame description.
* No "to copied" option, because I think people usually want to define a radial tile just where the base tile is, but I could be wrong.
For Tiling along path:
* On selected Path. Note: this can be a closed path. A pop-up allows you to choose additional options and values.
* As selected path's line pattern: takes the selected path and makes the Tiling along path its new pattern.
* As new line pattern: if clone patterns can somehow be saved somewhere.
Alternatively, the "target" field could be excluded from the toolbar, and appear as options in a pop-up when clicking "Render."

== Options ==
Opens a Tiling dialogue. From here you can see what options have been applied to an existing tiling, change them and toggle tile stacking.

[[File:Tiling_Tool_Dialogue.png|UI proposal for tiling tool dialogue]]
 

== Guide points and other guides ==

[[File:Tiling_Tool_Guides.png|UI proposal for guide points feature for Tiling Tool]]
 

These features are there to help you design your tile pattern. Specifically, they're there to help design seamless tiles.
* Guide points: When a guide point is created on one side of a guide, counterparts are automatically created on all other sides of the basic guide. All changes to the original will be reflected onto counterpart. To create seamless designs, just make sure that all lines going in and out of a tile are connected to guide points.
* Guide segment: clicking and dragging on a guide point creates a guide segment, which also shows on all of the guide point's counterparts. The idea is to place a node on a guide point, snap its handle to the end of the segment, then repeat with the guide point's counterparts. When a "fuse" operation is applied, the result will be a perfectly smooth transition from one tile to the next.
See this [http://www.cgl.uwaterloo.ca/~csk/software/penrose/ javascript program] for an approximate idea of how it'd behave.
Note: programming-wise, the guide points don't actually do anything, they're just visual references. When Inkscape creates a "Fuse path" tiling, it just joins the nearest nodes. This means you can introduce slight dynamics and still have lines link up, though Inkscape can't guarantee the results in this case.
Depending on the guide type, other types of guides are available (parallel lines, arcs etc.)
== Render frame ==
[[File:Tiling_Tool_Render_Frame.png|Render frame feature for the tiling tool proposal]] 

A render frame is a tiling outline allowing the user to manually choose which frames to render. This is made up of a "central" tile and additional tiles (so when dynamics are applied, they start with the central tile). By default the frame is rendered over the original tile, but is a separate object that can be moved around, rotated and resized.

== Tile stacking ==

You can easily stack different tilings!

[[File:Tiling stacking.png|Explanation of tile stacking feature for my tiling proposal]] 

Inkscape will likely have an Effects stacking mechanism in the future. Whatever it is, tiling would also fit right into it.

== Line patterns ==

And why not "line patterns" while we're at it?

[[File:Tiling line patterns.png|UI proposal for line pattern choosing]] 

== Implementation ==

This proposal contains a lot of features, but it is also very modular, so features can be added separately.
* The base version of this tool would be a version only for wallpaper tiling, with only simple rectangular tile from which Inkscape will take coordinates. The base version could be a mere front-end to the old dialogue, with the difference being that the rectangular tile will be used to calculate coordinates.
* The different types of tiles and the Tile Edit Mode can be added separately. Users can first choose from a drop-down. Handles can also be programmed separately.
* In tile edit mode, additional "guides" (guide points etc.) can also be implemented separately.
* "Render frame" feature can also be implemented separately.
* All tiling modes can be implemented separately (clip, fuse and fuse cut). Note: the Fuse Cut operation requires the ability to perform Boolean operations (specifically “cut”) on a group of objects:
** [https://bugs.launchpad.net/inkscape/+bug/166302 Bug #166302: Cut Path looses some segments ]
** [https://bugs.launchpad.net/inkscape/+bug/171379 Bug #171379: Boolean Operations on Groups ]
** [https://bugs.launchpad.net/inkscape/+bug/701819 Bug #701819: Copy/Cut a Part of a Grouped Object ] (scenario of above)
** [https://bugs.launchpad.net/inkscape/+bug/408551 Bug #408551: Cut Path with a grouped object does nothing ]
* Dynamics drop-down and presets for dynamics can be implemented separately. The dialogue for dynamics can also be re-arranged independently.
* Most “target” options can be implemented separately.
* The above describes the tiling tool for just wallpaper tiling. All features can be expanded to radial tiling and line tiling separately.

[[Category:Proposals]]

Win32 Installer

2012-03-26T06:22:58Z

Kris: devdiscussion

{{DevDiscussion}}
There has been some complaints about the Windows installer and also many ideas has been raised. So I want to bundle all those ideas here on one page.

=== new feature request will cause complete rework ===
There is a request from a professor on the university to have a .msi installer in order to integrate inkscape into the university software distribution system.
This would require a complete rework and an entirely separate package as NSIS is not compatible with MSI packages. The standard recommendation from NSIS is to use the silent install options they provide to help automate large installations.

=== reported problems ===
* no uninstall option, this is a privilege issue as the user has no rigths to write the necessary registry strings
*- in order to install Inkscape on systems with limited rights the installer ignores such errors and just do not write registry keys
* Windows: problems installing as non-privileged user, same as above. We should help the user selecting the correct settings -- remove the check for all users or shortcuts in general (done)
* the uninstaller simply deletes the install directory. If the user installs accidentally to C:\Program Files\ ... oh that S****

=== coming up - where you can help ===
* check if Inkscape installer is not translated into your language and help translating it
* msi package using the wix installer, volunteers welcome

=== status ===
* screenshots [http://www.geocities.com/theAdib current version]
* multi user installation
*translated into catalan, english, czech, french, finnish, german, italian, polish, slovak, slovenian and spanish
* optional sets file associations for .svg and .svgz
* optional keeps the personal preferences
* selectable components (core, gtk, shortcuts, examples, tutorials, translations)
* show GPL, not need to accept just click next
* added non program files (README, AUTHORS, ...)
* crc validation
* does not show details any more during installation/deinstallation
* silent install, all settings can be done via command line
* test if the user has privileges to write registry,
* test if inkscape is installed and the previous installation is done by the same user
* ask to uninstall inkscape before overwriting
* test if the same user uninstalls inkscape
* optionally removes all reachable inkscape personal settings

=== feedback or what users say ===
* the file association should go to the toplevel three
* also associations for other file formats

=== component page ===
* inkscape core files (required)
* gtk files (required)
* shortcuts
*- install for all user
*- desktop icon
*- quick launch icon
*- default SVG editor
*- shell menu integration
* additional Files
*- examples
*- tutorials
* languages
*- English (required)
*- German
*- French
*- ...

=== ideas ===
# (DONE) installer installs everything, I don't need chinese translations
# (DONE) installer translations is bad, I don't understand the sense
* there are descriptions if you select/mouse-over that menu item
# (DONE) crc validation
# custom installations (examples, tutorial, translations)
# (DONE) silent installation
* is by default enables but no other option as /D directory can be set. Use /S to switch silent mode.
* now all the Options can be deselected with command line parameters
# use the common/extra gtk-lib as gaim or gimp are doing and only supply extra libs
* (Ishmal) We have talked about this before, and it is something that we need to examine. But
what we need is more of a reason to do this than only download size or disk space. This
would be much more work than just repackaging.
# The individual packages of their existing ports were built individually. This means that
for development, the dev must have the makefile point to all of their individual trees.
The pkg-config information thus also refers to individual trees. This would make development
-much- more difficult than is is now. Remember, the Win32 build is just another build
environment of the Inkscape tree. We can edit/compile/debug on it just as easily as
on Linux. It is -not- a port, where the development is done entirely on Linux.
# We would need for the startup code to look for the location of the Gtk directory in the
registry. We would then either need to add it to the path, or do explicit [[LoadLibrary]]()
calls.
# If the user does not already have the common Gtk directory, then it must be part of our
install process. We cannot ask the user to go to some website, download and install it.
We provide -everything- now. We would need an extremely good reason to stop doing this.
Actually, if you have ever used [[InstallShield]], you would know that it provides all of its
dependencies, too (the huge ODBC or OLE packages within your installer are examples).
I am not against this. We just need to do it a different way. What we have discussed is the
possibility of being able to build the entire set of libraries from source, all of the way from
iconv to Gtkmm and libxslt and beyond. If we could do this, then the build would be clean, and have
valid interdependencies (no missing DLLs or DLLs with the wrong names). A single pkg-config
directory would point to all of the correct places. This would benefit everyone; Gimp, Gaim,
Inkscape, and anyone else who wanted to build a Gtk app on Win32 would find it much easier
this way. We need to talk with the guys doing the porting, about doing something just like this.

There is a promising subproject of [[MinGW]], 'portmaker,' which can maybe allow this to happen.
It is [http://sourceforge.net/forum/forum.php?forum_id=476731 here].

# (DONE) there is no need to show the GPL just for the usage of the program. Make it not mandatory to accept.
* (Ishmal) I think the GPL is cool. It basically says "Welcome to Open Source," and reminds
the users that it is not a commercial application, but a community effort.
# (DONE) not to show Details by default
# test dependencies before installing extensions
# associate more than just .svg
* uh, again how do we test which dependencies are supported uberconverter, ghostscript, etc

=== problems and questions ===
* (DONE) we need to detect, what are the inkscape translations and let the user choose
: how we present the languages?
: In the native one "English, Deutsch, Italiano" or in the language of the installer?
* currently it is presented like that, ordered by ISO code "am Amharic, de German)
: once we detected inkscape translation we can left over the other languages from the gtk package
* how can we put the translations out of the installer so that more people can help translating
* what about let a script write the translation part ?
this script then should access the po files for the translations
Q: does python or perl allow to access the inkscape po files ?
* (DONE) what should a silent installation do, what are the options ?
* all options are supported a /? gives a screen with all possible options
* (DONE) we also need to add some none program-files: license (done), authors, hacking, news (release-notes), readme,

=== more todo ===
* please provide samples or screenshots of a application that you satisfied and think is good
* other ideas

=== screenshots ===
* [[http://www.geocities.com/theAdib screenshots Abiword Blender Gaim Gimp NSIS WinCVS WinMerge installer]]

Adib

MediaWiki:Spam-blacklist

2012-03-24T20:49:55Z

Kris: +1

Release notes/0.91

2012-03-24T18:01:21Z

Kris: /* User interface */

==Inkscape 0.49==

'''(not released yet - [[AnnouncePlanning049]])'''

==Release highlights==

* Cairo rendering for display and PNG export
* OpenMP multithreading for all filters

==Rendering and performance==

Inkscape 0.49 includes a new renderer based on the Cairo library. This work was done during Google Summer of Code 2010 and 2011 projects.
* '''Improved performance.''' The new renderer is significantly faster on most drawings. Renderings of the most complex objects are automatically cached to improve responsiveness during editing.
* '''OpenMP multithreading for filters.''' Filters use all available processor cores for computation. This results in substantial speedups when editing drawings containing large filtered objects on multi-core systems.
* '''Substantial memory savings.''' Inkscape now uses less memory when opening complex drawings, in some cases using only 25% of the memory used by Inkscape 0.48. Larger files can now be opened.
* '''Responsiveness improvements.''' The rendering of the SVG drawing is now cached. This results in massive improvements in responsiveness of path highlights, object selection / deselection, and path editing in delayed update mode.
* '''Rendering bug fixes.''' Most of the rendering glitches in our bug tracker are no longer present in Inkscape 0.49. The following things now render correctly:
** Pattern fills (no more gaps between tiles, regardless of transformation)
** Stroke of transformed objects in patterns
** Patterns containing clipped objects
** Nested clipping paths
** Masked and clipped objects with large masks / clipping paths in Outline view
** Paths with wide strokes and long miters

==Tools==

=== Selector tool ===

It is now easier to select items which are not at the top of the Z-order: use Alt+mouse wheel scroll to cycle through all items that are stacked on top of each other at the location of the mouse pointer (use Shift+Alt+mouse wheel scroll to add to the existing selection). At present, groups are not honoured, i.e., only individual items within groups are considered.

=== Node tool ===
The Node tool's toolbar contains new buttons to insert new knots on the selected path segments' extreme values. Click the dropdown arrow next to the insert knots button.

=== Align and distribute dialog ===
New "Exchange position of selected objects" feature. It adds three buttons in the Align and Distribute dialog (rearrange group) that exchange the positions of the selected objects: 1. according to the selection order, 2. according to the Z-order, and 3. clockwise.

===Live Path Effects===

The object's Live Path Effects are now forked upon object duplication.

====PowerStroke====
Here a list of the current state. Note that this is very much work in progress and '''anything can change'''. I think this is the most efficient place of keeping track how the powerstroke LPE works.
* stroke knots are purple diamonds
* when first applied, 3 stroke knots are added one at start, one at end, one somewhere in the middle along the path.
* adding nodes: Ctrl+click purple knot, unselect object, reselect it.
* deleting nodes: Ctrl+Alt+click purple knot, unselect object, reselect it.
* "sort points" reorders the stroke knots according to where they lie along the path (where they are closest to the path), instead of keeping them in original order.

[http://imgh.us/powerstroke-ell.png example screenshot]

====Clone original====
The Clone original LPE ignores the path data of the path it has been applied to; instead, it '''copies the original-d path data''', i.e. the path data before LPE calculation, from the path linked to by the Linked path parameter.

The Clone original LPE is made to be used in conjunction with powerstroke. Powerstroke creates a path with a variable stroke, but this path can then not be filled (because the fill is used as the stroke). To fill a powerstroked path, one must create a second path (dummy path), apply the Clone original LPE and link it to the powerstroked path. Because this second path clones the original path data before the Powerstroke LPE, it can be used to fill the powerstroked path.
To quickly create a dummy path and apply this effect, one can select the path to 'clone' and click the menu item '''Edit > Clone > Clone original path (LPE)'''.

Like for normal clones, pressing Shift+D, when the selected path has the Clone original LPE applied, selects the path referred to by the LPE.

===Filters===
The new Custom predefined filters allow users to create predefined filters with custom parameters. See [[SpecCustomPredefinedFilters]].

==Import/Export==
* New Flash XML Graphics (FXG) export format.
* New Synfig Animation Studio (SIF) export format.
* XAML export improvements.
* Compressed SVG and media export extension improvements. New options: set an image directory in the zip file, and add a text file that lists the fonts used in the SVG document.
* New preference to allow users to always link, embed or ask when importing bitmaps.

===Gimp XCF improvements===
* The "Save Background" option allows users to choose if the page background is saved with each Gimp layer.
* The exported layers now use the label attribute or, if not set, the id attribute.
* New help tab.
* Some bugs and warnings fixed.

===PDF/EPS/PS + LaTeX===
* Added the possibility of scaling the image. The 'calc' package must be included in the preamble. Then the image can be scaled by defining '\svgscale' instead of '\svgwidth'.
* The font shape is now also exported. '\textit{}' for italic text, '\textbf{}' for bold text, and '\textsl{}' (slanted) for oblique text. It is important to note that '''Arial''' has an '''oblique''' font shape and not '''italic''', so the result in LaTeX will be '''slanted instead of italic'''. It is better to '''use another font''' in Inkscape when you want true italics.

==Extensions==
===New===
* The new guillotine extension is used for exporting png slices from a drawing. The slice rectangles are defined by adding horizontal and vertical guides within the canvas boundary, the canvas boundary serves as the outside of the sliced area.
* The new [http://en.wikipedia.org/wiki/G-code G-code] tools extension converts paths to G-code (using circular interpolation), makes offset paths and engraves sharp corners using cone cutters.
* New [http://en.wikipedia.org/wiki/QR_code QR code] generator
* New isometric grid generator
* New bitmap crop extension (Extensions>Bitmaps>Crop)
* New "Extract text" extension outputs the text elements of the document in a chosen order.

===Improvements===
* Number nodes. New parameters allowing users to choose the starting dot number and the numbering step between two nodes.
* Color Markers to Match Stroke extension improvements. The markers can now inherit the fill and stroke colors and alpha channels from the object, or be customized with color selectors in a separate tab.
* Optional sliders added on float and int extension parameters (full and minimal modes).
* Extension parameters values (''except attributes!'') can now be contextualized for translation (with msgctxt).

==User interface==
*The interface elements are accessible through the keyboard with ALT+key in many more dialogs.
*Ability to set the canvas background color without exporting it (background transparency is only used for export but not the canvas).
*The following dialogs are now also dockable: "Object properties", "Object attributes", "Text and Font", "Check spelling", "Export bitmap", "XML editor", "Find", and "Tiled clones".
*New preference to allow Windows users to choose between native and Gtk open/save dialog.
*Preferences dialog cleanup.
*Menus: "Text and Font", "Fill and Stroke", and "Check Spelling" dialogs are added to the text object context menu (right click).

===Simple calculations in spinboxes===
In most spinboxes (a spinbox is an entry field with up and down "spinbuttons" next to it) you can now write simple calculations. For example: "2 * 3", "50 + 100", or "((12 + 34) * (5 + 5) - 2) / 2".
Moreover, you can use units in entering values, like "2 + 2 cm". The result will be converted to the selected unit for the particular entry.

==Translations==
* The ''Keyboard and mouse reference'' (inkscape-docs project) and color palettes' labels are now translatable.
* New UI translation in Latvian.
* New tutorial translations in Galician and Greek.
* New man pages in Chinese (zh_TW) Greek (el), Japanese (ja) and Slovak (sk), and updated French translation. ''[Galician (gl) and Polish (pl) in progress]''
* Man pages now use PO files for translation (inkscape-docs project).
* The tutorial generation system now fully supports RTL languages.

==SVG Support==

* The <tt>clip-rule</tt> property is now supported. No UI to set it exists at the moment, other than the XML editor.

== Snapping ==
* The snapping preferences and the snap toolbar have been reworked, both in the underlying code as well as in the GUI. This should make the snapping preferences easier to understand, easier to maintain, and make it easier to find and fix any remaining snapping bugs
* Inkscape now also snaps perpendicularly and tangentialy to paths, when creating paths in the pen tool, when dragging nodes, or when manipulating guides. Newly created guides (dragged off the ruler) will snap perpendicularly or tangentialy to any curve that is being snapped to. Two checkboxes have been added to the document properties dialog (on the snapping tab). Please note that snapping perpendicularly or tangetialy will not work in the selector tool when transforming an object or a selection of objects.
* Intersections of paths and guides can now be snapped to too
* Snapping has been implemented fully for transforming selections of multiple nodes in the node tool
* Snapping to text anchors and baselines has been implemented properly
* If one has chosen for only snapping the snap source closest to the mouse pointer, then the tab key can be used to cycle to the next closest snap source

==Notable bug fixes==
Notable bug fixes since last bug fix release ([[Release notes/0.48.3|0.48.3]]):
* Relative image paths are no longer stored as absolute (regression introduced with [[Release notes/0.47|0.47]]).
* Many rendering glitches were fixed.
* The rendering of the stroke on transformed objects now matches the SVG specification.
* Values entered in the numeric input boxes for the selector tool (X/Y/width/height) are much more accurately applied.

==Known issues==
* The Cairo library used in the new renderer does not implement downscaling, which causes large bitmaps to be pixelated on export. [https://bugs.launchpad.net/inkscape/+bug/804162]

==Previous releases==
* [[Release notes/0.48]] ([[Release notes/0.48.1 |0.48.1]], [[Release notes/0.48.2 | 0.48.2]], [[Release notes/0.48.3 | 0.48.3]])
* [[Release notes/0.47]]
* [[Release notes/0.46]]
* [[Release notes/0.45]]
* [[Release notes/0.44]]
* [[Release notes/0.43]]
* [[Release notes/0.42]]
* [[Release notes/0.41]]
* [[Release notes/0.40]]
* [[Release notes/0.39]]
* [[Release notes/0.38]]
* [[Release notes/0.37]]
* [[Release notes/0.36]]
* [[Release notes/0.35]]

[[Category:Marketing]]

Release notes/0.91

2012-03-22T07:39:02Z

Kris: /* New */

==Inkscape 0.49==

'''(not released yet - [[AnnouncePlanning049]])'''

==Release highlights==

* Cairo rendering for display and PNG export
* OpenMP multithreading for all filters

==Rendering and performance==

Inkscape 0.49 includes a new renderer based on the Cairo library. This work was done during Google Summer of Code 2010 and 2011 projects.
* '''Improved performance.''' The new renderer is significantly faster on most drawings. Renderings of the most complex objects are automatically cached to improve responsiveness during editing.
* '''OpenMP multithreading for filters.''' Filters use all available processor cores for computation. This results in substantial speedups when editing drawings containing large filtered objects on multi-core systems.
* '''Substantial memory savings.''' Inkscape now uses less memory when opening complex drawings, in some cases using only 25% of the memory used by Inkscape 0.48. Larger files can now be opened.
* '''Responsiveness improvements.''' The rendering of the SVG drawing is now cached. This results in massive improvements in responsiveness of path highlights, object selection / deselection, and path editing in delayed update mode.
* '''Rendering bug fixes.''' Most of the rendering glitches in our bug tracker are no longer present in Inkscape 0.49. The following things now render correctly:
** Pattern fills (no more gaps between tiles, regardless of transformation)
** Stroke of transformed objects in patterns
** Patterns containing clipped objects
** Nested clipping paths
** Masked and clipped objects with large masks / clipping paths in Outline view
** Paths with wide strokes and long miters

==Tools==

=== Selector tool ===

It is now easier to select items which are not at the top of the Z-order: use Alt+mouse wheel scroll to cycle through all items that are stacked on top of each other at the location of the mouse pointer (use Shift+Alt+mouse wheel scroll to add to the existing selection). At present, groups are not honoured, i.e., only individual items within groups are considered.

=== Node tool ===
The Node tool's toolbar features new buttons to insert new knots on the selected path segments' extreme values. Click the dropdown arrow next to the insert knots button.

=== Align and distribute dialog ===
New "Exchange position of selected objects" feature. It adds three buttons in the Align and Distribute dialog (rearrange group) that exchange the positions of the selected objects: 1. according to the selection order, 2. according to the Z-order, and 3. clockwise.

===Live Path Effects===

The object's Live Path Effects are now forked upon object duplication.

====PowerStroke====
Here a list of the current state. Note that this is very much work in progress and '''anything can change'''. I think this is the most efficient place of keeping track how the powerstroke LPE works.
* stroke knots are purple diamonds
* when first applied, 3 stroke knots are added one at start, one at end, one somewhere in the middle along the path.
* adding nodes: Ctrl+click purple knot, unselect object, reselect it.
* deleting nodes: Ctrl+Alt+click purple knot, unselect object, reselect it.
* "sort points" reorders the stroke knots according to where they lie along the path (where they are closest to the path), instead of keeping them in original order.

[http://imgh.us/powerstroke-ell.png example screenshot]

====Clone original====
The Clone original LPE ignores the path data of the path it has been applied to; instead, it '''copies the original-d path data''', i.e. the path data before LPE calculation, from the path linked to by the Linked path parameter.

The Clone original LPE is made to be used in conjunction with powerstroke. Powerstroke creates a path with a variable stroke, but this path can then not be filled (because the fill is used as the stroke). To fill a powerstroked path, one must create a second path (dummy path), apply the Clone original LPE and link it to the powerstroked path. Because this second path clones the original path data before the Powerstroke LPE, it can be used to fill the powerstroked path.
To quickly create a dummy path and apply this effect, one can select the path to 'clone' and click the menu item '''Edit > Clone > Clone original path (LPE)'''.

Like for normal clones, pressing Shift+D, when the selected path has the Clone original LPE applied, selects the path referred to by the LPE.

===Filters===
The new Custom predefined filters allow users to create predefined filters with custom parameters. See [[SpecCustomPredefinedFilters]].

==Import/Export==
* New Flash XML Graphics (FXG) export format.
* New Synfig Animation Studio (SIF) export format.
* XAML export improvements.
* Compressed SVG and media export extension improvements. New options: set an image directory in the zip file, and add a text file that lists the fonts used in the SVG document.
* New preference to allow users to always link, embed or ask when importing bitmaps.

===Gimp XCF improvements===
* The "Save Background" option allows users to choose if the page background is saved with each Gimp layer.
* The exported layers now use the label attribute or, if not set, the id attribute.
* New help tab.
* Some bugs and warnings fixed.

===PDF/EPS/PS + LaTeX===
* Added the possibility of scaling the image. The 'calc' package must be included in the preamble. Then the image can be scaled by defining '\svgscale' instead of '\svgwidth'.
* The font shape is now also exported. '\textit{}' for italic text, '\textbf{}' for bold text, and '\textsl{}' (slanted) for oblique text. It is important to note that '''Arial''' has an '''oblique''' font shape and not '''italic''', so the result in LaTeX will be '''slanted instead of italic'''. It is better to '''use another font''' in Inkscape when you want true italics.

==Extensions==
===New===
* The new guillotine extension is used for exporting png slices from a drawing. The slice rectangles are defined by adding horizontal and vertical guides within the canvas boundary, the canvas boundary serves as the outside of the sliced area.
* The new [http://en.wikipedia.org/wiki/G-code G-code] tools extension converts paths to G-code (using circular interpolation), makes offset paths and engraves sharp corners using cone cutters.
* New [http://en.wikipedia.org/wiki/QR_code QR code] generator
* New isometric grid generator
* New bitmap crop extension (Extensions>Bitmaps>Crop)
* New "Extract text" extension outputs the text elements of the document in a chosen order.

===Improvements===
* Number nodes. New parameters allowing users to choose the starting dot number and the numbering step between two nodes.
* Color Markers to Match Stroke extension improvements. The markers can now inherit the fill and stroke colors and alpha channels from the object, or be customized with color selectors in a separate tab.
* Optional sliders added on float and int extension parameters (full and minimal modes).
* Extension parameters values (''except attributes!'') can now be contextualized for translation (with msgctxt).

==User interface==
*The interface elements are accessible through the keyboard with ALT+key in many more dialogs.
*Ability to set the canvas background color without exporting it (background transparency is only used for export but not the canvas).
*The following dialogs are now also dockable: "Object properties", "Object attributes", "Text and Font", "Check spelling", "Export bitmap", and "XML editor".
*New preference to allow Windows users to choose between native and Gtk open/save dialog.
*Preferences dialog cleanup.

===Menus===
"Text and Font", "Fill and Stroke", and "Check Spelling" dialogs are added to the text object context menu (right click).

===Simple calculations in spinboxes===
In most spinboxes (a spinbox is an entry field with up and down "spinbuttons" next to it) you can now write simple calculations. For example: "2 * 3", "50 + 100", or "((12 + 34) * (5 + 5) - 2) / 2".
Moreover, you can use units in entering values, like "2 + 2 cm". The result will be converted to the selected unit for the particular entry.

==Translations==
* The ''Keyboard and mouse reference'' (inkscape-docs project) and color palettes' labels are now translatable.
* New UI translation in Latvian.
* New tutorial translations in Galician and Greek.
* New man pages in Chinese (zh_TW) Greek (el), Japanese (ja) and Slovak (sk), and updated French translation. ''[Galician (gl) and Polish (pl) in progress]''
* Man pages now use PO files for translation (inkscape-docs project).
* The tutorial generation system now fully supports RTL languages.

==SVG Support==

* The <tt>clip-rule</tt> property is now supported. No UI to set it exists at the moment, other than the XML editor.

== Snapping ==
* The snapping preferences and the snap toolbar have been reworked, both in the underlying code as well as in the GUI. This should make the snapping preferences easier to understand, easier to maintain, and make it easier to find and fix any remaining snapping bugs
* Inkscape now also snaps perpendicularly and tangentialy to paths, when creating paths in the pen tool, when dragging nodes, or when manipulating guides. Newly created guides (dragged off the ruler) will snap perpendicularly or tangentialy to any curve that is being snapped to. Two checkboxes have been added to the document properties dialog (on the snapping tab). Please note that snapping perpendicularly or tangetialy will not work in the selector tool when transforming an object or a selection of objects.
* Intersections of paths and guides can now be snapped to too
* Snapping has been implemented fully for transforming selections of multiple nodes in the node tool
* Snapping to text anchors and baselines has been implemented properly
* If one has chosen for only snapping the snap source closest to the mouse pointer, then the tab key can be used to cycle to the next closest snap source

==Notable bug fixes==
Notable bug fixes since last bug fix release ([[Release notes/0.48.3|0.48.3]]):
* Relative image paths are no longer stored as absolute (regression introduced with [[Release notes/0.47|0.47]]).
* Many rendering glitches were fixed.
* The rendering of the stroke on transformed objects now matches the SVG specification.
* Values entered in the numeric input boxes for the selector tool (X/Y/width/height) are much more accurately applied.

==Known issues==

==Previous releases==
* [[ReleaseNotes048]] ([[Release notes/0.48.1 |0.48.1]], [[Release notes/0.48.2 | 0.48.2]], [[Release notes/0.48.3 | 0.48.3]])
* [[ReleaseNotes047]]
* [[ReleaseNotes046]]
* [[ReleaseNotes045]]
* [[ReleaseNotes044]]
* [[ReleaseNotes043]]
* [[ReleaseNotes042]]
* [[ReleaseNotes041]]
* [[ReleaseNotes040]]
* [[ReleaseNotes039]]
* [[ReleaseNotes038]]
* [[ReleaseNotes037]]
* [[ReleaseNotes036]]
* [[ReleaseNotes035]]

[[Category:Marketing]]

Release notes/0.91

2012-03-22T07:35:33Z

Kris: /* Translations */

==Inkscape 0.49==

'''(not released yet - [[AnnouncePlanning049]])'''

==Release highlights==

* Cairo rendering for display and PNG export
* OpenMP multithreading for all filters

==Rendering and performance==

Inkscape 0.49 includes a new renderer based on the Cairo library. This work was done during Google Summer of Code 2010 and 2011 projects.
* '''Improved performance.''' The new renderer is significantly faster on most drawings. Renderings of the most complex objects are automatically cached to improve responsiveness during editing.
* '''OpenMP multithreading for filters.''' Filters use all available processor cores for computation. This results in substantial speedups when editing drawings containing large filtered objects on multi-core systems.
* '''Substantial memory savings.''' Inkscape now uses less memory when opening complex drawings, in some cases using only 25% of the memory used by Inkscape 0.48. Larger files can now be opened.
* '''Responsiveness improvements.''' The rendering of the SVG drawing is now cached. This results in massive improvements in responsiveness of path highlights, object selection / deselection, and path editing in delayed update mode.
* '''Rendering bug fixes.''' Most of the rendering glitches in our bug tracker are no longer present in Inkscape 0.49. The following things now render correctly:
** Pattern fills (no more gaps between tiles, regardless of transformation)
** Stroke of transformed objects in patterns
** Patterns containing clipped objects
** Nested clipping paths
** Masked and clipped objects with large masks / clipping paths in Outline view
** Paths with wide strokes and long miters

==Tools==

=== Selector tool ===

It is now easier to select items which are not at the top of the Z-order: use Alt+mouse wheel scroll to cycle through all items that are stacked on top of each other at the location of the mouse pointer (use Shift+Alt+mouse wheel scroll to add to the existing selection). At present, groups are not honoured, i.e., only individual items within groups are considered.

=== Node tool ===
The Node tool's toolbar features new buttons to insert new knots on the selected path segments' extreme values. Click the dropdown arrow next to the insert knots button.

=== Align and distribute dialog ===
New "Exchange position of selected objects" feature. It adds three buttons in the Align and Distribute dialog (rearrange group) that exchange the positions of the selected objects: 1. according to the selection order, 2. according to the Z-order, and 3. clockwise.

===Live Path Effects===

The object's Live Path Effects are now forked upon object duplication.

====PowerStroke====
Here a list of the current state. Note that this is very much work in progress and '''anything can change'''. I think this is the most efficient place of keeping track how the powerstroke LPE works.
* stroke knots are purple diamonds
* when first applied, 3 stroke knots are added one at start, one at end, one somewhere in the middle along the path.
* adding nodes: Ctrl+click purple knot, unselect object, reselect it.
* deleting nodes: Ctrl+Alt+click purple knot, unselect object, reselect it.
* "sort points" reorders the stroke knots according to where they lie along the path (where they are closest to the path), instead of keeping them in original order.

[http://imgh.us/powerstroke-ell.png example screenshot]

====Clone original====
The Clone original LPE ignores the path data of the path it has been applied to; instead, it '''copies the original-d path data''', i.e. the path data before LPE calculation, from the path linked to by the Linked path parameter.

The Clone original LPE is made to be used in conjunction with powerstroke. Powerstroke creates a path with a variable stroke, but this path can then not be filled (because the fill is used as the stroke). To fill a powerstroked path, one must create a second path (dummy path), apply the Clone original LPE and link it to the powerstroked path. Because this second path clones the original path data before the Powerstroke LPE, it can be used to fill the powerstroked path.
To quickly create a dummy path and apply this effect, one can select the path to 'clone' and click the menu item '''Edit > Clone > Clone original path (LPE)'''.

Like for normal clones, pressing Shift+D, when the selected path has the Clone original LPE applied, selects the path referred to by the LPE.

===Filters===
The new Custom predefined filters allow users to create predefined filters with custom parameters. See [[SpecCustomPredefinedFilters]].

==Import/Export==
* New Flash XML Graphics (FXG) export format.
* New Synfig Animation Studio (SIF) export format.
* XAML export improvements.
* Compressed SVG and media export extension improvements. New options: set an image directory in the zip file, and add a text file that lists the fonts used in the SVG document.
* New preference to allow users to always link, embed or ask when importing bitmaps.

===Gimp XCF improvements===
* The "Save Background" option allows users to choose if the page background is saved with each Gimp layer.
* The exported layers now use the label attribute or, if not set, the id attribute.
* New help tab.
* Some bugs and warnings fixed.

===PDF/EPS/PS + LaTeX===
* Added the possibility of scaling the image. The 'calc' package must be included in the preamble. Then the image can be scaled by defining '\svgscale' instead of '\svgwidth'.
* The font shape is now also exported. '\textit{}' for italic text, '\textbf{}' for bold text, and '\textsl{}' (slanted) for oblique text. It is important to note that '''Arial''' has an '''oblique''' font shape and not '''italic''', so the result in LaTeX will be '''slanted instead of italic'''. It is better to '''use another font''' in Inkscape when you want true italics.

==Extensions==
===New===
* The new guillotine extension is used for exporting png slices from a drawing. The slice rectangles are defined by adding horizontal and vertical guides within the canvas boundary, the canvas boundary serves as the outside of the sliced area.
* The new [http://en.wikipedia.org/wiki/G-code G-code] tools extension converts paths to G-code (using circular interpolation), makes offset paths and engraves sharp corners using cone cutters.
* New [http://en.wikipedia.org/wiki/QR_code QR code] generator.
* New isometric grid generator.
* New bitmap crop extension (Extensions>Bitmaps>Crop).
* The new Extract text extension output the text elements of the document in a chosen order.

===Improvements===
* Number nodes. New parameters allowing users to choose the starting dot number and the numbering step between two nodes.
* Color Markers to Match Stroke extension improvements. The markers can now inherit the fill and stroke colors and alpha channels from the object, or be customized with color selectors in a separate tab.
* Optional sliders added on float and int extension parameters (full and minimal modes).
* Extension parameters values (''except attributes!'') can now be contextualized for translation (with msgctxt).

==User interface==
*The interface elements are accessible through the keyboard with ALT+key in many more dialogs.
*Ability to set the canvas background color without exporting it (background transparency is only used for export but not the canvas).
*The following dialogs are now also dockable: "Object properties", "Object attributes", "Text and Font", "Check spelling", "Export bitmap", and "XML editor".
*New preference to allow Windows users to choose between native and Gtk open/save dialog.
*Preferences dialog cleanup.

===Menus===
"Text and Font", "Fill and Stroke", and "Check Spelling" dialogs are added to the text object context menu (right click).

===Simple calculations in spinboxes===
In most spinboxes (a spinbox is an entry field with up and down "spinbuttons" next to it) you can now write simple calculations. For example: "2 * 3", "50 + 100", or "((12 + 34) * (5 + 5) - 2) / 2".
Moreover, you can use units in entering values, like "2 + 2 cm". The result will be converted to the selected unit for the particular entry.

==Translations==
* The ''Keyboard and mouse reference'' (inkscape-docs project) and color palettes' labels are now translatable.
* New UI translation in Latvian.
* New tutorial translations in Galician and Greek.
* New man pages in Chinese (zh_TW) Greek (el), Japanese (ja) and Slovak (sk), and updated French translation. ''[Galician (gl) and Polish (pl) in progress]''
* Man pages now use PO files for translation (inkscape-docs project).
* The tutorial generation system now fully supports RTL languages.

==SVG Support==

* The <tt>clip-rule</tt> property is now supported. No UI to set it exists at the moment, other than the XML editor.

== Snapping ==
* The snapping preferences and the snap toolbar have been reworked, both in the underlying code as well as in the GUI. This should make the snapping preferences easier to understand, easier to maintain, and make it easier to find and fix any remaining snapping bugs
* Inkscape now also snaps perpendicularly and tangentialy to paths, when creating paths in the pen tool, when dragging nodes, or when manipulating guides. Newly created guides (dragged off the ruler) will snap perpendicularly or tangentialy to any curve that is being snapped to. Two checkboxes have been added to the document properties dialog (on the snapping tab). Please note that snapping perpendicularly or tangetialy will not work in the selector tool when transforming an object or a selection of objects.
* Intersections of paths and guides can now be snapped to too
* Snapping has been implemented fully for transforming selections of multiple nodes in the node tool
* Snapping to text anchors and baselines has been implemented properly
* If one has chosen for only snapping the snap source closest to the mouse pointer, then the tab key can be used to cycle to the next closest snap source

==Notable bug fixes==
Notable bug fixes since last bug fix release ([[Release notes/0.48.3|0.48.3]]):
* Relative image paths are no longer stored as absolute (regression introduced with [[Release notes/0.47|0.47]]).
* Many rendering glitches were fixed.
* The rendering of the stroke on transformed objects now matches the SVG specification.
* Values entered in the numeric input boxes for the selector tool (X/Y/width/height) are much more accurately applied.

==Known issues==

==Previous releases==
* [[ReleaseNotes048]] ([[Release notes/0.48.1 |0.48.1]], [[Release notes/0.48.2 | 0.48.2]], [[Release notes/0.48.3 | 0.48.3]])
* [[ReleaseNotes047]]
* [[ReleaseNotes046]]
* [[ReleaseNotes045]]
* [[ReleaseNotes044]]
* [[ReleaseNotes043]]
* [[ReleaseNotes042]]
* [[ReleaseNotes041]]
* [[ReleaseNotes040]]
* [[ReleaseNotes039]]
* [[ReleaseNotes038]]
* [[ReleaseNotes037]]
* [[ReleaseNotes036]]
* [[ReleaseNotes035]]

[[Category:Marketing]]

MacromediaFreehand

2012-03-16T06:22:01Z

Kris: Reverted edits by Garcia (talk) to last revision by Colin Marquardt

Please post links to screenshots and/or criticism of this vector drawing application.

==About Macromedia Freehand==

Freehand is a quality-leading vectorial editor, early develpment started from Aldus (early than 1990) from the postscript boom of 80's

Versions 1 to 3 were targeted to 1 page documents Versions since 4 allows multiple page over one drawing table (allowing us to see all pages just from zooming out) MacromediaMX (11) seems to be the actual version, and very targeted to .swf and web development.

Macromedia has been bought by Adobe in 2006.

== Reviews ==

A review specifically comparing Inkscape 0.42.2 and FreeHand MXA: [http://mikesalsbury.com/mambo/content/view/231/1/]

The most effective site which covers Macromedia Freehand is [http://www.freehandsource.com/ The Freehand Source]. (It is also a proof-by-example that Flash can be used on the Web). Whilst the author admits a little bias with such phrases as "ode to a fantastic program I've grown to love over the years", it really is a wart and all look at the program in its many versions. The (framed) pages on Tips, and Bugs are probably the most useful, but the whole site is worth looking at.

See [http://www.atpm.com/7.07/freehand.shtml Review: FreeHand 10], though this might contain too little information to be useful.

Note that Macromedia never really took the trouble to encourage invisible or unsanctioned copying of this product, and there are few if any plug-ins for it, nor many good books. I doubt that after the early nineties many youngsters chose or were exposed to it. Further a Google search containing the term 'Freehand' will (in general) take you to many pages with the phrase 'Freehand Tool' or 'Freehand Technique' that often are about Illustrator.

I have found Freehand to be good for doing precise work (such as charts, maps and diagrams), and also good for people with limited artistic skills; Whilst you will find a few artists who like Freehand, you only have to watch a talented person using Illustrator to realise how good that program is, if you have good drawing skills. Also, the concrete interface to Illustrator is now an excellent match to Photoshop.

Whilst there are many individual features of Freehand that are superior, and ought to be incorporated into Inkscape, I suggest that the history of this program and its current state, is a lesson in how not to run a business unit. Having said that, Freehand has missed most opportunities for bloat, and its feature set is no greater than its loyal customers actually use, it has an excellent reputation for the quality of its Postscript output - though I suspect that Illustrator has caught up (if it were ever behind), and its file format, though binary, has allowed Macromedia's developers to produce a program which handles a lot of metadata for each object.

# The Generic pointer tool is small and neat
# Selection markers are unobtrusive
# Envelopes are only shown on request

== Features ==
* Inset Tool (see below)

== Screenshots ==

[http://images.google.com/images?q=Freehand&btnG=Google+Search Google Image Search:Freehand]

[http://www.vecpix.com/tutorials/freehand/images/fh006/chrome12.gif Freehand Inset Tool] taken from a [http://www.vecpix.com/tutorials/freehand/fh006.php Freehand tutorial] (and another [http://www.webdersleri.com/sayfa.asp?id=708&mode=print tutorial on using Inset])

Please add more...

== User Interface ==

[http://davitjcc.tripod.com/fh10info.html Macintosh Keyboard Shortcuts for FreeHand]

== Offical Links and General Information ==

[http://www.macromedia.com/software/freehand/ Macromedia Freehand Official web site]

[http://en.wikipedia.org/wiki/Macromedia_Freehand Macromedia Freehand at Wikipedia]

== See Also ==

Macromedia Freehand is the product most directly relevant to Inkscape but we can also learn from Macromedia Fireworks and [[MacromediaFlash]] which all seem to be funadmentally very vector orientated software.

[[Category:Developer Discussion]]
[[Category:Other Software]]

File:Tutorial-paintbucket-optionsscreenshot.png

2012-03-14T19:42:13Z

Kris: Correctly scaled version of thumb

Correctly scaled version of [[File:Tutorial-paintbucket-optionsscreenshot.svg|thumb]]

Scratchpad paintbuckettutorial

2012-03-14T19:41:28Z

Kris: /* Paint Bucket's control bar options */

{{Tutorial_scratchpad_header}}

=Title=
Paint Bucket Tool

=Author(s)=
ryan lerch, ryanlerch at gmail dot com
=Abstract=
This tutorial covers the use of the Paint Bucket tool and it's options. The paint bucket tool was an addition to Inkscape in release 0.46.
=Body=
==Basics==
The paint bucket tool allows a fully bounded area to be quickly traced and generates a path that "fills in" that area. This tool is especially useful when "inking" line drawings; On the following example (it is one path that was traced from a bitmap) try using the paint bucket tool to fill in his hair and his face:

[[File:Paintbuckettutorial-happyguy.svg|thumb|center]] 

After using the paint bucket tool to "fill" the hair and the face, the result should look something like this:

[[File:Paintbuckettutorial-happyguycolor.svg|thumb|center]] 

The drawing now has 3 paths (the original, the path of the hair color and the path of the face color.) It is important to note that the paint bucket does not change the fill property of any object in the document, it merely creates a new path to represent the "fill".

==How the paint bucket tool works==
the majority of this text was taken from the release notes...

The paint bucket tool works by performing a bitmap-based flood fill on a rendered version of the visible canvas it then traces the resulting fill and places the traced path into the document.

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.

==Using the paint bucket tool==
this text was taken from the release notes...
* '''Single click''' performs filling from the click point.
[[File:Tutorial-paintbucket-clickonce.svg|thumb|center|300px]] 

* '''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.
[[File:Tutorial-paintbucket-shiftclick.png|thumb|center|300px]] 

* '''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.
[[File:Tutorial-paintbucket-clickdrag.png|thumb|center|300px]] 

* '''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.
[[File:Tutorial-paintbucket-altdrag.png|thumb|center|300px]] 

==Paint Bucket's control bar options==
There are several options that allow the use of the paint bucket to be refined. Below is a screen shot of the tool's options that are displayed in the control bar.

[[File:Tutorial-paintbucket-optionsscreenshot.png|thumb|center|500px]] 

# Color Channels
# Threshold
The threshold option is used to control if a colour is determine to be the same or not. A threshold setting of 0 means that only the exact same colour is considered the same, whereas a setting of 100 means that every colour is viewed as being the same. For diagrams and technical drawings a setting of 0 is often used, whereas in artistic work a higher setting ~ 20-30 is not uncommon.
# Grow/Shrink amount
# Grow/Shrink units
Grow and shrink is used mainly to make up for a lack of autocracy of the paint bucket fill. Often the paint bucket fill will not completely fill a region so by growing the fill region to cover a larger area the gaps will be filled in and no longer noticeable once placed behind the edge objects.

Interesting visual effects can be created by shrinking the fill area and by using multiple fills and strokes or colours.

# Auto Gap setting

Some gapes in an outline will not be visible to the human eye, but will cause the area not to be bounded. One method to fix this is to zoom out, therefore hiding the gap to the computer, but meaning the fill will be less accurate.
The auto gap setting is used to fill a gap of 1 to ~ 8 pixels so that the gap is ignored and the area is filled despite the break in the surrounding objects

# Reset to defaults
# Style swatch
is used to show the fill style that is about to be used

Scratchpad paintbuckettutorial

2012-03-14T19:37:11Z

Kris: /* Paint Bucket's control bar options */

{{Tutorial_scratchpad_header}}

=Title=
Paint Bucket Tool

=Author(s)=
ryan lerch, ryanlerch at gmail dot com
=Abstract=
This tutorial covers the use of the Paint Bucket tool and it's options. The paint bucket tool was an addition to Inkscape in release 0.46.
=Body=
==Basics==
The paint bucket tool allows a fully bounded area to be quickly traced and generates a path that "fills in" that area. This tool is especially useful when "inking" line drawings; On the following example (it is one path that was traced from a bitmap) try using the paint bucket tool to fill in his hair and his face:

[[File:Paintbuckettutorial-happyguy.svg|thumb|center]] 

After using the paint bucket tool to "fill" the hair and the face, the result should look something like this:

[[File:Paintbuckettutorial-happyguycolor.svg|thumb|center]] 

The drawing now has 3 paths (the original, the path of the hair color and the path of the face color.) It is important to note that the paint bucket does not change the fill property of any object in the document, it merely creates a new path to represent the "fill".

==How the paint bucket tool works==
the majority of this text was taken from the release notes...

The paint bucket tool works by performing a bitmap-based flood fill on a rendered version of the visible canvas it then traces the resulting fill and places the traced path into the document.

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.

==Using the paint bucket tool==
this text was taken from the release notes...
* '''Single click''' performs filling from the click point.
[[File:Tutorial-paintbucket-clickonce.svg|thumb|center|300px]] 

* '''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.
[[File:Tutorial-paintbucket-shiftclick.png|thumb|center|300px]] 

* '''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.
[[File:Tutorial-paintbucket-clickdrag.png|thumb|center|300px]] 

* '''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.
[[File:Tutorial-paintbucket-altdrag.png|thumb|center|300px]] 

==Paint Bucket's control bar options==
There are several options that allow the use of the paint bucket to be refined. Below is a screen shot of the tool's options that are displayed in the control bar.

[[File:Tutorial-paintbucket-optionsscreenshot.svg|thumb|center|500px]] 

# Color Channels
# Threshold
The threshold option is used to control if a colour is determine to be the same or not. A threshold setting of 0 means that only the exact same colour is considered the same, whereas a setting of 100 means that every colour is viewed as being the same. For diagrams and technical drawings a setting of 0 is often used, whereas in artistic work a higher setting ~ 20-30 is not uncommon.
# Grow/Shrink amount
# Grow/Shrink units
Grow and shrink is used mainly to make up for a lack of autocracy of the paint bucket fill. Often the paint bucket fill will not completely fill a region so by growing the fill region to cover a larger area the gaps will be filled in and no longer noticeable once placed behind the edge objects.

Interesting visual effects can be created by shrinking the fill area and by using multiple fills and strokes or colours.

# Auto Gap setting

Some gapes in an outline will not be visible to the human eye, but will cause the area not to be bounded. One method to fix this is to zoom out, therefore hiding the gap to the computer, but meaning the fill will be less accurate.
The auto gap setting is used to fill a gap of 1 to ~ 8 pixels so that the gap is ignored and the area is filled despite the break in the surrounding objects

# Reset to defaults
# Style swatch
is used to show the fill style that is about to be used

File:Tutorial-paintbucket-altdrag.png

2012-03-14T19:34:14Z

Kris: Correctly scaled version of thumb

Correctly scaled version of [[File:Tutorial-paintbucket-altdrag.svg|thumb]]

Scratchpad paintbuckettutorial

2012-03-14T19:32:37Z

Kris: /* Using the paint bucket tool */ let's do it this way :-(

{{Tutorial_scratchpad_header}}

=Title=
Paint Bucket Tool

=Author(s)=
ryan lerch, ryanlerch at gmail dot com
=Abstract=
This tutorial covers the use of the Paint Bucket tool and it's options. The paint bucket tool was an addition to Inkscape in release 0.46.
=Body=
==Basics==
The paint bucket tool allows a fully bounded area to be quickly traced and generates a path that "fills in" that area. This tool is especially useful when "inking" line drawings; On the following example (it is one path that was traced from a bitmap) try using the paint bucket tool to fill in his hair and his face:

[[File:Paintbuckettutorial-happyguy.svg|thumb|center]] 

After using the paint bucket tool to "fill" the hair and the face, the result should look something like this:

[[File:Paintbuckettutorial-happyguycolor.svg|thumb|center]] 

The drawing now has 3 paths (the original, the path of the hair color and the path of the face color.) It is important to note that the paint bucket does not change the fill property of any object in the document, it merely creates a new path to represent the "fill".

==How the paint bucket tool works==
the majority of this text was taken from the release notes...

The paint bucket tool works by performing a bitmap-based flood fill on a rendered version of the visible canvas it then traces the resulting fill and places the traced path into the document.

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.

==Using the paint bucket tool==
this text was taken from the release notes...
* '''Single click''' performs filling from the click point.
[[File:Tutorial-paintbucket-clickonce.svg|thumb|center|300px]] 

* '''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.
[[File:Tutorial-paintbucket-shiftclick.png|thumb|center|300px]] 

* '''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.
[[File:Tutorial-paintbucket-clickdrag.png|thumb|center|300px]] 

* '''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.
[[File:Tutorial-paintbucket-altdrag.png|thumb|center|300px]] 

==Paint Bucket's control bar options==
There are several options that allow the use of the paint bucket to be refined. Below is a screen shot of the tool's options that are displayed in the control bar.

[[File:Tutorial-paintbucket-optionsscreenshot.svg|thumb|center]] 

# Color Channels
# Threshold
The threshold option is used to control if a colour is determine to be the same or not. A threshold setting of 0 means that only the exact same colour is considered the same, whereas a setting of 100 means that every colour is viewed as being the same. For diagrams and technical drawings a setting of 0 is often used, whereas in artistic work a higher setting ~ 20-30 is not uncommon.
# Grow/Shrink amount
# Grow/Shrink units
Grow and shrink is used mainly to make up for a lack of autocracy of the paint bucket fill. Often the paint bucket fill will not completely fill a region so by growing the fill region to cover a larger area the gaps will be filled in and no longer noticeable once placed behind the edge objects.

Interesting visual effects can be created by shrinking the fill area and by using multiple fills and strokes or colours.

# Auto Gap setting

Some gapes in an outline will not be visible to the human eye, but will cause the area not to be bounded. One method to fix this is to zoom out, therefore hiding the gap to the computer, but meaning the fill will be less accurate.
The auto gap setting is used to fill a gap of 1 to ~ 8 pixels so that the gap is ignored and the area is filled despite the break in the surrounding objects

# Reset to defaults
# Style swatch
is used to show the fill style that is about to be used

File:Tutorial-paintbucket-clickdrag.png

2012-03-14T19:32:05Z

Kris: Correctly scaled version of thumb

Correctly scaled version of [[File:Tutorial-paintbucket-clickdrag.svg|thumb]]

Scratchpad paintbuckettutorial

2012-03-14T19:30:18Z

Kris: /* Using the paint bucket tool */ let's do it this way :-(

{{Tutorial_scratchpad_header}}

=Title=
Paint Bucket Tool

=Author(s)=
ryan lerch, ryanlerch at gmail dot com
=Abstract=
This tutorial covers the use of the Paint Bucket tool and it's options. The paint bucket tool was an addition to Inkscape in release 0.46.
=Body=
==Basics==
The paint bucket tool allows a fully bounded area to be quickly traced and generates a path that "fills in" that area. This tool is especially useful when "inking" line drawings; On the following example (it is one path that was traced from a bitmap) try using the paint bucket tool to fill in his hair and his face:

[[File:Paintbuckettutorial-happyguy.svg|thumb|center]] 

After using the paint bucket tool to "fill" the hair and the face, the result should look something like this:

[[File:Paintbuckettutorial-happyguycolor.svg|thumb|center]] 

The drawing now has 3 paths (the original, the path of the hair color and the path of the face color.) It is important to note that the paint bucket does not change the fill property of any object in the document, it merely creates a new path to represent the "fill".

==How the paint bucket tool works==
the majority of this text was taken from the release notes...

The paint bucket tool works by performing a bitmap-based flood fill on a rendered version of the visible canvas it then traces the resulting fill and places the traced path into the document.

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.

==Using the paint bucket tool==
this text was taken from the release notes...
* '''Single click''' performs filling from the click point.
[[File:Tutorial-paintbucket-clickonce.svg|thumb|center|300px]] 

* '''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.
[[File:Tutorial-paintbucket-shiftclick.png|thumb|center|300px]] 

* '''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.
[[File:Tutorial-paintbucket-clickdrag.png|thumb|center|300px]] 

* '''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.
[[File:Tutorial-paintbucket-altdrag.svg|thumb|center]] 

==Paint Bucket's control bar options==
There are several options that allow the use of the paint bucket to be refined. Below is a screen shot of the tool's options that are displayed in the control bar.

[[File:Tutorial-paintbucket-optionsscreenshot.svg|thumb|center]] 

# Color Channels
# Threshold
The threshold option is used to control if a colour is determine to be the same or not. A threshold setting of 0 means that only the exact same colour is considered the same, whereas a setting of 100 means that every colour is viewed as being the same. For diagrams and technical drawings a setting of 0 is often used, whereas in artistic work a higher setting ~ 20-30 is not uncommon.
# Grow/Shrink amount
# Grow/Shrink units
Grow and shrink is used mainly to make up for a lack of autocracy of the paint bucket fill. Often the paint bucket fill will not completely fill a region so by growing the fill region to cover a larger area the gaps will be filled in and no longer noticeable once placed behind the edge objects.

Interesting visual effects can be created by shrinking the fill area and by using multiple fills and strokes or colours.

# Auto Gap setting

Some gapes in an outline will not be visible to the human eye, but will cause the area not to be bounded. One method to fix this is to zoom out, therefore hiding the gap to the computer, but meaning the fill will be less accurate.
The auto gap setting is used to fill a gap of 1 to ~ 8 pixels so that the gap is ignored and the area is filled despite the break in the surrounding objects

# Reset to defaults
# Style swatch
is used to show the fill style that is about to be used

File:Tutorial-paintbucket-shiftclick.png

2012-03-14T19:29:40Z

Kris: typo

Correctly scaled version of [[File:Tutorial-paintbucket-shiftclick.svg|thumb]]

File:Tutorial-paintbucket-shiftclick.png

2012-03-14T19:28:55Z

Kris: Correctly scaled version of thumb

Correctly scaled version of [[File:Tutorial-paintbucket-shiftclick.png|thumb]]

Scratchpad paintbuckettutorial

2012-03-14T19:27:34Z

Kris: /* Using the paint bucket tool */ let's do it this way :-(

{{Tutorial_scratchpad_header}}

=Title=
Paint Bucket Tool

=Author(s)=
ryan lerch, ryanlerch at gmail dot com
=Abstract=
This tutorial covers the use of the Paint Bucket tool and it's options. The paint bucket tool was an addition to Inkscape in release 0.46.
=Body=
==Basics==
The paint bucket tool allows a fully bounded area to be quickly traced and generates a path that "fills in" that area. This tool is especially useful when "inking" line drawings; On the following example (it is one path that was traced from a bitmap) try using the paint bucket tool to fill in his hair and his face:

[[File:Paintbuckettutorial-happyguy.svg|thumb|center]] 

After using the paint bucket tool to "fill" the hair and the face, the result should look something like this:

[[File:Paintbuckettutorial-happyguycolor.svg|thumb|center]] 

The drawing now has 3 paths (the original, the path of the hair color and the path of the face color.) It is important to note that the paint bucket does not change the fill property of any object in the document, it merely creates a new path to represent the "fill".

==How the paint bucket tool works==
the majority of this text was taken from the release notes...

The paint bucket tool works by performing a bitmap-based flood fill on a rendered version of the visible canvas it then traces the resulting fill and places the traced path into the document.

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.

==Using the paint bucket tool==
this text was taken from the release notes...
* '''Single click''' performs filling from the click point.
[[File:Tutorial-paintbucket-clickonce.svg|thumb|center|300px]] 

* '''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.
[[File:Tutorial-paintbucket-shiftclick.png|thumb|center|300px]] 

* '''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.
[[File:Tutorial-paintbucket-clickdrag.svg|thumb|center]] 

* '''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.
[[File:Tutorial-paintbucket-altdrag.svg|thumb|center]] 

==Paint Bucket's control bar options==
There are several options that allow the use of the paint bucket to be refined. Below is a screen shot of the tool's options that are displayed in the control bar.

[[File:Tutorial-paintbucket-optionsscreenshot.svg|thumb|center]] 

# Color Channels
# Threshold
The threshold option is used to control if a colour is determine to be the same or not. A threshold setting of 0 means that only the exact same colour is considered the same, whereas a setting of 100 means that every colour is viewed as being the same. For diagrams and technical drawings a setting of 0 is often used, whereas in artistic work a higher setting ~ 20-30 is not uncommon.
# Grow/Shrink amount
# Grow/Shrink units
Grow and shrink is used mainly to make up for a lack of autocracy of the paint bucket fill. Often the paint bucket fill will not completely fill a region so by growing the fill region to cover a larger area the gaps will be filled in and no longer noticeable once placed behind the edge objects.

Interesting visual effects can be created by shrinking the fill area and by using multiple fills and strokes or colours.

# Auto Gap setting

Some gapes in an outline will not be visible to the human eye, but will cause the area not to be bounded. One method to fix this is to zoom out, therefore hiding the gap to the computer, but meaning the fill will be less accurate.
The auto gap setting is used to fill a gap of 1 to ~ 8 pixels so that the gap is ignored and the area is filled despite the break in the surrounding objects

# Reset to defaults
# Style swatch
is used to show the fill style that is about to be used

Scratchpad paintbuckettutorial

2012-03-14T19:19:35Z

Kris: /* Using the paint bucket tool */

{{Tutorial_scratchpad_header}}

=Title=
Paint Bucket Tool

=Author(s)=
ryan lerch, ryanlerch at gmail dot com
=Abstract=
This tutorial covers the use of the Paint Bucket tool and it's options. The paint bucket tool was an addition to Inkscape in release 0.46.
=Body=
==Basics==
The paint bucket tool allows a fully bounded area to be quickly traced and generates a path that "fills in" that area. This tool is especially useful when "inking" line drawings; On the following example (it is one path that was traced from a bitmap) try using the paint bucket tool to fill in his hair and his face:

[[File:Paintbuckettutorial-happyguy.svg|thumb|center]] 

After using the paint bucket tool to "fill" the hair and the face, the result should look something like this:

[[File:Paintbuckettutorial-happyguycolor.svg|thumb|center]] 

The drawing now has 3 paths (the original, the path of the hair color and the path of the face color.) It is important to note that the paint bucket does not change the fill property of any object in the document, it merely creates a new path to represent the "fill".

==How the paint bucket tool works==
the majority of this text was taken from the release notes...

The paint bucket tool works by performing a bitmap-based flood fill on a rendered version of the visible canvas it then traces the resulting fill and places the traced path into the document.

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.

==Using the paint bucket tool==
this text was taken from the release notes...
* '''Single click''' performs filling from the click point.
[[File:Tutorial-paintbucket-clickonce.svg|thumb|center|300px]] 

* '''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.
[[File:Tutorial-paintbucket-shiftclick.svg|thumb|center|300px]] 

* '''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.
[[File:Tutorial-paintbucket-clickdrag.svg|thumb|center]] 

* '''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.
[[File:Tutorial-paintbucket-altdrag.svg|thumb|center]] 

==Paint Bucket's control bar options==
There are several options that allow the use of the paint bucket to be refined. Below is a screen shot of the tool's options that are displayed in the control bar.

[[File:Tutorial-paintbucket-optionsscreenshot.svg|thumb|center]] 

# Color Channels
# Threshold
The threshold option is used to control if a colour is determine to be the same or not. A threshold setting of 0 means that only the exact same colour is considered the same, whereas a setting of 100 means that every colour is viewed as being the same. For diagrams and technical drawings a setting of 0 is often used, whereas in artistic work a higher setting ~ 20-30 is not uncommon.
# Grow/Shrink amount
# Grow/Shrink units
Grow and shrink is used mainly to make up for a lack of autocracy of the paint bucket fill. Often the paint bucket fill will not completely fill a region so by growing the fill region to cover a larger area the gaps will be filled in and no longer noticeable once placed behind the edge objects.

Interesting visual effects can be created by shrinking the fill area and by using multiple fills and strokes or colours.

# Auto Gap setting

Some gapes in an outline will not be visible to the human eye, but will cause the area not to be bounded. One method to fix this is to zoom out, therefore hiding the gap to the computer, but meaning the fill will be less accurate.
The auto gap setting is used to fill a gap of 1 to ~ 8 pixels so that the gap is ignored and the area is filled despite the break in the surrounding objects

# Reset to defaults
# Style swatch
is used to show the fill style that is about to be used

File:Tutorial-paintbucket-clickonce.svg

2012-03-14T19:16:02Z

Kris: uploaded a new version of "File:Tutorial-paintbucket-clickonce.svg": There seems to be a bug ...

File:Tutorial-paintbucket-clickonce.svg

2012-03-14T19:05:11Z

Kris: uploaded a new version of "File:Tutorial-paintbucket-clickonce.svg": Scaled to page content (for layout purposes - to remove white space)

MediaWiki:Spam-blacklist

2012-03-14T18:53:22Z

Kris:

ArticleIntroducingInkscape0.40

2012-03-14T18:49:24Z

Kris: Reverted edits by Pakitof1 (talk) to last revision by DavidHOzAu

This is intended to be a PR piece to support the 0.40 release and outline
a few of the key features in a conversational style, to supplement the
[[Release Notes|release notes]], and to drum up interest in participating in Inkscape
development.

= Introducing Inkscape 0.40 =

The November 2004 release of the Inkscape drawing application brings to
users a number of oft-requested features. In this article we'll review
these features and briefly demonstrate their usage and potential. It's
also important to emphasize Inkscape as a participatory project, so
we'll close with some things you can do to help nudge the ball forward.

== Inkscape Tutorage ==

If you've ever used a vector drawing tool before, you'll probably find
the buttons and controls pretty obvious. If not, or if you want to
learn the tool in detail, Inkscape includes several handy tutorials
under the Help menu item. While these don't cover every aspect of
Inkscape, the Inkscape team has made great strides at fleshing them
out. In this release, the team has added new tutorials about the Shape
and Calligraphy tools, the "Potrace" tracing feature, and updated other
tutorials with new sections and more detailed information.

It's worth noting that the Tutorials themselves are created in - you
guessed it - Inkscape itself! In fact, as you become skilled with
Inkscape and develop new tricks and techniques, you're strongly
encouraged to write them up and contribute them to be included in future
tutorials. (If you speak another language than English, the project also maintains
translations of the tutorials, so do consider contributing a translation
or two!)

== Layers Feature ==
<nowiki>
<img src="/wiki_uploads/layers01.png" alt="Layers" align="right">
</nowiki>
The principal feature for this release is the addition of layer
management to Inkscape. This oft-requested feature has required a good
deal of internal rework to support, but leverages SVG's "Group"
mechanism to allow seperation of shapes, text and paths onto different layers.

The promise of this feature is to allow sets of shapes to be hidden or
visible, or to be "locked" from editing so the artist can focus on one
set of items at a time. This capability should hopefully enable artists
to create much more sophisticated artwork than has been possible in previous
releases of Inkscape.

<nowiki>
<img src="/wiki_uploads/layers02.png" alt="Layers 2" align="left">
</nowiki>

TODO - Demonstrate usage

== Text On Path ==

<nowiki>
<img src="/wiki_uploads/textpath01.png" alt="Text on Path Screenshot" align="right">
</nowiki>
Another long-requested feature is the ability to place text on arbitrary
paths. Inkscape 0.40 brings this feature to use in a big way.

TODO - Demonstrate usage

== Bitmap Tracing ==

An exciting (and unplanned) feature new to this release is the ability
to vectorize bitmap, or 'raster', images. Tools had been available
since well before Inkscape to do this, but until now it had to be done
manually and separately from Inkscape. With a smack to the head, one of
the developers realized it'd be easy to add this feature directly within
Inkscape, and so it was. We recommend checking out the tracing tutorial
under Tutorial section of the Help menu.

TODO - Demonstrate the feature

Already, we've seen some rather stunning artistic applications of this
tool, and we're looking forward to seeing what use people can make out
of this new capability.

== POV Raytracing ==

Another intriguing addition in this release is the ability to export
SVG as inputs to POV Ray, to be able to generate 3D renderings of your
2D drawings. This is sort of a proof-of-concept-ish feature; we're
curious what folks think of it; if you find an interesting use of it,
please show it off and give some ideas for how to make it even more
useful.

TODO: Example please

== Randomized Stars ==

The ability to 'randomize' the shapes of stars was another feature added
due not to user requests but mostly just because it could be done.
We don't know how useful the feature is, but it's terribly fun to play
with. Again, please show off if you create something cool with it.

TODO: Provide an example image

== Calligraphy ==

In past releases of Inkscape, the Calligraphy Tool was not really
considered a very useful tool, but with a few tweaks, it's been turned
into something quite powerful.

After clicking on the Calligraphy Tool, look at the controls in the Tool
Control Bar. Here's what the different controls do:

Width: This is the width of the stroke to draw. Think of it as the
width of your pen's nib.

Thinning: This controls how much the stroke narrows when you draw
the pen quickly. This emulates brush-like behavior where slow strokes
produce fatter lines than thin ones. For a perfect calligraphy style,
set it to a value of 0.00.

Angle: This is the angle (in degrees) of the nib compared with
horizontal. Change this to emulate different ways of holding the pen.

Fixation: This controls whether the nib angle varies with the stroke
direction. Essentially, with a value of 1 it makes the nib behave like
a carefully held calligraphy pen, and with a value of 0 it works more
like a felt pen.

Mass: This controls the pen's "inertia". Essentially, it lets you
control how smooth the stroke will be, at the expense of
responsiveness. With a value of 0 your stroke will be jagged and
irregular, capturing your every twitch. With a value of 1 the pen feels
like you're dragging a boat through water, but the stroke is quite
smooth and regular. If you find the pen doesn't "feel right", try
fiddling with this parameter - each artist will find a different value
to be most comfortable.

Drag: This is the resistance to movement of the pen. A value of 0.50
will feel most natural; lower values mean that slight motions will
produce large, sweeping curves; higher values make it feel like you're
writing in clay, and it takes very strong movements to produce much of a
line. This may be useful for altering the artistic style of your
lettering.

While the Calligraphy Tool has always been available in Inkscape, the
variety of controls made available in this release should hopefully give
you a lot more to experiment with, and make this tool much more
powerful for your work.

== And Much More! ==

<nowiki>
<a href="/wiki_uploads/screenshot.png"><img src="/wiki_uploads/screenshot_thn.png" alt="Screenshot" align="center"></a>
</nowiki>

The above should cover most of the major changes you'll notice in
Inkscape, but is far from exhaustive. Many small usability tweaks,
performance enhancements, bug fixes, and code cleanup have also gone
into this release. Most of these are identified in the Release Notes,
but of course the most fun is to discover them while using the tool!
;-)

You'll notice some changes in layout of a few dialogs, for instance.
Copy and paste, grid, use of current style, the statusbar, XML editor,
and so on have all received some attention and show off new ideas that
users and developers have had lately.

In addition to the controls mentioned earlier, many shapes have new
controls and ways of manipulating them. See the Shapes tutorial for a
full overview of the capabilities.

<nowiki>
<img src="/wiki_uploads/preferences.png" alt="Preferences" align="right">
</nowiki>
A most convenient feature was added to the tool buttons - double clicking
on them brings up the preferences for that tool. Quite handy!

In the past, Windows users have lagged behind Linux users for Inkscape
functionality due to Windows-specific issues that the developers hadn't
been able to address. In this release, focus has gone into helping get
those issues figured out, so hopefully Windows users will find Inkscape
as stable as the Linux users.

== Participation ==

Inkscape is different from commercial software that you may be used to,
in that it is a grassroots-driven, open effort to create the tool.
Everyone that works on it does so as a volunteer. There's no budget to
worry about, no salaries being paid, no quarterly sales forcasts.
Everyone participates for the simple reason that they wish to have a
great SVG-based drawing tool freely available on Linux, Windows and
other platforms.

The implication of all this is that unlike commercial software, where
your role starts and ends at the cash register, with open source
projects you have an important role to play within the process. You've
heard the phrase, "Time is money," which you can interpret to mean that
your time is as valuable as your money. In an open source project like
Inkscape, your time can actually be much more valuable than money - your
efforts can directly assist in improving the software for everyone,
whereas money usually has to be translated into something that benefits
the project, so it's more of an indirect process.

Of course, not everyone can afford to dedicate as much time as the core
developers have to Inkscape, so you probably wonder how you could
contribute a small amount - perhaps no more than a couple hours on just
one evening - helping improve Inkscape without getting committed to
something huge. Fortunately, there are many ways to help.

First and foremost is to simply spread the word. Inkscape doesn't have
a marketing budget, nor does it put out any advertising. Instead it
depends on users to share their experiences with others, help people
install it, and show them how to use it. Figure that for every ten
people you help use it, you'll gain a convert that will contribute to
Inkscape in some way some day.

Second, and probably even more important is to strengthen the feedback
loop. Since its release, Inkscape has benefitted immensely from the bug
reports, testing, and feature suggestions from hundreds of users. These
efforts by users help us identify breakage and issues in new code
swiftly, and has helped Inkscape increase in quality faster than
expected. Because of this powerful, tight feedback loop with the user
community, Inkscape has achieved a level of stability that commercial
software only achieves through expensive manual regression and usability
testing efforts. Inkscape instead benefits from the "Many eyes make
bugs shallow" effect that comes from good open source practices. So
bang on the tires, peek in all the nooks and corners, and if you see
something that's obviously wrong, send in a report! Or review the
existing reported bugs and see if you can replicate them; if so, add
some notes about your own observations, to help give the programmer some
additional evidence to help narrow in on the problem.

Third, as a skilled user of Inkscape your Inkscape talents can be used
directly to help the software in a variety of ways. As mentioned above,
tutorial writing is an easy way to share your skill with other users.
Inkscape also has a sister project, the Open Clip Art Library
(www.openclipart.org) where you can share templates, clipart, patterns,
and other such works with users. This is especially valuable for the
less artistic amongst us, and opens usefulness of Inkscape (and other
SVG tools) to a much wider audience - even programmers!

Fourth, Inkscape maintains a wiki for discussing feature development and
documenting various aspects of the project. If you're into wikis,
please consider joining in on the wiki discussions. Help with scoping
out new architectures, fleshing out feature suggestions into plan of
actions, and turning the rough notes into finished forms.

Finally, if you can program there are a variety of ways of helping out
in even small ways. In addition to working on the codebase itself,
Inkscape supports "extensions", which are simple scripts or commandline
tools to provide functionalities to Inkscape. You can find these tools
in the Inkscape 'share' directory
(e.g. /usr/share/inkscape/extensions). To add a new tool, you create an
XML file with a .inx extension to register it with Inkscape. These
tools should accept SVG on standard in and produce a different file
format to standard out (or vice versa). Browse some of the examples and
think about other file formats worth supporting in Inkscape, and write
up your own script.

== "Draw Freely." ==

To sum up: Lots of cool new features, hope y'all like it, and do think
about donating a few spare cycles to making the tool better.

We've got a lot to look forward to in the future. In the near to mid
term, we expect to reimplement the UI in C++, investigate some
performance optimization ideas, and of course continue adding many more
features and fixes. Longer term, we want to make Inkscape better suited
for both advanced artistic use as well as basic technical drawing use
(already we have an eye on a Visio VDX-to-SVG converter, mmm...)

[[Category:Marketing]]

File:Paintbuckettutorial-happyguy.svg

2012-03-12T14:13:37Z

Kris: uploaded a new version of "File:Paintbuckettutorial-happyguy.svg": Scaled to page content (for layout purposes - to remove white space)