Inkscape Wiki - User contributions [en]

Working with Bazaar

2011-01-11T14:48:57Z

AurelioAHeckert: Conflict handling

==Bazaar concepts==

It is assumed that you are familiar with the basic concepts of version control, like working copy, committing, updating, conflicts. There will be a section that explains the basic functionality soon.

; '''Branch'''
: is a working copy of the project's code. Typically you use one branch per set of related changes, for example a new output extension. Once your work is finished, you ''merge'' your branch into a larger project. Initially, there is only one branch, the trunk; all other branches are its (probably indirect) descendants. To create a new branch, you have to copy an existing one.
; '''Checkout'''
: is a copy of code contained in a branch that is not stored on your computer (a remote branch). Committing to a checkout will immediately apply the changes to the remote branch. Commits will not succeed if somebody else modified the branch while you were working - you need to have an up-to-date working copy - or when you're offline.
:When branches A and B have a common ancestor branch but each contain changes not present in the other, they have '''diverged'''. For example, when you work on an improved rectangle tool in your own branch and at the same time somebody else applies a PDF export bugfix to the trunk, your rectangle tool branch becomes diverged from the trunk.
; '''Trunk'''
: is the main branch, which represents cutting-edge working code. You should start from it when doing any new development.
; '''Merge'''
: is the process of reconciling changes made between two branches since they diverged. This operation is asymmetric. When you merge A into B, all changes made to A since it was branched from B are applied to B. A is not changed. When you work on some feature, you typically work in a branch, periodically merging the trunk into your branch (to sync up with the latest changes), then you merge your work into the trunk. Merging is similar to applying a patch - it only changes your working copy. To apply a merge, you need to commit the changes it introduced. Merging un-diverges branches.
; '''Repository'''
: is a place where branches of a project are stored. Having a shared repository reduces the storage requirements of multiple branches of one project. Instead of O(number of branches) space, the Bazaar data takes up O(total size of changes in all branches) space.
; '''Bind'''
: is the process of converting a non-diverged local branch into a checkout of the remote branch.
; '''Push'''
: is the process of publishing an exact copy (a mirror) of your branch in some other location. The difference between pushing and checkouts is that a checked out remote branch is updated every time you commit, while a pushed remote branch is updated only when you push to it - you can commit any amount of changes between pushes. You can only push to a branch if the mirror has not diverged from your local copy. This can happen if more than 1 person can push to the same location.
; '''Pull'''
: is the process of creating a local exact copy (mirror) of a branch, in principle a reverse of pushing.

==First steps==

First you need to tell Bazaar your name. This will appear on all your commits. You should use your real e-mail, but you can obfuscate it if you are afraid of spam.

Obfuscated e-mail examples:
$ bzr whoami "John Q. Public <john dot q dot public at-sign bigmail dot com>"
$ bzr whoami "John Q. Public <removethis.john.q.public@bigmail.com>"
Unobfuscated e-mail example:
$ bzr whoami "John Q. Public <john.q.public@bigmail.com>"

If you have an account on launchpad and want to commit changes there, you need to specify your launchpad login:
$ bzr launchpad-login johnq

Then fetch Inkscape's trunk
$ bzr branch lp:inkscape

To carry out a later update of Inkscape's trunk
$ bzr pull lp:inkscape

==Using a centralized (SVN-like) workflow==

In this case, every commit that you make is immediately sent to the central repository. There are two ways of achieving this:

===SVN-style checkout===

Get the latest Inkscape code as a checkout, rather than a branch:
$ bzr checkout lp:inkscape

Now work as in SVN:
<do work>
$ bzr commit
<error, someone else has changed things>
$ bzr update
<check all is okay>
$ bzr commit

If you add new files, add them to version control with <tt>bzr add ''file''</tt>. You can recursively add all new files by writing simply <tt>bzr add</tt> in the top level directory.

===Binding a BZR branch===

Get Inkscape's code the regular bzr way:
$ bzr branch lp:inkscape

Then transform your banch into a checkout:
$ cd inkscape
$ bzr bind lp:inkscape

Now work as in SVN:
<do work>
$ bzr commit
<error, someone else has changed things>
$ bzr update
<check all is okay>
$ bzr commit

===Differences from SVN===

* Commits will fail if your checkout is not up to date, even if there would be no conflicts.
* The revision number is an attribute of the working tree, not of individual files. It is not possible to have different portions of the working tree at different revisions.
* <tt>bzr commit ''file''</tt> works like <tt> svn commit ''file'' && svn update ''project-root''</tt>. After a successful partial commit, the entire tree's revision is increased by 1.
* No special server is needed to publish a branch. You can push branches to anywhere, including simple FTP shares. In our scenario, Launchpad works like a central repository, but it's not required to publish everything there.
* You create branches locally. To simulate creating a SVN-style branch on Launchpad, you need to create a local branch, push it, then bind it to the pushed location.


==Using a decentralized workflow==

In this case you will be working locally until you are ready to publish your changes. The basic idea is to perform the work in a ''branch'' of the Inkscape repository, since committing to a branch stores the changes locally in the branch itself. Then, to share the work with the rest of the Inkscape community, the changes in the branch are merged across to a ''checkout'' of the Inkscape repository. As the previous centralized workflow section describes, committing to a checkout sends the changes directly to the remote repository, making them part of the official Inkscape codebase.

'''NOTE:''' this workflow has been updated to avoid the "other people's commits become subrevisions of your commit" problem.

This will assume this directory layout:
inkscape
+-trunk
| +-doc
| +-share
| +-src
| +-po
| +-...
+-myproject
+-some-other-branch

In this layout, "trunk" is the checkout used for uploading changes to the central Inkscape repository, while "myproject" and "some-other-branch" are local branches used for working on specific features.

===Repository setup===

To speed things up, it's good to create a local shared repository. This way revision histories will only be stored in one place, instead of in every branch, so local branching will be faster and the branches will take up less space.

Create a shared repository and enter it:
$ bzr init-repo inkscape
$ cd inkscape

===Working locally===

Get Inkscape's code
$ bzr branch lp:inkscape myproject

Now work:
$ cd myproject
... work work work ...
$ bzr commit -m "Some changes"
... more work work work ...
$ bzr commit -m "More changes"
... create new file ...
$ bzr add new-file.c
$ bzr commit -m "Added new file with kittens"

===Advanced local features===

To undo a commit:
$ bzr uncommit
This will leave your working tree in the state it was just before you wrote "bzr commit". This is useful for example if you forgot to add a file, and want to keep a clean revision history. This will NOT work on a trunk checkout.

Let's say you started from r770 200 local commits, but you decided that what you did since r954 is completely wrong. You want to go back to revision 825 and do it differently. Here's one way to do this. First branch locally to preserve your work (maybe later you'll find out there's some way to save it). Then uncommit everything up to r954 and revert.
$ bzr branch myproject myproject-dead-end
$ cd myproject
$ bzr uncommit -r 954
$ bzr revert

A different scenario: let's say that commit 1524 introduced a bug, but there were 50 other commits since then and you only want to revert the changes introduced by 1524.
$ bzr merge -r1524..1523

Sometimes a big change gets committed while you are working on a feature. If you want to check whether your code still works after the big change, merge from trunk.
$ bzr merge

In this case, you can omit where you are merging from, because the default is to merge from the branch you started from (the parent).

===Publishing your work on Launchpad===

To publish branches on Launchpad, you have to add an SSH key to your account. If you don't have one yet, generate it:
$ ssh-keygen
... follow instructions ...

Once you created the key, go to your Launchpad profile page, edit SSH keys and paste the contents of the key file (by default it's in <tt>~/.ssh/id_rsa.pub</tt> or <tt>~/.ssh/id_dsa.pub</tt>) into the window. You can now use the Launchpad integration features.

Login to Launchpad, if you didn't do it yet. You only need to do this once on each computer. You need to use your login name, not the display name.
$ bzr launchpad-login johnq

Publish your branch on Launchpad.
$ bzr push lp:~johnq/inkscape/myproject

The push location will be saved. After more commits, you can simply write
$ bzr push

It's sometimes convenient to update the Launchpad copy after each commit. To save on typing, you can bind your working tree to the remote branch. This way every commit will be immediately published on the remote branch. Note that you won't be able to commit while offline.
$ bzr bind :push

===Putting your work in the trunk===

Once your new killer feature is ready, you need to merge your changes into a checkout of the trunk. If you don't have one, do (in the directory ''containing'' myproject):
$ bzr checkout lp:inkscape trunk
$ cd trunk

If you already have one on hand, make sure it's up to date:
$ cd trunk
$ bzr update

Now that you have a local checkout of the current trunk:
$ bzr merge ../myproject
$ bzr commit -m'added my feature'

WARNING: There is an alternative method that consists of merging trunk into your local branch, then pushing the result as trunk. Do not do this! It obfuscates the revision history.

===Working with patch files===

If you don't have permission to commit to the trunk, you can bundle your branch's changes into a patch instead:
$ bzr send -o mychanges.patch

To apply patches produced by the above command, just do this:
$ bzr merge somechanges.patch

===Local branching===

Naturally, all this also works locally. For example, when you're in the <tt>inkscape</tt> directory, you can write <tt>bzr branch trunk export-dialog</tt> to create a new branch of the trunk called <tt>export-dialog</tt>, where you'll work only on improving the export dialog. Similarly, you can merge between local branches.

==Best Practices for Inkscape Project==

===Registering Bugfixes===

Launchpad will automatically mark a bug "Fix Available" (rather than "Fix Committed") once somebody commits using the flag --fixes, e.g. (if you fix those two bugs in one commit):
bzr commit --fixes lp:123456 --fixes lp:123457 -m 'patch description'
Then, bugs can be changed automatically from "Fix Available" to "Fix Released"

[http://doc.bazaar-vcs.org/bzr.dev/en/tutorials/using_bazaar_with_launchpad.html#changing-the-state-in-launchpad-while-committing-in-bazaar Read more: "Changing the state in Launchpad while committing in Bazaar"]

===Proper way of merging===

To repeat, NEVER do something like:
$ bzr branch lp:inkscape myproject
... work ...
$ bzr commit
$ bzr merge # NOOOO!!! We are doomed!
$ bzr push lp:inkscape

It will obfuscate the revision history: trunk commits that happened between the time you branched and the time you pushed will get grouped into one. Do the merge the other way around:
$ bzr branch lp:inkscape myproject
$ cd myproject
... work ...
$ bzr commit
$ cd ../trunk
$ bzr merge ../myproject # correct!
$ bzr commit

You'll need a trunk checkout, but the revision history will be much less confusing, and it's useful to have a trunk checkout anyway.

===Fixing a bug in both trunk and a release branch===

This will assume this directory layout:
inkscape
+-trunk
| +-src
| +-...
+-0.48.x
| +-src
| +-...

Fix the bug in trunk and commit it, let's say it will be revision 1234.
Then go to the release branch directory, e.g. 0.48.x
Then write

bzr merge -r 1233..1234 ../trunk

The operation can take a while...
Then commit to the release branch, or post the diff to Launchpad.

==Conflict handling==

Sometimes you ''(or the building script)'' change a file in the same place that other one change and when you update your local repository a conflict happens.

$ bzr update
Enter passphrase for key '/home/aurium/.ssh/id_rsa':
M configure.ac
M po/POTFILES.in
RN po/inkscape.pot => po/inkscape.pot.OTHER
M po/it.po
M src/zoom-context.cpp
Contents conflict in po/inkscape.pot
Conflict adding id to po/inkscape.pot.OTHER. Unversioned existing file po/inkscape.pot.
2 conflicts encountered.
Updated to revision 10002 of branch bzr+ssh://bazaar.launchpad.net/%2Bbranch/inkscape

Now '''po/inkscape.pot''' become two files:
$ ls po/inkscape.pot*
po/inkscape.pot.BASE po/inkscape.pot.OTHER

If you forgot/lost the conflict message or has many conflicts to resolve, you may list it wih this command:
$ bzr conflicts
Contents conflict in po/inkscape.pot
Conflict adding id to po/inkscape.pot.OTHER. Unversioned existing file po/inkscape.pot.

You may use the diff command to help you to discover what was changed and choice for a solution.
$ diff po/inkscape.pot.BASE po/inkscape.pot.OTHER
11c11
< "POT-Creation-Date: 2010-12-23 18:43+0100\n"
---
> "POT-Creation-Date: 2011-01-05 20:49+0100\n"
...

Sometimes the diff will be really big and will not help you. That happens with automatic generated files like '''po/inkscape.pot'''.

On this case my solution was to use the newer pot:
$ bzr mv po/inkscape.pot.OTHER po/inkscape.pot

If you resolve all, run it:
$ bzr resolve -all

More information on the "[http://doc.bazaar.canonical.com/latest/en/user-guide/resolving_conflicts.html Bazaar manual - Conflict handling]".

==External links==
* [http://doc.bazaar-vcs.org/latest/en/ Bazaar manual]

Multipage

2010-11-04T18:17:29Z

AurelioAHeckert:

== Multipage support ==
* this feature is currently not implemented
* this page describes how the feature should be implemented
* there should be multiple pages within a document
* problem arises when saving to singlepage file formats (jpg, png, etc)
* SVG does not support multipage per se, but upcomming SVG will do [[http://www.w3.org/TR/2004/WD-SVG12-20041027/multipage.html see W3.org]]
* There are two contrary implementattions in the real world:
** distribute pages around the graphics elements - the Adobe way
** distribute graphics elements around the pages - how Corel does it and how SVG propose it

== multipage in the SVG standard ==
* All pages are contained within a single pageSet element. A pageSet may contain any number of page elements. Each page element defines a single container of graphical objects.
* In a screen-based user agent, only one page element is displayed at any time on the main canvas.
* The SVG content typically defines a page dimension or aspect ratio in the topmost svg element and its viewBox. The viewBox transformation applies to printed SVG in the same way as screen display.
* The orientation of each page element can be controlled by the page-orientation property. This enables the content to define whether a portrait or landscape mode is used for display and printing.

== multipage ala Corel ==
* there is a list of pages as tabs on the lower side of the drawing window
* all pages share the same page properties
* a '''master page''' contains elements that are visible on all other pages: drawings, markers
* in an object browser pages and layers are integrated
* see a screenshot [[http://wiki.inkscape.org/wiki/images/Corel_pages.PNG here]]

== Multicanvas (similar to multi-Artboard on adobe illustrator cs4). ==
Multicanvas solution is not the same as pages and can't follow the SVG pageSet spec. The multicanvas, as the multi-artboard, can (frequently must) have different sizes and can be freely placed on the 2D space. A canvas may overlap a part other canvas.

Each canvas can be printed independently and that feature helps to unify the art conception for the most applications of an art project.

* see this adobe tutorial [[http://www.adobe.com/designcenter/illustrator/articles/lrvid4016_ai.html here]]
* there is an [[http://www.vimeo.com/2503097 video]] by Valessio Brito presenting an UI mockup how multipage can be handled in inkscape

The multicanvas feature may be incompatible with the multipage feature, so, the user may chose the working mode on the "document properties" dialog. The default must be multipage and that will show the page tabs on the interface and the "new page" button, when selecting multicanvas that will show the canvas controls and the "new canvas" button.

Feature request registered: https://bugs.launchpad.net/inkscape/+bug/671081

== implementation ==
* see this [http://www.nabble.com/Multipage-plan-td16394431.html thread]
* all export dialogues must becom extra properties to handle multiple pages, in order to specify not only the elements but also the pages to be exported

Multipage

2010-11-04T18:03:28Z

AurelioAHeckert:

== Multipage support ==
* this feature is currently not implemented
* this page describes how the feature should be implemented
* there should be multiple pages within a document
* problem arises when saving to singlepage file formats (jpg, png, etc)
* SVG does not support multipage per se, but upcomming SVG will do [[http://www.w3.org/TR/2004/WD-SVG12-20041027/multipage.html see W3.org]]
* There are two contrary implementattions in the real world:
** distribute pages around the graphics elements - the Adobe way
** distribute graphics elements around the pages - how Corel does it and how SVG propose it

== multipage in the SVG standard ==
* All pages are contained within a single pageSet element. A pageSet may contain any number of page elements. Each page element defines a single container of graphical objects.
* In a screen-based user agent, only one page element is displayed at any time on the main canvas.
* The SVG content typically defines a page dimension or aspect ratio in the topmost svg element and its viewBox. The viewBox transformation applies to printed SVG in the same way as screen display.
* The orientation of each page element can be controlled by the page-orientation property. This enables the content to define whether a portrait or landscape mode is used for display and printing.

== multipage ala Corel ==
* there is a list of pages as tabs on the lower side of the drawing window
* all pages share the same page properties
* a '''master page''' contains elements that are visible on all other pages: drawings, markers
* in an object browser pages and layers are integrated
* see a screenshot [[http://wiki.inkscape.org/wiki/images/Corel_pages.PNG here]]

== Multicanvas (similar to multi-Artboard on adobe illustrator cs4). ==
Multicanvas solution is not the same as pages and can't follow the SVG pageSet spec. The multicanvas, as the multi-artboard, can (frequently must) have different sizes and can be freely placed on the 2D space. A canvas may overlap a part other canvas.

Each canvas can be printed independently and that feature helps to unify the art conception for the most applications of an art project.

* see this adobe tutorial [[http://www.adobe.com/designcenter/illustrator/articles/lrvid4016_ai.html here]]
* there is an [[http://www.vimeo.com/2503097 video]] by Valessio Brito presenting an UI mockup how multipage can be handled in inkscape

The multicanvas feature may be incompatible with the multipage feature, so, the user may chose the working mode on the "document properties" dialog. The default must be multipage and that will show the page tabs on the interface and the "new page" button, when selecting multicanvas that will show the canvas controls and the "new canvas" button.

== implementation ==
* see this [http://www.nabble.com/Multipage-plan-td16394431.html thread]
* all export dialogues must becom extra properties to handle multiple pages, in order to specify not only the elements but also the pages to be exported

Class Inkscape::UI::Widget::ProgressPannel

2010-05-02T01:35:11Z

AurelioAHeckert: /* Inkscape::UI::Widget::ProgressPannel */

== Inkscape::UI::Widget::ProgressPannel ==

Discussion and documentation about Inkscape::UI::Widget::ProgressPannel class, a specific Inkscape widget.

ProgressPannel will replace the current content of the extension working dialog, defined inside [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head%3A/src/extension/execution-env.cpp execution-env.cpp] and may be used on any other progress or loading related action on Inkscape.

The GUI pieces:
[[File:Progress-pannel-mockup.png|center|link=File:Progress-pannel-mockup.svg]]

The panel by default starts with a empty icon, but set it is important for a fast and beauty visual communication.

Stock icons can be used with this constructor:
Gtk::Image ( const Gtk::StockID& stock_id, IconSize size )
Example values:
Gtk::Stock::DIALOG_INFO
Gtk::ICON_SIZE_DIALOG

progressText may have variables to show optional values:
* '''%1''' : minimum value
* '''%2''' : maxmum value
* '''%3''' : current value
* '''%4''' : percentage value
Example: "building %3 of %2 pieces. %4%% done."

[[File:Extension-progress.png]]
[[File:Saveing-progress.png]]
[[File:Loading-fonts-progress.png]]

Source SVGs: [http://wiki.inkscape.org/wiki/images/Progress-pannel-mockup.svg Progress-pannel-mockup.svg] [http://wiki.inkscape.org/wiki/images/Progress-pannel-examples-mockup.svg Progress-pannel-examples-mockup.svg]

=== Code ===

The progress_text must be updated together to the progress bar values. A possible updater code is:
[http://library.gnome.org/devel/gtkmm/stable/classGtk_1_1ProgressBar.html progress]->set_text( Glib::ustring::compose(
progress_text,
Glib::ustring::format(std::dec, min),
Glib::ustring::format(std::dec, max),
Glib::ustring::format(std::dec, val),
Glib::ustring::format(std::fixed, std::setprecision(pct_precision),
((double)val-min)*100/(max-min) )

Class Inkscape::UI::Widget::ProgressPannel

2010-05-02T01:34:27Z

AurelioAHeckert: code to update progress_text

== Inkscape::UI::Widget::ProgressPannel ==

Discussion and documentation about Inkscape::UI::Widget::ProgressPannel class, a specific Inkscape widget.

ProgressPannel will replace the current content of the extension working dialog, defined inside [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head%3A/src/extension/execution-env.cpp execution-env.cpp] and may be used on any other progress or loading related action on Inkscape.

The GUI pieces:
[[File:Progress-pannel-mockup.png|center|link=File:Progress-pannel-mockup.svg]]

The panel by default starts with a empty icon, but set it is important for a fast and beauty visual communication.

Stock icons can be used with this constructor:
Gtk::Image ( const Gtk::StockID& stock_id, IconSize size )
Example values:
Gtk::Stock::DIALOG_INFO
Gtk::ICON_SIZE_DIALOG

progressText may have variables to show optional values:
* '''%1''' : minimum value
* '''%2''' : maxmum value
* '''%3''' : current value
* '''%4''' : percentage value
Example: "building %3 of %2 pieces. %4%% done."

[[File:Extension-progress.png]]
[[File:Saveing-progress.png]]
[[File:Loading-fonts-progress.png]]
Source SVGs: [http://wiki.inkscape.org/wiki/images/Progress-pannel-mockup.svg Progress-pannel-mockup.svg] [http://wiki.inkscape.org/wiki/images/Progress-pannel-examples-mockup.svg Progress-pannel-examples-mockup.svg]

=== Code ===

The progress_text must be updated together to the progress bar values. A possible updater code is:
[http://library.gnome.org/devel/gtkmm/stable/classGtk_1_1ProgressBar.html progress]->set_text( Glib::ustring::compose(
progress_text,
Glib::ustring::format(std::dec, min),
Glib::ustring::format(std::dec, max),
Glib::ustring::format(std::dec, val),
Glib::ustring::format(std::fixed, std::setprecision(pct_precision),
((double)val-min)*100/(max-min) )

File:Progress-pannel-mockup.png

2010-05-02T01:11:56Z

AurelioAHeckert: uploaded a new version of "File:Progress-pannel-mockup.png": Mockup with pieces of Class Inkscape::UI::Widget::ProgressPannel

Mockup with pieces of [[Class Inkscape::UI::Widget::ProgressPannel]]

File:Progress-pannel-mockup.svg

2010-05-02T01:11:32Z

AurelioAHeckert: Mockup with pieces of Class Inkscape::UI::Widget::ProgressPannel

Mockup with pieces of [[Class Inkscape::UI::Widget::ProgressPannel]]

UI Mockup Screenshots

2010-05-02T01:01:56Z

AurelioAHeckert: /* UI Mockup Screenshots */

== UI Mockup Screenshots ==

<gallery caption="Load splash" widths="200px" perrow="3">
Image:Compact_load_splash.png
</gallery>

<gallery caption="Commom Progress Pannel" widths="300px" perrow="3">
File:Extension-progress.png
File:Saveing-progress.png
File:Loading-fonts-progress.png
</gallery>
Read [[Class Inkscape::UI::Widget::ProgressPannel]] for more information

<gallery caption="Fill and Stroke" widths="300px" perrow="3">
Image:Fillstroke1.png
Image:Fillstroke2.png
Image:Mockup-Fill-Stroke-Toolbar.png
</gallery>

<gallery caption="Styles editor and Toolbars" widths="300px" perrow="3">
Image:Styleseditor.png
Image:Mockup-Font-Style-Toolbar.png
</gallery>

<gallery caption="Others and Bug fix" widths="300px" perrow="3">
Image:Nitpicksquad1.png
Image:Nitpicksquad2.png
</gallery>

== UI Source SVG Version ==

Get Version UI SVG to create Mockups: http://valessiobrito.info/projetos/inkscape/ink-ui/

Class Inkscape::UI::Widget::ProgressPannel

2010-05-02T00:24:25Z

AurelioAHeckert: Created page with '== Inkscape::UI::Widget::ProgressPannel == Discussion and documentation about Inkscape::UI::Widget::ProgressPannel class, a specific Inkscape widget. ProgressPannel will replac...'

== Inkscape::UI::Widget::ProgressPannel ==

Discussion and documentation about Inkscape::UI::Widget::ProgressPannel class, a specific Inkscape widget.

ProgressPannel will replace the current content of the extension working dialog, defined inside [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head%3A/src/extension/execution-env.cpp execution-env.cpp] and may be used on any other progress or loading related action on Inkscape.

The GUI pieces:
[[File:Progress-pannel-mockup.png|center]]

The panel by default starts with a empty icon, but set it is important for a fast and beauty visual communication.

Stock icons can be used with this constructor:
Gtk::Image ( const Gtk::StockID& stock_id, IconSize size )
Example values:
Gtk::Stock::DIALOG_INFO
Gtk::ICON_SIZE_DIALOG

progressText may have variables to show optional values:
* '''%1''' : minimum value
* '''%2''' : maxmum value
* '''%3''' : current value
* '''%4''' : percentage value
Example: "building %3 of %2 pieces. %4%% done."

[[File:Extension-progress.png]]
[[File:Saveing-progress.png]]
[[File:Loading-fonts-progress.png]]

Source SVGs: [http://wiki.inkscape.org/wiki/images/Progress-pannel-mocup.svg Progress-pannel-mocup.svg] [http://wiki.inkscape.org/wiki/images/Progress-pannel-examples-mockup.svg Progress-pannel-examples-mockup.svg]

File:Progress-pannel-mockup.png

2010-05-02T00:11:40Z

AurelioAHeckert: Mockup with pieces of Class Inkscape::UI::Widget::ProgressPannel

Mockup with pieces of [[Class Inkscape::UI::Widget::ProgressPannel]]

File:Loading-fonts-progress.png

2010-05-01T23:59:54Z

AurelioAHeckert: Mockup with usage example of Class Inkscape::UI::Widget::ProgressPannel

Mockup with usage example of [[Class Inkscape::UI::Widget::ProgressPannel]]

File:Extension-progress.png

2010-05-01T23:59:42Z

AurelioAHeckert: Mockup with usage example of Class Inkscape::UI::Widget::ProgressPannel

Mockup with usage example of [[Class Inkscape::UI::Widget::ProgressPannel]]

File:Saveing-progress.png

2010-05-01T23:59:12Z

AurelioAHeckert: Mockup with usage example of Class Inkscape::UI::Widget::ProgressPannel

Mockup with usage example of [[Class Inkscape::UI::Widget::ProgressPannel]]

File:Progress-pannel-examples-mockup.svg

2010-05-01T23:56:49Z

AurelioAHeckert: Mockup with usage examples of Class Inkscape::UI::Widget::ProgressPannel

Mockup with usage examples of [[Class Inkscape::UI::Widget::ProgressPannel]]

User Interface Modules

2010-05-01T23:50:42Z

AurelioAHeckert: Created page with '== User Interface Modules == Discussion and documentation about specific Inkscape dialogs, widgets, tools and more inside the [http://bazaar.launchpad.net/~inkscape.dev/inkscape...'

== User Interface Modules ==

Discussion and documentation about specific Inkscape dialogs, widgets, tools and more inside the [http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/files/head%3A/src/ui/ src/ui] directory.

=== src/ui/dialogs ===
* ...

=== src/ui/widgets ===
* [[Class Inkscape::UI::Widget::ProgressPannel]]
* ...

=== src/ui/tools ===
* ...

Architectural overview

2010-05-01T22:57:16Z

AurelioAHeckert: Main subsystems - User Interface Modules

This is a high-level overview of how Inkscape works.

==Main subsystems==
Inkscape can be roughly subdivided into a few subsystems:
* [[Display subsystem]] - contained in the <tt>src/display/</tt> directory of the source tree. It is responsible for rendering graphic primitives, displaying things on the screen, and providing the main canvas widget. It also dispatches events to tools.
* [[XML subsystem]] - provides classes to store the parsed XML of an SVG document. It is fairly generic and does not contain significant SVG-related functionality. The main feature that distinguishes it from e.g. libxml++ is that it provides notification about XML changes and undo functionality. The classes of this subsystem are garbage collected. Because the XML nodes were formerly C structures called <tt>SPRepr</tt>, the XML tree is sometimes called the "repr tree", and XML nodes "reprs" - a short form of "representation".
* [[Object tree]] - implements a mapping from the XML to display primitives, and provides a hierarchy of objects that can be modified using the tools. This is where the bulk of Inkscape's functionality is contained. This system is based on GObject. Each document has an object tree and an XML tree. Changes in the XML tree are automatically propagated to the object tree via observers, but not the other way around - a function called <tt>updateRepr()</tt> needs to be explicitly called.
* [[Tools subsystem]] - provides tools, internally called event contexts, that process input events happening on the canvas and translate them into document changes. This subsystem is based on GObject, dispersed in the <tt>src/</tt> directory and several subdirs. Files that contain event handling code end with <tt>-context.cpp</tt>.
* [[Extension subsystem]] - allows Inkscape to use third-party extensions without modifying Inkscape's code. Currently extensions can provide additional input and output formats, effects, path effects and printing backends.
* [[Preferences subsystem]] - this small, but relatively self-contained piece of code provides a shared storage for all of Inkscape's user settings. It keeps the parsed XML tree of the preferences file, but it's not directly accessible - the intent is to separate the preferences implementation (which in future might not be based on an XML file) from the API used to access them. It is contained in <tt>preferences.cpp</tt>
* [[User Interface Modules]] - contains specific Inkscape dialogs, widgets, tools and more.

==How Inkscape starts==
# First, the <tt>main()</tt> function is called. On Windows, it is called from a <tt>WinMain()</tt> stub, so that the command prompt is not displayed.
# <tt>main()</tt> determines whether Inkscape was run in command-line mode or in graphical mode.
# Based on that decision, <tt>sp_main_console()</tt> or <tt>sp_main_gui()</tt> is called. Both those functions call <tt>sp_common_main()</tt>, which handles parameter parsing. Parameters are parsed into a lot global variables (needs to be heavily refactored).
# An <tt>Inkscape::NSApplication::Application</tt> object is instantiated. This object is an unfinished attempt at converting top-level Inkscape structures to C++ classes. It creates the legacy <tt>Inkscape::Application</tt> structure and creates <tt>SPDesktop</tt>s for each opened document. (<tt>SPDesktop</tt>, "desktop" for short is a window used to edit a document - the main window you see when you start Inkscape.)
# Finally, the created desktops are shown.

==Historical note==
Inkscape is derived from an earlier vector drawing program called Sodipodi. Sodipodi was written entirely in plain C using GObject, the C object system used by GTK+. Writing and maintaining GObject code is cumbersome, because C lacks any syntax support for this system. There are still many places that use old GObject-based code, notably the tools and the SPObject tree. The long-term goal is to convert GObject-based code to regular C++ objects, but in the meanwhile some knowledge of GObject is needed to develop Inkscape.

File:Progress-pannel-mocup.svg

2010-05-01T21:23:26Z

AurelioAHeckert: The GUI for Inkscape::UI::Widget::ProgressPannel. A new Widget for progress notification like the extension execution.

The GUI for Inkscape::UI::Widget::ProgressPannel. A new Widget for progress notification like the extension execution.

Release notes/0.48

2010-04-25T03:14:41Z

AurelioAHeckert: Web > Slicer

==Inkscape 0.48==
'''(not released yet - [[AnnouncePlanning048]])'''

==Release highlights==

(TODO)

==Tools==

===Node Tool===

During Google Summer of Code 2009, the node tool underwent an extensive rewrite. Along with more maintainable code, it brings several new features.

; '''Multi-path editing'''
: Any number of paths can be selected for node editing at once.
; '''Improved clippath / mask editing'''
: The clipping path or mask of an object can be edited at the same time as the object. The clip / mask editing buttons in the node tool are now toggle buttons, rather than mode switch buttons. If the object is transformed after applying a clipping path, the clipping path is no longer offset when editing it in the node tool. If the clipping path is a group, all paths in the group can be edited simultaneously.
; '''Improved node join'''
: It is now possible to join nodes from different paths. More than two endnodes can be joined at once—the distances between nodes will be used to determine which nodes to join, with the closest pairs being joined first. When nothing can be joined (less than 2 endnodes in selecion), each selected stretch of nodes will be joined into one node.
; '''Improved segment join'''
: It is now possible to create a segment between endnodes from different paths. More than one segment can be created at once—the distances between nodes will be used to determine which nodes to join with a segment, with the closest pairs being joined first. When nothing can be joined (less than 2 endnodes in selection), each selected stretch of nodes will have its middle nodes removed, leaving only one segment.
; '''Node transforms'''
: It is now possible to transform the nodes using the mouse and transformation handles similar to those in the selector tool. They can be turned on and off using the button in the node toolbar. When the handles are visible, clicking on a selected node will switch between scaling and rotation mode, instead of selecting only that node. You can also use Shift+H to switch the mode. All other operations work normally when transform handles are shown.
; '''Path direction tools'''
: Little harpoons are optionally shown in the middle of each segment, visualizing the direction of the path. This is useful when preparing a guide path for text, setting markers, and debugging extensions and Inkscape itself. The "Reverse" command (Shift+R) reverses the direction of subpaths that have some selected nodes, or all subpaths if the node selection is empty.
; '''Customizable path update'''
: Two new preferences allow you to specify when the path and its outline should be updated. Turning off live update of paths will improve performance for complex drawings.
; '''Improved tips'''
: The tips displayed for nodes and handles are more concise and affected by what modifier keys are pressed.

For a detailed feature comparison between the old and new tool, see [[GSoC2009 Node Tool Rewrite]].

===Spray Tool===
You first need to select one or several items, then select the Spray Tool. To spray, click on the canvas, then move the mouse or scroll the mouse wheel.

Three modes are available.

*''Spray Copy mode :'' each sprayed item is independent from the others.
*''Spray Clone mode :'' each sprayed item is a clone of the selected item. Changing the properties of the original item will affect the clones.
*''Spray Single Path Mode :'' everything you spray is in a single path. You may need to convert your item into a path to make it work properly.

'''Spray options'''

*Amount : spray more or less items.

*Rotation : randomly rotates items around the original rotation value.
*Scale : randomly scales items around the original scale value.

*Scatter : low values to spray items under the cursor, high values for a more uniform repartition over the spray zone.
*Focus : items are sprayed following a ring. This parameters modifies the radius of the circle. Default at 0 to spray a spot.

Use keys ↑ and ↓ to control the size of of sprayed items. Use ← and → to set the width of the cursor.

The Spray tool is a perfect match for the transforming, duplicating, and deleting modes of the Tweak tool.



==Import/Export==
===Improved bitmap image import===

Bitmaps are now always embedded when pixel data is pasted or dragged into Inkscape's window (for example when copying parts of an image from GIMP). Files with automatically generated names like "inkscape_pasted_image_..." are no longer created in the document directory. When importing or opening bitmap images, a dialog is displayed that asks whether you want to link the image or embed it.

===New LaTeX export for PDF/EPS/PS===

Similar to GNUPlot's `epslatex' output terminal and Xfig's combined PDF/LaTeX output, Inkscape can now export graphics to PDF with an accompanying LaTeX file that overlays the text over the PDF when inputted in LaTeX. The image's text is typeset by LaTeX, so for example mathematical expressions are rendered correctly, and all text will be in the font and style of the LaTeX document (even when changing the document's font afterwards).

''(the following description assumes export to PDF, but will work the same for EPS and PS)''
Two files will be created: a PDF file containing all graphics, without text; and a LaTeX file with the same name, containing all text, and code to include the PDF and overlay the text. To include the exported image in LaTeX, one writes

\begin{figure}
\centering
\def\svgwidth{\columnwidth} % sets the image width, this is optional
\input{image.tex}
\end{figure}

A more thorough description of how to use the new feature (and automate the exporting/inclusion of the image in LaTeX) is given in this PDF: [http://wiki.inkscape.org/wiki/images/SVG_in_LaTeX.pdf SVG in LaTeX].

====From the GUI====
When exporting to PDF/EPS/PS from Inkscape's GUI, the usual dialog pops up after selecting to which PDF/EPS/PS file to export to. In this dialog, you can find the PDF/EPS/PS+LaTeX option.

====Command line option====
When exporting to PDF/EPS/PS from the command line, adding --export-latex will turn the LaTeX export on. For example

inkscape image.svg -z -D --export-pdf=image.pdf --export-latex

===Fixed PDF/EPS/PS export of non-integer sized documents===
The long standing [https://bugs.launchpad.net/inkscape/+bug/168275 bug 168275] has now been fixed. Documents with a non-integer height or width are now correctly exported to PDF, EPS and PS.

==Extensions==
===New and improved extensions===

* The new '''Generate from Path > Voronoi Pattern''' extension creates a random pattern of Voronoi cells. The pattern will be accessible from the Fill and Stroke dialog. The pattern can be made to be smooth at the edges by choosing a positive border, or sparse at the edges by using a negative border.
* The new '''Render > Wireframe Sphere''' extension draws the globe as a collection of ellipses representing a sphere's latitude and longitude lines. The number of lines is adjustable, as well as the tilt and rotation. There is an option to hide the lines at the back of the sphere.
* The new '''Render > Barcode - Datamatrix''' extension renders a DataMatrix 2D barcode, as specified in BS ISO/IEC 16022:2006. The number of rows and columns of the DataMatrix is adjustable. If more data is given than can be contained in one DataMatrix, more than one DataMatrix will be produced.
* The new '''Modify Path > Pixelsnap''' extension aligns rectangles and paths to pixel boundaries, to create sharp web and digital graphics.
* The new '''Color > Black and White''' extension turns the selection colors into black and white.
* The new '''Text > Split Text''' extension splits texts into different lines, words or letters.
* The new '''Web > Slicer''' extensions to slice web layouts into multiple images and help the HTML+CSS creation.
* '''Images > Extract Image''': all relative paths (or filenames without path) are now relative to the user's home directory.



==Other features==

* Arch paper sizes are added in the Document Properties dialog
* Displaying the '''font samples''' in the drop-down list of the Text tool is now optional. In Inkscape Preferences, go to Tools, Text, and uncheck "Show font samples in the drop-down list" if you don't want to see the samples. This will speed up displaying the list the first time you open it
* Items in the File > Open Recent menu, when mouseovered, show tooltips with the full URI of each file in the list. Also, files that are in the list but are missing or unaccessible are automatically hidden
* When a flowed text is truncated (i.e. the frame is too small for the entire text), the frame is shown red, and the statusbar hint includes '''[truncated]'''. You need to resize the frame to see the truncated end of the text. Analogously, if the path of a text-on-path object is too short to display the entire text, the statusbar will report it as '''[truncated]'''
* Clicking the text alignment buttons (Left, Center, Right) on the Text tool's controls bar now does not let the text jump: it stays within the same bounding box as before, only changing the alignment
* The position of text's baseline anchor (the small square) is now dependent of the alignment: for left-aligned text it is, as before, at the left end, for centered text in the middle, and for the right-aligned text it is at the right end of the text's first line (this is for horizontal text; for vertical, it is correspondingly at top, middle, or bottom of the first column). This allows snapping, aligning and distributing of text relative the side to which it's aligned
* Snapping of gradient handles has been improved and now behaves similar to the snapping of all other handles and objects
* When snapping to a bounding box, that bounding box will be shown for a moment (tied to the snap indicator)
* If a new object is being created on the canvas with snapping enabled, then a snap indicator will also be shown for the first point
* There are now options for Margins when resizing a document to a selection or the drawing in Document Properties
* Preferences have been added to allow automatic grouping when setting a Clippath or Mask
* Bitmap copies created using the Make a Bitmap Copy command (Alt+B) are now embedded. Previously they were saved in an automatically generated file and linked
* The file preview size limit (in the File > Open and File > Import dialog box) is now 10 MB (1.3 MB in 0.47)

===Extended input device configuration===

The stock Input Devices dialog has been replaced with a completely redone version that provides a more useful representation of settings. It also contains a simple area for testing different inputs of different devices.

Additionally hardware setup itself has been separated from general settings to allow for easier dynamic switching of settings appropriate to the task at hand.

==User interface==

===Adaptive UI===
(In progress [[User:JonCruz|JonCruz]])

===Custom Swatches===

Custom swatches can be created and used on a per-document basis. An "Auto" color palette will track swatches in the current document and allow them to be set and used. The use is "live" with changes to the swatch being applied automatically to all objects set to it. The swatches can also be gradients and not just simple colors.

===New cursors in Selector===

Selector tool has a new mouse cursor (arrow with an open hand) for when your mouse is over a selectable object, and another (arrow with clinched hand) for when you're dragging an object. This improves precision of selection and UI consistency (previously, the mouse cursor over a selectable object was different across platforms, e.g. hand icon on Linux or four-way arrow on Windows).

===Translations===

New Farsi translation (in progress).

==Tutorials==

* SVG files are now optimized with Scour (filesize reduced by 40%).
* Bitstream Vera fonts replaced with generic sans and serif fonts (solves many font substitution issues).
* New Interpolate tutorial (Help > Tutorials > Inkscape: Interpolate).
* New translations in Farsi, Belarussian and Dutch.

==Windows port improvements==

The quality of the Windows port was improved substantially.

===Command line interface===

Command line functionality on Windows is now on par with Unix.

'''Single executable'''
:It's no longer needed to compile Inkscape with special flags or use third-party wrapper executables to see the command line output. Just type "inkscape" (without any extension) in the command prompt. This is made possible by a command-line wrapper named <tt>inkscape.com</tt>.
'''Relative paths'''
:You can now specify relative paths to files in options like <tt>--export-png</tt>. Commands like this will now execute correctly:
C:\svg> inkscape tiger.svgz --export-png=tiger.png

===Stability improvements===

Thanks to library updates, Inkscape should no longer randomly crash when editing documents. Most of them were caused by a GDI resource leak in Pango. It will also no longer crash when trying to import a corrupted image.

===Unicode compatibility===

Inkscape will now work correctly regardless of installation path. Previously, it was unusable when installed into a directory that contains characters not representable in the system codepage (icons were not shown in the UI, and no language files were found).

==Notable bug fixes==

* The 3D tool no longer inserts an inkscape:perspective element into SVG when it is not needed (i.e. when the document has no 3D box objects).
* Wrong clippaths and masks with cyclic recursion (i.e. clippaths or masks that refer to themselves via other clippaths or masks) no longer crash Inkscape.
* Default unit setting for the XY grid is now respected when creating a new grid.
* Pasting Live Path Effect stacks now works. It adds the stack of the copied object to the end of the LPE stack (if present) of the object it is pasted to.
* The accuracy of the bounding box calculation has been significantly improved when converting objects to patterns or markers. This should make it much easier to create patterns where the tiles should 'connect' to each other, e.g. a tile with a plus sign to create a hatched pattern.

==Known issues==

==Previous releases==

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

[[Category:Marketing]]

INX extension descriptor format

2010-03-02T21:39:05Z

AurelioAHeckert: effect needs-live-preview

== Introduction ==

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

== Localisation of extensions ==

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

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

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

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

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

== DTD ==

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

<!ATTLIST check reldir (absolute|path|extensions|plugins) #REQUIRED>
<!ATTLIST command reldir (absolute|path|extensions|plugins) #REQUIRED>
<!ATTLIST command interpreter CDATA #REQUIRED>
<!ATTLIST dependency type (executable|extension) #REQUIRED>
<!ATTLIST dependency location (absolute|path|extensions|plugins) #IMPLIED>
<!ATTLIST dependency description CDATA #IMPLIED>
<!ATTLIST effect needs-live-preview (true|false) #REQUIRED>
<!ATTLIST page name CDATA #REQUIRED>
<!ATTLIST page gui-text CDATA #IMPLIED>
<!ATTLIST param name CDATA #REQUIRED>
<!ATTLIST param type (int|float|string|boolean|enum|notebook|description|optiongroup|color) #REQUIRED>
<!ATTLIST param min CDATA #IMPLIED>
<!ATTLIST param max CDATA #IMPLIED>
<!ATTLIST param max_length CDATA #IMPLIED>
<!ATTLIST param precision CDATA #IMPLIED>
<!ATTLIST param gui-text CDATA #IMPLIED>
<!ATTLIST param gui-tip CDATA #IMPLIED>
<!ATTLIST param gui-description CDATA #IMPLIED>
<!ATTLIST param scope CDATA #IMPLIED>
<!ATTLIST param gui-hidden CDATA #IMPLIED>
<!ATTLIST param appearance (minimal|) "">
<!ATTLIST submenu name CDATA #REQUIRED>

== See Also ==
*[[INX Parameters]]
*[[ScriptingHOWTO]]

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

Talk:Inkscape

2009-12-16T14:54:31Z

AurelioAHeckert: Created page with '* The Working with SVN link must be removed from the front page and consider to remove the refereed svn page from this wiki.'

* The [[Working with SVN]] link must be removed from the front page and consider to remove the refereed svn page from this wiki.

Working with Bazaar

2009-12-01T17:15:41Z

AurelioAHeckert: Registering Bugfixes doc link

'''WARNING: <tt>lp:inkscape</tt> is currently out of date. Do not use it until the migration to Launchpad is complete.'''

==Bazaar concepts==

It is assumed that you are familiar with the basic concepts of version control, like working copy, committing, updating, conflicts. There will be a section that explains the basic functionality soon.

* '''Branch''' is a working copy of the project's code. Typically you use one branch per set of related changes, for example a new output extension. Once your work is finished, you ''merge'' your branch into a larger project. Initially, there is only one branch, the trunk; all other branches are its (probably indirect) descendants. To create a new branch, you have to copy an existing one.
* '''Checkout''' is a copy of code contained in a branch that is not stored on your computer (a remote branch). Committing to a checkout will immediately apply the changes to the remote branch. Commits will not succeed if somebody else
* When branches A and B have a common ancestor branch but each contain changes not present in the other, they have '''diverged'''. For example, when you work on an improved rectangle tool in your own branch and at the same time somebody else applies a PDF export bugfix to the trunk, your rectangle tool branch becomes diverged from the trunk.
* '''Trunk''' is the main branch, which represents cutting-edge working code. You should start from it when doing any new development.
* '''Merge''' is the process of reconciling changes made between two branches since they diverged. This operation is asymmetric. When you merge A into B, all changes made to A since it was branched from B are applied to B. A is not changed. When you work on some feature, you typically work in a branch, periodically merging the trunk into your branch (to sync up with the latest changes), then you merge your work into the trunk. Merging is similar to applying a patch - it only changes your working copy. To apply a merge, you need to commit the changes it introduced. Merging un-diverges branches.
* '''Repository''' is a place where branches of a project are stored. Having a shared repository reduces the storage requirements of multiple branches of one project. Instead of O(number of branches) space, they take roughly O(size of changes).
* '''Bind''' is the process of converting a non-diverged local branch into a checkout.
* '''Push''' is the process of publishing an exact copy (a mirror) of your branch in some other location. The difference between pushing and checkouts is that a checked out remote branch is updated every time you commit, while a pushed remote branch is updated only when you push to it. You can only push to a branch if the mirror has not diverged from your local copy. This can happen if more than 1 person can push to the same location.
* '''Pull''' is the process of creating a local exact copy (mirror) of a branch, in principle a reverse of pushing.

==First steps==

First you need to tell Bazaar your name. This will appear on all your commits. You should use your real e-mail, but you can obfuscate it if you are afraid of spam.

Obfuscated e-mail example:
$ bzr whoami "John Q. Public <john dot q dot public at-sign bigmail dot com>"
Unobfuscated e-mail example:
$ bzr whoami "John Q. Public <john.q.public@bigmail.com>"

The basic usage:
$ bzr branch lp:inkscape
$ cd inkscape
$ bzr bind lp:inkscape
<do work>
$ bzr commit
<error, someone else has changed things>
$ bzr update
<check all is okay>
$ bzr commit

==SVN-style checkout==

Bazaar can be used very much like SVN.

* Get the latest Inkscape code: <tt>bzr checkout lp:inkscape</tt>
* Make changes to the files. If you add new files, add them to version control with <tt>bzr add ''file''</tt>. You can recursively add all new files by writing simply <tt>bzr add</tt> in the top level directory.
* Commit the changes, making them accessible to others: <tt>bzr commit</tt>
* Receive the most up-to-date version of the code: <tt>bzr update</tt>

===Differences from SVN===

* Commits will fail if your checkout is not up to date, even if there would be no conflicts.
* The revision number is an attribute of the working tree, not of individual files. It is not possible to have different portions of the working tree at different revisions.
* <tt>bzr commit ''file''</tt> works like <tt> svn commit ''file'' && svn update ''project-root''</tt>. After a successful partial commit, the entire tree's revision is increased by 1.
* No special server is needed to publish a branch. You can push branches to anywhere, including simple FTP shares. In our scenario, Launchpad works like a central repository, but it's not required to publish everything there.
* You create branches locally. To simulate creating a SVN-style branch on Launchpad, you need to create a local branch, push it, then bind it to the pushed location.

==Using branches==
This will asumme this directory layout:
inkscape
+-trunk
| +-doc
| +-share
| +-src
| +-po
| +-...
+-my-branch
+-some-other-branch

===Repository setup===
If you are working on several things at once, it's better to use one branch per feature. Here is how to work with branches.

* Create a shared repository for your branches. This brings significant space savings if you have several branches, but is not mandatory: <tt>bzr init-repo --rich-root inkscape</tt>. This will create the directory <tt>inkscape</tt>, which will contain a shared repository used by all branches within it, in the rich root format. This is the format currently used by our Launchpad repository - if you choose another format, you might not be able to push your branches to Launchpad. Enter the directory just created: <tt>cd inkscape</tt>
* Create a new branch: <tt>bzr branch lp:inkscape my-branch</tt>. This will retrieve the main branch of Inkscape and put it in the subdirectory <tt>my-branch</tt>.
* Make changes. Commit them locally using <tt>bzr commit</tt>. Note that this doesn't touch the trunk on Launchpad; you are only committing to your local repository.
* If somebody else modified the trunk, resync with it: <tt>bzr merge</tt> (merging will automatically use the parent branch if none is specified)

===Publishing branches on Launchpad===
To publish branches on Launchpad, you have to add an SSH key to your account. You can generate a key using the program <tt>ssh-keygen</tt>.

When you added a key to your account, you can now use the Launchpad integration features.

* First you have to log in: <tt>bzr launchpad-login ''launchpad-username''</tt>. You need to use your username, not your display name.
* Publish your branch on Launchpad: <tt>bzr push lp:~''launchpad-username''/inkscape/my-branch</tt>. Of course if you're working with a different project, substitute <tt>inkscape</tt> with its Launchpad name.
* The push location will be saved. To update the branch on Launchpad, write <ttbzr push</tt> after your commits.
* If you want to always commit directly to the remote branch on Launchpad, write <tt>bzr bind lp:~''launchpad-username''/inkscape/my-branch</tt> after the initial push. This will convert your local branch into a checkout of the remote branch.

===Merging branches into trunk===

Way A: commit to a checkout of the trunk. This requires a trunk checkout, but for some people is more logical.

* Navigate to a checkout of the trunk.
* Execute <tt>bzr merge ''branch-url''</tt>. This will modify the files to receive the changes from the specified branch but will not modify the trunk.
* After verifying the changes (e.g. compile the program and see whether it doesn't crash on startup), execute <tt>bzr commit</tt> to apply the changes from the merge to the trunk.

Way B: merge from trunk, then push. It doesn't require a trunk checkout, but it may be less obvious what is happening.

* Navigate to the branch you want to merge.
* Execute <tt>bzr merge ''trunk-location''</tt>, where ''trunk-location'' might be your local trunk checkout or <tt>lp:inkscape</tt>
* Verify the changes, then execute <tt>bzr commit</tt>.
* Push to trunk: <tt>bzr push lp:inkscape</tt>

===Local branching===

Naturally, all this also works locally. For example, when you're in the <tt>inkscape</tt> directory, you can write <tt>bzr branch trunk export-dialog</tt> to create a new branch of the trunk called <tt>export-dialog</tt>, where you'll work only on improving the export dialog. Similarly, you can merge between local branches.

==Best Practicals for Inkscape Project==

===Registering Bugfixes===

Launchpad will automatically mark a bug "Fix Available" (rather than "Fix Committed") once somebody commits using the flag --fixes, e.g. (if you fix those two bugs in one commit):
bzr commit --fixes lp:123456 --fixes lp:123457 -m 'patch description'
Then, bugs can be changed automatically from "Fix Available" to "Fix Released"

[http://doc.bazaar-vcs.org/bzr.dev/en/tutorials/using_bazaar_with_launchpad.html#changing-the-state-in-launchpad-while-committing-in-bazaar Read more: "Changing the state in Launchpad while committing in Bazaar"]

==External links==
* [http://doc.bazaar-vcs.org/latest/en/ Bazaar manual]

Working with Bazaar

2009-12-01T17:14:23Z

AurelioAHeckert: /* First steps */

'''WARNING: <tt>lp:inkscape</tt> is currently out of date. Do not use it until the migration to Launchpad is complete.'''

==Bazaar concepts==

It is assumed that you are familiar with the basic concepts of version control, like working copy, committing, updating, conflicts. There will be a section that explains the basic functionality soon.

* '''Branch''' is a working copy of the project's code. Typically you use one branch per set of related changes, for example a new output extension. Once your work is finished, you ''merge'' your branch into a larger project. Initially, there is only one branch, the trunk; all other branches are its (probably indirect) descendants. To create a new branch, you have to copy an existing one.
* '''Checkout''' is a copy of code contained in a branch that is not stored on your computer (a remote branch). Committing to a checkout will immediately apply the changes to the remote branch. Commits will not succeed if somebody else
* When branches A and B have a common ancestor branch but each contain changes not present in the other, they have '''diverged'''. For example, when you work on an improved rectangle tool in your own branch and at the same time somebody else applies a PDF export bugfix to the trunk, your rectangle tool branch becomes diverged from the trunk.
* '''Trunk''' is the main branch, which represents cutting-edge working code. You should start from it when doing any new development.
* '''Merge''' is the process of reconciling changes made between two branches since they diverged. This operation is asymmetric. When you merge A into B, all changes made to A since it was branched from B are applied to B. A is not changed. When you work on some feature, you typically work in a branch, periodically merging the trunk into your branch (to sync up with the latest changes), then you merge your work into the trunk. Merging is similar to applying a patch - it only changes your working copy. To apply a merge, you need to commit the changes it introduced. Merging un-diverges branches.
* '''Repository''' is a place where branches of a project are stored. Having a shared repository reduces the storage requirements of multiple branches of one project. Instead of O(number of branches) space, they take roughly O(size of changes).
* '''Bind''' is the process of converting a non-diverged local branch into a checkout.
* '''Push''' is the process of publishing an exact copy (a mirror) of your branch in some other location. The difference between pushing and checkouts is that a checked out remote branch is updated every time you commit, while a pushed remote branch is updated only when you push to it. You can only push to a branch if the mirror has not diverged from your local copy. This can happen if more than 1 person can push to the same location.
* '''Pull''' is the process of creating a local exact copy (mirror) of a branch, in principle a reverse of pushing.

==First steps==

First you need to tell Bazaar your name. This will appear on all your commits. You should use your real e-mail, but you can obfuscate it if you are afraid of spam.

Obfuscated e-mail example:
$ bzr whoami "John Q. Public <john dot q dot public at-sign bigmail dot com>"
Unobfuscated e-mail example:
$ bzr whoami "John Q. Public <john.q.public@bigmail.com>"

The basic usage:
$ bzr branch lp:inkscape
$ cd inkscape
$ bzr bind lp:inkscape
<do work>
$ bzr commit
<error, someone else has changed things>
$ bzr update
<check all is okay>
$ bzr commit

==SVN-style checkout==

Bazaar can be used very much like SVN.

* Get the latest Inkscape code: <tt>bzr checkout lp:inkscape</tt>
* Make changes to the files. If you add new files, add them to version control with <tt>bzr add ''file''</tt>. You can recursively add all new files by writing simply <tt>bzr add</tt> in the top level directory.
* Commit the changes, making them accessible to others: <tt>bzr commit</tt>
* Receive the most up-to-date version of the code: <tt>bzr update</tt>

===Differences from SVN===

* Commits will fail if your checkout is not up to date, even if there would be no conflicts.
* The revision number is an attribute of the working tree, not of individual files. It is not possible to have different portions of the working tree at different revisions.
* <tt>bzr commit ''file''</tt> works like <tt> svn commit ''file'' && svn update ''project-root''</tt>. After a successful partial commit, the entire tree's revision is increased by 1.
* No special server is needed to publish a branch. You can push branches to anywhere, including simple FTP shares. In our scenario, Launchpad works like a central repository, but it's not required to publish everything there.
* You create branches locally. To simulate creating a SVN-style branch on Launchpad, you need to create a local branch, push it, then bind it to the pushed location.

==Using branches==
This will asumme this directory layout:
inkscape
+-trunk
| +-doc
| +-share
| +-src
| +-po
| +-...
+-my-branch
+-some-other-branch

===Repository setup===
If you are working on several things at once, it's better to use one branch per feature. Here is how to work with branches.

* Create a shared repository for your branches. This brings significant space savings if you have several branches, but is not mandatory: <tt>bzr init-repo --rich-root inkscape</tt>. This will create the directory <tt>inkscape</tt>, which will contain a shared repository used by all branches within it, in the rich root format. This is the format currently used by our Launchpad repository - if you choose another format, you might not be able to push your branches to Launchpad. Enter the directory just created: <tt>cd inkscape</tt>
* Create a new branch: <tt>bzr branch lp:inkscape my-branch</tt>. This will retrieve the main branch of Inkscape and put it in the subdirectory <tt>my-branch</tt>.
* Make changes. Commit them locally using <tt>bzr commit</tt>. Note that this doesn't touch the trunk on Launchpad; you are only committing to your local repository.
* If somebody else modified the trunk, resync with it: <tt>bzr merge</tt> (merging will automatically use the parent branch if none is specified)

===Publishing branches on Launchpad===
To publish branches on Launchpad, you have to add an SSH key to your account. You can generate a key using the program <tt>ssh-keygen</tt>.

When you added a key to your account, you can now use the Launchpad integration features.

* First you have to log in: <tt>bzr launchpad-login ''launchpad-username''</tt>. You need to use your username, not your display name.
* Publish your branch on Launchpad: <tt>bzr push lp:~''launchpad-username''/inkscape/my-branch</tt>. Of course if you're working with a different project, substitute <tt>inkscape</tt> with its Launchpad name.
* The push location will be saved. To update the branch on Launchpad, write <ttbzr push</tt> after your commits.
* If you want to always commit directly to the remote branch on Launchpad, write <tt>bzr bind lp:~''launchpad-username''/inkscape/my-branch</tt> after the initial push. This will convert your local branch into a checkout of the remote branch.

===Merging branches into trunk===

Way A: commit to a checkout of the trunk. This requires a trunk checkout, but for some people is more logical.

* Navigate to a checkout of the trunk.
* Execute <tt>bzr merge ''branch-url''</tt>. This will modify the files to receive the changes from the specified branch but will not modify the trunk.
* After verifying the changes (e.g. compile the program and see whether it doesn't crash on startup), execute <tt>bzr commit</tt> to apply the changes from the merge to the trunk.

Way B: merge from trunk, then push. It doesn't require a trunk checkout, but it may be less obvious what is happening.

* Navigate to the branch you want to merge.
* Execute <tt>bzr merge ''trunk-location''</tt>, where ''trunk-location'' might be your local trunk checkout or <tt>lp:inkscape</tt>
* Verify the changes, then execute <tt>bzr commit</tt>.
* Push to trunk: <tt>bzr push lp:inkscape</tt>

===Local branching===

Naturally, all this also works locally. For example, when you're in the <tt>inkscape</tt> directory, you can write <tt>bzr branch trunk export-dialog</tt> to create a new branch of the trunk called <tt>export-dialog</tt>, where you'll work only on improving the export dialog. Similarly, you can merge between local branches.

==Best Practicals for Inkscape Project==

===Registering Bugfixes===

Launchpad will automatically mark a bug "Fix Available" (rather than "Fix Committed") once somebody commits using the flag --fixes, e.g. (if you fix those two bugs in one commit):
bzr commit --fixes lp:123456 --fixes lp:123457 -m 'patch description'
Then, bugs can be changed automatically from "Fix Available" to "Fix Released"

[[http://doc.bazaar-vcs.org/bzr.dev/en/tutorials/using_bazaar_with_launchpad.html#changing-the-state-in-launchpad-while-committing-in-bazaar Read more: "Changing the state in Launchpad while committing in Bazaar"]]

==External links==
* [http://doc.bazaar-vcs.org/latest/en/ Bazaar manual]

Working with Bazaar

2009-12-01T17:10:53Z

AurelioAHeckert: /* First steps */

'''WARNING: <tt>lp:inkscape</tt> is currently out of date. Do not use it until the migration to Launchpad is complete.'''

==Bazaar concepts==

It is assumed that you are familiar with the basic concepts of version control, like working copy, committing, updating, conflicts. There will be a section that explains the basic functionality soon.

* '''Branch''' is a working copy of the project's code. Typically you use one branch per set of related changes, for example a new output extension. Once your work is finished, you ''merge'' your branch into a larger project. Initially, there is only one branch, the trunk; all other branches are its (probably indirect) descendants. To create a new branch, you have to copy an existing one.
* '''Checkout''' is a copy of code contained in a branch that is not stored on your computer (a remote branch). Committing to a checkout will immediately apply the changes to the remote branch. Commits will not succeed if somebody else
* When branches A and B have a common ancestor branch but each contain changes not present in the other, they have '''diverged'''. For example, when you work on an improved rectangle tool in your own branch and at the same time somebody else applies a PDF export bugfix to the trunk, your rectangle tool branch becomes diverged from the trunk.
* '''Trunk''' is the main branch, which represents cutting-edge working code. You should start from it when doing any new development.
* '''Merge''' is the process of reconciling changes made between two branches since they diverged. This operation is asymmetric. When you merge A into B, all changes made to A since it was branched from B are applied to B. A is not changed. When you work on some feature, you typically work in a branch, periodically merging the trunk into your branch (to sync up with the latest changes), then you merge your work into the trunk. Merging is similar to applying a patch - it only changes your working copy. To apply a merge, you need to commit the changes it introduced. Merging un-diverges branches.
* '''Repository''' is a place where branches of a project are stored. Having a shared repository reduces the storage requirements of multiple branches of one project. Instead of O(number of branches) space, they take roughly O(size of changes).
* '''Bind''' is the process of converting a non-diverged local branch into a checkout.
* '''Push''' is the process of publishing an exact copy (a mirror) of your branch in some other location. The difference between pushing and checkouts is that a checked out remote branch is updated every time you commit, while a pushed remote branch is updated only when you push to it. You can only push to a branch if the mirror has not diverged from your local copy. This can happen if more than 1 person can push to the same location.
* '''Pull''' is the process of creating a local exact copy (mirror) of a branch, in principle a reverse of pushing.

==First steps==

First you need to tell Bazaar your name. This will appear on all your commits. You should use your real e-mail, but you can obfuscate it if you are afraid of spam.

Obfuscated e-mail example: <tt><nowiki>bzr whoami "John Q. Public <john dot q dot public at-sign bigmail dot com>"</nowiki></tt>

Unobfuscated e-mail example: <tt><nowiki>bzr whoami "John Q. Public <john.q.public@bigmail.com>"</nowiki></tt>

The basic usage:
$ bzr branch lp:inkscape
$ cd inkscape
$ bzr bind lp:inkscape
<do work>
$ bzr commit
<error, someone else has changed things>
$ bzr update
<check all is okay>
$ bzr commit

==SVN-style checkout==

Bazaar can be used very much like SVN.

* Get the latest Inkscape code: <tt>bzr checkout lp:inkscape</tt>
* Make changes to the files. If you add new files, add them to version control with <tt>bzr add ''file''</tt>. You can recursively add all new files by writing simply <tt>bzr add</tt> in the top level directory.
* Commit the changes, making them accessible to others: <tt>bzr commit</tt>
* Receive the most up-to-date version of the code: <tt>bzr update</tt>

===Differences from SVN===

* Commits will fail if your checkout is not up to date, even if there would be no conflicts.
* The revision number is an attribute of the working tree, not of individual files. It is not possible to have different portions of the working tree at different revisions.
* <tt>bzr commit ''file''</tt> works like <tt> svn commit ''file'' && svn update ''project-root''</tt>. After a successful partial commit, the entire tree's revision is increased by 1.
* No special server is needed to publish a branch. You can push branches to anywhere, including simple FTP shares. In our scenario, Launchpad works like a central repository, but it's not required to publish everything there.
* You create branches locally. To simulate creating a SVN-style branch on Launchpad, you need to create a local branch, push it, then bind it to the pushed location.

==Using branches==
This will asumme this directory layout:
inkscape
+-trunk
| +-doc
| +-share
| +-src
| +-po
| +-...
+-my-branch
+-some-other-branch

===Repository setup===
If you are working on several things at once, it's better to use one branch per feature. Here is how to work with branches.

* Create a shared repository for your branches. This brings significant space savings if you have several branches, but is not mandatory: <tt>bzr init-repo --rich-root inkscape</tt>. This will create the directory <tt>inkscape</tt>, which will contain a shared repository used by all branches within it, in the rich root format. This is the format currently used by our Launchpad repository - if you choose another format, you might not be able to push your branches to Launchpad. Enter the directory just created: <tt>cd inkscape</tt>
* Create a new branch: <tt>bzr branch lp:inkscape my-branch</tt>. This will retrieve the main branch of Inkscape and put it in the subdirectory <tt>my-branch</tt>.
* Make changes. Commit them locally using <tt>bzr commit</tt>. Note that this doesn't touch the trunk on Launchpad; you are only committing to your local repository.
* If somebody else modified the trunk, resync with it: <tt>bzr merge</tt> (merging will automatically use the parent branch if none is specified)

===Publishing branches on Launchpad===
To publish branches on Launchpad, you have to add an SSH key to your account. You can generate a key using the program <tt>ssh-keygen</tt>.

When you added a key to your account, you can now use the Launchpad integration features.

* First you have to log in: <tt>bzr launchpad-login ''launchpad-username''</tt>. You need to use your username, not your display name.
* Publish your branch on Launchpad: <tt>bzr push lp:~''launchpad-username''/inkscape/my-branch</tt>. Of course if you're working with a different project, substitute <tt>inkscape</tt> with its Launchpad name.
* The push location will be saved. To update the branch on Launchpad, write <ttbzr push</tt> after your commits.
* If you want to always commit directly to the remote branch on Launchpad, write <tt>bzr bind lp:~''launchpad-username''/inkscape/my-branch</tt> after the initial push. This will convert your local branch into a checkout of the remote branch.

===Merging branches into trunk===

Way A: commit to a checkout of the trunk. This requires a trunk checkout, but for some people is more logical.

* Navigate to a checkout of the trunk.
* Execute <tt>bzr merge ''branch-url''</tt>. This will modify the files to receive the changes from the specified branch but will not modify the trunk.
* After verifying the changes (e.g. compile the program and see whether it doesn't crash on startup), execute <tt>bzr commit</tt> to apply the changes from the merge to the trunk.

Way B: merge from trunk, then push. It doesn't require a trunk checkout, but it may be less obvious what is happening.

* Navigate to the branch you want to merge.
* Execute <tt>bzr merge ''trunk-location''</tt>, where ''trunk-location'' might be your local trunk checkout or <tt>lp:inkscape</tt>
* Verify the changes, then execute <tt>bzr commit</tt>.
* Push to trunk: <tt>bzr push lp:inkscape</tt>

===Local branching===

Naturally, all this also works locally. For example, when you're in the <tt>inkscape</tt> directory, you can write <tt>bzr branch trunk export-dialog</tt> to create a new branch of the trunk called <tt>export-dialog</tt>, where you'll work only on improving the export dialog. Similarly, you can merge between local branches.

==Best Practicals for Inkscape Project==

===Registering Bugfixes===

Launchpad will automatically mark a bug "Fix Available" (rather than "Fix Committed") once somebody commits using the flag --fixes, e.g. (if you fix those two bugs in one commit):
bzr commit --fixes lp:123456 --fixes lp:123457 -m 'patch description'
Then, bugs can be changed automatically from "Fix Available" to "Fix Released"

[[http://doc.bazaar-vcs.org/bzr.dev/en/tutorials/using_bazaar_with_launchpad.html#changing-the-state-in-launchpad-while-committing-in-bazaar Read more: "Changing the state in Launchpad while committing in Bazaar"]]

==External links==
* [http://doc.bazaar-vcs.org/latest/en/ Bazaar manual]

Working with Bazaar

2009-12-01T17:05:54Z

AurelioAHeckert: Registering Bugfixes

'''WARNING: <tt>lp:inkscape</tt> is currently out of date. Do not use it until the migration to Launchpad is complete.'''

==Bazaar concepts==

It is assumed that you are familiar with the basic concepts of version control, like working copy, committing, updating, conflicts. There will be a section that explains the basic functionality soon.

* '''Branch''' is a working copy of the project's code. Typically you use one branch per set of related changes, for example a new output extension. Once your work is finished, you ''merge'' your branch into a larger project. Initially, there is only one branch, the trunk; all other branches are its (probably indirect) descendants. To create a new branch, you have to copy an existing one.
* '''Checkout''' is a copy of code contained in a branch that is not stored on your computer (a remote branch). Committing to a checkout will immediately apply the changes to the remote branch. Commits will not succeed if somebody else
* When branches A and B have a common ancestor branch but each contain changes not present in the other, they have '''diverged'''. For example, when you work on an improved rectangle tool in your own branch and at the same time somebody else applies a PDF export bugfix to the trunk, your rectangle tool branch becomes diverged from the trunk.
* '''Trunk''' is the main branch, which represents cutting-edge working code. You should start from it when doing any new development.
* '''Merge''' is the process of reconciling changes made between two branches since they diverged. This operation is asymmetric. When you merge A into B, all changes made to A since it was branched from B are applied to B. A is not changed. When you work on some feature, you typically work in a branch, periodically merging the trunk into your branch (to sync up with the latest changes), then you merge your work into the trunk. Merging is similar to applying a patch - it only changes your working copy. To apply a merge, you need to commit the changes it introduced. Merging un-diverges branches.
* '''Repository''' is a place where branches of a project are stored. Having a shared repository reduces the storage requirements of multiple branches of one project. Instead of O(number of branches) space, they take roughly O(size of changes).
* '''Bind''' is the process of converting a non-diverged local branch into a checkout.
* '''Push''' is the process of publishing an exact copy (a mirror) of your branch in some other location. The difference between pushing and checkouts is that a checked out remote branch is updated every time you commit, while a pushed remote branch is updated only when you push to it. You can only push to a branch if the mirror has not diverged from your local copy. This can happen if more than 1 person can push to the same location.
* '''Pull''' is the process of creating a local exact copy (mirror) of a branch, in principle a reverse of pushing.

==First steps==

First you need to tell Bazaar your name. This will appear on all your commits. You should use your real e-mail, but you can obfuscate it if you are afraid of spam.

Obfuscated e-mail example: <tt><nowiki>bzr whoami "John Q. Public <john dot q dot public at-sign bigmail dot com>"</nowiki></tt>

Unobfuscated e-mail example: <tt><nowiki>bzr whoami "John Q. Public <john.q.public@bigmail.com>"</nowiki></tt>

==SVN-style checkout==

Bazaar can be used very much like SVN.

* Get the latest Inkscape code: <tt>bzr checkout lp:inkscape</tt>
* Make changes to the files. If you add new files, add them to version control with <tt>bzr add ''file''</tt>. You can recursively add all new files by writing simply <tt>bzr add</tt> in the top level directory.
* Commit the changes, making them accessible to others: <tt>bzr commit</tt>
* Receive the most up-to-date version of the code: <tt>bzr update</tt>

===Differences from SVN===

* Commits will fail if your checkout is not up to date, even if there would be no conflicts.
* The revision number is an attribute of the working tree, not of individual files. It is not possible to have different portions of the working tree at different revisions.
* <tt>bzr commit ''file''</tt> works like <tt> svn commit ''file'' && svn update ''project-root''</tt>. After a successful partial commit, the entire tree's revision is increased by 1.
* No special server is needed to publish a branch. You can push branches to anywhere, including simple FTP shares. In our scenario, Launchpad works like a central repository, but it's not required to publish everything there.
* You create branches locally. To simulate creating a SVN-style branch on Launchpad, you need to create a local branch, push it, then bind it to the pushed location.

==Using branches==
This will asumme this directory layout:
inkscape
+-trunk
| +-doc
| +-share
| +-src
| +-po
| +-...
+-my-branch
+-some-other-branch

===Repository setup===
If you are working on several things at once, it's better to use one branch per feature. Here is how to work with branches.

* Create a shared repository for your branches. This brings significant space savings if you have several branches, but is not mandatory: <tt>bzr init-repo --rich-root inkscape</tt>. This will create the directory <tt>inkscape</tt>, which will contain a shared repository used by all branches within it, in the rich root format. This is the format currently used by our Launchpad repository - if you choose another format, you might not be able to push your branches to Launchpad. Enter the directory just created: <tt>cd inkscape</tt>
* Create a new branch: <tt>bzr branch lp:inkscape my-branch</tt>. This will retrieve the main branch of Inkscape and put it in the subdirectory <tt>my-branch</tt>.
* Make changes. Commit them locally using <tt>bzr commit</tt>. Note that this doesn't touch the trunk on Launchpad; you are only committing to your local repository.
* If somebody else modified the trunk, resync with it: <tt>bzr merge</tt> (merging will automatically use the parent branch if none is specified)

===Publishing branches on Launchpad===
To publish branches on Launchpad, you have to add an SSH key to your account. You can generate a key using the program <tt>ssh-keygen</tt>.

When you added a key to your account, you can now use the Launchpad integration features.

* First you have to log in: <tt>bzr launchpad-login ''launchpad-username''</tt>. You need to use your username, not your display name.
* Publish your branch on Launchpad: <tt>bzr push lp:~''launchpad-username''/inkscape/my-branch</tt>. Of course if you're working with a different project, substitute <tt>inkscape</tt> with its Launchpad name.
* The push location will be saved. To update the branch on Launchpad, write <ttbzr push</tt> after your commits.
* If you want to always commit directly to the remote branch on Launchpad, write <tt>bzr bind lp:~''launchpad-username''/inkscape/my-branch</tt> after the initial push. This will convert your local branch into a checkout of the remote branch.

===Merging branches into trunk===

Way A: commit to a checkout of the trunk. This requires a trunk checkout, but for some people is more logical.

* Navigate to a checkout of the trunk.
* Execute <tt>bzr merge ''branch-url''</tt>. This will modify the files to receive the changes from the specified branch but will not modify the trunk.
* After verifying the changes (e.g. compile the program and see whether it doesn't crash on startup), execute <tt>bzr commit</tt> to apply the changes from the merge to the trunk.

Way B: merge from trunk, then push. It doesn't require a trunk checkout, but it may be less obvious what is happening.

* Navigate to the branch you want to merge.
* Execute <tt>bzr merge ''trunk-location''</tt>, where ''trunk-location'' might be your local trunk checkout or <tt>lp:inkscape</tt>
* Verify the changes, then execute <tt>bzr commit</tt>.
* Push to trunk: <tt>bzr push lp:inkscape</tt>

===Local branching===

Naturally, all this also works locally. For example, when you're in the <tt>inkscape</tt> directory, you can write <tt>bzr branch trunk export-dialog</tt> to create a new branch of the trunk called <tt>export-dialog</tt>, where you'll work only on improving the export dialog. Similarly, you can merge between local branches.

==Best Practicals for Inkscape Project==

===Registering Bugfixes===

Launchpad will automatically mark a bug "Fix Available" (rather than "Fix Committed") once somebody commits using the flag --fixes, e.g. (if you fix those two bugs in one commit):
bzr commit --fixes lp:123456 --fixes lp:123457 -m 'patch description'
Then, bugs can be changed automatically from "Fix Available" to "Fix Released"

[[http://doc.bazaar-vcs.org/bzr.dev/en/tutorials/using_bazaar_with_launchpad.html#changing-the-state-in-launchpad-while-committing-in-bazaar Read more: "Changing the state in Launchpad while committing in Bazaar"]]

==External links==
* [http://doc.bazaar-vcs.org/latest/en/ Bazaar manual]

Release notes/0.47

2009-03-10T14:17:53Z

AurelioAHeckert: /* New and improved effects */

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

==Refactoring effort==

The focus of the 0.47 release was to clean up legacy code and push forward the migration to clean object-oriented C++. The goal of this effort was to increase reliability and maintainability of Inkscape. In the long run, it will mean less bugs and more new features, because it will be easier to develop and find bugs in Inkscape.

===Migration to lib2geom===
Many parts of the code have been changed to use the 2Geom library for geometrical calculations instead of the old libnr and Livarot libraries.

===Preferences===
Instead of global functions directly manipulating an XML document, the preferences API is now exposed through the <code>Inkscape::Preferences</code> singleton. It abstracts away the way the preferences are stored in memory. In fitire it may allow for different user settings storage backends (like GConf or the upcoming dconf on GNOME desktops or .plist files on OS X). Previously, Inkscape directly manipulated an internal XML document.

==Tools==

===Node tool===

* When hovering over a path in the Node tool, the path's outline will be displayed for a short time. This effect, its duration and the color of the outline is configurable.
* The Node tool can now edit '''clipping paths''' and '''masks''' of objects on canvas, without releasing them. If the selected object has a clipping path and mask, the corresponding buttons on the controls bar of the tool will be enabled; pressing these buttons will display the editable paths or handles of the clippath or mask. A clipping path is stroked green, a mask is stroked blue (the same colors as those used for them in Outline mode).
* Snapping has been improved (more details in Snapping below)
* When dragging a node handle with Ctrl pressed, it now snaps not only to the 15 degree increments starting from 0 and to the original handle direction, but also to the direction of the opposite handle (if it exists) or of the opposite line segment (if it is a straight line).
* The behavior of the buttons/shortcuts that make a node smooth or cusp has been improved:
** If a node is already a cusp (diamond shaped), pressing Shift+C again on it will retract both its handles. As this works for any number of selected nodes, you can always retract all handles in all nodes by selecting all nodes and pressing Shift+C twice.
** If a non-smooth node is next to a straight line segment, pressing Shift+S once makes it ''half-smooth'': it now has one handle aligned with that line segment. Another press of Shift+S will expand the second handle as well turning it into a full smooth node. If a node is between two curve segments, Shift+S will expand both handles as before.
*'''Auto smooth nodes''': a new "auto" node type was added, similar to the one Xara Xtreme has. An auto node is a smooth node which automatically adjusts (rotates and stretches) its handles when this node or its neighbors are moved. This adjustment (same as what you get when you convert node type to Smooth, but continuous) keeps the curve at this node as smooth as possible. It feels a bit like Spiro paths (see below); although not as smooth as a Spiro, auto nodes may often be preferable as they work without applying any Path Effect. Whenever you manually adjust the handles of an auto node or drag the adjacent curve, it loses its auto state and becomes simply smooth; for this reason, it is recommended to edit smooth nodes with the node handles hidden via a toggle button on the controls bar. Auto nodes are represented by little circles, as opposed to smooth/symmetric nodes (squares) and cusp nodes (diamonds). To convert selected node(s) to auto, press '''Shift+A''' or use the corresponding node type button on the controls bar.

===Tweak tool===

Several new modes are added to the Tweak tool for transforming, duplicating, and deleting selected objects using the same "soft brush" metaphor that the path editing and coloring modes use. Using these new modes, it is easy to "sculpt" scatterings of small objects, such as clone tilings, into complex and naturalistic textures.

* '''Push mode''' moves those selected objects that are under the brush in the direction in which you move the brush. This is similar to the Push path mode, except that the Move mode affects entire objects and not parts of the paths under the brush.

* '''Attract/Repel Objects mode''' moves those selected objects that are under the brush towards the cursor (default) or away from cursor (with '''Shift''' pressed). This is similar to the Attract/repel path mode, except that the Move in/out mode affects entire objects and not parts of the paths under cursor.

* '''Jitter mode''' moves those selected objects that are under the brush in random directions and by random amounts, but the overall amount of movement depends on Force, pen pressure (if you're using a tablet pen), on the closeness of the object to the center of brush, and on how long you apply the brush.

* '''Scale mode''' scales those selected objects that are under the brush down (by default) or up (with '''Shift''' pressed). The speed of scaling depends on Force, pen pressure (if you're using a tablet pen), on the closeness of the object to the center of brush, and on how long you apply the brush.

* '''Rotate mode''' rotates those selected objects that are under the brush clockwise (by default) or counterclockwise (with '''Shift''' pressed). The speed of rotation depends on Force, pen pressure (if you're using a tablet pen), on the closeness of the object to the center of brush, and on how long you apply the brush.

* '''Duplicate/delete mode''' randomly duplicates those selected objects that are under the brush (by default) or deletes them (with '''Shift''' pressed). The chance of an object to be duplicated and deleted depends on Force, pen pressure (if you're using a tablet pen), on the closeness of the object to the center of brush, and on how long you apply the brush. Like with the regular Duplicate command, duplicating with Tweak tool places the copies right over the originals, and you may need to use the Jitter mode to ruffle them apart. The duplicates created by the tool are automatically added to selection if the originals objects were in selection (e.g. if you're tweaking a group of objects, they are duplicated within that group and are not by themselves selected).

*'''Blur mode''' blurs the selected objects under the brush more (by default) or less (with Shift pressed). The amount of blur added or removed depends on Force, pen pressure (if you're using a tablet pen), on the closeness of the object to the center of brush, and on how long you apply the brush.

Also, the existing path editing modes of the tool have been rearranged: now Shrink and Grow are one mode (shrinks by default, grows with Shift), and Attract and Repel are one mode (attracts by default, repels with Shift). Here is a complete list of modes and shortcuts of the Tweak tool:

Shift+m, Shift+0 move mode
Shift+i, Shift+1 attract/repel objects mode
Shift+z, Shift+2 jitter mode
Shift+<, Shift+>, Shift+3 scale mode
Shift+[, Shift+], Shift+4 rotate mode
Shift+d, Shift+5 duplicate/delete mode
Shift+p, Shift+6 push path mode
Shift+s, Shift+7 shrink/grow path mode
Shift+a, Shift+8 attract/repel path mode
Shift+r, Shift+9 roughen mode
Shift+c paint mode
Shift+j color jitter mode
Shift+b blur mode

In Paint mode, painting with Shift inverts the color you're applying (e.g. when painting with yellow, Shift will switch the applied color to blue).

===Calligraphy tool===

* The tool's settings can now be saved and restored as presets.

* When drawing with Alt pressed, Inkscape subtracts the path you have created from the selected path. With Shift, it unions with the selected path. This allows you to quickly patch or fix problems in a stroke you have drawn without leaving the tool.

* The behavior of the tool when tracking a guide (drawing with Ctrl) has been improved:

** The initial "jerk" when you start drawing is suppressed.

** The undesired flipping of the stroke to the other side of the guide path, when drawing along closed paths, is fixed.

** If you lose connection with your guide path, the tool tries to continue moving in the same direction as if by inertia, so as to minimize the tearoff jerk.

===Paint Bucket tool===
* Paint Bucket is now more tightly integrated with potrace. As a result, memory and CPU usage on each fill operation have been reduced significantly.

===Eraser Tool===
A new eraser tool has been added. Its shortcut is Shift+E. It has two main modes:

* Delete Objects mode where any shape touched by the tool is deleted completely. This operation is in line with "vector" editing.
* Cut mode where erasing acts similar to erasing in a standard bitmap editor. It acts on all objects in the current layer.

===Pen and Pencil===

Apart from the regular Bezier mode, the pen tool now provides several new modes:

* '''Spiro mode''': This mode automatically applies the new Spiro Splines LPE (see the section on new effects) to any newly drawn path. As mentioned below, it is not yet possible to preview Spiros before the path is finished.

* '''Polyline mode''': This mode makes it easy to draw many straight line segments in quick succession by disallowing curves (even when you drag with the mouse).

* '''Paraxial polyline mode''': In this mode, you can create straight line segments that are parallel to one of the coordinate axes. Normally, each line segment is drawn perpendicular to the previous one. The direction of the line segment being drawn can be toggled with Shift. When clicking on the start anchor, the path is closed with an L-shaped segment (the direction of which can also be flipped with Shift).

Furthermore, it is now possible to automatically apply predefined vector brushes to path strokes in pen and pencil tools. This is a first step towards [http://wiki.inkscape.org/wiki/index.php/Vector-brushes this blueprint].

In Pencil tool, the controls bar now provides the '''Smoothing''' parameter, changeable in the range from 1 to 100, which controls how much smoothing is applied to the freehand line. Small Smoothing values produce rough lines with many nodes; large values give smooth lines with few nodes. Previously, this control was only available in Inkscape Preferences.

====Pencil sketch mode====
[johan]
Press alt and sketch away, release alt to finalize result.

===Text tool===

When editing multiline or flowed text, the '''PgUp''' and '''PgDn''' keys now work to move the cursor by one screen (i.e. by as many lines as fit into the screen at current zoom).

==Path effects==
===Notable bug fixes and effect changes===
We try to refrain from changing the behavior of LPE's, because it will change appearance in old files when opened in new version of Inkscape (but not in any other SVG viewer or editor). However, when an effect is really broken, we have to fix it:

* The Pattern Along Path effect:
**The pattern used to be stretched across discontinuities. This has been fixed; now it treats a discontinuous path as a group of continuous paths and applies the effect separately to each.
** Successive copies of the pattern can now be fused into continuous paths (using the new "fuse nearby ends" feature) so that "filling" the result works as expected.

===New effects===

* '''Sketch''': Simulates hand-drawn lines. A set of parameters lets you tune the effect. They are all summarized in this [[:Image:SketchParameters.png|picture]].

:[[Image:SketchExemple.png|300px]]

* '''Hatches''' Fills the given shape with rough, configurable and randomized hatches, simulating a quick hand drawing.
:[[Image:hatches-lpe.png|300px]].



* '''Knot''': Creates a knot from a flat self intersecting curve. At each crossing, one string is interrupted to make it look like going under the other. The "sign" of each crossing can be set independantly.
:[[Image:KnotExample.png|300px]]

:''Known limitation'': can not be applied to groups nor be shared by different objects.

* '''Perspective paths''': Draw an arbitrary path as if viewed in perspective. This is work in progress. Known limitations (among others): It can only use the first perspective that exists in the document defs, and the perspective cannot be adapted interactively yet (the effect must be removed and reapplied after modifying the perspective). [max]

* '''Spiro splines''' are a novel way of defining curvilinear paths [http://www.levien.com/spiro/ developed by Raph Levien]. It takes some getting used to, but for certain tasks (such as lettershape design) Spiros have a clear advantage over Bezier curves. Recently, Spiro support was added to the FontForge font editor; now it is available in Inkscape too, which means you can use all the convenient Inkscape path tools (moving and transforming groups of nodes, node sculpting, etc.) on Spiro paths.

:A Spiro path is defined by a sequence of points, but unlike a regular path with Bezier curves, all Spiro points lie on the path and there are no off-path handles. The curvature of the path is defined entirely by the positions of the points and their types. The path behaves very similar to a springy rod which is forced to pass through the given points and which uses the minimum possible curvature to satisfy the requirement. As such, it feels quite natural and the resulting path is very smooth - not just superficially smooth (i.e. having no cusps), but smooth at a deeper level, which you can achieve with Beziers only after a lot of laborious tweaking.

:To create a Spiro path, select any path and assign the "Spiro spline" path effect to it. There are no parameters. Each node of your path becomes a point of a Spiro path, depending on the type of node:

:* Smooth nodes (those with two collinear Bezier handles; use Shift+S to make a node smooth) become smooth curve points of the Spiro path. Note that the length or direction of the Bezier handles of the source path is ignored; the only thing that matters is their collinearity.

:* Cusp nodes of the source path become corner points of the Spiro path, like free hinges on the springy rod. Between two corner points, the path is always a straight line. To make a node cusp, retract its Bezier handles by Ctrl+click, or press Shift+C and move one of the handles so they are no longer collinear.

:* Half-smooth nodes - those with one Bezier handle collinear with a straight line segment on the other hand - become "left" or "right" points on the Spiro path which behave exactly the same: they sit between a straight line and a curve and enforce that these two segments join smoothly without a cusp. To create such a node, make sure one of the segments is a line (select its ends and press Shift+L), then Ctrl+drag the remaining handle to make it snap to the direction of the straight line segment on the other side, or press Shift+S to lock it to that direction.

:Note that what matters is the actual collinearity of a node's handles, regardless of the node type that the node has in the Node tool; for example, if a node designated as cusp (diamond-shaped) has collinear handles, it will become a smooth curve point of the Spiro path.

:Some configurations of points do not converge and produce wild loops and spirals instead of a smooth curve. According to Raph, "The spline solver in this release is _not_ numerically robust. When you start drawing random points, you'll quickly run into divergence. However, "sensible" plates based on real fonts usually converge." Avoid too sharp changes in direction between points to prevent divergence. Hopefully, the robustness of the algorithm will be improved in future releases.

:For now, to edit Spiro paths viewing the result in real time, you have to use the Node tool; it is recommended to turn off the red highlight of the source path. The Pen tool does not yet allow you to preview a Spiro as you draw, although you can paste the Spiro effect on the path and see the result as soon as the path is finalized.

:You can always use the Node tool to continue a Spiro path by duplicating and dragging away its end nodes. Also, when you have a Spiro path selected, you can add a new subpath to it with Pen or Pencil if you start drawing with Shift.

* '''Construct Grid''' [johan]

* '''Perpendicular bisector''' [max]

* '''Angle bisector''' [max]

* '''Tangent to a curve''' [max]

* '''Circle through 3 points''' [max]

* '''Circle with radius''' [max]

* '''Envelope Deformation''' allows you to deform an object (or a group of object) by deforming its sides. Modifications are done by deforming the four path parameters: Top, Bottom, Left and Right.

* '''Lattice Deformation''' allows you to deform an object (or a group of objects) by moving 16 control points.

* '''Ruler''': [max]

* '''Freehand Shape''': [max]

* '''Interpolate Subpaths''': [Johan]

* '''Path Length''': [max]

* '''Text Label''': [max]

===New features===
* The '''Paste Path Effect''' command is enabled to assign the path effect of the clipboard to any number of paths, going recursively into groups if necessary.

* A new command, '''Remove path effect''' removes any path effects from all selected objects, going recursively into groups if necessary.

* Along with the commands to open the path effects dialog and to paste path effects, the three commands were collected in a submenu under Path menu.

* Live path effects can now be assigned to the sides of a 3D box (use Ctrl+click to select individual sides).

* The Pen and Pencil tools now correctly work with paths with LPEs: you can continue such a path or add a new subpath to it by drawing with Shift, all preserving the effect applied to it.

* Path type parameters can now link to existing shapes <b>and text</b>, like clones do. Now it is possible to use text as input for the Pattern Along Path effect for example!

* Lib2geom now has an implementation for EllipticalArc. For Inkscape, this means that it is now possible to directly copy-paste ellipse shapes on path parameters (e.g. 'pattern' in Pattern along Path), without the need to convert the ellipse object to path first. [needs coding and checking]

===Live Path Effects for groups===

LPE can now be assigned to a group. For most LPEs, the effect is applied recursively but for Bend Path or Deformations the result is more powerful : the distortion applies on the whole group.

*You can as usual enter the group by double-clicking on it.
*It applies recursively, this means that a LPE can be assigned to groups of groups
*The Effect can be applied definitively with "Convert Object to path"

===Live Path Effects stacking===

With Live Path Effects stacking, more than one Live Path Effect can be assigned to an item. A new UI was created to control the stack.

==Import/Export==
===PostScript and EPS import===

Inkscape's capability to open or import PS and EPS files now uses Ghostscript instead of pstoedit. If you need to open files of these types, install Ghostscript and make sure the directory with the <code>ps2pdf</code> utility from Ghostscript installation is in your PATH. On opening, you will see a preferences dialog similar to PDF import, which, for multipage PS files, allows you to select the page to open.

===PDF import from the command line===

Now you can use, for example,

inkscape file.pdf --export-plain-svg=file.svg

It will take the first page of the PDF and all the default import options, and save the result to SVG. If you try to import PDF without an <code>--export</code> command, it will show the import options dialog as before and open the file in the UI.

===PDF, PostScript, and EPS export===

The new Cairo-based PS and EPS exporter provides a much better support for various vector features, including clipping paths, patterns, and non-ASCII characters. Those features that are not supported by the target formats are exported via embedded rasters that preserve the appearance; in particular:

* transparency is always rasterized in PS or EPS (but not PDF, as PDF supports vector transparency);

* filters, such as blur, are by default rasterized in all three formats (PS, EPS, PDF), but this can be turned off by unchecking the "Rasterize filter effects" option in the UI or adding the --export-ignore-filters option via the command line, in which case filtered objects are rendered as vectors without filters and without rasterization.

All of PS, EPS, and PDF export formats uniformly support the export area options (canvas or drawing) and the new export-id option:

* You can now export a single object from a complex document (for example, a single layer) if you specify the ID of that object in the "Limit export to the object with ID" field in the GUI or via the '''--export-id=ID''' option on the command line. The export will show only that object (all others will not be exported at all). The BoundingBox (page size) of the exported PS/EPS/PDF file will correspond to the bounding box of that object; you can override that with "Export area is whole canvas" (GUI) or '''--export-area-canvas''' (command line) option which forces the output to have the size of the SVG document's canvas (this may not be possible with EPS, see below).

* The "Export area is whole canvas" (GUI) or '''--export-area-canvas''' (command line) option forces the output to have the size of the SVG document's canvas. This is the default for PS and PDF but not for EPS.

**Note that for EPS, the specification of the format does not allow its bounding box to extend beyond its content. This means that when --export-area-canvas is used with EPS export, the canvas bounding box will be trimmed inwards (but never outwards) to the bounding box of the content if it is smaller. If you want a file which has a %BoundingBox different from the bounding box of its content, you can use PS or PDF export formats instead of EPS, or add a white background rectangle with the required size to source document before exporting to EPS.

** The <b>--export-bbox-page</b> command line parameter is removed; use <b>--export-area-canvas</b> instead.

* The "Export area is the drawing" (GUI) or '''--export-area-drawing''' (command line) option forces the output to have the size of the exported objects' bounding box, regardless of canvas size. If no --export-id is specified, this means the bounding box of the entire drawing; with --export-id, this means the bounding box of the exported object only. This is the default for EPS.

* The <b>--export-embed-fonts</b> option is removed; now Inkscape always embeds and subsets all fonts used in the document when exporting PS, EPS, or PDF.

===CUniConvertor-based import import===

Inkscape can now use UniConvertor to import files of the following types:

* Corel DRAW Compressed Exchange files (CCX)
* Corel DRAW 7-X4 Template files (CDT)
* Corel DRAW Presentation Exchange files (CMX)
* sK1 files
* Computer Graphics Metafiles (CGM)

Text objects are not supported as of UniConvertor 1.1.1.

===HPGL export===

Inkscape can now export to HPGL (Hewlett-Packard Graphics Language). It is a file format that is used for various cutters/plotters.

===JavaFX export===

[]

===DXF export===

DXF export is much faster than in previous versions.

===PNG export===

* If you specify a relative path for exported PNG file (e.g. <code>../</code>) it will now be resolved relative to the current document's location.

* PNG export has been updated to include metadata if present in the source SVG.

==Autosave==

Autosave has now been added to allow for automatic timed backups as work goes on. Saved versions are put in a designated directory and do not overwrite the original SVG file and each other. Go to Inkscape Preferences, Autosave tab, to enable this feature and specify the backup time interval, the directory, and the maximum number of saved backups (if this number is exceeded, old backups will start to be deleted).

==Extensions==

* The former Effects menu is renamed to '''Extensions'''. This is less confusing and better reflects the content of the menu: a collection of extensions, written mostly in Python, which perform various tasks with or without selection.

===New and improved effects===

* The new '''Arrange > Restack''' extension restacks the Z-order of selected objects, from left to right, top to bottom (or vice versa), with radial outward or inward or by an arbitrary angle, specifying the base point for comparison (top, left, middle, etc.).
* The improved '''Modify Path > Add Nodes''' extension now also allows segments to be divided into a given number of subsegments.
* The new '''Printing > Add printing marks''' extension add useful printing marks and color bars required by printing bureaus. You can either manually define margins by which cut marks are created.
* The new '''Render > 3D Polyhedron''' extension allows drawing polyhedrons from scratch and render them from OBJ files.
* The new '''Render > Alphabet Soup''' extension is a vector rework of Matt Chrisholm's [http://www.theory.org/artprojects/alphabetsoup/main.html GPLed script]. Alphabet Soup randomly mashes glyph-elements together to make exotic looking text.
* The new '''Render > Cartesian Grid''' extension plots Cartesian (square) grids that do not fill the page, but offer three levels of division, logarithmic scales (with clutter-reduction and arbitrary base) and customisable line width. All like elements (eg x-axis subminor divisions) are put into subgroups together. A proper border is also drawn, with an independent line thickness.
* The new '''Render > Draw from Triangle''' extension takes a triangle drawn as a path (only the first three nodes of a path are counted) and allows to draw many triangle-related geometrical objects such as circumcircles, excentral triangles, etc. It also allows entry of custom trilinear coordinated and triangle centre functions, as well as computation of basic triangle properties such as area and semiperimeter.
* The new '''Render > Guides Creator''' extension allows creating easily horizontal and vertical guides for dividing equally the canvas. You can choose the divisions from None, 1/2, 1/3 ... to 1/10.
* The new '''Render > Polar Grid''' extension plots a polar co-ordinate grid, with options for arbitrary-base logarithmic subdivisions, clutter-reduction around the origin, circumferential labels and custom line widths.
* The new '''Render > Calendar''' extension draws a calendar for a given year with localizable month/weekday names, colors, and other options.
* The new '''Text > Convert to Braille''' extension recodes English (or just Latin letters) text to [http://en.wikipedia.org/wiki/Braille Braille] code. This is obviously just an aesthetical feature. It is not intended to create real braille text for visually impaired people but instead it is meant to enable an accurate graphical representation of braille text to be used in illustrations.
* The new '''Render > Foldable Box''' extension helps to design and construct paper boxes.

===API changes===

While the "Live preview" checkbox is useful for most effects, for some it just does not make sense. Now, you can add the attribute <code>needs-live-preview="false"</code> in the <code>effect</code> element in the .inx file of the effect to suppress this checkbox for your effect.

Parameters passed to extensions (via the <param> element) now have a new boolean attribute - <code>gui-hidden</code> to indicate that the parameter should not be represented in the GUI. If all parameters are marked as hidden no GUI is presented for such extension.

All '''.inx''' files are now properly formatted XML files with its own namespace of: <code><nowiki>http://www.inkscape.org/namespace/inkscape/extension</nowiki></code> and a Relax NG schema to define it. More information can be found in the [[Extensions]] Article.

==Filters==

The Filter Editor (former Filter Effects) and Remove Filters commands are moved from the Object menu to the new '''Filters''' top-level menu, which also contains a collection of preset filters.

===Preset filters===

The Filter Editor is powerful, but can be quite cumbersome. You can now add complex preset filters to the selected objects with a single command by choosing it from the new '''Filters''' top-level menu. Submenus categorize the filters by function or appearance. Most filters apply immediately after selecting the command; some present a dialog where you can adjust some of the parameters before applying the filter (such filters have "..." at the end of the command in the menu). If the selected object already has some filter applied, the chosen filter will be merged with the existing filter for combined effect.

You can easily add your own filters to these menus. Simply place any SVG file with the filters to the <code>filters</code> subdirectory of your config directory (<code>~/.config/Inkscape/</code> on Linux) and the filters will be picked up. By default, they will be placed in the Personal submenu under Effects > Filters. If you want to control this, add the following attributes to the <code>filter</code> element:

inkscape:label is the command label
inkscape:menu is the submenu to place the command into
inkscape:menu-tooltip is the tooltip (displayed in the statusbar
as you select the command)

===''No Filters'' rendering mode===
In order to facilitate editing documents that use lots of SVG filter effects, filter effects can now be disabled for a particular document window by selecting '''View|Display mode|No Filters''' from its menu. This provides an intermediate step between "normal" and "outline" view modes.

The Toggle view command in the Display mode submenu (Ctrl+keypad 5) toggles between the outline view and either regular or no-filters view, depending on which was used most recent.

===Filter quality setting===

Instead of the 'blur quality' setting, Inkscape now has a general 'filter effects quality' setting. It affects all filters and gives you an opportunity to find optimum balance between speed and accuracy when rendering filters.

==SVG support==

===Optimized CSS properties===

* As a file size optimization, Inkscape does not write into SVG some of the stroke properties if the object has <code>stroke:none</code> and some of the fill properties when it has <code>fill:none</code>. The only situation where this might affect you is if you remove stroke from an object and then turn it back on - the object will get the default stroke instead of the same it had before.

:Also, in manually-edited SVG where a parent group has no stroke but sets some stroke properties to be inherited by its descendants, you will need to set stroke property to other than none on the group, and suppress inheritance with stroke:none on those children that don't need it.

:Specifically, if stroke:none, the following properties do not get written to SVG:

stroke-width
stroke-linecap
stroke-linejoin
stroke-miterlimit
stroke-opacity
stroke-dasharray
stroke-dashoffset

:Note that this does not include marker properties, which means you can still have markers on a path without visible stroke.

:If fill:none, the following properties do not get written to SVG:

fill-opacity
fill-rule

*The <code>opacity</code> property is not written if it has the default value of 1 (this property is not inherited, so the change should have no side effects).

*The <code>marker-start</code>, <code>marker-mid</code>, and <code>marker-end</code> properties are not written if the <code>marker</code> property is already present with the same value.

===Optimized path data===

In this version, the size of the path data written in the <code>d=</code> attribute of <code>path</code> elements is reduced by about 10%. Inkscape generates the shortest possible path strings by avoiding repeated operators and using relative coordinates (when it helps).

This is controlled by the '''SVG output''' page of Inkscape Preferences dialog, as well as the following attributes in <code>group id="svgoutput"</code> in your preferences.xml file:

* allowrelativecoordinates (default 1) to switch relative coordinates on (1) or off (0)
* forcerepeatcommands (default 0) to force repeating operators (1) or allow use of the more compact representation without repeated operators (0)

===No more explicit closing line segment===
Inkscape used to always explicitly write the closing line segment to SVG for closed paths. For example: "M 0,0 L 1,0 L 1,1 L 0,1 L 0,0 z". With the improved SVG path data writing, Inkscape no longer generates this closing line segment, resulting in "M 0,0 L 1,0 L 1,1 L 0,1 z".
When SVG path data input contains this explicit closing segment, it is maintained throughout transformations, but is removed after using the node edit tool.
[this seems no longer to be true, fix it!!! -johan]

===Horizontal and vertical path segments===

If an SVG contains paths with shorthands for horizontal and vertical path segments ('H' or 'V'), then Inkscape will try to maintain those shorthands if possible, so the saved file will also contain them.

===<script> tag preserved===

While Inkscape does not yet support SVG scripting via the <script> element, this element is now preserved after editing the file in Inkscape.

===Initial SVG Fonts support===

As a SoC 2008 project, JucaBlues implemented initial parsing and rendering of [http://www.w3.org/TR/SVG11/fonts.html SVG Fonts].
You can design fonts within Inkscape, but using them to render text on the canvas is not yet supported. Currently the main benefit of this feature is to improve the font design workflow when working with FontForge: you only need one file per font instead of one file per glyph.

You can open the SVG Font dialog through Text->SVG Fonts menu option.

===SVG Test Suite Compliance===

[describe what has been improved over 0.46 and point to recent test result website]
As a result of last year's GSoC, there is now a rendering test framework along with a number of tests (found in the SVN repository [http://inkscape.svn.sourceforge.net/svnroot/inkscape/gsoc-testsuite/tester/ here]. These tests can be run reasonably easily on any system (you don't need to be able to compile Inkscape) and include a large part of the [http://www.w3.org/Graphics/SVG/Test/ [[W3C]] SVG Test Suite]. See [http://home.hccnet.nl/th.v.d.gronde/inkscape/ResultViewer.html this list] for up-to-date rendering results. Also see [[TestingInkscape]] for information on running and creating rendering tests.

List of render test changes with respect to 0.46:
...[files which failed on 0.46 and now pass, and vice versa]

==Editing Aids==

===Grids===
* The dotted rectangular grid now shows small crosses at the intersection points of emphasis lines.

===Guides===

* Guides can now be rotated using the mouse. Each guide has an anchor that determines the point around which it rotates.
* There is now an option to treat groups as single objects during conversion to guides (as opposed to converting each object inside the group separately).

===Snapping===

The code relating to the snapping mechanisms has undergone major changes to make it more reliable and easier to use from a developer's perspective. Snapping to objects now invokes routines from the 2geom library, which is actively maintained and less error prone than the old Livarot library. This fixes at least two known snapping bugs.

There is a new toolbar to control the snapping options and modes. Use View > Show/Hide > Snap controls bar to show or hide this toolbar. To control some other new snapping features, a dedicated tab has been created in the preferences dialog. The new features found on this tab are:
* '''Snap indicator''': When snapping has occurred, an indicator is displayed at that specific position. For now that indicator is just a cross that disappears after a second. In the future the shape of the indicator will be related to the type of target that has been snapped to
* '''Snap delay''': Inkscape now optionally waits some time after the mouse pointer has stopped moving before it tries to snap. This makes Inkscape much more responsive on complex documents and allows moving objects in a straight line over a grid, amongst others.
* Inkscape can be forced to only try snapping the (source) node that is '''closest to the mouse pointer''', à la Corel DRAW. When this mode is enabled, a snap indicator will shortly be shown at that node. This will give you maximum control of the snapping which is useful for complex drawings with many nodes.
* When multiple snap solutions are found, Inkscape can either prefer the closest transformation (when the weight-slider is set to 0; this is the old mode), or prefer the moved object's node that was initially the closest to the pointer (when the slider is set to 1). The way Inkscape calculates the preferred snap has been improved too, which should lead to more predictable snapping.

Other improvements are:
* The '''Node tool''' now snaps to any unselected node (both cusp and smooth) within the path that's being edited, and nodes of other paths. It also snaps to the path itself, but only to the stationary segments in between two unselected nodes. It is now also possible to snap while moving nodes along a vertical or horizontal constraint.
* In the document properties dialog, the checkbox for "always snap" has been replaced by two radiobuttons; this should eliminate most of the confusion surrounding this option.
* Holding the Shift key now also disables snapping while dragging node handles, and while creating single dots
* During constrained drawing (using Ctrl), Inkscape will now only snap to the points on the constrained line.
* In the selector tool, snapping while skewing or moving with a constraint (with Ctrl) has been improved.

Inkscape now also considers the following objects for snapping:
* Clipping paths and masks
* Midpoints of line segments
* Midpoints of bounding box edges
* Page border
* Intersections of any kind of paths
* Smooth nodes
* Cusp nodes
* Each of the handle points when creating new shapes
* Single dots

==Other features==

===Spell checker===

There's now a built-in spell checker. Press '''Ctrl+Alt+K''' or choose ''Text > Check spelling'' to check all visible text objects in your document (they need not be selected) in turn, going top-to-bottom and left-to-right. Once a misspelled word is found, a red frame around it is displayed, and the object with the misspelling is selected; if you are in Text tool, it also places the text cursor at the beginning of the misspelled word.

In the dialog, you can choose one of the listed suggestions and '''Accept''' it (this button is disabled unless you choose something in the list); '''Ignore''' the word for the rest of this session; or '''Add''' the word to the local dictionary.

Also, since the dialog does not lock Inkscape's window, you can simply edit the word with Text tool. Once you edit it to something acceptable to the speller, it will automatically turn off the red frame and continue checking the
document.

On Linux, you need to install Aspell and its dictionaries for the languages you want to check. On Windows, for now, only the English dictionary is included with Inkscape builds.

===Desktop integration improvements===

* '''Clipboard is system-wide''' - you can now copy/paste objects between different Inkscape instances as well as between Inkscape and other applications (which must be able to handle SVG on the clipboard to use this).

* '''Open Recent menu''' now integrates with Windows recent documents management as well as freedesktop.org recent document lists (used by Gnome, KDE and Xfce). The list can be cleared from the Preferences dialog (the Interface tab).

* '''Themable Icons''' - all icons used in Inkscape are now themable using the standard freedesktop.org theming mechanism. The list of names used is available [[themable icons|here]].

===Shell mode===

TODO: if it is intended for scripts, why does it spam the console so much? It should only print anything when there are errors. --[[User:Tweenk|Tweenk]] 00:04, 27 February 2009 (UTC)

If you run inkscape with <code>--shell</code>, it will enter a shell mode. In this mode, you type in commands at the prompt and Inkscape executes them, without you having to run a new copy of Inkscape for each command. This feature is mostly useful for scripting and server uses: it adds no new capabilities but allows you to improve the speed and memory requirements of any script that repeatedly calls Inkscape to perform command line tasks (such as export or conversions). Each command in shell mode must be a complete valid Inkscape command line but without the Inkscape program name, for example:

$ inkscape --shell
Inkscape 0.46+devel interactive shell mode. Type 'quit' to quit.
>file.svg --export-pdf=file.pdf
>otherfile.svg --export-png=bitmap.png
Background RRGGBBAA: ffffff00
Area 0:0:744.094:1052.36 exported to 744 x 1052 pixels (90 dpi)
Bitmap saved as: bitmap.png
>quit

===Gesture-based stroke width adjustment===

Similar to editing the fill or stroke colors by dragging away from the swatch in the status bar, which was added in the last version, this version allows you to drag away from the stroke width value displayed there to change the stroke width of selection. Dragging above the 45-degree line from the swatch increases the width (up to twice the original width), dragging below it decreases the width (down to half the original width). With this feature, quick and precise stroke width adjustments are possible without opening any dialogs or menus.

===Enhanced tablet support===

====Input device tool switching====

Tablets and other input devices that report separate hardware are now recognized and current tool and/or settings can be set to switch in response to the physical tool being used.

====Extended input device configuration====

The stock Input Devices dialog has been replaced with a completely redone version that provides a more useful representation of settings. It also contains a simple area for testing different inputs of different devices.

Additionally hardware setup itself has been separated from general settings to allow for easier dynamic switching of settings appropriate to the task at hand.

===Layers===

The Layers dialog now allows for hiding or showing all layers other than the current layer. This "solo" feature allows for faster switching between working layers and for quick checking with and without others shown.

A new command, '''Duplicate Layer''', has been added to the Layers menu to allow for duplicating an existing layer with all of its objects (even hidden or locked objects) and any sub-layers.

The New Layer dialog can be opened with '''Ctrl+Shift+N''' shortcut.

Layer names can now be non-unique.

Several layer-handling inconsistencies have been fixed.

===Linked bitmaps===
Linked bitmaps have a context menu option to launch editing in an external application. Linked images now will reload when the linked file changes on disk. Both the external editor application and the reload behavior is configurable.

===Command for relinking clones===

A new command, '''Relink Clone to Copied''' in ''Edit > Clone'', allows you to relink any clone to a different original object without changing its other properties. Just copy (Ctrl+C) the object you want to be the new original, select any number of clones, and choose the Relink command. Now all selected clones are linked to the copied object.

===Automatic relinking of clones on Duplicate===

If you turn on the '''When duplicating original+clones: Relink duplicated clones''' option on Clones tab of Inkscape Preferences (default is off), duplicating a selection containing both a clone and its original (possibly in groups) will relink the duplicated clone to the duplicated original instead of the old original.

===Pattern editing===

When editing pattern fills:
* The pattern origin and scale handles now snap.
* The pattern scaling can now be different in X and Y direction. Press '''Ctrl''' to have a fixed 1:1 ratio scaling (old behavior).
* The handles are now positioned at the corners of the unit cell, instead of only a quarter of that cell as before. So, now a rectangle filled with pattern will have all of the pattern handles in the corners, making it harder to manipulate them. However, the handles can be dragged outside the rectangle by moving the pattern's origin handle.

===Transform dialog: spacing out option===

TODO: is this feature really useful? It will look like a bug. --[[User:Tweenk|Tweenk]] 00:04, 27 February 2009 (UTC)

Previously, the '''Apply to each object separately''' checkbox had no effect for the '''Move''' tab. Now, if several objects are selected, this checkbox is on, and "Relative move" is on, each object is shifted relative to the closest selected object on the left (for X) or below (for Y).

For example, if you have a horizontal row of objects and you move them relatively by x = 5 px with "Apply to each object separately" on, the leftmost object will shift by 5px, the next one to the right by 10px, and so on; the rightmost selected object is displaced by 5*n px where n is the number of selected objects. As a result, the distance in each pair of adjacent objects will increase by 5px and the whole row will be spaced out, much like a letterspacing adjustment spaces out a text string. Moving these objects by X=-5px will, conversely, squeeze them tighter together: the leftmost will move by -5px, the next one by -10px, and so on. For Y, the effect is the same except that the move starts from the object closest to the bottom (i.e. with smallest Y coordinate).

When determining the order of shifting objects, for X, the left edges of their bounding boxes are sorted horizontally, and for Y, the bottoms of their bounding boxes are sorted vertically. Order of selecting the objects or z-order does not matter.

===Converting text to path produces a group===

Converting a text or flowed text to path (Ctrl+Shift+C) now produces a group of paths, one path for each glyph of text, instead of a single monolithic path as before. Apart from easier manipulation, an additional advantage is that if your text contained styled spans (i.e. fragments with different color, opacity, or other properties), these styles will be preserved by the corresponding glyph paths after the conversion.

===Combine works on groups===

The Combine command now works transparently on groups, i.e. combines paths inside selected groups at any level of grouping.

===Path exclusion===
The Exclusion boolean operation can now operate on an arbitrary number of paths.

==User interface==

===Inkscape Preferences dialog===

* This dialog has been rearranged for more logical grouping of options. New pages have been added: '''Bitmaps''' (options for the new update-on-file-change and external editor features), '''UI''' (options for toolbar icon sizes), and '''SVG Output''' (options for SVG formatting, introduced in 0.46 and now editable from the dialog as well).

* A new option on the Bitmaps tab, '''Resolution for Create Bitmap Copy''', allows you to set the resolution of the bitmap created by the corresponding command (by default bound to Alt+B). The default value of 90 dpi forces the resulting bitmap to align with the default 1px-spaced grid on the canvas.

* '''Zoom correction factor''': the Interface tab has an adjustable ruler. Move the slider until the ruler's on-screen size matches its true size. This is used as a reference point for 100% (original size) zoom.

* The application's interface language can be set from the preferences dialog. You'll have to restart Inkscape to see the changes.

===Toolbars===

* The toolbar icon sizes for the three main toolbars are now separately configurable and to a few different sizes. This allows for a more compact user interface.
* The main tools toolbar has been converted to a standard GtkToolbar, removing the problem of it pushing the main window taller. Tools that don't fit automatically flow into a popup menu.
* When torn off, toolbars now keep the size they last had in the main window. They can be resized by docking, resizing the main window, and then undocking again.
* Some controls (such as the Width in Calligraphic/Tweak/Eraser tools, Tremor, Wiggle, and Mass in Calligraphic, Threshold in Paintbucket, Tolerance in Pencil) are converted from numeric editable fields into draggable sliders, with labels and values (usually in the range 0..100) displayed on top. As these values don't usually require much precision, this makes adjusting them much easier and faster.

===Clone/original visualization===

When you press Shift+D to find and select the original of the selected clone, Inkscape draws a dashed line between the centers of the bounding boxes of the clone and the original. This line disappears after one second.

===Miscellaneous===
* The Windows builds of Inkscape now have Windows-native file dialogs to keep consistency with other Windows applications.
* The file dialogs have two new entries in the File type list, All Bitmaps and All Vectors, allowing you to limit the listing to bitmap or vector formats only.
* In the Align and Distribute dialog there is now an option to treat all selected objects as a group when aligning. This spares the trouble of manually grouping them, aligning, and ungrouping afterwards).
* The confusing icons on buttons in the controls bar of the Dropper tool (pick/assign opacity) are replaced by text labels.
* The Document Properties dialog now has a Color Management tab. In this new tab, you can declare multiple ICC color profiles for the current document.
* Hovering over a swatch now shows the name of the swatch in the status bar. This makes it easier for tablet users to identify a swatch by name, as holding a stylus still enough for the tooltip to show up is difficult.
* Title and Description fields in the Object Properties dialog [sas]

==Notable bug fixes==

* Several '''memory leaks''' are stopped, reducing the memory consumption during long editing sessions considerably. Closing the last window with a document now frees memory used by that document immediately.

* Inkscape is now able to handle paths with only 'movetos', i.e. "M 0,0 M 1,1 M 2,2". These kind of paths can be used to only show markers on a path without the rest of the path visible.

* The '''visual bounding box''' (which is the default bounding box type used by Inkscape) of an object with a filter applied, now includes the expanded area of the filter. For '''single blur filter''' (such as the blur you apply with a slider in the Fill and Stroke dialog), this expands the bounding box by 2.4*radius; although theoretically, blur is infinite, this is the distance at which the opacity of the object drops below the perceptibility threshold of our renderer. For all other filters, the area is expanded by the relative amounts you specify on the "Filter general settings" tab of the Filter Effects dialog.

:Only visual bounding box is affected; if you use geometric bounding box, you will notice no change in most cases. However, the Export bitmap dialog always uses the visual bounding box for selection of the export area; this means that you can now export a blurred object to bitmap without any clipping of the blur.

* Bounding box calculation does not include the invisible objects. [https://bugs.launchpad.net/inkscape/+bug/252547 bug #252547]

* Several fixes allows Inkscape to correctly render and edit SVG files that use <code>currentColor</code> in objects' style (this includes files created by gnuplot).

* '''No more ID clashes on import and paste''': previously, importing or pasting SVG objects might sometimes distort their colors, because the imported objects referred to gradients with the same IDs as those that already exist in the document but look different. Now, IDs of all gradients in the pasted document are checked for clashes with those in the host document, and if necessary changed with all their users updated correspondingly, so such unexpected color changes will never happen.

* File dialogs remember last visited directory.

* The --vacuum-defs command line parameter erroneously deleted markers which are in use.

* No more garbage lines in outline mode.

* No more artifacts left by the circle cursor in Tweak tool.

* The Live Path Effects '''Bend Path''' and '''Pattern along Path''' now work correctly with closed paths.

* Several '''[[ViewBoxToDo|viewBox]]''' related bugs fixed
** Documents with viewBox are now editable without transformation defects. In particular this affected documents created with e.g. pstoedit. [https://bugs.launchpad.net/inkscape/+bug/168370 bug #168370]
** Resizing the page adjusts viewBox. [https://bugs.launchpad.net/inkscape/+bug/167682 bug #167682]
** preserveAspectRatio parsing code fixed. [https://bugs.launchpad.net/inkscape/+bug/166885 bug #166885]

* open paths (as opposed to closed paths) are now correctly drawn when start and end points are equal. (SVG test suite ''paths-data-10-t.svg'')

* The shorthand 'marker' property is now correctly interpreted (SVG test suite ''painting-marker-03-f.svg'')

* Coordinates and lengths specified in percentages are now correctly interpreted (SVG test suite ''coords-units-02-b.svg'')

==Previous releases==

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

[[Category:Marketing]]

Google Summer of Code 2008

2008-12-02T16:05:30Z

AurelioAHeckert: /* Suggested Ideas */

= Welcome to Inkscape! =

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.

The Inkscape team plans to focus this summer on codebase cleanup and refactoring. This will affect the type of projects we can accept this year; we're looking for ones that either won't affect core code too significantly (such as Extension scripts, or File Input/Output formats) or that would actually result in improving the state of the codebase (adding tests, modularization, etc.). Students who have already been active developers in Inkscape previously will be allowed more latitude to work on core code (particularly if it will result in cleanup/refactoring of their past work).

= Student Applications =

* Google program information
** 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

= Suggested Ideas =

* [https://blueprints.launchpad.net/inkscape/+spec/test-suite Inkscape test suite]
* Python extensions test suite
* Python effects/extension scripts
* New file import or export support
* [https://blueprints.launchpad.net/inkscape/+spec/lib2geom-integration Integrate lib2geom] -
* [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/new-from-template-dialog 'New From Template' dialog]
* [https://blueprints.launchpad.net/inkscape/+spec/lpe-blueprint More Live Path Effects] - There is a lengthy list of ideas to choose from here.
* [https://blueprints.launchpad.net/inkscape/+spec/kml-svg-translation KML SVG translation] - For use of Inkscape with Google Earth or Maps
* [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.
* [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.
* [https://blueprints.launchpad.net/inkscape/+spec/guides-improvement Guides Improvements]
* [https://blueprints.launchpad.net/inkscape/+spec/transformation-anchors Transformation Anchors]
* Add a palette of objects to Inkscape. Such a palette would contain often used objects and would allow categorizing such objects. Examples of categories: UML, electric, network.
* [https://blueprints.launchpad.net/inkscape/+spec/power-stroke Power Stroke] - Modulated width stroke LPE.

* [http://bugzilla.gnome.org/show_bug.cgi?id=496958 Tablet on windows] - Fix up tablet support on windows.

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/

Extension repository

2008-08-25T18:48:54Z

AurelioAHeckert:

It would be very useful to have a central Internet repository for Inkscape extensions, similarly as Firefox has. This way, Inkscape could update installed extensions from the web site, with no need for the user to know if an extension is updated.

== Extensions ==

'''What extensions are there? We can start listing them here:'''
* [http://www.ekips.org/comp/inkscape/ Inkscape Effects] - Aaron Spikes set of extensions is now included in Inkscape.
* [[ExtrudeEffect]] - extrude polygons to "3d", also make "string art"
* [http://www.colibre.com.br/bin/view/Aurium/InkscapeCalendarShellScript InkscapeCalendarShellScript] - Create Calendars sucks or is impracticable if you do not have something that automatizes the process of to put the days organized in blocks of months to you. To format manually is easy, but this extension can help you on this too [Bash script, works for win32 with cygwin].
* [http://www.colibre.com.br/bin/view/Aurium/InkscapeAreaCuter InkscapeAreaCutter] - For Webdesigners, layout for sites, slice area into .png images. util! (pt_BR)
* [http://julvitard.free.fr/eqtexsvg/ EQTeXSVG] - EQTeXSVG is an extension for Inkscape used to convert an inline LATEX equation into SVG path using Python.
* [http://www.kono.cis.iwate-u.ac.jp/~arakit/inkscape/inklatex.html InkLaTeX] Insert LaTeX text or equations into Inkscape.
* [http://www.iki.fi/pav/software/textext/ TexText] Embed re-editable LaTeX objects in SVG drawings.
* [http://math.univ-lille1.fr/~barraud/Inkscape/pathdeform/ PathDeform] - Here is an Inkscape extension whose purpose is to bend a path according to another one. Note: it was added to Inkscape 0.45 as "Pattern along Path".
* [http://www.inkbar.lineaire.net/ InkBar] - This is an Inkscape extension whose purpose is to draw EAN13 bar code.
* [http://technoargia.free.fr/swftools/ SWF output] - A little extension to save as Swf from Inkscape.
* [http://www.colivre.coop.br/Aurium/Puff Puff] - Fluffs elements! :-D
* [http://www.colivre.coop.br/Aurium/InkSudoku Sudoku Generator] - Generates Sudoku square with the solution ''(in a small square if you want)''.
* [[CalligraphedOutlineFill]] - helps to fill in the inside area of shapes drawn with the Calligraphy tool
* [http://edlab.die.unipd.it/Site4.html SlotStar] - helps to draw the star of slot of a winding of an electrical machine
* [http://richard.henwood.googlepages.com/inkscapelatexextension inkscapeLatexExtension] - Extract text in an inkscape drawing to a latex picture environment.
* [http://saws.googlecode.com s.a.w.s] - export the svg Inkscape file in valid xhtml / css files.
* [http://www.colivre.coop.br/Aurium/InkscapeGenerator Generator] - replace text and data to automatic generate files done for usage (like PDF, PS, JPG, etc...), based in a SVG template and a data file.

'''For Programmers:'''
* [http://www.colivre.coop.br/bin/view/Aurium/RubyInk RubyInk] - Inkscape extension with Ruby
* [http://www.colivre.coop.br/bin/view/Aurium/InkBash Ink-Bash] - <nowiki>ShellScript</nowiki> Forever!
* [http://www.colivre.coop.br/bin/view/Aurium/InkMoz InkMoz] - the Bridge from Inkscape to Mozilla (Inkscape extension with Javascript and more)

== The Repository Specification ==

A website where programmers can publish their extensions, users can search by that, and an update program can access this updates.

=== The Website ===

Must Have:
* '''User Registration''': to allow upload, votes and comments
* '''Extension Validation''': when published, it is public, but the user must be notified that was not validated (the code must be viewed by an validator user). The software updater do not update non-validated versions.
** '''Validation Feedback''': the validator user must write why the extension was not validated.
** '''Extension Deletion''': the validator user can delete an extension or version when he found a malicious code. The upload user must be marked as a malicious user and the account must be blocked.
* '''Extension Search''': with filter, by any available data.
* '''User Votes and Comments for Extensions''': The user can vote and/or comment an extension version.
* '''Extension Bug-Traker''': today, third part extensions are in simple web-pages. The site may have a Bug-Traker to help all little scripts.
* '''User Extensions Requests''': a lot of users have ideas. Here is a good place for programers see and make that alive.
* '''Host a cool page for the extension''': allow introduction text, documenbtation, screenshots, examples, and '''i18n'''!
* '''Help the l10n of this extensions''': with a web interface, like pootle and provide the l10n file for the updater program.
* '''Provide Version Control''': A SVN account will be cool, but web uploads (by web-forms) can be transparently SVN commits.

=== The Extension Meta-Data ===

''The data in INX file and more some, like the O.S. and Inkscape version compatibility...''

The INX file will define the meta-data settable by that. If some extension uses multiples INX files to have more than one option in the menu, all INX files must be read to set the meta-data. The meta-data will be cached in a database to help the search. The DB only need the meta-data of the last validated version and the last non-validated (if that is newer).

=== The Update Program ===

* '''Search for New Extensions''': when the user request
* '''Update Extensions''': search for updates and install that
* '''Help the Code Validation''': for advanced users. Show the extension code and the diff if is that an update.
* '''Help the User Bug-Reporting''': that is not working! The user must say now! ''(When the Update Program be part of the Inkscape, the error window can have a button to submit a bug-report)''
* '''Must test the extension dependencies''': the user must know what is needed to install before try to use.

== Name Proposal ==

Propose a name for the Inkscape Extension Repository:

* '''The Factory'''
* '''Extension Factory'''
* '''INX Factory'''

''Why Factory? Because it is not only a repository. ;-)''

[[Category:Developer Documentation]]
[[Category:Extensions]]

Extension repository

2008-08-25T18:37:48Z

AurelioAHeckert:

It would be very useful to have a central Internet repository for Inkscape extensions, similarly as Firefox has. This way, Inkscape could update installed extensions from the web site, with no need for the user to know if an extension is updated.

== Extensions ==

'''What extensions are there? We can start listing them here:'''
* [http://www.ekips.org/comp/inkscape/ Inkscape Effects] - Aaron Spikes set of extensions is now included in Inkscape.
* [[ExtrudeEffect]] - extrude polygons to "3d", also make "string art"
* [http://www.colibre.com.br/bin/view/Aurium/InkscapeCalendarShellScript InkscapeCalendarShellScript] - Create Calendars sucks or is impracticable if you do not have something that automatizes the process of to put the days organized in blocks of months to you. To format manually is easy, but this extension can help you on this too [Bash script, works for win32 with cygwin].
* [http://www.colibre.com.br/bin/view/Aurium/InkscapeAreaCuter InkscapeAreaCutter] - For Webdesigners, layout for sites, slice area into .png images. util! (pt_BR)
* [http://julvitard.free.fr/eqtexsvg/ EQTeXSVG] - EQTeXSVG is an extension for Inkscape used to convert an inline LATEX equation into SVG path using Python.
* [http://www.kono.cis.iwate-u.ac.jp/~arakit/inkscape/inklatex.html InkLaTeX] Insert LaTeX text or equations into Inkscape.
* [http://www.iki.fi/pav/software/textext/ TexText] Embed re-editable LaTeX objects in SVG drawings.
* [http://math.univ-lille1.fr/~barraud/Inkscape/pathdeform/ PathDeform] - Here is an Inkscape extension whose purpose is to bend a path according to another one. Note: it was added to Inkscape 0.45 as "Pattern along Path".
* [http://www.inkbar.lineaire.net/ InkBar] - This is an Inkscape extension whose purpose is to draw EAN13 bar code.
* [http://technoargia.free.fr/swftools/ SWF output] - A little extension to save as Swf from Inkscape.
* [http://www.colivre.coop.br/Aurium/Puff Puff] - Fluffs elements! :-D
* [http://www.colivre.coop.br/Aurium/InkSudoku Sudoku Generator] - Generates Sudoku square with the solution ''(in a small square if you want)''.
* [[CalligraphedOutlineFill]] - helps to fill in the inside area of shapes drawn with the Calligraphy tool
* [http://edlab.die.unipd.it/Site4.html SlotStar] - helps to draw the star of slot of a winding of an electrical machine
* [http://richard.henwood.googlepages.com/inkscapelatexextension inkscapeLatexExtension] - Extract text in an inkscape drawing to a latex picture environment.
* [http://saws.googlecode.com s.a.w.s] - export the svg Inkscape file in valid xhtml / css files.
* [http://www.colivre.coop.br/Aurium/InkscapeGenerator Generator] - replace text and data to automatic generate files done for usage (like PDF, PS, JPG, etc...), based in a SVG template and a data file.

'''For Programmers:'''
* [http://www.colivre.coop.br/bin/view/Aurium/RubyInk RubyInk] - Inkscape extension with Ruby
* [http://www.colivre.coop.br/bin/view/Aurium/InkBash Ink-Bash] - <nowiki>ShellScript</nowiki> Forever!
* [http://www.colivre.coop.br/bin/view/Aurium/InkMoz InkMoz] - the Bridge from Inkscape to Mozilla (Inkscape extension with Javascript and more)

== The Repository Specification ==

A website where programmers can publish their extensions, users can search by that, and an update program can access this updates.

=== The Website ===

Must Have:
* '''User Registration''': to allow upload, votes and comments
* '''Extension Validation''': when published, it is public, but the user must be notified that was not validated (the code must be viewed by an validator user). The software updater do not update non-validated versions.
** '''Validation Feedback''': the validator user must write why the extension was not validated.
** '''Extension Deletion''': the validator user can delete an extension or version when he found a malicious code. The upload user must be marked as a malicious user and the account must be blocked.
* '''Extension Search''': with filter, by any available data.
* '''User Votes and Comments for Extensions''': The user can vote and/or comment an extension version.
* '''Extension Bug-Traker''': today, third part extensions are in simple web-pages. The site may have a Bug-Traker to help all little scripts.
* '''User Extensions Requests''': a lot of users have ideas. Here is a good place for programers see and make that alive.
* '''Host a cool page for the extension''': allow introduction text, documenbtation, screenshots, examples, and '''i18n'''!
* '''Help the l10n of this extensions''': with a web interface, like pootle and provide the l10n file for the updater program.
* '''Provide Version Control''': A SVN account will be cool, but web uploads (by web-forms) can be transparently SVN commits.

=== The Extension Meta-Data ===

''The data in INX file and more some, like the O.S. and Inkscape version compatibility...''

The INX file will define the meta-data settable by that. If some extension uses multiples INX files to have more than one option in the menu, all INX files must be read to set the meta-data. The meta-data will be cached in a database to help the search. The DB only need the meta-data of the last validated version and the last non-validated (if that is newer).

=== The Update Program ===

* '''Search for New Extensions''': when the user request
* '''Update Extensions''': search for updates and install that
* '''Help the Code Validation''': for advanced users. Show the extension code and the diff if is that an update.
* '''Help the User Bug-Reporting''': that is not working! The user must say now! ''(When the Update Program be part of the Inkscape, the error window can have a button to submit a bug-report)''
* '''Must test the extension dependencies''': the user must know what is needed to install before try to use.

[[Category:Developer Documentation]]
[[Category:Extensions]]

Extension repository

2008-08-25T18:18:53Z

AurelioAHeckert:

It would be very useful to have a central Internet repository for Inkscape extensions, similarly as Firefox has. This way, Inkscape could update installed extensions from the web site, with no need for the user to know if an extension is updated.

== Extensions ==

'''What extensions are there? We can start listing them here:'''
* [http://www.ekips.org/comp/inkscape/ Inkscape Effects] - Aaron Spikes set of extensions is now included in Inkscape.
* [[ExtrudeEffect]] - extrude polygons to "3d", also make "string art"
* [http://www.colibre.com.br/bin/view/Aurium/InkscapeCalendarShellScript InkscapeCalendarShellScript] - Create Calendars sucks or is impracticable if you do not have something that automatizes the process of to put the days organized in blocks of months to you. To format manually is easy, but this extension can help you on this too [Bash script, works for win32 with cygwin].
* [http://www.colibre.com.br/bin/view/Aurium/InkscapeAreaCuter InkscapeAreaCutter] - For Webdesigners, layout for sites, slice area into .png images. util! (pt_BR)
* [http://julvitard.free.fr/eqtexsvg/ EQTeXSVG] - EQTeXSVG is an extension for Inkscape used to convert an inline LATEX equation into SVG path using Python.
* [http://www.kono.cis.iwate-u.ac.jp/~arakit/inkscape/inklatex.html InkLaTeX] Insert LaTeX text or equations into Inkscape.
* [http://www.iki.fi/pav/software/textext/ TexText] Embed re-editable LaTeX objects in SVG drawings.
* [http://math.univ-lille1.fr/~barraud/Inkscape/pathdeform/ PathDeform] - Here is an Inkscape extension whose purpose is to bend a path according to another one. Note: it was added to Inkscape 0.45 as "Pattern along Path".
* [http://www.inkbar.lineaire.net/ InkBar] - This is an Inkscape extension whose purpose is to draw EAN13 bar code.
* [http://technoargia.free.fr/swftools/ SWF output] - A little extension to save as Swf from Inkscape.
* [http://www.colivre.coop.br/Aurium/Puff Puff] - Fluffs elements! :-D
* [http://www.colivre.coop.br/Aurium/InkSudoku Sudoku Generator] - Generates Sudoku square with the solution ''(in a small square if you want)''.
* [[CalligraphedOutlineFill]] - helps to fill in the inside area of shapes drawn with the Calligraphy tool
* [http://edlab.die.unipd.it/Site4.html SlotStar] - helps to draw the star of slot of a winding of an electrical machine
* [http://richard.henwood.googlepages.com/inkscapelatexextension inkscapeLatexExtension] - Extract text in an inkscape drawing to a latex picture environment.
* [http://saws.googlecode.com s.a.w.s] - export the svg Inkscape file in valid xhtml / css files.
* [http://www.colivre.coop.br/Aurium/InkscapeGenerator Generator] - replace text and data to automatic generate files done for usage (like PDF, PS, JPG, etc...), based in a SVG template and a data file.

'''For Programers:'''
* [http://www.colivre.coop.br/bin/view/Aurium/RubyInk RubyInk] - Inkscape extension with Ruby
* [http://www.colivre.coop.br/bin/view/Aurium/InkBash Ink-Bash] - <nowiki>ShellScript</nowiki> Forever!
* [http://www.colivre.coop.br/bin/view/Aurium/InkMoz InkMoz] - the Bridge from Inkscape to Mozilla (Inkscape extension with Javascript and more)

== The Repository Specification ==

A website where programers can publish their extensions, users can search by that, and an update program can access this updates.

=== The Website ===

Must Have:
* '''User Registration''': to allow upload, votes and comments
* '''Extension Validation''': when published, it is public, but the user must be notified that was not validated (the code must be viewed by an validator user). The software updater do not update non-validated versions.
* '''Extension Search''': with filter, by any avaliable data.
* '''User Votes and Comments for Extensions''': The user can vote and/or comment an extension version.
* '''Extension Bug-Traker''': today, third part extensions are in simple web-pages. The site may have a Bug-Traker to help all little scripts.
* '''User Extensions Requests''': a lot of users have ideas. Here is a good place for programers see and make that alive.
* '''Host a cool page for the extension''': allow introduction text, documenbtation, screenshots, examples, and '''i18n'''!
* '''Help the l10n of this extensions''': with a web interface, like pootle and provide the l10n file for the updater program.
* '''Provide Version Control''': A SVN account will be cool, but web uploads (by web-forms) can be transparently SVN commits.

=== The Extension Meta-Data ===

''The data in INX file and more some, like the inkscape version...''

=== The Update Program ===

* '''Search for New Extensions''': when the user request
* '''Update Extensions''': search for updates and install that
* '''Help the Code Validation''': for advanced users. Show the extension code and the diff if is that an update.
* '''Help the User Bug-Reporting''': that is not working! The user must say now! ''(When the Update Program be part of the Inkscape, the error window can have a button to submit a bug-report)''

[[Category:Developer Documentation]]
[[Category:Extensions]]

User:AurelioAHeckert

2008-08-25T17:31:40Z

AurelioAHeckert: New page: Aurélio A. Heckert (aka '''Aurium''') Web Site: http://Aurium.Colivre.coop.br '''Programer and Artist''' -- '''Inkscape Extension Writer''' -- '''[http://inkscapebrasil.org InkscapeBras...

Aurélio A. Heckert (aka '''Aurium''')

Web Site: http://Aurium.Colivre.coop.br

'''Programer and Artist''' -- '''Inkscape Extension Writer''' -- '''[http://inkscapebrasil.org InkscapeBrasil.org] Founder and Member'''

BenutzerGalerien

2007-08-24T18:33:29Z

AurelioAHeckert: /* Clipart */

== Urprungsfassung ==

Englische Ursprungsfassung [[Galleries|hier]]

== Galerien ==

Füg hier einen Link zu deiner eigenen Inkscape-Galerie an

* [http://commons.wikimedia.org/wiki/Category:SVG Kategorie:SVG im Wikimedia-Projekt]

=== Clipart ===
* [http://openclipart.org Open Clip Art Library] (en)
* [http://edeca.net/site/graphics [[NauticalFlags]]] freie SVG-Flaggen (nautisches Alphabet; en)
* [http://inkscapeBrasil.org/.Galeria Inkscape Brasil Galeria (pt_BR)]

=== Comics & Cartoons ===
* [http://www.poulejapon.com [[PouleJapon]]] täglicher Comic, gemacht mit Inkscape (en, fr, jap)
* [http://www.inkpipe.com Inkpipe.com] SVG-Cartoons und -Gekritzel (en)
* [http://www.xp-swiss.org/wiki/index.php?title=Comics_%28english%29 X-Coders] die XP-Swiss eXtreme Programming Cartoons (en)
* [http://lunar8.rydia.net/ Mental's Lunar 8 Comics] (en)
* [http://www.bakedbabies.com Baked Babies] (ein paar mit Inkscape erstellte Comics; WARNUNG: nicht für Kinder!; en)
* [http://thmayos.free.fr/inkscape/manga_inspiration.svgz Manga Inspiration] schnelle Zeichnung mit Inkscape 0.42 (SVG)

== Artwork & Wallpapers ==
* [http://programmer-art.org/artwork Daniel G. Taylor's Art Page] (funktioniert wieder!; en)
* [http://www.le-radar.com/?art/galerie Cedric Gemy] (fr)
* [http://urke.deviantart.com/gallery/ Urke MMI] (en)
* [http://hooboo.free.fr/index.php franz. [[OpenOffice]].org Maskottchen] von Ben Bois, gemacht mit Inkscape (fr)
* [http://kde-look.org/content/show.php?content=16627 [[AmaroK]] Icon] KDE Artwork von Zekant (en)
* [http://kde-look.org/content/show.php?content=18204 Mupen64 Icon] KDE Artwork von Zekant (en)
* [http://www.volvoguy.net/ubuntu/ Ubuntu SVG Artwork] (en)
* [http://www.smartart.it/albums/wallpapers/abducted_1600x1200.sized.png Gentoo SVG Artwork] Wenn es sich bewegt, kompilier es!
* [http://www.kde-look.org/usermanager/search.php?username=salahuddin66 Großartige Wallpapers!] (en)
* [http://zvonsully.home.ro/ zvonSully Wallpapers] powered by Inkscape & SVG (en)
* [http://www.senses0.org.mv/popzees/artwork_white.html Artwork von Senses0 mit Inkscape] (en)
* [http://gatonegro.ceibes.org Gatonegro deseño - gatonegro.ceibes.org] (gl)
* [http://sunedonath.de/bilder.htm Wallpaper von Sune Donath] inkl. SVG download (de)
''' SVG Artworks von mr.manders
http://pixel-pics.de/upload/1180029955.png[/img][/url]
http://pixel-pics.de/upload/1180030022.png[/img][/url]'''

=== Künstler/innen, die Inkscape verwenden ===
* [http://www.dushkin.org/ Dushkin] ist ein Digital-Künstler des modernen Zeitalters. Die meisten seiner Werke sind mit Inkscape gemacht.

=== Inkscapebezogenes ===
* [http://popolon.org/inkscape/ Popolon Inkscape Tutorials and Illustrationen] das meiste auf Französisch, manches auf Englisch oder Chinesisch

=== Mit Inkscape erstellte Projekte ===
* [http://www.joncampbell.ca/inkscape/gallery.php Jon Campbell] Auswahl von mit Inkscape gemachten Projekten (en)
* [http://david.bellot.free.fr/svg-cards SVG-Spielkarten] (en)
* [http://nicubunu.ro/pictures/rpg/inkscape_rpg_map.png RPG-Landkarte] (Screenshot) von [http://nicubunu.ro/ Nicu Buculei]
* [http://www.coggy.de www.coggy.de / Webseite] (de)

=== Andere ===
* [http://inkscape.deviantart.com/ inkscape.deviantart.com] die Inkscape-Gruppe auf deviantART 1 (en)
* [http://inkscapers.deviantart.com/ inkscapers.deviantart.com] die Inkscape-Gruppe auf deviantART 2 (en)
* [http://zubauza.deviantart.com/gallery zubauza's Galerie @ deviantART] (en)
* [[Haypo]] (en)
* [[simarilius]] (en)
* [[Jofo]] (en)
* [[Simondebelem]] (en)
* [[Gwyn]] (en)
* [http://www.insert.waw.net.pl/vector/firecat_large.jpg Piotr Kosmala]
* [http://erture.webpark.pl/vinci.html Radek Turek] (en)
* [http://haef.szm.sk/ Henrich Fichna] (en)
* [http://blog.die-scheiss-kiste.de/wordpress/ Andy's Blog] Blog; Inkscape ist eines der Themen, mit Beispielen und freien SVG-Downloads (de)
* [http://www.dirk-hoeschen.de/content/index.php?opi=view&id=8 Bevel Tutorial] Tutorial für Anfänger/innen über das Erzeugen von Schrägen-[[/Kanten]]-Effekten mittels Farbverläufen (de)
* [http://imaginaciongnu.tk Imaginación GNU] (esp)

[[Category:German]]

Galleries

2007-08-10T21:20:50Z

AurelioAHeckert: /* Multiple-author galleries */

== localized versions ==
localized versions of that link list
* [[BenutzerGalerien|Benutzergalerien auf deutsch]]

== Galleries ==

=== Multiple-author galleries ===

* [http://openclipart.org Open Clip Art Library]
* [http://InkscapeBrasil.org/.Galeria Inkscape Brasil Galeria]
* [http://commons.wikimedia.org/wiki/Category:Created_with_Inkscape Category:Created with Inkscape] at Wikimedia Commons contains thousands of Inkscape SVG images of all kinds
* [http://inkscape.deviantart.com/favourites/ inkscape.deviantart.com] The Inkscape group on deviantART
* [http://gould.cx/ted/ink-about/ Museum of Sodipodi and Inkscape About Screens]

=== Single-author galleries ===

* [http://manowarrior.deviantart.com/ ManoWarrior] Inkscape vectors by Luchezar Petkov
* [http://conichiwua.wordpress.com/ Conichiwua] - Inkscape art
* [http://www.ufowebfactory.net/download/free-svg_en.htm illustrations] and associated SVG files
* [http://www.revis.co.uk/site/?q=taxonomy/term/7 Inkscape animations] and CC licensed SVG source files, plus a gear making tutorial
* A tiny selection of [http://marksinkscape.blogspot.com/ Mark H's] inkscape pics.
* [http://www.jeromehouix.info/ Jiije] artworks by jiije
* [http://www.pictura4.1gb.at picturi,reproduceri,portrete]
* [http://www.dushkin.org/ Dushkin] is an artist of the digital age. A graduate of iidabashi hoikuen. Please be sure to leave a comment in his blog. Check out his gallery for the latest Inkscape creations.
* [[Haypo]]
* A few experimental Inkscape creations from [http://clik.to/cal Cal Russell-Thompson]; more on his [http://rubberkeith.deviantart.com DeviantART page].
* Dan Wells' beautiful gallery of Inkscape art is viewable [http://monkeydan1.deviantart.com here.]
* [http://lunar8.rydia.net/ Mental's Lunar 8 Comics]
* [[simarilius]]
* [http://www.le-radar.com/?art/galerie Cedric Gemy]
* [[Jofo]]
* [http://www.kde-look.org/usermanager/search.php?username=salahuddin66 Great Wallpapers!]
* [[Simondebelem]]
* [http://david.bellot.free.fr SVG-cards]
* [http://zubauza.deviantart.com/gallery zubauza's gallery @ deviantART]
* [[Gwyn]]
* [http://edeca.net/graphics.xml Free SVG nautical flags]
* [http://gatonegro.ceibes.org Gatonegro deseño - gatonegro.ceibes.org]. Inkscape-based graphic design, with the occasional aid of the GIMP and Scribus. Stickers, posters, tee-shirts, pamphlets, logotypes, wallpapers... Most of them released under the Creative Commons Attribution-Sharealike. (Language: galizan.)
* [http://imaginaciongnu.iespana.es/ Imaginacion GNU] Artwork created with Inkscape by Daniel Cremades (Graphic designer, spanish)
* [http://www.bakedbabies.com Baked Babies] (a few comics created with inkscape WARNING: not for kids)
* [http://www.pictura4.1gb.at/portrete_in_creion_pe_hartie.html portrete la comanda in creion] (portraits by pictures)
* [http://kde-look.org/content/show.php?content=16627 AmaroK Icon], [http://kde-look.org/content/show.php?content=18204 Mupen64 Icon] KDE artwork by Zekant
* [http://www.insert.waw.net.pl/vector/firecat_large.jpg Piotr Kosmala]
* [http://erture.webpark.pl/vinci.html Radek Turek]
* [http://haef.szm.sk/ Henrich Fichna]
* [http://blog.die-scheiss-kiste.de/wordpress/ Andy's Blog] Blog german. Inkscape is one topic, w. Examples & free SVG Downloads.
* [http://hooboo.free.fr/index.php LaMouette] french OpenOffice.org Mascot by Ben Bois made with Inkscape
* [http://www.joncampbell.ca/inkscape/gallery.php Jon Campbell] Variety of projects done in inkscape
* [http://f-r-e-d.org/ Fred's SVG Wallpapers]
* [http://panzi.deviantart.com/gallery/ panzi.deviantArt.com] only some pictures are SVG (e.g. see: [http://www.deviantart.com/view/4617948/ my orc])
* [http://dump.c7.se/tribal.png Tribal tattoo drawn in Inkscape] ([http://c7.se/?entry=69 Result])
* [http://ggw.stfu.ee/ GeeksGoneWild] A webcomic drawn with inkscape
* [http://xterminador.deviantart.com/gallery/ xterminador.deviantart.com] Artwork by Xterminator at Deviantart Parental Advisory Explicit Content
* [http://www.braincud.com/ Brain Cud] A webcomic now drawn with Inkscape (starting with installment number 24).
* [http://popolon.org/inkscape/ popolon.org/inkscape/] Tutorial for Inkscape and pictures made with Inkscape, mostly in french some in english or chinese.
* [http://www.protemporeevents.com/larrys/ Larry's Main Entrance] A restaurant menu redesign project done in Inkscape!
* [http://yeknan.free.fr/blog/index.php?2006/03/22/74-galerie-svg yeKcim] Free SVG (Wormux, Crocobox, Mille bornes,...)
* [[Paramate]]
* [http://jhuss.com/download.php?list.3 jhuss's artwork] a some works, all made in inkscape
* [http://www.awns.com/galeri/ Galeri] A growing collection of colourful and stylish artwork.
* [http://blog.organicadtm.com/wp-gallery2.php OrganicaDTM Studio's gallery] Our projects are doing with Inkscape, Gimp and Blender.
*[http://www.freewaydesign.com/ freewaydesign] Dr-Hamza`s Blog Misc. Designs
* [http://proximus1.deviantart.com/gallery/?catpath=digitalart/vector/&offset=0 Proximus1] Vector Artwork by Proximus1
* [http://singularityblues.com Singularity Blues] A webcomic done in Inkscape. SVG files available upon request.
*[http://hrum.deviantart.com/gallery ~hrum] Konstantin R. page on deviantart with pictures made in Inkscape (most of them) and GIMP
* [http://www.kde-files.org/index.php?xcontentmode=644 KDE-Files Inkscape directory] artwork by various contrubters, you can also upload your own work.
* [http://sunedonath.de/bilder.htm Sune Donath] anime wallpapers made with Inkscape incl. SVG download.
* [http://www.rammbauer.nl/?cat=3 Rayart Rammbauer] some poster and cartoons made with Inkscape
* [http://vorg.pl/design/tag/vector Vorg.pl] artwork by graphic designer Marcin Ignac
* [http://playful-geometer.deviantart.com | A Playful Geometer's deviantart gallery] Images made mostly using [http://sourceforge.net/projects/play-svg pLAySVG] the GPL'd python libraries for the easy generation of SVG vector graphics
* [http://www.alpha-release.com Alpha Release] an online comic under a Creative Commons license, drawn entirely in Inkscape
* [http://geronimo89.deviantart.com geronimo89@deviantART.com] He often uses Inkscape for his vector works and tries to give an impression how powerful Inkscape is.
* [http://mathburton.deviantart.com/ Mathburton] Inkscape vectors by James Avila
* [http://hamletoilcriceto.blogspot.com Hamleto Il Criceto] Italian online comic strips about an hamster called Hamleto entirely drawn in Inkscape
* [http://plurib.us/1shot/2007/svg_art/ Plurib.us SVG Art] Gallery of Inkscape created SVG art (some CC licensed).


Add a link to your Inkscape gallery here!

[[Category:About Inkscape]]

Extension repository

2007-04-08T02:33:37Z

AurelioAHeckert:

Extension repository

2007-04-07T20:05:28Z

AurelioAHeckert: Puff, Sudoku, RubyInk, Ink-Bash e InkMoz

ReleaseAnnounce045-ptBR

2007-02-05T21:17:06Z

AurelioAHeckert: /* Inkscape Anuncia Lançamento da Versão 0.45 :: http://www.inkscape.org :: Desenhando Livremente */

Esta é uma concepção do Anuncio de Lançamento para a versão 0.45.

== Inkscape Anuncia Lançamento da Versão 0.45 :: http://www.inkscape.org :: Desenhando Livremente ==

A comunidade Inkscape anuncia hoje a mais nova versão do programa para edição gráfica vetorial. O Inkscape 0.45 apresenta seu novo filtro SVG de Desfoque Gaussiano. Patrocinado pela Google's Summer of Code, o desfoque Gaussiano permite desfocar e suavizar naturalmente todos os objetos do Inkscape, incluindo formas, texto e imagens. Isto permite uma grande escala de efeitos Fotorrealistas: matizes e luzes de fomas variadas, profundidade de campo, sombras, incandescência, etc. Os objetos desfocados também podem ser usados como máscaras para outros objetos conseguindo o efeito de "máscara feathered".

Inúmeras outras novas funções, melhorias nas funções existentes e correções de erros foram incluídos. Um diálogo de histórico permite que você navegue no seu histórico de mudanças. Muitos efeitos novos foram adicionados como extensões, incluindo o Padrão ao longo do Caminho e os efeitos de cores. Houve algumas melhorias de desempenho da renderização, da ordem de 2-3% em geral e de até 5-10% para desenhos usando transparência pesada ou gradientes radiais. A qualidade de composição foi também melhorada com a remoção das bordas vistas nos gradientes.

Na versão em português do Brasil, temos 99% de tradução da interface e documentação 100% traduzida. Agradecemos ao trabalho de Thiago Pimentel na documentação e a toda a comunidade Inkscape Brasil, que colaborou com a tradução e a revisão da interface.

Download para Linux, Windows, e Mac OS X:

http://sourceforge.net/project/showfiles.php?group_id=93438

Para muito mais detalhes, veja a Nota de Anúncio completo para 0.45 em:

http://wiki.inkscape.org/wiki/index.php/Release_Notes

Screenshot enviado pela comunidade:

http://www.inkscape.org/screenshots/

===Sobre o Inkscape===

O Inkscape é uma ferramenta de desenho de código aberto que utiliza o formato de gráficos vetoriais escaláveis (SVG) do World Wide Web Consortium's ([[W3C]]).
Algumas funções suportadas pelo SVG incluem formas básicas, caminhos, texto, marcadores, clones, mesclagem alfa, transfomações, gradientes e agrupamento.
Em adição, o Inkscape suporta metadados Creative Commons, edição de nós, camadas, operações complexas com caminhos, texto em caminhos, texto em formas e edição do XML SVG. Também pode importar arquivos EPS, <nowiki>PostScript</nowiki>, e a maioria dos formatos de bitmaps, e exportar PNGs, PS, PDF e vários formatos vetoriais.

A principal motivação do Inkscape é dar à comunidade Open Source uma ferramenta de desenho totalmente compatível com XML, SVG e CSS2 do [[W3C]]. Trabalhos adicionais incluem a conversão da base de código de <nowiki>C/Gtk</nowiki> para
<nowiki>C++/Gtkmm</nowiki>, com ênfase em uma base leve com ferramentas poderosas adicionadas através de um mecanismo de extensões, e mantendo um processo de desenvolvimento amigável, aberto e voltado para a comunidade.

== Release announce translations ==

Catalan: http://wiki.inkscape.org/wiki/index.php/NotaAlliberament045

Czech: http://wiki.inkscape.org/wiki/index.php/ReleaseAnnounce045-cs

Deutsch: http://wiki.inkscape.org/wiki/index.php/ReleaseAnnounce045-de

French: http://wiki.inkscape.org/wiki/index.php/ReleaseAnnounce045-fr

Italian: http://wiki.inkscape.org/wiki/index.php/ReleaseAnnounce045-it

Japanese: http://wiki.inkscape.org/wiki/index.php/ReleaseAnnounce045-ja

Portuguese: http://wiki.inkscape.org/wiki/index.php/ReleaseAnnounce045-ptBR

Vietnamese: http://wiki.inkscape.org/wiki/index.php/ReleaseAnnounce045-vi

Español: http://wiki.inkscape.org/wiki/index.php/ReleaseAnnounce045-es

[[Category:Marketing]]

Script extensions

2006-10-29T01:38:36Z

AurelioAHeckert:

=== Introduction ===

Inkscape provides the ability for its functionality to be extended using traditional unix scripts. By this, we mean a program that takes in a stream of data through standard in, and then outputs that data on standard out. This is a very easy way to expand Inkscape, and provide custom functionality, without learning the internals of Inkscape. Plus, there are SVG read and writing libraries out there for almost any language, and the rest of them all have XML support (which is really what you probably want to use anyway). This HOWTO discusses the ends and outs of writing one of these scripts and getting it to work with the Inkscape core functionality.

=== Types of scripts ===

Basically there are three functions that added with a script:

* Input, providing translation from a file format to SVG
* Output, providing translation from SVG to a format
* Filter, taking in SVG, changing it, and then outputing SVG

While all of these are very similar in the scripting interface, there are slight differences between them.

=== Interaction ===

It is important for a script author to understand how Inkscape and scripts communicate.

(interpreter)? your_script (--param=value)* /path/to/input[[/SVGfile]] | inkscape

Inkscape runs your script (optionally with an interpreter) passing it any number of parameters in long gnu style. The final argument is the name of the temporary svg file your script should read. After processing, the script should return the modified svg file to inkscape on STDOUT.

=== Localisation of extensions ===

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

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

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

=== Description ===

In order for Inkscape to make use of an external script or program, you must describe that script to inkscape using an INX file. See the inkscape share directory for examples.

==== Parameters ====
The INX file describes which parameters the extension needs. Inkscape will prompt the user with a UI to fill out these parameters before the

extension is called. Each parameter will be passed through the commandline as "--paramname=paramvalue". Eg. if you have described a string

parameter with name 'string1' in the INX file, Inkscape will present a textbox to the user. When the user fills in "text" and presses OK, it

will pass '--string1="text"' to the program specified by the <command> tag.

There are several types of parameters that can be requested by the INX description:

===== Boolean =====

===== Int =====

===== Float =====

===== String =====

===== Description =====

===== Enum =====

===== Notebook =====

=== Installing ===

Installing is as simple as copying the script (unless it resides in your path) and its INX file to the inkscape/share/extensions (home/.inkscape/extensions) directory.

If you are looking to use scripts that have already been written, the most difficult part will likely be the installation. Since scripts are seperate programs they may have any number of dependencies that are not included with inkscape. Currently, the best way to find missing dependencies is by reading the error messages produced by running the script from the command line.

=== See Also ===

*http://www.ekips.org/comp/inkscape/extending.php#ignorance

*[[MakingAnExtension]]

[[Category:Extensions]]

INX extension descriptor format

2006-08-19T22:54:08Z

AurelioAHeckert: start about INX file

How an extension must work and how to write an INX file.

''It's only an working draft!''

== About the Inkscape Extension Interface ==

The inkscape call a program with some arguments and as the last argumet it tells to the extension program where is the temporay SVG file to do the work. The temporay SVG file represents the actual state of the working SVG.

After the extension program work it writes the modified SVG to the default output, the Inkscape get this and update the SVG for the user.

''An Inkscape Developer can say it better...''

== How an Extension Must Work ==

* Recive the inkscape arguments.
* Clear temp files if it creates one.
* Write full changed SVG to the default output.
* Don't break an xml:space="preserve" area.
* Send error text to the error output and help the user.

''An Inkscape Developer can say more?''

== How to Write an INX File ==

'''Example:'''
<inkscape-extension>
<_name>{Friendly Extension Name}</_name>
<id>{org.domain.sub-domain.extension-name}</id>
<dependency type="executable"
location="[extensions|{location}]">program.ext</dependency>
<param name="{argumentName}" type="[int|float|string]"
min="{number}" max="{number}"
_gui-text="{Friendly Argument Name}">{default value}</param>
<effect>
<object-type>[all|{element type}]</object-type>
<effects-menu>
<submenu _name="{Extension Group Name}"/>
</effects-menu>
</effect>
<script>
<command reldir="extensions"
interpreter="[python|perl|bash|{some other}]">program.ext</command>
</script>
</inkscape-extension>

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

INX extension descriptor format

2006-08-19T22:41:07Z

AurelioAHeckert: Creating

Inkscape

2006-08-19T22:25:07Z

AurelioAHeckert: puting MakingAnExtension link

This is a freeform area for Inkscape development and discussion.
Curious about [[WikiSyntax]]?

Aqui la versión del wiki de [[Inkscape en español]]

Aquí la versió del wiki de [[L'Inkscape en Català]]

Hier die Version des Wiki auf [[Startseite|Deutsch]]
<table cellspacing="11" width="100%"><tr valign="top">
<td style="width:33%;background-color: #EFFBFF; padding:.5em; border: 1px solid #BFEEFF">
=== About Inkscape ===
* [http://www.inkscape.org/ Inkscape Homepage]
* [[About Inkscape]]
* [[InkscapeFeatures]]
* [[FAQ]] - Frequently Asked Questions
* [[ProjectInfo]]
* [[SupportedOperatingSystems]]
* [[Tools]] - Supporting Tools and Applications
* [[Galleries]]
* [[ArticlesAndPresentations]]
* [[TestimonialComments]]
* [[InkscapePopularity]]
* [[ContactInfo]] our heroes

</td><td style="width:33%;;background-color: #FFF1EF; padding:.5em; border: 1px solid #FFC7BF;margin:.5em">

=== User Documentation ===
* [[InstallHelp]]
* [[InkscapeTerminology]]
* [[UserManual]]
* [http://inkscape.org/doc/ Tutorials]
* [[InkscapeSVG|Inkscape SVG vs. Plain SVG]]
* [[GettingExtensionsWorking]]
* [[GettingEffectsWorking]]
* [[WhatEffectsDo]]
* [[UsingTheConnectorTool]]
* [[Installing Fonts as a User]]
* [[EmergencySave]]
* [[ReleaseNotes045|Release Notes]] for 0.45 (unstable)
* [[ReleaseNotes044|Release Notes]] for 0.44 and past
* [[Announcing Releases]] for 0.44 and past
* [[ArticleIntroducingInkscape0_40|Introducing Inkscape 0.40]]
* [[TricksAndTips]]
</td><td style="width:33%;background-color: #FFFAE5; padding:.5em; border: 1px solid #FFFF66; margin:.5em">

=== Help Inkscape Without Coding ===

* [[PrintingConsensusPoll]]
* [[HelpWanted]]
* [[CreatingDists]]: how to build packages
* [[WebsiteEditing]]
* [[UpdatingTrackerItems]]
* [[TutorialIdeas]]
* [[How_To_Start_A_Page]] how to use the wiki
* [[TestingInkscape]]

</td></tr></table><table cellspacing="0" width="100%" style="background-color: #FFFAE5; border-width:0em .5em; border-style:solid; border-color:white"><tr valign="top" style="padding:11px 0em 0em 11px">
<th colspan="2" align="left" style="padding:.5em 0em 0em .5em">

=== Developer Documentation ===
</th></tr><tr valign="top" align="left"><td style="width:50%;padding:.5em">
==== General ====
* [[DeveloperManual]]
* [[CompilingInkscape]]
* [[WorkingWithSVN]]
* [[HandlingPreferences]]: creating and using preference values
* [[AddSPObject]]: how to add a new SPObject type
* [[ReprListeners]]: responding to XML doc changes
* [[ErrorsAndWarnings]]: how to deal with reporting errors, warnings, and other messages
* [[DebuggingTips]]: random tips to help debug problems

* [[DeveloperTitles]]: terms for various roles in Inkscape
* [[InkscapeJanitors]]: small tasks that need doing
* [http://livarot.sourceforge.net/ Livarot]: for boolean ops
* [[ExtensionAttributes]]: currently defined attributes in Inkscape's XML namespace and what they do
* [[MakingAnExtension]]: how extension must work and how to write an INX file
* [[ExtensionsRepository]]: an Internet central for Inkscape Extensions
* [[OtherProjects]] (outside links)

</td><td style="width:50%;padding:.5em">

==== Development Discussion ====
* [[Roadmap]]: the main todo list
* [[NewFeatureProposals]]
* [[ExtensionArchitectureProposals]]
* [[Coding Style|Coding Style Discussion]]
* [[FileTypes]]
* [[ApplicationIcons]] ( Application + Interface )
* [[InkscapeColor]]
* [[PrintingSubsystem]]
* [[SVG Competitors Plan]] - MS WVG vs SVG, etc
* [[SVG Tiny Compliance]]
* [[SVG Test Suite Compliance]] - [[W3C]] full test suite
* [[CSS Support]]
* [[OpenVG]] Standard (draft)
* [[OpenDocument proposal]]
* [[Googles Summer Of Code]]
* [[UI MockupScreenshots]]

</td></tr><tr valign="top" align="left"><td style="width:50%;padding:.5em">

==== User Interface Discussion ====
* [[Translation_information]]
* [[AccessibleGraphics]]
* [[ObjectManager]]
* [[DialogsReorganization]]
* [[DialogReplacement]]
* [[ModalInterfaces]]
* [[TextUsability]]: text tool /dialog dialog
* [[KeyboardShortcutsToDo]]
** [[KeyboardProfiles]]: how you can help
* [[StatusbarAPI]]
* [[Animation-(Timeline)]]
* [[Free Desktop Graphic Suite]]

</td><td style="width:50%;padding:.5em">
==== Rearchitecture Discussion ====
* [[SubsystemRearchitecture]]
* [[GtkMMification]]: replace C boilerplate with gtkmm objects
* [[PathRepresentation]]
* [[Cairoification]]
* [[ScribusInteroperability]]

</td></tr></table>
----
* [[WikiAttic]]: pages that are no longer relevant but kept for historical value

__NOTOC__

[[Category:About Inkscape]]
[[Category:User Documentation]]

ScriptingLanguages

2005-02-14T20:55:35Z

AurelioAHeckert: New Proposal

Lilypond is a musical typesetter. All of its internal structure is exported via scheme. I think inkscape should aim for this as it has paid off for lilypond in reduced time in adding functionality and ease of tweaking. My personal preference is python, being a language which sucks in new users at a phenominal rate, and provides the [http://www.boost.org/ Boost] [http://www.boost.org/libs/python/doc/index.html Seamless Python] integration.

Scripting allows many more developers to contribute, and allows new ideas to be prototyped essentially on the spot.

I think the core scripting interface should be relatively simple and language-neutral, like [[The_Gimp]]'s PDB, though object-oriented. A slightly perverse idea might be to use the Ruby interpreter's excellent C API for this purpose. But that's just one idea.

Another great scripting language is called [http://www.lua.org Lua]: very small footprint, great flexibility, can be easily embedded into any C/C++ application without any strings attached (LGPL). [http://www.lua.org Lua] is being largely used for game development. There are cases from Microsoft and Lucas Arts using it.

Another idea is to start extending with [http://www.corba.org CORBA], while it is a bit combersome to start out with, we end up not having to support individual languages. I think with a few examples of functionality implemented in those languages it would be easy for many people to pick up closely. The list of supported languages for [http://www.gnome.org/projects/ORBit2/index.html ORBit] is pretty large, and something we could build on.

---

Corba's C++ binding is nasty, though, which IMO has a great deal to do with why it's not more prevalent. I think, for the sake of bindings to other languages, all we really neede is a very thin wrapper layer that adds the necessary reflection facilities to C++'s in order for a language like Python or Ruby or whatever to generate bindings dynamically at runtime.

Oh, and we need to draw the line at simple reflection stuff (class membership, class name, method names and prototypes), or else we really will end up reimplementing CORBA (badly) all over again...

-- MenTaLguY

---

I think the key here is coming up with a way to load the modules in, independent of what language they are in - then lanuage bindings can grow and grow - but always be useful. I'll start some more discussion on this in ModuleFormat.

---

Probably the best thing is to work on the concepts to be exposed. Once they are specified, then it's easy to implement the exposure in different languages.

Of course, some decisions need to be made as to what to potentially support. This would apply to potential scripting languages and to potential features. Think of both the tasks to accomplish and of the languages to accomplish them in.

For an example of the tasks/concepts, we could think of a raster paint program (like [[The Gimp]] or PhotoShop). These deal with raster images. Additionally, it's nice to be able to work on images with different numbers of channels, different bit-depths and different colorspaces. The PhotoShop
plugin API has supported all of this for years. Sadly, [[The Gimp]] did not at the begining. Thus problems with working in CMYK or in bit depths neede for Hollywood work both have been problematic for [[The Gimp]] and its plugins.

Blocking future functionality, I think, is the main thing that Inkscape needs to avoid. As MenTaLguY has said, it's best if plugins were first-class citizens. So what needs to be exposed?

Things off the top of my head:

-Document
|-XML / parse tree
|-view tree

-UI Thingies / dialogs / user interaction

-Utility calls / factories

-- JonCruz

---

More then one language to write extensions can help the development.

The [http://www.mozilla.org/js/spidermonkey/ SpiderMonkey] is a great javascript engine, used by Mozilla web browser, and inplements the [http://www.mozilla.org/js/language/js20/ JavaScript 2.0] specification.

The JavaScript is a easy language and is the defined language to anime SVG. With the powerful 2.0 version we can do good extensions to Inkscape.

The [[AST]] is a great idea to manipulate the SVG, but may we acess in the same DOM used to [[DHTML]]. And it will be natural to DHTML scripters and developers.

It's writed in C, is fast and low weight. I'm waiting to write new efects to Inkscape with my prefered language! :-)

-- AurelioAHeckert

---