Inkscape Wiki - User contributions [en]

User:Tweenk

2019-03-06T02:59:41Z

Tweenk:

I'm an Inkscape contributor since March 2008, and my Gitlab username is 'tweenk'. Some things I've done so far:
* Fixed the clipboard to use the system-wide clipboard instead of a bunch of variables
* Refactored preference handling
* Heavily cleaned up and simplified the build system
* Made all icons themable and created a big mess in the process :)
* Made bitmap images automatically embedded where suitable
* Substantially improved the Windows port by (among others) updating and rebuilding the devlibs
* Worked on [[GSoC2009 Node Tool Rewrite]]
* Worked on GSoC2010 Cairo rendering
* Wrote tutorials for libsigc++, shared pointers and updated the tutorial for preferences

I have a lot of ideas for refactoring and generally making Inkscape easier to work with from the developer perspective.

==Notes==

Building on OSX:

cmake .. -DICONV_INCLUDE_DIR:PATH=/opt/local/include -DICONV_LIBRARIES:FILEPATH=/opt/local/lib/libiconv.dylib -DCMAKE_INSTALL_PREFIX=$(pwd)/../inst

User:Tweenk

2019-03-06T02:53:37Z

Tweenk:

I'm an Inkscape contributor since March 2008, and my SVN nickname is 'tweenk'. Some things I've done so far:
* Fixed the clipboard to use the system-wide clipboard instead of a bunch of variables
* Refactored preference handling
* Heavily cleaned up and simplified the build system
* Made all icons themable and created a big mess in the process :)
* Made bitmap images automatically embedded where suitable
* Substantially improved the Windows port by (among others) updating and rebuilding the devlibs
* Worked on [[GSoC2009 Node Tool Rewrite]]
* Worked on GSoC2010 Cairo rendering
* Wrote tutorials for libsigc++, shared pointers and updated the tutorial for preferences

I have a lot of ideas for refactoring and generally making Inkscape easier to work with from the developer perspective.

==Notes==

Building on OSX:

cmake .. -DICONV_INCLUDE_DIR:PATH=/opt/local/include -DICONV_LIBRARIES:FILEPATH=/opt/local/lib/libiconv.dylib -DCMAKE_INSTALL_PREFIX=$(pwd)/../inst

Compiling Inkscape on Chrome OS

2019-03-05T20:54:36Z

Tweenk: /* Walkthrough */

Chrome OS offers beta support for Linux apps on some Chromebook models starting with version 69. The Linux environment on Chrome OS is called Crostini and is basically a virtual machine that runs Debian with a few custom packages. It can be used to run and develop Inkscape.

==Supported hardware==

Inkscape can only be compiled on Chromebooks that support Linux apps. There is a list available on the [https://www.reddit.com/r/Crostini/wiki/getstarted/crostini-enabled-devices Crostini subreddit's wiki]. Pixelbook, Pixel Slate and several other premium Chromebook models are known to work and include both x86-64 and ARM64 models. 32-bit ARM and Intel Chromebooks are not supported.

You will need at least 4 GB of disk space for the Inkscape repository and the intermediate build files, plus some space for the Crostini installation, dependencies and tools. We recommend at least 6 GB of free space.

==Walkthrough==

This walkthrough assumes you have some familiarity with Linux commands.

* Modify the APT configuration to include source package repositories. This step is needed to use APT's <code>build-dep</code> command. Open the file <code>/etc/apt/sources.list</code> and duplicate both lines there, then change the first word from <code>deb</code> to <code>deb-src</code>. Example file content after modification:

<pre><nowiki>
deb https://deb.debian.org/debian stretch main
deb-src https://deb.debian.org/debian stretch main
deb https://deb.debian.org/debian-security stretch/updates main
deb-src https://deb.debian.org/debian-security stretch/updates main
</nowiki></pre>

* Install build dependencies for Inkscape and a few tools.

<pre>
sudo apt build-dep inkscape
sudo apt install git wget libsoup2.4-dev libgtkmm-3.0-dev libgtkspellmm-3.0-dev
</pre>

* Create a new default SSH key: <code>ssh-keygen</code> (you can just hit Enter for every question)
* Add the newly generated public key to your GitLab account. One way is to use the command <code>cat ~/.ssh/id_rsa.pub</code>, select the text (it is automatically copied to the clipboard) and paste it into the text box on the website.
* Check out the source in a directory of your choice: <code>git clone git@gitlab.com:inkscape/inkscape.git</code>
** This will take some time, because the Inkscape repo is multiple gigabytes.
* Run the GTest download script: <code>./download-gtest.sh</code>
* Run CMake: <code>mkdir build && cd build && cmake ..</code>
* Compile Inkscape: <code>make -j4</code>
* Install Inkscape: <code>sudo make install</code>
* Run Inkscape: <code>inkscape</code>
** Currently, Inkscape will crash when run if it was never installed, but running the binary from the build directory should work after installing it once; you don't need to perform the installation after every build, unless you make significant changes to the installed files.

Compiling Inkscape on Chrome OS

2019-03-05T19:24:58Z

Tweenk: /* Walkthrough */

Chrome OS offers beta support for Linux apps on some Chromebook models starting with version 69. The Linux environment on Chrome OS is called Crostini and is basically a virtual machine that runs Debian with a few custom packages. It can be used to run and develop Inkscape.

==Supported hardware==

Inkscape can only be compiled on Chromebooks that support Linux apps. There is a list available on the [https://www.reddit.com/r/Crostini/wiki/getstarted/crostini-enabled-devices Crostini subreddit's wiki]. Pixelbook, Pixel Slate and several other premium Chromebook models are known to work and include both x86-64 and ARM64 models. 32-bit ARM and Intel Chromebooks are not supported.

You will need at least 4 GB of disk space for the Inkscape repository and the intermediate build files, plus some space for the Crostini installation, dependencies and tools. We recommend at least 6 GB of free space.

==Walkthrough==

This walkthrough assumes you have some familiarity with Linux commands.

* Modify the APT configuration to include source packages. This step is needed to use APT's <code>build-dep</code> command. Open the file <code>/etc/apt/sources.list</code> and duplicate both lines there, then change the first word from <code>deb</code> to <code>deb-src</code>. Example file content after modification:

<pre><nowiki>
deb https://deb.debian.org/debian stretch main
deb-src https://deb.debian.org/debian stretch main
deb https://deb.debian.org/debian-security stretch/updates main
deb-src https://deb.debian.org/debian-security stretch/updates main
</nowiki></pre>

* Install build dependencies for Inkscape and a few tools.

<pre>
sudo apt build-dep inkscape
sudo apt install git wget libsoup2.4-dev libgtkmm-3.0-dev libgtkspellmm-3.0-dev
</pre>

* Create a new default SSH key: <code>ssh-keygen</code> (you can just hit Enter for every question)
* Add the newly generated public key to your GitLab account. One way is to use the command <code>cat ~/.ssh/id_rsa.pub</code>, select the text (it is automatically copied to the clipboard) and paste it into the text box on the website.
* Check out the source in a directory of your choice: <code>git clone git@gitlab.com:inkscape/inkscape.git</code>
** This will take some time, because the Inkscape repo is multiple gigabytes.
* Run the GTest download script: <code>./download-gtest.sh</code>
* Run CMake: <code>mkdir build && cd build && cmake ..</code>
* Compile Inkscape: <code>make -j4</code>
* Install Inkscape: <code>sudo make install</code>
* Run Inkscape: <code>inkscape</code>
** Currently, Inkscape will crash when run if it was never installed, but running the binary from the build directory should work after installing it once; you don't need to perform the installation after every build, unless you make significant changes to the installed files.

Compiling Inkscape on Chrome OS

2019-03-05T19:24:01Z

Tweenk: /* Walkthrough */

Chrome OS offers beta support for Linux apps on some Chromebook models starting with version 69. The Linux environment on Chrome OS is called Crostini and is basically a virtual machine that runs Debian with a few custom packages. It can be used to run and develop Inkscape.

==Supported hardware==

Inkscape can only be compiled on Chromebooks that support Linux apps. There is a list available on the [https://www.reddit.com/r/Crostini/wiki/getstarted/crostini-enabled-devices Crostini subreddit's wiki]. Pixelbook, Pixel Slate and several other premium Chromebook models are known to work and include both x86-64 and ARM64 models. 32-bit ARM and Intel Chromebooks are not supported.

You will need at least 4 GB of disk space for the Inkscape repository and the intermediate build files, plus some space for the Crostini installation, dependencies and tools. We recommend at least 6 GB of free space.

==Walkthrough==

This walkthrough assumes you have some familiarity with Linux commands.

* Modify the APT configuration to include source packages. This step is needed to use APT's <code>build-dep</code> command. Open the file <code>/etc/apt/sources.list</code> and duplicate both lines there, then change the first word from <code>deb</code> to <code>deb-src</code>. Example file content after modification:

<pre><nowiki>
deb https://deb.debian.org/debian stretch main
deb-src https://deb.debian.org/debian stretch main
deb https://deb.debian.org/debian-security stretch/updates main
deb-src https://deb.debian.org/debian-security stretch/updates main
</nowiki></pre>

* Install Git: <code>sudo apt install git</code>
* Install build dependencies for Inkscape.

<pre>
sudo apt build-dep inkscape
sudo apt install libsoup2.4-dev libgtkmm-3.0-dev libgtkspellmm-3.0-dev
</pre>

* Create a new default SSH key: <code>ssh-keygen</code> (you can just hit Enter for every question)
* Add the newly generated public key to your GitLab account. One way is to use the command <code>cat ~/.ssh/id_rsa.pub</code>, select the text (it is automatically copied to the clipboard) and paste it into the text box on the website.
* Check out the source in a directory of your choice: <code>git clone git@gitlab.com:inkscape/inkscape.git</code>
** This will take some time, because the Inkscape repo is multiple gigabytes.
* Run the GTest download script: <code>./download-gtest.sh</code>
* Run CMake: <code>mkdir build && cd build && cmake ..</code>
* Compile Inkscape: <code>make -j4</code>
* Install Inkscape: <code>sudo make install</code>
* Run Inkscape: <code>inkscape</code>
** Currently, Inkscape will crash when run if it was never installed, but running the binary from the build directory should work after installing it once; you don't need to perform the installation after every build, unless you make significant changes to the installed files.

Compiling Inkscape on Chrome OS

2019-03-05T19:21:25Z

Tweenk: /* Walkthrough */

Chrome OS offers beta support for Linux apps on some Chromebook models starting with version 69. The Linux environment on Chrome OS is called Crostini and is basically a virtual machine that runs Debian with a few custom packages. It can be used to run and develop Inkscape.

==Supported hardware==

Inkscape can only be compiled on Chromebooks that support Linux apps. There is a list available on the [https://www.reddit.com/r/Crostini/wiki/getstarted/crostini-enabled-devices Crostini subreddit's wiki]. Pixelbook, Pixel Slate and several other premium Chromebook models are known to work and include both x86-64 and ARM64 models. 32-bit ARM and Intel Chromebooks are not supported.

You will need at least 4 GB of disk space for the Inkscape repository and the intermediate build files, plus some space for the Crostini installation, dependencies and tools. We recommend at least 6 GB of free space.

==Walkthrough==

This walkthrough assumes you have some familiarity with Linux commands.

* Modify the APT configuration to include source packages. This step is needed to use APT's <code>build-dep</code> command. Open the file <code>/etc/apt/sources.list</code> and duplicate both lines there, then change the first word from <code>deb</code> to <code>deb-src</code>. Example file content after modification:

<pre><nowiki>
deb https://deb.debian.org/debian stretch main
deb-src https://deb.debian.org/debian stretch main
deb https://deb.debian.org/debian-security stretch/updates main
deb-src https://deb.debian.org/debian-security stretch/updates main
</nowiki></pre>

* Install Git: <code>sudo apt install git</code>
* Install build dependencies for Inkscape: <code>sudo apt build-dep inkscape</code>
** Install dependencies that are newly added in the master branch: <code>sudo apt install libsoup2.4-dev libgtkmm-3.0-dev libgtkspellmm-3.0-dev</code>
* Create a new default SSH key: <code>ssh-keygen</code> (you can just hit Enter for every question)
* Add the newly generated public key to your GitLab account. One way is to use the command <code>cat ~/.ssh/id_rsa.pub</code>, select the text (it is automatically copied to the clipboard) and paste it into the text box on the website.
* Check out the source in a directory of your choice: <code>git clone git@gitlab.com:inkscape/inkscape.git</code>
** This will take some time, because the Inkscape repo is multiple gigabytes.
* Run the GTest download script: <code>./download-gtest.sh</code>
* Run CMake: <code>mkdir build && cd build && cmake ..</code>
* Compile Inkscape: <code>make -j4</code>
* Install Inkscape: <code>sudo make install</code>
* Run Inkscape: <code>inkscape</code>
** Currently, Inkscape will crash when run if it was never installed, but running the binary from the build directory should work after installing it once; you don't need to perform the installation after every build, unless you make significant changes to the installed files.

Compiling Inkscape on Chrome OS

2019-03-05T19:18:13Z

Tweenk: /* Supported hardware */

Chrome OS offers beta support for Linux apps on some Chromebook models starting with version 69. The Linux environment on Chrome OS is called Crostini and is basically a virtual machine that runs Debian with a few custom packages. It can be used to run and develop Inkscape.

==Supported hardware==

Inkscape can only be compiled on Chromebooks that support Linux apps. There is a list available on the [https://www.reddit.com/r/Crostini/wiki/getstarted/crostini-enabled-devices Crostini subreddit's wiki]. Pixelbook, Pixel Slate and several other premium Chromebook models are known to work and include both x86-64 and ARM64 models. 32-bit ARM and Intel Chromebooks are not supported.

You will need at least 4 GB of disk space for the Inkscape repository and the intermediate build files, plus some space for the Crostini installation, dependencies and tools. We recommend at least 6 GB of free space.

==Walkthrough==

This walkthrough assumes you have some familiarity with Linux commands.

* Modify the APT configuration to include source packages. This step is needed to use APT's <code>build-dep</code> command. Open the file <code>/etc/apt/sources.list</code> and duplicate both lines there, then change the first word from <code>deb</code> to <code>deb-src</code>. Example file content after modification:

<pre><nowiki>
deb https://deb.debian.org/debian stretch main
deb-src https://deb.debian.org/debian stretch main
deb https://deb.debian.org/debian-security stretch/updates main
deb-src https://deb.debian.org/debian-security stretch/updates main
</nowiki></pre>

* Install Git: <code>sudo apt install git</code>
* Install build dependencies for Inkscape: <code>sudo apt build-dep inkscape</code>
** Install dependencies that are newly added in the master branch: <code>sudo apt install libsoup2.4-dev libgtkmm-3.0-dev libgtkspellmm-3.0-dev</code>
* Create a new default SSH key: <code>ssh-keygen</code> (you can just hit Enter for every question)
* Add the newly generated public key to your GitLab account. One way is to use the command <code>cat ~/.ssh/id_rsa.pub</code>, select the text (it is automatically copied to the clipboard) and paste it into the text box on the website.
* Check out the source in a directory of your choice: <code>git clone git@gitlab.com:inkscape/inkscape.git</code>
** This will take some time, because the Inkscape repo is multiple gigabytes.
* Run the GTest download script: <code>./download-gtest.sh</code>
* <code>mkdir build && cd build && cmake ..</code>
* <code>make -j4</code>

Compiling Inkscape on Chrome OS

2019-03-05T19:10:23Z

Tweenk: /* Walkthrough */

Chrome OS offers beta support for Linux apps on some Chromebook models starting with version 69. The Linux environment on Chrome OS is called Crostini and is basically a virtual machine that runs Debian with a few custom packages. It can be used to run and develop Inkscape.

==Supported hardware==

Inkscape can only be compiled on Chromebooks that support Linux apps. There is a list available on the [https://www.reddit.com/r/Crostini/wiki/getstarted/crostini-enabled-devices Crostini subreddit's wiki]. Pixelbook, Pixel Slate and several other premium Chromebook models are known to work and include both x86-64 and ARM64 models. 32-bit ARM and Intel Chromebooks are not supported.

==Walkthrough==

This walkthrough assumes you have some familiarity with Linux commands.

* Modify the APT configuration to include source packages. This step is needed to use APT's <code>build-dep</code> command. Open the file <code>/etc/apt/sources.list</code> and duplicate both lines there, then change the first word from <code>deb</code> to <code>deb-src</code>. Example file content after modification:

<pre><nowiki>
deb https://deb.debian.org/debian stretch main
deb-src https://deb.debian.org/debian stretch main
deb https://deb.debian.org/debian-security stretch/updates main
deb-src https://deb.debian.org/debian-security stretch/updates main
</nowiki></pre>

* Install Git: <code>sudo apt install git</code>
* Install build dependencies for Inkscape: <code>sudo apt build-dep inkscape</code>
** Install dependencies that are newly added in the master branch: <code>sudo apt install libsoup2.4-dev libgtkmm-3.0-dev libgtkspellmm-3.0-dev</code>
* Create a new default SSH key: <code>ssh-keygen</code> (you can just hit Enter for every question)
* Add the newly generated public key to your GitLab account. One way is to use the command <code>cat ~/.ssh/id_rsa.pub</code>, select the text (it is automatically copied to the clipboard) and paste it into the text box on the website.
* Check out the source in a directory of your choice: <code>git clone git@gitlab.com:inkscape/inkscape.git</code>
** This will take some time, because the Inkscape repo is multiple gigabytes.
* Run the GTest download script: <code>./download-gtest.sh</code>
* <code>mkdir build && cd build && cmake ..</code>
* <code>make -j4</code>

Compiling Inkscape on Chrome OS

2019-03-05T02:13:17Z

Tweenk: new page

Inkscape

2019-03-05T01:54:13Z

Tweenk: /* First Steps */

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

{| style="width: 100%;"
|- style="vertical-align: top;"
| style="width: 33%; background: #EEE; padding: 1em;" |
== Project Info ==
* [http://www.inkscape.org/ Inkscape Homepage]
* [[About Inkscape]]
* [[Features of Inkscape|Features]]
* [[FAQ]] — Frequently Asked Questions
* [[Supported operating systems]]
* [[Tools]] — Supporting Tools and Applications
* [[Galleries]]
* [[Inkscape coverage|Coverage]] — Awards, articles, presentations, books about Inkscape
* [[Inkscape popularity|Popularity]]
* [[Inkscape invariants|Inkscape's Mission]]
* [https://inkscape.org/en/community/ Communication] — How to reach us
* [[Announcement to Sodipodi]] — This started it all
* [[Branding]]
* [[Travel Reimbursement Policy]]
* [[Funded Project System Development]]
* Hackfests
** upcoming/proposed events: [[Hackfest2019 Saarbrücken|2019 Saarbrücken (LGM)]], [[Hackfest2019 SCALE|2019 Pasadena (SCALE)]]
** past events: [[Hackfest2018 Kiel|2018 Kiel]], [[Hackfest2018 LGM|2018 Seville (LGM)]], [[Hackfest2018|2018 Boston]], [[Hackfest2017|2017 Paris]], [[Hackfest2016|2016 Leeds (LGM)]], [[Hackfest2015|2015 Toronto (LGM)]]

| style="width: 33%; padding: 1em;" |
== User Documentation ==
* [[Installing Inkscape|Installation]]
* [[International and Local Communities]]
* [[Inkscape glossary]]
* [[User manual information]] — Where to find the free Inkscape manual and how to contribute to it
* [http://inkscape.org/en/learn/tutorials/ Tutorials]
* [[Inkscape SVG vs. plain SVG]]
* [[Output format requirements]] — What's needed to save in some formats
* [[Extension requirements]] — What's needed to use some extensions (slightly outdated)
* [[Extension reference]] — What each extension does (slightly outdated)
* [[Connector tool tutorial]]
* [[Installing fonts]]
* [[Emergency save]] — Recovery in case Inkscape crashed
* [[Release notes]]

** '''for versions [[Release notes/0.92.4|0.92.4]] (current bugfix release) and [[Release notes/0.92|0.92]] (current major release)'''
** older versions: [[Release notes/0.92.3|0.92.3]], [[Release notes/0.92.2|0.92.2]], [[Release notes/0.92.1|0.92.1]], [[Release notes/0.91|0.91]], [[Release notes/0.48.5|0.48.5]], [[Release notes/0.48.4|0.48.4]], [[Release notes/0.48.3|0.48.3]], [[Release notes/0.48.2|0.48.2]], [[Release notes/0.48.1|0.48.1]], [[Release notes/0.48|0.48]], [[Release notes/0.47|0.47]]
** future versions: [[Release notes/0.92.5|0.92.5]] (upcoming bugfix release) and [[Release notes/1.0|1.0]] (upcoming major release)
* [[Announcing Releases]]
* [[Release Process Debrief]]
* [[Tricks and tips]] — Miscellaneous advice, may be slightly outdated

| style="width: 33%; background: #EEE; padding: 1em;" |

== Help Inkscape Without Coding ==
* [[Help wanted]]
* [[Bug management]]
** [[Projects#Bug_Triage]]
* [[Testing]]
* [[Translation information]]
* [[WebSite]]
* [[Inkscape Classes]]
* [[Conferences]]
* [[Fundraising Ideas]]
* [[Creating Inkscape distributions]] — How to build packages
* [[Stable branch updates]]
* [[Updating tracker items]]
* [[Tutorials and help]]
* [[How to start a page]] — How to use the wiki
* [[Creating screencasts]]
* [[About-Screen contest]]
* [[social media|Participate in social media]]
|}

<div style="margin-top: 1em; padding: .5em 1em 1em; border: 1px solid #62C012;">

== Developer Documentation ==
{| style="width: 100%;"
|- style="vertical-align: top;"
| style="width: 50%; padding-right: 1em;" |
=== First Steps ===
* [[Working with Git]] — How to obtain the source code. A quick start on how to use our version control system.
* [[Compiling Inkscape]]
* [[Using Eclipse]] — Debug Inkscape on Windows using Eclipse (outdated)
* [[Using Visual Studio]] — Debug Inkscape on Windows using Microsoft Visual Studio
* [[Developer manual]] — Various important information, be sure to read this before coding
* [[Debugging Inkscape|Debugging]] — Random tips to help debug problems
* [[Project organization]] — Procedures, hierarchy, developer roles and the likes
* [[Janitorial tasks]] — Small tasks that need doing
* [[Doxygen documentation]]
* [[Working with CMake]] — Getting started with CMake coding for configuring and building Inkscape

=== Developer tutorials ===
* [[Architectural overview]] — A high-level look at Inkscape
* [[Preferences subsystem]] — Creating and using preference values

* Extensions
** [[Extension subsystem]] — An overview of the functionality provided by extensions and the possible implementations
** [[Script extensions]] — Extend Inkscape easily using scripting languages (Python, Perl, …)
** [[Python modules for extensions]] — Some helpful routines for use in Python script extensions
** [[INX extension descriptor format]]
* [[Creating Live Path Effects]]
* [[Boost shared pointers]]
* [[Using libsigc++ signals]]
* [[Windows development on Linux]]

=== User Interface Discussion ===
* [[Interface translation]]
* [[Adding interface verbs]]
* [[Accessible graphics]]
* [[Object Manager]]
* [[Dialogs reorganization]]
* [[Modal interfaces]]
* [[Text usability]] — Text tool and dialog
* [[KeyboardShortcutsToDo]]
** [[Keyboard profiles]] — How you can help
* [[Statusbar API]]
* [[Animation-(Timeline)]]
* [[Free Desktop Graphic Suite]]
* [[Skeletal Strokes]] — Brushes, Strokes, Pressure Sensibility...

| style="width: 50%;" |

=== Development Discussion ===
* [[Roadmap]] — The main todo list
* [[Dependencies]] — What libs are needed to build Inkscape
* [[C++11]] — Which C++11 features can be used
* [[New feature proposals]]
* [[Extension architecture proposals]]
* [[Coding Style|Coding Style Discussion]]
* [[File types]]
* [[Application icons]] — Application + Interface
* [[Icons]]
* [[Color management]]
* [[Printing subsystem]]
* [[SVG Tiny Compliance]]
* [[SVG Test Suite Compliance]] — [[W3C]] full test suite
* [[CSS Support]]
* [[Google Summer of Code]]
* [[Improved Media Management]]
* [[UI Mockup Screenshots]]
* [[Swatch Book]]
* [[Tablet Dialog]]
* [[ViewBoxToDo]] — View box support info
* [[Caching]]
* [[UI and Document coordinates‎]]
* [[GtkMMification]] — Replace C boilerplate with gtkmm objects
* [[CMake Tasks]] — Converting the Inkscape build system to CMake
* [[Bug Reporting Workflow]] — Options for improving Inkscape bug workflow from user to developer
* [[1.0 Release Bug Fix List]] — List of bugs that need to be fixed for 1.0
* [[1.0 Release Planning]] — Roadmap and planning for 1.0 Release

=== Miscellaneous ===
* [[Inkscape-specific XML attributes]] — Documentation of attributes from Inkscape's XML namespace
* [[Extension repository]] — An Internet central for Inkscape extensions
* [[Related programs]]
* [[Sponsors list]]

=== [[Lib2geom]] ===
* [[Lib2geom]]
* [[Lib2geom Goals]]
* [[Lib2geom FAQ]]
* [[Lib2geom SVN Repository Guide]]
* [[Working with 2Geom FAQ]] — Real-life questions answered about using 2Geom in real code
* [[Lib2geom py2geom]] — Python bindings to 2geom. With this you can use the power of 2geom in Python scripts.

=== Historical pages ===
These pages are outdated, but linked here for posterity.

* [[Working with Bazaar]] — Our former control version system, no longer used. See [[Working with Git]] for current instructions.
* [[Creating a new SPObject]]

|}
</div>

== See also ==
* [[:Category:Wiki Attic|Wiki Attic]] — Pages that are no longer relevant but kept for historical value

__NOTOC__

[[Category:Top level categories]]

Compiling Inkscape

2019-03-05T01:46:50Z

Tweenk: /* OS & Distribution Specific */

Hopefully, Inkscape will compile right out of the box. If it doesn't, well that's what this page is for.

Jot down notes, questions, findings, tips, etc. here on things you run into. It's a good idea to make mention of what version of the code you're trying to compile, the distribution you're running, and other such information that might be pertinent.

If legitimate bugs are found or patches developed, please move them to the [https://bugs.launchpad.net/inkscape tracker] rather than inlining them here.

== Notes ==

Inkscape 0.91 and earlier needs automake 1.7, 1.8, 1.10 or higher. Please consider NOT using automake 1.9, because it has a bug that may prevent Inkscape from compiling.

You may want to also [[Related programs#Inkscape Plugins, Scripts, and Templates|add plugins]] during or after compiling.

Please use CMake instead of Automake for Inkscape 0.92 onwards.

== CMake Notes ==

CMake is a crossplatform makefile generator similar to autotools. It tests dependencies and creates makefiles to be used with make.

Work is in progress to build Inkscape using CMake. Please see the [[CMake]] wiki page.

== OS & Distribution Specific ==

* '''Linux'''
** [[CompilingAutopackage|Autopackage]] (multi-distro)
** [[CompilingGentoo|Gentoo]]
** [[CompilingDebian|Debian]]
** [[CompilingUbuntu|Ubuntu]]
** [[CompilingSuse|Suse]]
** [[CompilingSlackware|Slackware]]
** [[CompilingYoper|Yoper]]
** [[CompilingMandrake|Mandrakelinux]]
** [[CompilingRHEL|Red Hat Enterprise Linux Version #4]]
* [[CompilingMacOsX|Mac OS X]]
* [[Compiling Inkscape on Windows|Windows]]
* [[Compiling Inkscape on Chrome OS|Chrome OS]]
* [[CompilingSPARC|SPARC]]
* [[CompilingSunSolaris|Sun Solaris]]
* [[CompilingStatic|Static Compiles]]
* '''Cross-compiling'''
** [[CrossCompilingOsX|For OS X (from Linux)]]
** [[CrossCompilingWindows|For Windows (from Linux)]]

== Package Config (pkg-config) ==

If you must compile and install any of these from source, you may find an error like this when trying to
compile them or Inkscape itself:
<pre>
checking for gtk+-2.0 >= 2.0.0 libxml-2.0 >= 2-2.4.24 sigc++-1.2 gtkmm-2.0... Package gtkmm-2.0 was not found in the pkg-config search path.
Perhaps you should add the directory containing `gtkmm-2.0.pc'
to the PKG_CONFIG_PATH environment variable
No package 'gtkmm-2.0' found
</pre>

A solution is to set the PKG_CONFIG_PATH variable as so:
* for Bash: <code>export PKG_CONFIG_PATH=/usr/local/lib/pkgconfig:/usr/lib/pkgconfig</code>
* for csh: <code>setenv PKG_CONFIG_PATH /usr/local/lib/pkgconfig:/usr/lib/pkgconfig</code>

A good place to put this line is in your .bashrc or .cshrc file.

== Dependencies ==

If your distro does not have some packages available (like many don't, ie, Fedora Core 2), you must often download and build source packages and/or install them yourself. See [[Tracking Dependencies]].

== Developer Compilation ==

Plain vanilla compilation is done as documented in INSTALL.

Now, you should use [[CMake]] to compile Inkscape:
<pre>
mkdir build
cd build
cmake ..
make
</pre>

But you can still use autoconf:
<pre>
./autogen.sh # optionally
./configure
make
</pre>

Then, to run tests and install Inkscape, you may do:
<pre>
make check
sudo make install || su -c "make install"
</pre>

See INSTALL for more on that.

But if you're going to be doing a lot of development, there's some tricks and techniques you should know, to get best results.

# Turn off optimization.
# Use ccache for faster compilation.
# Set up a separate build directory (nice for testing both gcc and g++, or cross-compiling).
# Use the -j N flag to increment the number of threads available to make, with N = 1 + number of processors.

Example: Setting up the build environment (in separate tree), and using ccache for faster
compilations on a dual-processor machine, with no optimization and full debug symbols, assuming /bin/bash:
<pre>
mkdir build
bzr checkout lp:inkscape
cd inkscape
./autogen.sh
cd ../build
export CFLAGS="-g -O0 -Wall" CC="ccache gcc"
export CXXFLAGS="-g -O0 -Wall" CXX="ccache g++"
../inkscape/configure
make -j 3 -k
</pre>

Turning off just optimization:
<pre>
export CXXFLAGS="-g -O0 -Wall"
export CFLAGS="-g -O0 -Wall"
./configure
</pre>

See [[Testing Inkscape]] for information on building and executing (unit) tests.

[[Category:Developer Documentation]]

Inkscape

2019-03-04T22:54:25Z

Tweenk: /* Developer Documentation */

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

{| style="width: 100%;"
|- style="vertical-align: top;"
| style="width: 33%; background: #EEE; padding: 1em;" |
== Project Info ==
* [http://www.inkscape.org/ Inkscape Homepage]
* [[About Inkscape]]
* [[Features of Inkscape|Features]]
* [[FAQ]] — Frequently Asked Questions
* [[Supported operating systems]]
* [[Tools]] — Supporting Tools and Applications
* [[Galleries]]
* [[Inkscape coverage|Coverage]] — Awards, articles, presentations, books about Inkscape
* [[Inkscape popularity|Popularity]]
* [[Inkscape invariants|Inkscape's Mission]]
* [https://inkscape.org/en/community/ Communication] — How to reach us
* [[Announcement to Sodipodi]] — This started it all
* [[Branding]]
* [[Travel Reimbursement Policy]]
* [[Funded Project System Development]]
* Hackfests
** upcoming/proposed events: [[Hackfest2019 Saarbrücken|2019 Saarbrücken (LGM)]], [[Hackfest2019 SCALE|2019 Pasadena (SCALE)]]
** past events: [[Hackfest2018 Kiel|2018 Kiel]], [[Hackfest2018 LGM|2018 Seville (LGM)]], [[Hackfest2018|2018 Boston]], [[Hackfest2017|2017 Paris]], [[Hackfest2016|2016 Leeds (LGM)]], [[Hackfest2015|2015 Toronto (LGM)]]

| style="width: 33%; padding: 1em;" |
== User Documentation ==
* [[Installing Inkscape|Installation]]
* [[International and Local Communities]]
* [[Inkscape glossary]]
* [[User manual information]] — Where to find the free Inkscape manual and how to contribute to it
* [http://inkscape.org/en/learn/tutorials/ Tutorials]
* [[Inkscape SVG vs. plain SVG]]
* [[Output format requirements]] — What's needed to save in some formats
* [[Extension requirements]] — What's needed to use some extensions (slightly outdated)
* [[Extension reference]] — What each extension does (slightly outdated)
* [[Connector tool tutorial]]
* [[Installing fonts]]
* [[Emergency save]] — Recovery in case Inkscape crashed
* [[Release notes]]

** '''for versions [[Release notes/0.92.4|0.92.4]] (current bugfix release) and [[Release notes/0.92|0.92]] (current major release)'''
** older versions: [[Release notes/0.92.3|0.92.3]], [[Release notes/0.92.2|0.92.2]], [[Release notes/0.92.1|0.92.1]], [[Release notes/0.91|0.91]], [[Release notes/0.48.5|0.48.5]], [[Release notes/0.48.4|0.48.4]], [[Release notes/0.48.3|0.48.3]], [[Release notes/0.48.2|0.48.2]], [[Release notes/0.48.1|0.48.1]], [[Release notes/0.48|0.48]], [[Release notes/0.47|0.47]]
** future versions: [[Release notes/0.92.5|0.92.5]] (upcoming bugfix release) and [[Release notes/1.0|1.0]] (upcoming major release)
* [[Announcing Releases]]
* [[Release Process Debrief]]
* [[Tricks and tips]] — Miscellaneous advice, may be slightly outdated

| style="width: 33%; background: #EEE; padding: 1em;" |

== Help Inkscape Without Coding ==
* [[Help wanted]]
* [[Bug management]]
** [[Projects#Bug_Triage]]
* [[Testing]]
* [[Translation information]]
* [[WebSite]]
* [[Inkscape Classes]]
* [[Conferences]]
* [[Fundraising Ideas]]
* [[Creating Inkscape distributions]] — How to build packages
* [[Stable branch updates]]
* [[Updating tracker items]]
* [[Tutorials and help]]
* [[How to start a page]] — How to use the wiki
* [[Creating screencasts]]
* [[About-Screen contest]]
* [[social media|Participate in social media]]
|}

<div style="margin-top: 1em; padding: .5em 1em 1em; border: 1px solid #62C012;">

== Developer Documentation ==
{| style="width: 100%;"
|- style="vertical-align: top;"
| style="width: 50%; padding-right: 1em;" |
=== First Steps ===
* [[Working with Git]] — How to obtain the source code. A quick start on how to use our version control system.
* [[Compiling Inkscape|Compilation]]
* [[Compiling Inkscape on Windows]]
* [[Using Eclipse]] — Debug Inkscape on Windows using Eclipse (outdated)
* [[Using Visual Studio]] — Debug Inkscape on Windows using Microsoft Visual Studio
* [[Developer manual]] — Various important information, be sure to read this before coding
* [[Debugging Inkscape|Debugging]] — Random tips to help debug problems
* [[Project organization]] — Procedures, hierarchy, developer roles and the likes
* [[Janitorial tasks]] — Small tasks that need doing
* [[Doxygen documentation]]
* [[Working with CMake]] — Getting started with CMake coding for configuring and building Inkscape

=== Developer tutorials ===
* [[Architectural overview]] — A high-level look at Inkscape
* [[Preferences subsystem]] — Creating and using preference values

* Extensions
** [[Extension subsystem]] — An overview of the functionality provided by extensions and the possible implementations
** [[Script extensions]] — Extend Inkscape easily using scripting languages (Python, Perl, …)
** [[Python modules for extensions]] — Some helpful routines for use in Python script extensions
** [[INX extension descriptor format]]
* [[Creating Live Path Effects]]
* [[Boost shared pointers]]
* [[Using libsigc++ signals]]
* [[Windows development on Linux]]

=== User Interface Discussion ===
* [[Interface translation]]
* [[Adding interface verbs]]
* [[Accessible graphics]]
* [[Object Manager]]
* [[Dialogs reorganization]]
* [[Modal interfaces]]
* [[Text usability]] — Text tool and dialog
* [[KeyboardShortcutsToDo]]
** [[Keyboard profiles]] — How you can help
* [[Statusbar API]]
* [[Animation-(Timeline)]]
* [[Free Desktop Graphic Suite]]
* [[Skeletal Strokes]] — Brushes, Strokes, Pressure Sensibility...

| style="width: 50%;" |

=== Development Discussion ===
* [[Roadmap]] — The main todo list
* [[Dependencies]] — What libs are needed to build Inkscape
* [[C++11]] — Which C++11 features can be used
* [[New feature proposals]]
* [[Extension architecture proposals]]
* [[Coding Style|Coding Style Discussion]]
* [[File types]]
* [[Application icons]] — Application + Interface
* [[Icons]]
* [[Color management]]
* [[Printing subsystem]]
* [[SVG Tiny Compliance]]
* [[SVG Test Suite Compliance]] — [[W3C]] full test suite
* [[CSS Support]]
* [[Google Summer of Code]]
* [[Improved Media Management]]
* [[UI Mockup Screenshots]]
* [[Swatch Book]]
* [[Tablet Dialog]]
* [[ViewBoxToDo]] — View box support info
* [[Caching]]
* [[UI and Document coordinates‎]]
* [[GtkMMification]] — Replace C boilerplate with gtkmm objects
* [[CMake Tasks]] — Converting the Inkscape build system to CMake
* [[Bug Reporting Workflow]] — Options for improving Inkscape bug workflow from user to developer
* [[1.0 Release Bug Fix List]] — List of bugs that need to be fixed for 1.0
* [[1.0 Release Planning]] — Roadmap and planning for 1.0 Release

=== Miscellaneous ===
* [[Inkscape-specific XML attributes]] — Documentation of attributes from Inkscape's XML namespace
* [[Extension repository]] — An Internet central for Inkscape extensions
* [[Related programs]]
* [[Sponsors list]]

=== [[Lib2geom]] ===
* [[Lib2geom]]
* [[Lib2geom Goals]]
* [[Lib2geom FAQ]]
* [[Lib2geom SVN Repository Guide]]
* [[Working with 2Geom FAQ]] — Real-life questions answered about using 2Geom in real code
* [[Lib2geom py2geom]] — Python bindings to 2geom. With this you can use the power of 2geom in Python scripts.

=== Historical pages ===
These pages are outdated, but linked here for posterity.

* [[Working with Bazaar]] — Our former control version system, no longer used. See [[Working with Git]] for current instructions.
* [[Creating a new SPObject]]

|}
</div>

== See also ==
* [[:Category:Wiki Attic|Wiki Attic]] — Pages that are no longer relevant but kept for historical value

__NOTOC__

[[Category:Top level categories]]

Hackfest2019 SCALE Topics

2019-03-01T07:35:42Z

Tweenk:

Other pages: [[Hackfest2019 SCALE]], [[Hackfest2019 SCALE Attendees]], [[Hackfest2018 Kiel Topics]].

== Topics for Inkscape Hackfest 2019 in Pasadena ==

=== Inkscape 1.0 release ===
* Planning
** 1.0 Beta in March/April timeframe
** 1.0 preN?
** 1.0 in June timeframe
* Bug review
** Priority bugs
* Testing

=== Inkscape refactoring ===
* [[Future Architecture]] [Tav]
* Complexity vs New Features [Tav]

=== Inkscape 1.1 Release ===
* Timeframe?
* Feature development objectives
* Stability objectives

=== Recruiting of new developers ===
* Extensions seems to be a popular path.
* Encourage people to write extensions.
* Organized outreach/recruitment efforts?
* Review developer onboarding guidelines
* What are the major questions new devs have
* What areas of the codebase do we need stronger institutional memory in?

=== Infrastructure ===
* Bug migration
* mailman3
* WebLate

=== Fundraising ===
* Sources
** Donation
** Fundraiser drives
** Sponsorship
** Grants
** Merchandise
* Destinations
** Hackfests & Conferences
** Organizational needs / staffing
** Contracts (very specific, highly supervised work, very short term)
** Grants (general topic, more self-directed, short/mid-term)
** Fellowships (open ended, long term)
** Education subsidizing
*** Books
*** Classes
** Equipment
* Set up a Funding Team
** Vectors-type team but chartered for to scout for money
** Actively goes out and ask for donations
** Develops fundraising ideas into actionable plans
** Maintains sponsor records
** Writes grant proposals
** Solicits sponsorship from companies
** Works with Vectors team on messaging and broader outreach efforts
** Works with Web team on sponsor visibility/appearance on website
** Works with Devel team on scoping out funding opportunities

Hackfest2019 SCALE Attendees

2019-03-01T07:29:41Z

Tweenk: /* Confirmed Attendees */

Other pages: [[Hackfest2019 SCALE Topics]], [[Hackfest2019 SCALE]].

== Confirmed Attendees ==

{| class="wikitable" style="text-align: center;"
|+ List of Attendees
Hackfest
|-
! rowspan="2" | Who
! rowspan="2" | Dates
! rowspan="2" | Maximum Allocation
! colspan="2" | Arrival
! colspan="2" | Departure
! rowspan="2" | Hotel
|-
! Date/Time
! Detail
! Date/Time
! Detail
|-
| Bryce Harrington
| 3/3 -3/10
| $2000
| 3/3 1:40pm
| BUR Alaska 3380
| 3/10 10:25am
| BUR Alaksa 3457
| Howard Johnson
|-
| Ted Gould
| 3/3 - 3/11
| $2000
|
|
|
|
| Howard Johnson (until 3/6)
|-
| Ryan Gorley
| 3/3 - 3/10
| $2000
|
|
|
|
| Howard Johnson
|-
| Martin Owens
| 3/3 - 3/10
| $2000
| 3/3 6:32pm
| BUR JetBlue 2338
| 3/10 8:00PM
| BUR JetBlue 2339
| Howard Johnson
|-
| Tavmjong Bah
| 3/3 - 3/7
| $2000
| 3/3 8:34pm
| LAX Spirit 323
| 3/7 11:50AM
| LAX Spirit 424
| Howard Johnson
|-
| Josh Andler
| 3/4 - 3/11
|
|
|
|
|
|
|-
| Krzysztof Kosiński
| 3/4 - 3/10
| N/A
| 3/3 near midnight
| car
| 3/10 evening
| car
| Howard Johnson
|}

== Unconfirmed but Likely Attendees ==

* Marc Jeanmougin

== Maybe or Unknown ==

* Alex
* Jabier

Hackfest2019 SCALE Attendees

2019-03-01T07:28:37Z

Tweenk:

Other pages: [[Hackfest2019 SCALE Topics]], [[Hackfest2019 SCALE]].

== Confirmed Attendees ==

{| class="wikitable" style="text-align: center;"
|+ List of Attendees
Hackfest
|-
! rowspan="2" | Who
! rowspan="2" | Dates
! rowspan="2" | Maximum Allocation
! colspan="2" | Arrival
! colspan="2" | Departure
! rowspan="2" | Hotel
|-
! Date/Time
! Detail
! Date/Time
! Detail
|-
| Bryce Harrington
| 3/3 -3/10
| $2000
| 3/3 1:40pm
| BUR Alaska 3380
| 3/10 10:25am
| BUR Alaksa 3457
| Howard Johnson
|-
| Ted Gould
| 3/3 - 3/11
| $2000
|
|
|
|
| Howard Johnson (until 3/6)
|-
| Ryan Gorley
| 3/3 - 3/10
| $2000
|
|
|
|
| Howard Johnson
|-
| Martin Owens
| 3/3 - 3/10
| $2000
| 3/3 6:32pm
| BUR JetBlue 2338
| 3/10 8:00PM
| BUR JetBlue 2339
| Howard Johnson
|-
| Tavmjong Bah
| 3/3 - 3/7
| $2000
| 3/3 8:34pm
| LAX Spirit 323
| 3/7 11:50AM
| LAX Spirit 424
| Howard Johnson
|-
| Josh Andler
| 3/4 - 3/11
|
|
|
|
|
|
|-
| Krzysztof Kosiński
| 3/4 - 3/10
| Google funded
| 3/3 near midnight
| car
| 3/10 evening
| car
| Howard Johnson
|}

== Unconfirmed but Likely Attendees ==

* Marc Jeanmougin

== Maybe or Unknown ==

* Alex
* Jabier

Hackfest2019 SCALE Attendees

2019-01-22T03:33:43Z

Tweenk:

Hackfest2019 SCALE Attendees

2019-01-22T03:31:00Z

Tweenk: /* Unconfirmed but Likely Attendees */

Hackfest2018 Kiel Attendees

2018-09-04T10:13:02Z

Tweenk: /* Who is Attending? */

Other pages: [[Hackfest2018 Kiel]], [[Hackfest2018 Kiel Topics]].

== Who is Attending? ==

{| class="wikitable" style="text-align: center;"
|+ List of Attendees
Hackfest
|-
! rowspan="2" | Who
! rowspan="2" | Dates
! rowspan="2" | Maximum Allocation
! colspan="2" | Arrival
! colspan="2" | Departure
! rowspan="2" | Hotel
|-
! Date/Time
! Detail
! Date/Time
! Detail
|-
| Tavmjong Bah
| 9/9, 9/10, 9/11, 9/12, 9/13 (TBC)
| $2000
| 2018-09-08
| ICE74 @18h44 (train)
| 2018-09-14
| ICE77 @11h13 (train)

|
|-
| Maren Hachmann
| 9/9, 9/10, 9/11, 9/12, 9/13
| N/A (local)
|
|
|
|
|
|-
| Martin Owens
| 9/9, 9/10, 9/11, 9/12, 9/13
| $2000
| 2018-09-08
| Iceland Air (FI632)-(FI510)
| 2018-09-14
| Iceland Air (FI511)-(FI633)
| (see Patrick)
|-
| Thomas Holder
| 9-13
| $2000
| 2018-09-08
| RE 21128 @19h55 (train)
| 2018-09-13
| RE 21017 @11h27
| Hotel Wiking
|-
| Christopher Rogers
| 9-13
| $2000
|
|
|
|
|
|-
| Marc Jeanmougin
| 9-13
| $2000
| 2018-09-08
| ICE74 @18h44 (train)
| 2018-09-15
| ICE77 @11h13 (train)
|
|-
| Jabier Arraiza
| 9/9, 9/10, 9/11, 9/12, 9/13
| $2000
| 2018-09-08
| Iberia (IB8529)
| 2018-09-14
| Iberia (IB3271)
| AirBnB Franckestraße
|-
| Mihaela Jurković
| 9-13 (TBC)
| $2000
|
|
|
|
|
|-
| Max Gaukler
| 9-12
| $2000
| 2018-09-08
| train IC2226 @17:23
| 2018-09-12
| train ICE801 @14:13
| shared apartment via booking.com
|-
| Patrick "Ede_123" Storz
| 9/9, 9/10, 9/11, 9/12, 9/13
| $2000
| 2018-09-08
| ICE74 @18h44 (train)
| 2018-09-15
| ICE77 @11h13 (train)
| B&B Hotel Kiel-Wissenschaftspark
|-
| Jürgen Weigert
| 9-13
| $2000
|
|
|
|
| Centro Hotel Consul
|-
| Alex Valavanis
| 9/? (TBD)
| $2000
|
|
|
|
|
|-
| Khaled Hosny
| 9/? (TBD)
| $2000
|
|
|
|
|
|-! Total
!
!
! $22,000
!
!
!
!
!
|}

TBD: "To Be Determined"

The Inkscape board has approved travel reimbursements of up to $2000 per person. Note: additional participants require the formality of a board vote.

Separate allocations for:
* Inkscape dinner, participants and guests (450€).
* Snacks, etc. (300€).
* Venue: Free.

1 Requires formality of board vote.

Hackfest2018 Kiel Attendees

2018-06-17T23:21:18Z

Tweenk: add myself

Google Summer of Code

2017-03-12T03:06:32Z

Tweenk: /* Suggested Project Ideas */

= Welcome to Inkscape! =

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

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

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

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

= Student Applications =

* Google program information:
** [https://summerofcode.withgoogle.com/ Home page].
** Summer of Code Application form. Applications open at 19:00 UTC on March 20th.

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

'''Student Applications for GSoC 2017 must be submitted to the GSoC site by 19:00 UTC on April 3rd 2017.'''

= The "two patches" rule =

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

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

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

= Performance Evaluation =

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

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

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

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

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

= Suggested Project Ideas =

The following is a list of formal project suggestions, but do not feel limited to only these - some of our best contributions have been unique ideas that students had in mind from other sources!

See also [[Development Project Ideas]] and https://blueprints.launchpad.net/inkscape/

==P1. Better CSS Style Sheet Support==

Enhance Inkscape's support for CSS style sheets.

* Estimation of difficulty: Moderately hard
* Potential mentors: Tavmjong Bah
* Programming skills needed: C++
* Prerequisites: Experience with CSS style sheets.

Detailed Description

Inkscape has rudimentary support for CSS style sheets that can read and parse one internal style sheet. A 2016 GSoC project added a simple style dialog that can create and modify the internal style sheet. The dialog is very limited and is not intuitive to use. This project will extend the usefulness of that dialog by making it more user friendly and by extending its functionality. The use of CSS classes should eventually replace the Selection Set dialog.

Stretch goals include:

* Support external style sheets.
* Support multiple internal style sheets.
* Support CSS 3 selectors.
* Support parsing of 'font-face'.

Use Cases

* Support externally created SVGs.
* Producing better SVGs for the Web.
* Changing style on multiple objects at once (palettes).

Related Material

* [https://www.w3.org/TR/CSS2/ CSS 2 Specification]
* [https://www.w3.org/TR/css-2015/ CSS 2015 Snapshot]

==P2. Development Project Management System==

Enhance Inkscape's web tools for managing development projects.

* Estimation of difficulty: Moderately hard
* Potential mentors: Bryce Harrington
* Programming skills needed: Python
* Prerequisites: Working knowledge of Django web application development

Detailed Description

Design and implement tools to allow submitting and editing ideas for development projects. Create various project listing views that display projects that need further editing, lists of projects meeting various criteria (e.g. janitorial, new features, programming language, etc.), assigned projects, completed projects, and so forth.

This work would be part of a larger, ongoing effort to unify Inkscape's various collections of task ideas into a single system, to make them easier for potential contributors to review and select from. Some of this project has already been implemented, so you would be focusing on enhancing its user interfaces to make it more powerful and more broadly usable.

Use Cases
* "Janitorial" tasks suitable for new developers looking for easy ways to get involved in Inkscape development
* Google Summer of Code Project Ideas (this page!!)
* Funded development work, with funds supplied by various fundraisers
* User-supplied requests for feature enhancements

Related Material
* Current collections of tasks that we want to eventually migrate into this system:
** http://wiki.inkscape.org/wiki/index.php/Janitorial_tasks
** https://blueprints.launchpad.net/inkscape/
* [https://inkscape.org/en/support-us/funded-development/ High level specification for the system]
* [[FundedProjectSystemDevelopment]] related tasks

==P3. Slice toolbar items==
[[File:Cuttool.png|200px|thumb|right|Example of result of the cut/eraser tool]]
* Estimation of difficulty: Moderately hard
* Potential mentors: Jabier Arraiza (Spanish, some English)
* Programming skills needed: C++

Detailed Description
The goal is a toolbar item, called "slice" to slice items in a easy way.
We check to convert strokes to path previously to cut, to avoid continuing with stroke thought cut-out item fills. 
Maybe positioned in the path menu after bool operations, the selected items are sliced from topmost path, converting strokes to paths, duplicating fills and maybe apply to groups (there is some work in groups boolops from Martin Owens). 
A lot of helper code is done yet in flatten branch (Alexander Brock lp:~inkscape+alexander/inkscape/flatten). 
There are new Boolean operations, implemented but not used in trunk. We need to switch the division and flatten branch methods from Livarot to these new operations. 
Another feature interesting is a second toolbar item "slice from guides" to get the guides over the selected item and use it as cut-out. 

Use Cases
* Better item slicing.

==P4. SVG 2 Text Support==

* Estimation of difficulty: Hard
* Potential mentors: Tavmjong Bah
* Programming skills needed: C++
* Prerequisites: Familiarity with text layout. Knowledge of CSS.

Detailed Description

Inkscape currently has a non-compliant flowed text feature (based on SVG 1.2 which was never adopted) that needs to be made compatible with both SVG2 and SVG 1.1. This project is to re-implement the flowed text feature within Inkscape to be SVG2 compliant and to have a proper SVG 1.1 fallback. In addition to the flowed text itself as it exists within Inkscape, SVG2 adds new formatting features including shape-margin and shape-padding, shape-inside and shape-outside, exclusions, additional white-space control settings, pre-wrap, pre-line, etc.

Use Cases
* Proper text flow into rectangles and other shapes.

Related Material
* [https://svgwg.org/svg2-draft/text.html Current draft of SVG 2 text specification.]

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

[[Category:Developer Documentation]]

Google Summer of Code

2017-03-12T03:06:21Z

Tweenk: /* Suggested Project Ideas */ remove completed project

GTK+ 3 issues

2016-05-03T07:42:23Z

Tweenk: /* Issues */

This page is for Gtk documentation, any issues, questions or notes about the porting of inkscape to Gtk3. This document will be sent to the gtk/gnome developers and may be useful for Gimp developers who undergo the same process.

== Issues ==

Document your issues with porting Inkscape to Gtk3 below.

* Jumping palette. The color bar/palette does not seem to be able to decide how high it should be, at least for some combinations of palette width, height, etc. See launchpad bug [https://bugs.launchpad.net/inkscape/+bug/1201545 #1201545].

* Icons are too small / cut. (if someone can find the launchpad bug for this one, please add link here). This is probably caused by the use of SPIcon instead of a standard GtkImage widget.

== Standard Practice ==

List any repetative actions during the upgrade and note anything that needed doing when moving from gtk2 to gtk3 widgets (for examine hbox and vbox) be clear if the action is using gtk3 or gtkmm (which often papers over some of the move to gtk3)

* No patterns documented yet

== Widgets ==

List any and all custom widgets currently being used in Inkscape.

* Rulers - src/widgets/ruler.cpp
** Should probably be updated from GIMP.
* SPIcon - src/widgets/icon.cpp
** Should be replaced with regular GtkImage.
* SPCanvas - src/display/sp-canvas.cpp
** Needs to stay a custom widget. Fixed for GTK3.

== Ideas ==

Any ideas which are interesting

* No ideas yet

GTK+ 3 issues

2016-05-03T07:41:48Z

Tweenk: /* Widgets */

This page is for Gtk documentation, any issues, questions or notes about the porting of inkscape to Gtk3. This document will be sent to the gtk/gnome developers and may be useful for Gimp developers who undergo the same process.

== Issues ==

Document your issues with porting Inkscape to Gtk3 below.

* Jumping palette. The color bar/palette does not seem to be able to decide how high it should be, at least for some combinations of palette width, height, etc. See launchpad bug [https://bugs.launchpad.net/inkscape/+bug/1201545 #1201545].

* Icons are too small / cut. (if someone can find the launchpad bug for this one, please add link here)

== Standard Practice ==

List any repetative actions during the upgrade and note anything that needed doing when moving from gtk2 to gtk3 widgets (for examine hbox and vbox) be clear if the action is using gtk3 or gtkmm (which often papers over some of the move to gtk3)

* No patterns documented yet

== Widgets ==

List any and all custom widgets currently being used in Inkscape.

* Rulers - src/widgets/ruler.cpp
** Should probably be updated from GIMP.
* SPIcon - src/widgets/icon.cpp
** Should be replaced with regular GtkImage.
* SPCanvas - src/display/sp-canvas.cpp
** Needs to stay a custom widget. Fixed for GTK3.

== Ideas ==

Any ideas which are interesting

* No ideas yet

GTK+ 3 issues

2016-05-03T07:41:37Z

Tweenk: /* Widgets */

This page is for Gtk documentation, any issues, questions or notes about the porting of inkscape to Gtk3. This document will be sent to the gtk/gnome developers and may be useful for Gimp developers who undergo the same process.

== Issues ==

Document your issues with porting Inkscape to Gtk3 below.

* Jumping palette. The color bar/palette does not seem to be able to decide how high it should be, at least for some combinations of palette width, height, etc. See launchpad bug [https://bugs.launchpad.net/inkscape/+bug/1201545 #1201545].

* Icons are too small / cut. (if someone can find the launchpad bug for this one, please add link here)

== Standard Practice ==

List any repetative actions during the upgrade and note anything that needed doing when moving from gtk2 to gtk3 widgets (for examine hbox and vbox) be clear if the action is using gtk3 or gtkmm (which often papers over some of the move to gtk3)

* No patterns documented yet

== Widgets ==

List any and all custom widgets currently being used in Inkscape.

* Rulers - src/widgets/ruler.cpp
** Should probably be updated from GIMP.
* SPIcon - src/widgets/icon.cpp
** Should be replaced with regular GtkImage.
* SPCanvas - src/display/sp-canvas.coo
** Needs to stay a custom widget. Fixed for GTK3.

== Ideas ==

Any ideas which are interesting

* No ideas yet

Roadmap

2016-04-13T11:06:25Z

Tweenk: /* Inkscape 0.93 ~ Maintenance and Optimization Focus */

This is a working document showing specific near-term tasks needed for achieving the numbered milestones. It is '''not a wishlist''' of features to be included in future releases. Because people often work on whatever they feel like, only the current and current+1 releases should be taken seriously. Beyond that is mainly conjectural.

''See [[OldRoadmap]] for milestones that have already been achieved.''

=== Inkscape 0.91 ~ Refactoring ===

0.91 will be a longer cycle focused on refactoring and new features.

* (DONE) <del>Merge GSoC 2010 work</del>
* (DONE) <del>Evaluate changing the numbering scheme to a date-based one, or setting more realistic goals for major (1.0, 2.0) releases</del>
* (DONE) <del>Port renderer to Cairo (Krzysztof - GSoC 2010)</del>
* (DONE) <del>Completely remove libnr</del>

=== Inkscape 0.92 ~ Infrastructure Focus ===
* <s>(DONE) Set up autogeneration of Inkscape source code documentation ([http://wiki.inkscape.org/wiki/index.php/Doxygen_documentation Doxygen not available online according to old wiki page] but [http://fossies.org/dox/inkscape-0.91pre2/ available here (fossies.org)])</s> (http://jenkins.inkscape.org/job/Inkscape_trunk_doxygen/doxygen/)
** <s>(DONE) Put it publicly somewhere on the inkscape domain for "official" access.</s> (http://jenkins.inkscape.org/job/Inkscape_trunk_doxygen/doxygen/)
* Build system: migrate away from Autotools (See [[Build system improvements]])
** Decide between CMake and Waf
*** <s>(DONE) Alex will be doing a "neutral party" review of the two</s> Decision to go with cmake for now.
** Get decided system working
*** See [[CMake_Tasks]]
** <s>(DONE) Switch release tools to use new build system</s> Documented for now; will wait on mechanizing it until after switch to git.
** Switch packaging tools to use new build system
** Retain Autotools support one final release (legacy support), then drop next release.
* Decide which Unit testing framework to use ([http://inkscape.13.x6.nabble.com/Unit-testing-td4967386.html Discussion July 2013 didn't get much traction])
** Hackfest consensus is Google test. Bryce will make RFC to devel list for any other opinions.
* Improved mailing list archive
** Move existing archive to inkscape.org or add an archive mirror at inkscape.org ("official" inkscape information is spread out wide between different domains), this would be an improvement.
** Consider also bringing lib2geom mailing lists?
** inkscape: We need postmaster@inkscape.org and abuse@inkscape.org set up. Maybe as part of a mailing list refresh?
* Make the Windows uninstaller work (reevaluate this, we now have msi installer for win32 and Win64)
* New Swatch dialog [Tomasz' GSoc project]

=== Inkscape 0.93 ~ Maintenance and Optimization Focus ===
* Migration to Git
* Migration to GitHub
* Set up continuous builds using Travis CI / Appveyor
* Make C++11 compiler a hard requirement
* Drop Autotools support (See [[Build system improvements]])
* Improved performance
** with an empty start
** when starting up with an existing file
* Flip y-coordinate to match SVG.
** Introduce a backwards compatibility mechanism that will allow us to modify the XML representation of editing info. This is needed to bring the desktop coordinate system in line with SVG due to guideline and 3D box problems (they save desktop coordinates in the XML). This can be done either at the SP tree level or by moving to a SAX-based parser which updates the editing information as the document is parsed.
* 2geom maintenance
** Clean up and move generally useful geometry code to 2Geom
** Stop embedding 2Geom in Inkscape's codebase; handle it as a regular dependency
** Possibly start doing lib2geom releases in conjunction with Inkscape's releases?
* Split tutorials and other content from the main executable, to enable them to be updated independently of our main release process
* Split out less well maintained extensions to an 'extras' package
** Add a test suite that runs each extension against a collection of test documents
** Possibly start doing inkscape-extras releases in conjunction with Inkscape's releases?
* Refactor out "Sodipodi" history
** SPItem, SPObject and other variables have names from the early versions of Sodipodi, these names no longer makes sense (especially for new developers).
* <s>Migrate potrace to be an external dependency</s> Done for 0.92
* Prepatory work for expanded testing
** Implement example unit tests for: SP objects, verbs, cmdline options, live effects, UI dialogs, UI widgets/tools, UI view, etc.

=== Inkscape 0.94 ~ New Features Focus ===
* Multi-page documents and parent/child document references
* SVG Flowed Text
** Fix flowtext
** Implement SVG 2 flowed text which has a natural SVG 1.1 fallback.
* Improve support for CMYK/spot colors
** Minor UI streamlining
** Eliminate the CMS tab
** Change the CMYK tab to allow selecting the CMYK colors directly
** Allow setting the document to CMYK, which sets a global CMYK profile
** Stores RGB colors as RGB, CMYK colors as CMYK
* Solicit community-contributed tutorial contributions
* (Optionally) Start allowing use of C++-11 features that we find to be sufficiently widely supported

=== Inkscape 0.95 ~ Stabilization Focus ===
* Update all core plugins to handle multi-page documents
* Special focus on bugs relating to multi-page, flowed text, 2geom, and coordinate system flip
* Write unit test cases
** Core functions
* Introduce new tutorials

=== Inkscape 1.0 ~ Documentation Focus ===
* Review, update, and expand existing documentation
** code documentation
** tutorials
** man page
** kickoff manual effort?
* Better translations - keep track of % translations for all languages. Drive to 95% on all major languages.
* Cleanup website and wiki
** Move pages of value to users from wiki to the main website
** Trim down amount of legacy material presented in the wiki

-----------------------------------
'''Following is a WIP draft of the post-1.0 release goals; this is not yet finalized, and should not be taken as official yet'''
-----------------------------------

=== Inkscape 1.1 ~ Refactoring ===
* Expand range of C++-11 features allowed; make C++-11 support more of a requirement for Inkscape
** http://en.cppreference.com/w/cpp/compiler_support
* Take a holistic approach to UI design ([http://sourceforge.net/p/inkscape/mailman/message/33080043/ Original email])
*# Analyze the existing UI, make a list of UI decisions that are inconsistent between each other.
*# Look around, see how other project solves these things, figure out what's good/applicable for Inkscape (like designing particular custom widgets that are less pixel-hungry etc.).
*# Design some sort of HIG (Human Interface Guidelines) for Inkscape
*# Use it to plan redesigns existing dialogs/docks.
*# Preserve dialog layouts between sessions
* Externalize some (easy) dependencies
** Switch to using libcroco as a regular dependency (not embedded in our codebase).
*** Contact maintainer to see if still actively maintaining, and if can roll a new release for us
*** Else, consider adopting maintenance of the library under the Inkscape project umbrella
*** Or consider replacement with libcss or other CSS parser.
*** See http://inkscape.13.x6.nabble.com/Should-inkscape-take-over-libcroco-td2784457.html
** Switch to using Adaptagrams (libvpsc, libcola & libavoid) as a regular dependency
*** Contact maintainer to see if still actively maintaining, and if can roll a new release for us
*** Else, consider adopting maintenance of the library under the Inkscape project umbrella
*** See https://bugs.launchpad.net/inkscape/+bug/1353833

=== Inkscape 1.2 ~ Infrastructure ===
* Replace VCS
* Greatly expand Unit test framework.
* Consider setting up workflow (passing tests, test coverage, code review) for getting code into trunk.
** Improve new contributor experience for getting patch reviews
** Switch patch review software from launchpad to something like mailing list + patchwork, or phabricator
* make msi Windows install multilingual

=== Inkscape 1.3 ~ Maintenance and Optimization ===
* Better modularization
** Break libdepixelize out to its own library
** Break libnrtype out to its own library
** Break libuemf out to its own library
* Switch to using Poppler's API rather than using internals (the current situation causes regular breakage with new releases of Poppler)
* [[GtkMMification]]
* XML refactoring: Remove direct manipulation of XML from as many places as possible and replace it with SP tree methods.
* Improved performance
** Working with large files
** Working with files with lots of filters

=== Inkscape 1.4 ~ Major Features ===
* Complete conversion to GTK 3
** Switch to using libgdl as a regular dependency
** Be smarter about toolbar layout so we never have invisible (but necessary) buttons off the screen.
** Rework panels so that they resize consistently and display contents better. Consider moving back to dialogs in some cases or moving more functionality to the canvas.
* Begin development of new plugin / extension system(s)
** Review the D-Bus scripting API GSoC work from 0.48 timeframe
** Easy to create
** Powerful enough to do LPEs, filters, etc.
** Establish an Extensions Center for community-collaborative sharing/reviewing/maintaining extensions
** Probably need several different APIs for different levels in the codebase, such as atop the object model, one for canvas stuff, one atop the UI, etc.
*** Core extensions are shipped with Inkscape
*** User review ranking
*** Developer review ranking
*** Auto-QC ranking (mechanical testing, and checking for docs, test cases, etc.)
** Search the Extensions Center and install from within Inkscape

=== Inkscape 1.5 ~ Stabilization ===

=== Milestone [Future] ===

===== Infrastructure =====

===== Maintenance =====
* Split backend / GUI frontend

===== New features / Improvements to existing features =====
* <strike>Make flowed text SVG-compliant.</strike>
* [[SVG2]] support (with proper SVG 1.1 fallbacks)
* Improve support for SVG switches: the first recognized element in a switch should appear directly in the SP tree, not as a child of the switch element.
* Improve support for changing the name of the XML element node in response to SP tree changes.
* Hardware acceleration: make use of modern GPUs to speed up rendering.
* Live path effects: investigate extending to cover generic vector transformations (vector effects). Provide live versions of several destructive operations: boolean ops, stroke to path, text to path, etc.
* Mesh gradient support
* CSS support
* Javascript support
* Animation support.
** frame-by-frame interpolations?
** SMIL?
** Javascripts?
** Something else?
* Evaluate pdf exporter to join features from scribus Export
** Improved export for printing industry ([http://sourceforge.net/p/inkscape/mailman/inkscape-devel/thread/trinity-c6dc9287-cda7-4d8d-9a49-3201dd64f2d1-1412200320248%403capp-gmx-bs01/#msg32887957 Mailing list thread from October 2014])
* For animation and css, a functionality to remove ALL transformations from an SVG
* PDF cleanup function - ungroup everything, remove all unnecessary clipping and masking
* Better marker support
* Object navigator (like in ponyscape)
* Inkscape for Android
* CAD drawing functionality
* More file format import compatibility
** TopDraw
* OCR of bitmap traces
* Rewrite / reintroduce 3D box.
** 3-dimensional grid, perspective deformed, with snapping

===== Documentation =====

===== Community =====

[[Category:Developer Documentation]]

Hackfest2016 Topics

2016-04-11T10:56:54Z

Tweenk:

Please add topics you would like to discuss or work you would like to see done at the hackfest.

Other pages: [[Hackfest2016]], [[Hackfest2016 Attendees]].

== Agenda ==

# Introductions
# Create Agenda
# Hacking:
## Tackle GTK3 flickering bug. (Blocker for 0.92?)
## Fix rendering artifacts due to tiling (and feTile rendering).
## Selection - boost multiindex (GSoC project?)
## Path offsetting in 2geom. (Pull in code from helper/geom-pathstroke.cpp?)
## CMake build
## Build against external 2geom
## Bug fixing
# Infrastructure:
## Mailing lists off Sourceforge
## Git
## CI
## Unifying/coordinating Inkscape and 2geom development activity
# Bugs
# Performance
# Code Review
# Code Documentation
# Roadmap Review
# Accessibility

== Work pages ==

* [[Killing Livarot]]
* Coordinate System flip
* [[Working with CMake]]
* [[CMake Tasks]]

== Discussions ==

# Fundraising
## Sponsorship rewards
# Roadmap
# Gtk3
# C++11
# Refactoring
# Testing - Switch to Google test
# Plugins
# 2Geom Maintenance
# Style dialog and Selections (both GSoC projects)
# Hardware Acceleration
# Community Development
# Release Process + 0.92
# Best route(roadmap) to enabling extensions to have more ability. E.g. Boolean ops. Via Dbus, Python API, ...
# Features VS Usability. UX Design.

== Topics from Inkscape's Google+ Page ==

# Interface
## Larger/smaller icons
## Port to GTK3
## Sidebar menus/issues with multiple work spaces
## Expanded Layer menu showing all items.
## Dark/light theme
## Angle/length restraints with Bezier-Tool
## Flexible Tool order

# Other
## Animation
## Linked text boxes for flow text
## Visual tearing, smooth zooming (Ctrl-Middle Mouse)
## Artistic brush library
## Custom brushes
## Multi-page
## Division of multiple paths
## Better AI Import/Export
## geoJSON importer

==Action Items (things to be done soon after the hackfest)==
* Krzysztof: test CMake build system on OSX and Windows

Hackfest2016 Attendees

2016-04-01T19:13:47Z

Tweenk: /* Who is Attending? */

Other pages: [[Hackfest2016]], [[Hackfest2016 Topics]].

== Who is Attending? ==

{| class="wikitable" style="text-align: center;"
|+ List of Attendees
Hackfest
|-
! rowspan="2" | Who
! colspan="2" | Dates
! colspan="2" | Allocation
! colspan="2" | Arrival
! colspan="2" | Departure
! rowspan="2" | Hotel
|-
! Hackfest
! LGM
! Hackfest
! LGM
! Date/Time
! Detail
! Date/Time
! Detail
|-
| Alex Valavanis (host)
| 4/11, 4/12, 4/13
| -
| $2000
| -
| colspan="5" |
|-
| Tavmjong Bah
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| $2000
| $500
| 10th 5:31PM
| Eurostar + Train
| xx
| xx
| xx
|-
| Martin Owens
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| $2000
| $500
| 10th 7:25AM
| BOS -> LHR
| 25th 1:05PM
| LHR -> BOS
| xx
|-
| C R
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| colspan="2" | -
| xx
| xx
| xx
| xx
| xx
|-
| Marc Jeanmougin
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| $1000
| $500
| 10th 5:31PM
| Eurostar + Train
| 19th 4:31PM
| Eurostar
| Boundary Hotel then YHA StPancras
|-
| Sebastian Faubel
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| colspan="2" | -
| xx
| xx
| xx
| xx
| xx
|-
| Sebastian's colleague
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| colspan="2" | -
| xx
| xx
| xx
| xx
| xx
|-
| Jabier Arraiza
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| $2000
| $500
| 10th 22:22PM
| BIO -> LHR BA 467 + Trainline
| 19th 15:40PM
| LHR -> BIO BA 468
| Airbnb
|-
| Krzysztof Kosiński
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| 1
| 1
| 10th 1:40PM
| BA286
| 19th 2:05PM
| BA287
| The Kingston, Eurotraveller Harrow
|-
| Olof Bjarnason
| 4/11, 4/12, 4/13
| NA
| $500
| -
| 11th Morning train
| Morning train
|
|
| AirBnB
|-
| the Adib
| -
| 4/15, 4/16, 4/17, 4/18
|
| $500
| xx
| xx
| xx
| xx
| xx
|-
| John Cliff
| -
| 4/15, 4/16, 4/17, 4/18
|
| $500
| xx
| xx
| xx
| xx
| xx
|-
! Total
!
!
! $9500
! $3000
!
!
!
|}

Venue (includes lunch and snacks): ~$1300.

1 Sponsored by outside organization.

Allocation for attending hackfest:
* Up to $2000 each for Inkscape developers who have contributed for 3+ years and > 200 commits.
* Up to $1500 each for Inkscape developers who have contributed for 2+ years and > 100 commits.
* Up to $1000 each for Inkscape developers who have contributed for 1+ year and > 50 commits.
* Up to $500 each for any Inkscape contributor listed in AUTHORS file with at least 10 commits by Jan 1, 2016.

Allocation for attending LGM (additional to allocation for hackfest):
* Up to $500 each for any Inkscape contributor listed in AUTHORS file by Jan 1, 2016.

If your are an active contributor to Inkscape but are NOT in the AUTHORS file (translator, documentor, etc.) we may still be able to provide some funding on a case-by-case basis.

== Travel ==

Attendees seeking reimbursement must follow [https://gitorious.org/conservancy/policies/raw/75b8894f8586503e5abd23bed84229bbe5c1b7ee:Travel/conservancy-travel-policy.txt SFC travel policy]. Most importantly, take a screen shot of your airfare search. Your ticket must be within $100 of the lowest fare. Keep receipts for transport and lodging. Meal cost and misc. expenses are handled by a per diem and don't require receipts.

=== Transport ===

Google Flights search is probably your best bet. kayak.com and mobissimo.com can also be useful.

There is a small airport in Leeds (Leeds-Bradford). http://www.justtheflight.co.uk/cheap-flights-from-LBA/

Manchester airport is 1.5 hours away (~$30, 50 min; ~$10 if booked several weeks in advance [http://www.thetrainline.com])

Trains between London (Kings Cross) and Leeds take a bit more than 2 hours. Book your ticket one month ahead to save 70%!

Trains between Paris and Leeds: $70 one way, 5 hours, booked far in advance.

Devenshire Hall is about 25 minutes by bus #1 (every 10 minutes) or a 40 minute walk from Leeds Train station.

=== Hotel ===

Check AirBnB. Often 1/3 the cost of a hotel room.

=== Venue ===

CONFIRMED

The hackfest will take place in Devenshire Hall at the University of Leeds. (Cumberland Road, Leeds, LS6 2EQ)

A map of the U. of Leeds campus can be found at http://www.meetinleeds.co.uk/map-of-venues

Note: Lunch and snacks will be provided.

== Reimbursements ==

After the event, forward your receipts (scans/pdf files/etc.) to me (Tavmjong). I'll collect them and forward them to the SFC. You need to also send payment information (name, currency, paypal account or bank information: see travel policy for more details).

Hackfest2016 Attendees

2016-03-18T07:09:29Z

Tweenk: /* Who is Attending? */

Other pages: [[Hackfest2016]], [[Hackfest2016 Topics]].

== Who is Attending? ==

{| class="wikitable" style="text-align: center;"
|+ List of Attendees
Hackfest
|-
! rowspan="2" | Who
! colspan="2" | Dates
! colspan="2" | Allocation
! colspan="2" | Arrival
! colspan="2" | Departure
! rowspan="2" | Hotel
|-
! Hackfest
! LGM
! Hackfest
! LGM
! Date/Time
! Detail
! Date/Time
! Detail
|-
| Alex Valavanis (host)
| 4/11, 4/12, 4/13
| -
| $2000
| -
| colspan="5" |
|-
| Tavmjong Bah
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| $2000
| $500
| 10th 5:31PM
| Eurostar + Train
| xx
| xx
| xx
|-
| Martin Owens
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| $2000
| $500
| 10th 7:25AM
| BOS -> LHR
| 25th 1:05PM
| LHR -> BOS
| xx
|-
| C R
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| colspan="2" | -
| xx
| xx
| xx
| xx
| xx
|-
| Marc Jeanmougin
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| $1000
| $500
| 10th 5:31PM
| Eurostar + Train
| 19th 4:31PM
| Eurostar
| Boundary Hotel then YHA StPancras
|-
| Sebastian Faubel
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| colspan="2" | -
| xx
| xx
| xx
| xx
| xx
|-
| Sebastian's colleague
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| colspan="2" | -
| xx
| xx
| xx
| xx
| xx
|-
| Jabier Arraiza
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| $2000
| $500
| xx
| xx
| xx
| xx
| xx
|-
| Krzysztof Kosiński
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| 1
| 1
| 10th 1:40PM
| BA286
| 19th 2:05PM
| BA287
| xx
|-
| the Adib
| -
| 4/15, 4/16, 4/17, 4/18
|
| $500
| xx
| xx
| xx
| xx
| xx
|-
| John Cliff
| -
| 4/15, 4/16, 4/17, 4/18
|
| $500
| xx
| xx
| xx
| xx
| xx
|-
! Total
!
!
! $9000
! $3000
!
!
!
|}

Venue (includes lunch and snacks): ~$1300.

1 Sponsored by outside organization.

Allocation for attending hackfest:
* Up to $2000 each for Inkscape developers who have contributed for 3+ years and > 200 commits.
* Up to $1500 each for Inkscape developers who have contributed for 2+ years and > 100 commits.
* Up to $1000 each for Inkscape developers who have contributed for 1+ year and > 50 commits.
* Up to $500 each for any Inkscape contributor listed in AUTHORS file with at least 10 commits by Jan 1, 2016.

Allocation for attending LGM (additional to allocation for hackfest):
* Up to $500 each for any Inkscape contributor listed in AUTHORS file by Jan 1, 2016.

If your are an active contributor to Inkscape but are NOT in the AUTHORS file (translator, documentor, etc.) we may still be able to provide some funding on a case-by-case basis.

== Travel ==

Attendees seeking reimbursement must follow [https://gitorious.org/conservancy/policies/raw/75b8894f8586503e5abd23bed84229bbe5c1b7ee:Travel/conservancy-travel-policy.txt SFC travel policy]. Most importantly, take a screen shot of your airfare search. Your ticket must be within $100 of the lowest fare. Keep receipts for transport and lodging. Meal cost and misc. expenses are handled by a per diem and don't require receipts.

=== Transport ===

Google Flights search is probably your best bet. kayak.com and mobissimo.com can also be useful.

There is a small airport in Leeds (Leeds-Bradford). http://www.justtheflight.co.uk/cheap-flights-from-LBA/

Manchester airport is 1.5 hours away (~$30, 50 min; ~$10 if booked several weeks in advance [http://www.thetrainline.com])

Trains between London (Kings Cross) and Leeds take a bit more than 2 hours. Book your ticket one month ahead to save 70%!

Trains between Paris and Leeds: $70 one way, 5 hours, booked far in advance.

Devenshire Hall is about 25 minutes by bus #1 (every 10 minutes) or a 40 minute walk from Leeds Train station.

=== Hotel ===

Check AirBnB. Often 1/3 the cost of a hotel room.

=== Venue ===

CONFIRMED

The hackfest will take place in Devenshire Hall at the University of Leeds. (Cumberland Road, Leeds, LS6 2EQ)

A map of the U. of Leeds campus can be found at http://www.meetinleeds.co.uk/map-of-venues

Note: Lunch and snacks will be provided.

== Reimbursements ==

After the event, forward your receipts (scans/pdf files/etc.) to me (Tavmjong). I'll collect them and forward them to the SFC. You need to also send payment information (name, currency, paypal account or bank information: see travel policy for more details).

Hackfest2016 Attendees

2016-03-18T07:08:41Z

Tweenk: /* Who is Attending? */

Other pages: [[Hackfest2016]], [[Hackfest2016 Topics]].

== Who is Attending? ==

{| class="wikitable" style="text-align: center;"
|+ List of Attendees
Hackfest
|-
! rowspan="2" | Who
! colspan="2" | Dates
! colspan="2" | Allocation
! colspan="2" | Arrival
! colspan="2" | Departure
! rowspan="2" | Hotel
|-
! Hackfest
! LGM
! Hackfest
! LGM
! Date/Time
! Detail
! Date/Time
! Detail
|-
| Alex Valavanis (host)
| 4/11, 4/12, 4/13
| -
| $2000
| -
| colspan="5" |
|-
| Tavmjong Bah
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| $2000
| $500
| 10th 5:31PM
| Eurostar + Train
| xx
| xx
| xx
|-
| Martin Owens
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| $2000
| $500
| 10th 7:25AM
| BOS -> LHR
| 25th 1:05PM
| LHR -> BOS
| xx
|-
| C R
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| colspan="2" | -
| xx
| xx
| xx
| xx
| xx
|-
| Marc Jeanmougin
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| $1000
| $500
| 10th 5:31PM
| Eurostar + Train
| 19th 4:31PM
| Eurostar
| Boundary Hotel then YHA StPancras
|-
| Sebastian Faubel
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| colspan="2" | -
| xx
| xx
| xx
| xx
| xx
|-
| Sebastian's colleague
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| colspan="2" | -
| xx
| xx
| xx
| xx
| xx
|-
| Jabier Arraiza
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| $2000
| $500
| xx
| xx
| xx
| xx
| xx
|-
| Krzysztof Kosiński
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| 1
| 1
| 10th 1:40PM
| BA286 SFO->LHR
| 19th 2:05PM
| BA287 LHR->SFO
| xx
|-
| the Adib
| -
| 4/15, 4/16, 4/17, 4/18
|
| $500
| xx
| xx
| xx
| xx
| xx
|-
| John Cliff
| -
| 4/15, 4/16, 4/17, 4/18
|
| $500
| xx
| xx
| xx
| xx
| xx
|-
! Total
!
!
! $9000
! $3000
!
!
!
|}

Venue (includes lunch and snacks): ~$1300.

1 Sponsored by outside organization.

Allocation for attending hackfest:
* Up to $2000 each for Inkscape developers who have contributed for 3+ years and > 200 commits.
* Up to $1500 each for Inkscape developers who have contributed for 2+ years and > 100 commits.
* Up to $1000 each for Inkscape developers who have contributed for 1+ year and > 50 commits.
* Up to $500 each for any Inkscape contributor listed in AUTHORS file with at least 10 commits by Jan 1, 2016.

Allocation for attending LGM (additional to allocation for hackfest):
* Up to $500 each for any Inkscape contributor listed in AUTHORS file by Jan 1, 2016.

If your are an active contributor to Inkscape but are NOT in the AUTHORS file (translator, documentor, etc.) we may still be able to provide some funding on a case-by-case basis.

== Travel ==

Attendees seeking reimbursement must follow [https://gitorious.org/conservancy/policies/raw/75b8894f8586503e5abd23bed84229bbe5c1b7ee:Travel/conservancy-travel-policy.txt SFC travel policy]. Most importantly, take a screen shot of your airfare search. Your ticket must be within $100 of the lowest fare. Keep receipts for transport and lodging. Meal cost and misc. expenses are handled by a per diem and don't require receipts.

=== Transport ===

Google Flights search is probably your best bet. kayak.com and mobissimo.com can also be useful.

There is a small airport in Leeds (Leeds-Bradford). http://www.justtheflight.co.uk/cheap-flights-from-LBA/

Manchester airport is 1.5 hours away (~$30, 50 min; ~$10 if booked several weeks in advance [http://www.thetrainline.com])

Trains between London (Kings Cross) and Leeds take a bit more than 2 hours. Book your ticket one month ahead to save 70%!

Trains between Paris and Leeds: $70 one way, 5 hours, booked far in advance.

Devenshire Hall is about 25 minutes by bus #1 (every 10 minutes) or a 40 minute walk from Leeds Train station.

=== Hotel ===

Check AirBnB. Often 1/3 the cost of a hotel room.

=== Venue ===

CONFIRMED

The hackfest will take place in Devenshire Hall at the University of Leeds. (Cumberland Road, Leeds, LS6 2EQ)

A map of the U. of Leeds campus can be found at http://www.meetinleeds.co.uk/map-of-venues

Note: Lunch and snacks will be provided.

== Reimbursements ==

After the event, forward your receipts (scans/pdf files/etc.) to me (Tavmjong). I'll collect them and forward them to the SFC. You need to also send payment information (name, currency, paypal account or bank information: see travel policy for more details).

Google Summer of Code

2016-03-17T06:33:11Z

Tweenk: /* P5. Better data structure for selections */

= Welcome to Inkscape! =

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

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

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

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

= Student Applications =

* Google program information:
** [https://summerofcode.withgoogle.com/ Home page].
** Summer of Code Application form. Applications open at 19:00 UTC on March 14th.

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

'''Student Applications for GSoC 2016 must be submitted to the GSoC site by 19:00 UTC on March 25th 2016.'''

= The "two patches" rule =

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

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

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

= Performance Evaluation =

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

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

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

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

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

= Suggested Project Ideas =

The following is a list of formal project suggestions, but do not feel limited to only these - some of our best contributions have been unique ideas that students had in mind from other sources!

See also [[Development Project Ideas]] and https://blueprints.launchpad.net/inkscape/

==P1. Better CSS Style Sheet Support==

Enhance Inkscape's support for CSS style sheets.

* Estimation of difficulty: Moderately hard
* Potential mentors: Tavmjong Bah
* Programming skills needed: C++
* Prerequisites: Experience with CSS style sheets.

Detailed Description

Currently Inkscape support of CSS style sheets is limited to the reading and parsing of one internal style sheet. The styles are immediately stored in the style attribute for each object thus changes to the style sheet (awkwardly possible now through the XML editor) are not recognized. This project will:

* Add to each object property a means to track the source of the property value.
* Create a dialog for editing internal style sheets. The dialog needs to:
** Support selectors based on object type, object id, and object class.
** Create selection sets based on the above selectors.
** Create and edit class names.

A dialog similar to (and perhaps merged with) the trunk Selection Set dialog might be a good model to follow.

Stretch goals include:

* Support external style sheets.
* Support multiple internal style sheets.
* Support CSS 3 selectors.
* Support parsing of 'font-face'.

Use Cases

* Support externally created SVGs.
* Producing better SVGs for the Web.
* Changing style on multiple objects at once (palettes).

Related Material

* [https://www.w3.org/TR/CSS2/ CSS 2 Specification]
* [https://www.w3.org/TR/css-2015/ CSS 2015 Snapshot]

==P2. Development Project Management System==

Enhance Inkscape's web tools for managing development projects.

* Estimation of difficulty: Moderately hard
* Potential mentors: Bryce Harrington
* Programming skills needed: Python
* Prerequisites: Working knowledge of Django web application development

Detailed Description

Design and implement tools to allow submitting and editing ideas for development projects. Create various project listing views that display projects that need further editing, lists of projects meeting various criteria (e.g. janitorial, new features, programming language, etc.), assigned projects, completed projects, and so forth.

This work would be part of a larger, ongoing effort to unify Inkscape's various collections of task ideas into a single system, to make them easier for potential contributors to review and select from. Some of this project has already been implemented, so you would be focusing on enhancing its user interfaces to make it more powerful and more broadly usable.

Use Cases
* "Janitorial" tasks suitable for new developers looking for easy ways to get involved in Inkscape development
* Google Summer of Code Project Ideas (this page!!)
* Funded development work, with funds supplied by various fundraisers
* User-supplied requests for feature enhancements

Related Material
* Current collections of tasks that we want to eventually migrate into this system:
** http://wiki.inkscape.org/wiki/index.php/Janitorial_tasks
** https://blueprints.launchpad.net/inkscape/
* [https://inkscape.org/en/support-us/funded-development/ High level specification for the system]
* [[FundedProjectSystemDevelopment]] related tasks

==P3. Slice toolbar items==
[[File:Cuttool.png|200px|thumb|right|Example of result of the cut/eraser tool]]
* Estimation of difficulty: Moderately hard
* Potential mentors: Jabier Arraiza (Spanish, some English)
* Programming skills needed: C++

Detailed Description
The goal is a toolbar item, called "slice" to slice items in a easy way.
We check to convert strokes to path previously to cut, to avoid continuing with stroke thought cut-out item fills. 
Maybe positioned in the path menu after bool operations, the selected items are sliced from topmost path, converting strokes to paths, duplicating fills and maybe apply to groups (there is some work in groups boolops from Martin Owens). 
A lot of helper code is done yet in flatten branch (Alexander Brock lp:~inkscape+alexander/inkscape/flatten). 
There are new Boolean operations, implemented but not used in trunk. We need to switch the division and flatten branch methods from Livarot to these new operations. 
Another feature interesting is a second toolbar item "slice from guides" to get the guides over the selected item and use it as cut-out. 

Use Cases
* Better item slicing.

==P4. SVG 2 Text Support==

* Estimation of difficulty: Hard
* Potential mentors: Tavmjong Bah
* Programming skills needed: C++
* Prerequisites: Familiarity with text layout. Knowledge of CSS.

Detailed Description

Inkscape currently has a non-compliant flowed text feature (based on SVG 1.2 which was never adopted) that needs to be made compatible with both SVG2 and SVG 1.1. This project is to re-implement the flowed text feature within Inkscape to be SVG2 compliant and to have a proper SVG 1.1 fallback. In addition to the flowed text itself as it exists within Inkscape, SVG2 adds new formatting features including shape-margin and shape-padding, shape-inside and shape-outside, exclusions, additional white-space control settings, pre-wrap, pre-line, etc.

Use Cases
* Proper text flow into rectangles and other shapes.

Related Material
* [https://svgwg.org/svg2-draft/text.html Current draft of SVG 2 text specification.]

==P5. Better data structure for selections==

* Estimation of difficulty: Medium
* Potential mentors: Krzysztof Kosiński (Polish, English)
* Programming skills needed: C++
* Prerequisites: Familiarity with STL and/or Boost, knowledge of basic data structures and their performance properties, some knowledge of glib a plus.

Detailed Description

Many useful functions in Inkscape, such as grouping, Boolean operations, etc., work on a selection. However, there is only one selection object per window, and its state is shown in the user interface. It would be useful to have an object type that represents the same concept, but not tied to the user interface.

This project would involve implementing an <code>Inkscape::ObjectSet</code> object that would serve as a base for <code>Inkscape::Selection</code>. The internal data structure should support fast lookup (checking whether a given object belongs to the set) and preserve the order of insertion (so that we can still determine which object was selected first or last). Internally, <code>ObjectSet</code> can be based on a Boost multi-index container with a list index and a hash index.

Related Material
* [http://www.boost.org/doc/libs/1_60_0/libs/multi_index/doc/index.html Boost Multi-Index Containers Documentation]

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

[[Category:Developer Documentation]]

Hackfest2016

2016-03-09T04:49:13Z

Tweenk:

This page details the planning of Inkscape's 2016 hackfest.

Other pages: [[Hackfest2016 Topics]], [[Hackfest2016 Attendees]]. Old: [[Hackfest2016 Location]], [[Hackfest2015]].

==Description==

A hackfest! We will work on Inkscape bugs, new features, and packaging as well as website issues; in fact anything that can benefit from developers and users being physically in the same space.

==Date==

April 11th through 13th just before the [http://libregraphicsmeeting.org/2016/ Libre Graphics meeting] (April 15th-18th).

==Venue==

The hackfest will take place in Devonshire Hall at the University of Leeds. (Cumberland Road, Leeds, LS6 2EQ)

A map of the U. of Leeds campus can be found at http://www.meetinleeds.co.uk/map-of-venues

==Attendance==

Anybody interested in Inkscape is welcome to attend. Funding is available for travel expenses based on past contributions to Inkscape. See the [[Hackfest2016 Attendees]] page for more details.

==Schedule==

A schedule will be developed based on input from attendees and the Inkscape community. See the [[Hackfest2016 Topics]] page for further details.

Working with Git

2016-03-05T17:03:17Z

Tweenk: /* Differences from Bazaar */

This page contains an introduction to the Git distributed version control system. For now, it is mainly useful to Bazaar users, but will be updated with general Git information over time.

==Cheat sheet for Bazaar users==

{| class="wikitable"
!Bazaar command
!Git command
|-
| class="mw-code" |bzr branch ''branch-url''
| class="mw-code" |git clone ''repository-url'' ''directory'' cd ''directory'' git checkout ''branch-name''
|-
| class="mw-code" |bzr checkout lp:project-name
| not supported
|-
| class="mw-code" |bzr update
| not supported
|-
| class="mw-code" |bzr pull
| class="mw-code" |git pull
|-
| class="mw-code" |bzr add ''file''
| class="mw-code" |git add ''file''
|-
| class="mw-code" |bzr diff
| class="mw-code" |git diff HEAD
|-
| class="mw-code" |bzr revert
| class="mw-code" |git reset --hard
|-
| class="mw-code" |bzr revert ''file'' -r ''revision''
| class="mw-code" |git checkout ''commit'' -- ''file''
|-
| class="mw-code" |bzr uncommit
| class="mw-code" |git reset HEAD^
|-
| class="mw-code" |bzr uncommit ...some changes... bzr commit
| class="mw-code" |...some changes... git commit -a --amend
|-
| class="mw-code" |bzr push ''location''
| class="mw-code" |git remote add ''remote-name'' ''location'' git push ''remote-name'' ''branch-name''
|-
| class="mw-code" |bzr commit
| class="mw-code" |git commit -a
|-
| class="mw-code" |bzr log -c 10
| class="mw-code" |git log -n 10
|-
| class="mw-code" |bzr switch ''branch-url''
| class="mw-code" |git checkout ''branch-name''
|-
| class="mw-code" |bzr switch -b ''branch-url''
| class="mw-code" |git checkout -b ''branch-name''
|-
| class="mw-code" |bzr merge ''branch-url''
| class="mw-code" |git merge ''branch-name''
|-
| class="mw-code" |bzr shelve --all
| class="mw-code" |git stash
|-
| class="mw-code" |bzr unshelve ''change-id''
| class="mw-code" |git stash pop
|}

===Differences from Bazaar===

Here are the most important differences between Bazaar and Git:
* Bazaar revisions are identified by sequential numbers. Git revisions (called commits in the documentation) are identified by cryptographic hashes which are strings of 40 hexadecimal numbers, though it is possible to also refer to them by a sequential number since the last tag (see <code>git describe</code>).
* Bazaar is branch-oriented, while Git is repository- and commit-oriented. Repositories in Bazaar are storage locations for potentially multiple branches. Repositories in Git are collections of commits, and branches are just pointers to particular commits that are updated after each <code>git commit</code> command. Cloning a Git repository by default retrieves all of its commits and branches.
* In Bazaar, you conceptually submit your work to only one place - the push branch. You can change this place at any time, but Bazaar remembers only one value for you. In Git, you can configure many remote repositories and work with code from multiple sources using a single working tree.
* By default, each branch in Bazaar has a separate working tree, while all branches in the same Git repository share the same working tree. It's possible to make Bazaar work in the latter mode as well, but it's not very well supported.

In Bazaar, if you want to try out someone else's code, you need to create a new checkout of their branch or use <code>bzr switch</code>. In Git, what you do depends on where the code is located.
* If the code to try out is in a branch in the project's main repository, you update the repository (<code>git fetch</code>) and then check out the branch (<code>git checkout origin/branch-to-try-out</code>). This creates a local branch called <code>branch-to-try-out</code>. (You can use a different name as well.)
* If the code is in a different repository, you first add it as a remote repository with <code>git remote add ''remote-name'' ''repository-url''</code>, fetch it with <code>git fetch ''remote-name''</code> and check out the relevant branch with <code>git checkout ''remote-name''/''branch-to-try-out''</code>.

Another difference is that in Git, you cannot directly make changes to remote branches - you must to use <code>git push</code> and <code>git pull</code>. Therefore, the Subversion-like checkout mode known from Bazaar is unsupported.

Working with Git

2016-03-05T17:00:20Z

Tweenk: /* Differences from Bazaar */

This page contains an introduction to the Git distributed version control system. For now, it is mainly useful to Bazaar users, but will be updated with general Git information over time.

==Cheat sheet for Bazaar users==

{| class="wikitable"
!Bazaar command
!Git command
|-
| class="mw-code" |bzr branch ''branch-url''
| class="mw-code" |git clone ''repository-url'' ''directory'' cd ''directory'' git checkout ''branch-name''
|-
| class="mw-code" |bzr checkout lp:project-name
| not supported
|-
| class="mw-code" |bzr update
| not supported
|-
| class="mw-code" |bzr pull
| class="mw-code" |git pull
|-
| class="mw-code" |bzr add ''file''
| class="mw-code" |git add ''file''
|-
| class="mw-code" |bzr diff
| class="mw-code" |git diff HEAD
|-
| class="mw-code" |bzr revert
| class="mw-code" |git reset --hard
|-
| class="mw-code" |bzr revert ''file'' -r ''revision''
| class="mw-code" |git checkout ''commit'' -- ''file''
|-
| class="mw-code" |bzr uncommit
| class="mw-code" |git reset HEAD^
|-
| class="mw-code" |bzr uncommit ...some changes... bzr commit
| class="mw-code" |...some changes... git commit -a --amend
|-
| class="mw-code" |bzr push ''location''
| class="mw-code" |git remote add ''remote-name'' ''location'' git push ''remote-name'' ''branch-name''
|-
| class="mw-code" |bzr commit
| class="mw-code" |git commit -a
|-
| class="mw-code" |bzr log -c 10
| class="mw-code" |git log -n 10
|-
| class="mw-code" |bzr switch ''branch-url''
| class="mw-code" |git checkout ''branch-name''
|-
| class="mw-code" |bzr switch -b ''branch-url''
| class="mw-code" |git checkout -b ''branch-name''
|-
| class="mw-code" |bzr merge ''branch-url''
| class="mw-code" |git merge ''branch-name''
|-
| class="mw-code" |bzr shelve --all
| class="mw-code" |git stash
|-
| class="mw-code" |bzr unshelve ''change-id''
| class="mw-code" |git stash pop
|}

===Differences from Bazaar===

Here are the most important differences between Bazaar and Git:
* Bazaar revisions are identified by sequential numbers. Git revisions (called commits in the documentation) are identified by cryptographic hashes which are strings of 40 hexadecimal numbers, though it is possible to also refer to them by a sequential number since the last tag (see <code>git describe</code>).
* Bazaar is branch-oriented, while Git is repository- and commit-oriented. Repositories in Git are collections of commits, and branches are just pointers to particular commits that are updated after each <code>git commit</code> command.
* In Bazaar, you conceptually submit your work to only one place - the push branch. You can change this place at any time, but Bazaar remembers only one value for you. In Git, you can configure many remote repositories and work with code from multiple sources using a single working tree.
* By default, each branch in Bazaar has a separate working tree, while all branches in the same Git repository share the same working tree. It's possible to make Bazaar work in the latter mode as well, but it's not very well supported.

In Bazaar, if you want to try out someone else's code, you need to create a new checkout of their branch or use <code>bzr switch</code>. In Git, what you do depends on where the code is located.
* If the code to try out is in a branch in the project's main repository, you update the repository (<code>git fetch</code>) and then check out the branch (<code>git checkout origin/branch-to-try-out</code>). This creates a local branch called <code>branch-to-try-out</code>. (You can use a different name as well.)
* If the code is in a different repository, you first add it as a remote repository with <code>git remote add ''remote-name'' ''repository-url''</code>, fetch it with <code>git fetch ''remote-name''</code> and check out the relevant branch with <code>git checkout ''remote-name''/''branch-to-try-out''</code>.

Another difference is that in Git, you cannot directly make changes to remote branches - you must to use <code>git push</code> and <code>git pull</code>. Therefore, the Subversion-like checkout mode known from Bazaar is unsupported.

Working with Git

2016-03-05T16:52:28Z

Tweenk: /* Cheat sheet for Bazaar users */

This page contains an introduction to the Git distributed version control system. For now, it is mainly useful to Bazaar users, but will be updated with general Git information over time.

==Cheat sheet for Bazaar users==

{| class="wikitable"
!Bazaar command
!Git command
|-
| class="mw-code" |bzr branch ''branch-url''
| class="mw-code" |git clone ''repository-url'' ''directory'' cd ''directory'' git checkout ''branch-name''
|-
| class="mw-code" |bzr checkout lp:project-name
| not supported
|-
| class="mw-code" |bzr update
| not supported
|-
| class="mw-code" |bzr pull
| class="mw-code" |git pull
|-
| class="mw-code" |bzr add ''file''
| class="mw-code" |git add ''file''
|-
| class="mw-code" |bzr diff
| class="mw-code" |git diff HEAD
|-
| class="mw-code" |bzr revert
| class="mw-code" |git reset --hard
|-
| class="mw-code" |bzr revert ''file'' -r ''revision''
| class="mw-code" |git checkout ''commit'' -- ''file''
|-
| class="mw-code" |bzr uncommit
| class="mw-code" |git reset HEAD^
|-
| class="mw-code" |bzr uncommit ...some changes... bzr commit
| class="mw-code" |...some changes... git commit -a --amend
|-
| class="mw-code" |bzr push ''location''
| class="mw-code" |git remote add ''remote-name'' ''location'' git push ''remote-name'' ''branch-name''
|-
| class="mw-code" |bzr commit
| class="mw-code" |git commit -a
|-
| class="mw-code" |bzr log -c 10
| class="mw-code" |git log -n 10
|-
| class="mw-code" |bzr switch ''branch-url''
| class="mw-code" |git checkout ''branch-name''
|-
| class="mw-code" |bzr switch -b ''branch-url''
| class="mw-code" |git checkout -b ''branch-name''
|-
| class="mw-code" |bzr merge ''branch-url''
| class="mw-code" |git merge ''branch-name''
|-
| class="mw-code" |bzr shelve --all
| class="mw-code" |git stash
|-
| class="mw-code" |bzr unshelve ''change-id''
| class="mw-code" |git stash pop
|}

===Differences from Bazaar===

Here are the most important differences between Bazaar and Git:
* Bazaar revisions are identified by sequential numbers. Git revisions (called commits in the documentation) are identified by cryptographic hashes which are strings of 40 hexadecimal numbers, though it is possible to also refer to them by a sequential number since the last tag (see <code>git describe</code>).
* Bazaar is branch-oriented, while Git is repository-oriented. A repository is a collection of branches.
* In Bazaar, you conceptually submit your work to only one place - the push branch. You can change this place at any time, but Bazaar remembers only one value for you. In Git, you can configure many remote repositories and work with code from multiple sources using a single working tree.
* By default, each branch in Bazaar has a separate working tree, while all branches in the same Git repository share the same working tree. It's possible to make Bazaar work in the latter mode as well, but it's not very well supported.

In Bazaar, if you want to try out someone else's code, you need to create a new checkout of their branch or use <code>bzr switch</code>. In Git, what you do depends on where the code is located.
* If the code to try out is in a branch in the project's main repository, you update the repository (<code>git fetch</code>) and then check out the branch (<code>git checkout origin/branch-to-try-out</code>). This creates a local branch called <code>branch-to-try-out</code>. (You can use a different name as well.)
* If the code is in a different repository, you first add it as a remote repository with <code>git remote add ''remote-name'' ''repository-url''</code>, fetch it with <code>git fetch ''remote-name''</code> and check out the relevant branch with <code>git checkout ''remote-name''/''branch-to-try-out''</code>.

Another difference is that in Git, you cannot directly make changes to remote branches - you must to use <code>git push</code> and <code>git pull</code>. Therefore, the Subversion-like checkout mode known from Bazaar is unsupported.

Working with Git

2016-03-05T16:46:02Z

Tweenk:

This page contains an introduction to the Git distributed version control system. For now, it is mainly useful to Bazaar users, but will be updated with general Git information over time.

==Cheat sheet for Bazaar users==

{| class="wikitable"
!Bazaar command
!Git command
|-
| class="mw-code" |bzr branch ''branch-url''
| class="mw-code" |git clone ''repository-url'' ''directory'' cd ''directory'' git checkout ''branch-name''
|-
| class="mw-code" |bzr checkout lp:project-name
| not supported
|-
| class="mw-code" |bzr update
| not supported
|-
| class="mw-code" |bzr pull
| class="mw-code" |git pull
|-
| class="mw-code" |bzr add ''file''
| class="mw-code" |git add ''file''
|-
| class="mw-code" |bzr diff
| class="mw-code" |git diff HEAD
|-
| class="mw-code" |bzr revert
| class="mw-code" |git reset --hard
|-
| class="mw-code" |bzr revert ''file'' -r ''revision''
| class="mw-code" |git checkout ''commit'' -- ''file''
|-
| class="mw-code" |bzr uncommit ...some changes... bzr commit
| class="mw-code" |...some changes... git commit -a --amend
|-
| class="mw-code" |bzr push ''location''
| class="mw-code" |git remote add ''remote-name'' ''location'' git push ''remote-name'' ''branch-name''
|-
| class="mw-code" |bzr commit
| class="mw-code" |git commit -a
|-
| class="mw-code" |bzr log -c 10
| class="mw-code" |git log -n 10
|-
| class="mw-code" |bzr switch ''branch-url''
| class="mw-code" |git checkout ''branch-name''
|-
| class="mw-code" |bzr switch -b ''branch-url''
| class="mw-code" |git checkout -b ''branch-name''
|-
| class="mw-code" |bzr merge ''branch-url''
| class="mw-code" |git merge ''branch-name''
|-
| class="mw-code" |bzr shelve --all
| class="mw-code" |git stash
|-
| class="mw-code" |bzr unshelve ''change-id''
| class="mw-code" |git stash pop
|}

===Differences from Bazaar===

Here are the most important differences between Bazaar and Git:
* Bazaar revisions are identified by sequential numbers. Git revisions (called commits in the documentation) are identified by cryptographic hashes which are strings of 40 hexadecimal numbers, though it is possible to also refer to them by a sequential number since the last tag (see <code>git describe</code>).
* Bazaar is branch-oriented, while Git is repository-oriented. A repository is a collection of branches.
* In Bazaar, you conceptually submit your work to only one place - the push branch. You can change this place at any time, but Bazaar remembers only one value for you. In Git, you can configure many remote repositories and work with code from multiple sources using a single working tree.
* By default, each branch in Bazaar has a separate working tree, while all branches in the same Git repository share the same working tree. It's possible to make Bazaar work in the latter mode as well, but it's not very well supported.

In Bazaar, if you want to try out someone else's code, you need to create a new checkout of their branch or use <code>bzr switch</code>. In Git, what you do depends on where the code is located.
* If the code to try out is in a branch in the project's main repository, you update the repository (<code>git fetch</code>) and then check out the branch (<code>git checkout origin/branch-to-try-out</code>). This creates a local branch called <code>branch-to-try-out</code>. (You can use a different name as well.)
* If the code is in a different repository, you first add it as a remote repository with <code>git remote add ''remote-name'' ''repository-url''</code>, fetch it with <code>git fetch ''remote-name''</code> and check out the relevant branch with <code>git checkout ''remote-name''/''branch-to-try-out''</code>.

Another difference is that in Git, you cannot directly make changes to remote branches - you must to use <code>git push</code> and <code>git pull</code>. Therefore, the Subversion-like checkout mode known from Bazaar is unsupported.

Working with Git

2016-03-05T16:45:22Z

Tweenk: Created page with "This page contains an introduction to the Git distributed version control system. It focuses on the use of Git to develop Inkscape and lib2geom, but should be useful to all wo..."

This page contains an introduction to the Git distributed version control system. It focuses on the use of Git to develop Inkscape and lib2geom, but should be useful to all would-be users of Git.

==Cheat sheet for Bazaar users==

{| class="wikitable"
!Bazaar command
!Git command
|-
| class="mw-code" |bzr branch ''branch-url''
| class="mw-code" |git clone ''repository-url'' ''directory'' cd ''directory'' git checkout ''branch-name''
|-
| class="mw-code" |bzr checkout lp:project-name
| not supported
|-
| class="mw-code" |bzr update
| not supported
|-
| class="mw-code" |bzr pull
| class="mw-code" |git pull
|-
| class="mw-code" |bzr add ''file''
| class="mw-code" |git add ''file''
|-
| class="mw-code" |bzr diff
| class="mw-code" |git diff HEAD
|-
| class="mw-code" |bzr revert
| class="mw-code" |git reset --hard
|-
| class="mw-code" |bzr revert ''file'' -r ''revision''
| class="mw-code" |git checkout ''commit'' -- ''file''
|-
| class="mw-code" |bzr uncommit ...some changes... bzr commit
| class="mw-code" |...some changes... git commit -a --amend
|-
| class="mw-code" |bzr push ''location''
| class="mw-code" |git remote add ''remote-name'' ''location'' git push ''remote-name'' ''branch-name''
|-
| class="mw-code" |bzr commit
| class="mw-code" |git commit -a
|-
| class="mw-code" |bzr log -c 10
| class="mw-code" |git log -n 10
|-
| class="mw-code" |bzr switch ''branch-url''
| class="mw-code" |git checkout ''branch-name''
|-
| class="mw-code" |bzr switch -b ''branch-url''
| class="mw-code" |git checkout -b ''branch-name''
|-
| class="mw-code" |bzr merge ''branch-url''
| class="mw-code" |git merge ''branch-name''
|-
| class="mw-code" |bzr shelve --all
| class="mw-code" |git stash
|-
| class="mw-code" |bzr unshelve ''change-id''
| class="mw-code" |git stash pop
|}

===Differences from Bazaar===

Here are the most important differences between Bazaar and Git:
* Bazaar revisions are identified by sequential numbers. Git revisions (called commits in the documentation) are identified by cryptographic hashes which are strings of 40 hexadecimal numbers, though it is possible to also refer to them by a sequential number since the last tag (see <code>git describe</code>).
* Bazaar is branch-oriented, while Git is repository-oriented. A repository is a collection of branches.
* In Bazaar, you conceptually submit your work to only one place - the push branch. You can change this place at any time, but Bazaar remembers only one value for you. In Git, you can configure many remote repositories and work with code from multiple sources using a single working tree.
* By default, each branch in Bazaar has a separate working tree, while all branches in the same Git repository share the same working tree. It's possible to make Bazaar work in the latter mode as well, but it's not very well supported.

In Bazaar, if you want to try out someone else's code, you need to create a new checkout of their branch or use <code>bzr switch</code>. In Git, what you do depends on where the code is located.
* If the code to try out is in a branch in the project's main repository, you update the repository (<code>git fetch</code>) and then check out the branch (<code>git checkout origin/branch-to-try-out</code>). This creates a local branch called <code>branch-to-try-out</code>. (You can use a different name as well.)
* If the code is in a different repository, you first add it as a remote repository with <code>git remote add ''remote-name'' ''repository-url''</code>, fetch it with <code>git fetch ''remote-name''</code> and check out the relevant branch with <code>git checkout ''remote-name''/''branch-to-try-out''</code>.

Another difference is that in Git, you cannot directly make changes to remote branches - you must to use <code>git push</code> and <code>git pull</code>. Therefore, the Subversion-like checkout mode known from Bazaar is unsupported.

Inkscape

2016-03-05T16:01:00Z

Tweenk: /* Developer Documentation */

{{Main_Page/Localized_versions}}

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

{| cellspacing="11" style="width:100%;"
|-style="vertical-align:top;"
| style="width:33%;background-color: #E6E6E6; padding:.5em;"|
=== Project Info ===
* [http://www.inkscape.org/ Inkscape Homepage]
* [[About Inkscape]]
* [[Features of Inkscape|Features]]
* [[FAQ]] - Frequently Asked Questions
* [[Supported operating systems]]
* [[Tools]] - Supporting Tools and Applications
* [[Galleries]]
* [[Inkscape coverage|Coverage]] - Awards, articles, presentations, books about Inkscape
* [[Inkscape popularity|Popularity]]
* [[InkscapeInvariants|Inkscape's Mission]]
* [[CommunicationChannels|Communication Channels]]: how to reach us
* [[AnnouncementToSodipodi|Announcement To Sodipodi]]: this started it all
* [[Branding]]
* [[Travel Reimbursement Policy]]
* [[FundedProjectSystemDevelopment|Funded Project System Development]]

|style="width:33%;;background-color: white; padding:.5em;"|

=== User Documentation ===
* [[Installing Inkscape|Installation]]
* [[International and Local Communities]]
* [[Inkscape glossary]]
* [[User manual information]] - where to find the free Inkscape manual and how to contribute to it
* [http://inkscape.org/en/learn/tutorials/ Tutorials]
* [[Inkscape SVG vs. plain SVG]]
* [[Output format requirements]] - what's needed to save in some formats
* [[Effect requirements]] - what's needed to use some effects
* [[Effect reference]] - what each effect does
* [[Connector tool tutorial]]
* [[Installing fonts]]
* [[Emergency save]] - recovery in case Inkscape crashed
* [[Release notes]]
** '''for version [[Release notes/0.92|0.92]] (active development)'''
** '''for version [[Release notes/0.91|0.91]] (current release)'''
** older versions: [[Release notes/0.48.5|0.48.5]] [[Release notes/0.48.4|0.48.4]] [[Release notes/0.48.3|0.48.3]], [[Release notes/0.48.2|0.48.2]], [[Release notes/0.48.1|0.48.1]], [[Release notes/0.48|0.48]], [[Release notes/0.47|0.47]]
* [[Announcing Releases]]
* [[Tricks and tips]] - miscellaneous advice, may be slightly outdated

|style="width:33%;background-color: #E6E6E6; padding:.5em;"|

=== Help Inkscape Without Coding ===
* [[Bug management]]
* [[Testing]]
* [[Translation information]]
* [[WebSite]]
* [[Inkscape Classes]]
* [[Conferences]]
* [[Fundraising Ideas]]

* [[HelpWanted]]
* [[BugTriageProjects]]
* [[CreatingDists]]: how to build packages
* [[StableBranchUpdates]]
* [[UpdatingTrackerItems]]
* [[TutorialsAndHelp]]
* [[How_To_Start_A_Page]] how to use the wiki
* [[CreatingScreencasts]]
* [[AboutScreenContest]]
|}

{| cellspacing="0" style="width: 100%; background-color: white; border-width:1px; border-style:solid; border-color:#62C012; align:left; padding:11px 0em 0em 11px;"
|- style="vertical-align:top;"
| colspan="2"|

=== Developer Documentation ===
|- style="vertical-align:top;"
| style="width:50%;|
==== First Steps ====
* [[Working with Bazaar]] - How to obtain the source code. A quick start on how to use our version control system
* [[Working with Git]]
* [[Compiling Inkscape|Compilation]]
* [[Compiling Inkscape on Windows]]
* [[Using Eclipse]] - Debug Inkscape on Windows using Eclipse (outdated)
* [[Using Visual Studio]] - Debug Inkscape on Windows using Microsoft Visual Studio
* [[Developer manual]] - various important information, be sure to read this before coding
* [[Debugging Inkscape|Debugging]] - random tips to help debug problems
* [[Project organization]] - procedures, hierarchy, developer roles and the likes
* [[Janitorial tasks]] - small tasks that need doing
* [[Doxygen documentation]]
* [[Working with SVN]] - besides the code in Bazaar, we still have some things in SVN.
* [[Working with CMake]] - Getting started with cmake coding for configuring and building Inkscape

==== Developer tutorials ====
* [[Architectural overview]] - a high-level look at Inkscape
* [[Preferences subsystem]] - creating and using preference values
* XML subsystem (WIP) - how to manipulate the XML representation of a document
* Display subsystem (WIP) - how to make things appear on the canvas
* Tools subsystem (WIP) - how to create a new tool
* [[Creating a new SPObject]]
* Extensions
** [[Extension subsystem]] - an overview of the functionality provided by extensions and the possible implementations
** [[Script extensions]]
** [[Python modules for extensions]] - some helpful routines for use in Python script extensions
* [[Creating Live Path Effects]]
* [[Boost shared pointers]]
* [[Using libsigc++ signals]]
* [[Windows development on Linux]]

==== Miscellaneous ====
* [[INX extension descriptor format]]
* [[Inkscape-specific XML attributes]] - documentation of attributes from Inkscape's XML namespace

* [[Extension repository]]: an Internet central for Inkscape Extensions
* [[Related programs]]

| style="width:50%;|
==== Continuous Integration (Automated testing) ====
* [http://jenkins.inkscape.org Our main testing website (Jenkins)]
* [[How to contribute to automated tests]]
* [[Jenkins server setup]]

==== Development Discussion ====
* [[Roadmap]]: the main todo list
* [[Dependencies]] - what libs are needed to build Inkscape
* [[C++11]] - What C++11 features can be used
* [[NewFeatureProposals]]
* [[ExtensionArchitectureProposals]]
* [[Coding Style|Coding Style Discussion]]
* [[FileTypes]]
* [[ApplicationIcons]] (Application + Interface)
* [[Icons]]
* [[InkscapeColor]]
* [[PrintingSubsystem]]
* [[SVG Tiny Compliance]]
* [[SVG Test Suite Compliance]] - [[W3C]] full test suite
* [[CSS Support]]
* [[Google Summer Of Code]]
* [[Improved Media Management]]
* [[UI MockupScreenshots]]
* [[Swatch Book]]
* [[Tablet Dialog]]
* [[ViewBoxToDo]] View box support info
* [[Caching]]
* [[UI and Document coordinates‎]]
* [[Mipmapping]]
* [[GtkMMification]]: replace C boilerplate with gtkmm objects
* [[CMake Tasks]]: Converting the Inkscape build system to CMake

===Lib2Geom===
*[[lib2geom]]
*[[lib2geom Goals]]
*[[lib2geom FAQ]]
*[[lib2geom SVN Repository Guide]]
*[[WorkingWith2GeomFAQ]]: real-life questions answered about using 2Geom in real code
*[[lib2geom py2geom]]: python bindings to 2geom. With this you can use the power of 2geom in python scripts.

|- style="vertical-align:top;"
| style="width:50%;|
==== User Interface Discussion ====
* [[Translation_information]]
* [[AddingInterfaceVerbs]]
* [[AccessibleGraphics]]
* [[ObjectManager]]
* [[DialogsReorganization]]
* [[ModalInterfaces]]
* [[TextUsability]]: text tool /dialog dialog
* [[KeyboardShortcutsToDo]]
** [[KeyboardProfiles]]: how you can help
* [[StatusbarAPI]]
* [[Animation-(Timeline)]]
* [[Free Desktop Graphic Suite]]

| style="width:50%; |
|}

* [[WikiAttic]]: pages that are no longer relevant but kept for historical value

__NOTOC__

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

Hackfest2016 Attendees

2016-03-05T15:39:17Z

Tweenk: /* Who is Attending? */

== Who is Attending? ==

{| class="wikitable"
|+ List of Attendees
Hackfest
|-
! rowspan="2" | Who
! colspan="2" | Dates
! colspan="2" | Allocation
! colspan="2" | Flights/Train
! rowspan="2" | Hotel
|-
! Hackfest
! LGM
! Hackfest
! LGM
! Arrival
! Departure
|-
| Tavmjong Bah
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| $2000
| $500
| xx
| xx
| xx
|-
| Martin Owens
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| $2000
| $500
| 7:25AM April 10th BOS -> LHR
| 1:05PM April 25th LHR -> BOS
| xx
|-
| C R
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| TBD
| TBD
| xx
| xx
| xx
|-
| Alex Valavanis (host)
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| $2000
| $500
| xx
| xx
| xx
|-
| Marc Jeanmougin
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| $1000
| $500
| xx
| xx
| xx
|-
| Sebastian Faubel
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| TBD
| TBD
| xx
| xx
| xx
|-
| Sebastian's colleague
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| TBD
| TBD
| xx
| xx
| xx
|-
| Jabier Arraiza
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| $2000
| $500
| xx
| xx
| xx
|-
| Krzysztof Kosiński
| 4/11, 4/12, 4/13
| 4/15, 4/16, 4/17, 4/18
| 1
| 1
| 2
| 2
| 1
|-
| the Adib
| -
| 4/15, 4/16, 4/17, 4/18
| NA
| $500
| xx
| xx
| xx
|-
| John Cliff
| -
| 4/15, 4/16, 4/17, 4/18
| NA
| $500
| xx
| xx
| xx
|-
! Total
!
!
! $TBD
! $TBD
!
!
!
|}

TBD: To Be Determined -> need to verify commits/years of activity.

1 Sponsored by outside organization.
2 Flight sponsored by outside organization.

Allocation for attending hackfest:
* Up to $2000 each for Inkscape developers who have contributed for 3+ years and > 200 commits.
* Up to $1500 each for Inkscape developers who have contributed for 2+ years and > 100 commits.
* Up to $1000 each for Inkscape developers who have contributed for 1+ year and > 50 commits.
* Up to $500 each for any Inkscape contributor listed in AUTHORS file with at least 10 commits by Jan 1, 2016.

Allocation for attending LGM (additional to allocation for hackfest):
* Up to $500 each for any Inkscape contributor listed in AUTHORS file by Jan 1, 2016.

If your are an active contributor to Inkscape but are NOT in the AUTHORS file (translator, documentor, etc.) we may still be able to provide some funding on a case-by-case basis.

== Travel ==

Attendees seeking reimbursement must follow [https://gitorious.org/conservancy/policies/raw/75b8894f8586503e5abd23bed84229bbe5c1b7ee:Travel/conservancy-travel-policy.txt SFC travel policy]. Most importantly, take a screen shot of your airfare search. Your ticket must be within $100 of the lowest fare. Keep receipts for transport and lodging. Meal cost and misc. expenses are handled by a per diem and don't require receipts.

=== Transport ===

Google Flights search is probably your best bet. kayak.com and mobissimo.com can also be useful.

There is a small airport in Leeds (Leeds-Bradford). http://www.justtheflight.co.uk/cheap-flights-from-LBA/

Manchester airport is 1.5 hours away (~$30, 50 min; ~$10 if booked several weeks in advance [http://www.thetrainline.com])

Trains between London (Kings Cross) and Leeds take a bit more than 2 hours. Book your ticket one month ahead to save 70%!

Trains between Paris and Leeds: $70 one way, 5 hours, booked far in advance.

Devenshire Hall is about 25 minutes by bus #1 (every 10 minutes) or a 40 minute walk from Leeds Train station.

=== Hotel ===

Check AirBnB. Often 1/3 the cost of a hotel room.

=== Venue ===

TENTATIVE

The hackfest will take place in Devenshire Hall at the University of Leeds. (Cumberland Road, Leeds, LS6 2EQ)

A map of the U. of Leeds campus can be found at http://www.meetinleeds.co.uk/map-of-venues

== Reimbursements ==

After the event, forward your receipts (scans/pdf files/etc.) to me (Tavmjong). I'll collect them and forward them to the SFC. You need to also send payment information (name, currency, paypal account or bank information: see travel policy for more details).

Google Summer of Code

2016-02-05T05:31:09Z

Tweenk: /* P5. Better data structure for selections */

= Welcome to Inkscape! =

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

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

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

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

= Student Applications =

* Google program information:
** [https://www.google-melange.com/gsoc/homepage/google/gsoc2014 Home page].
** Summer of Code Application form. Applications open at 19:00 UTC on March 10th.

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

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

= The "two patches" rule =

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

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

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

= Performance Evaluation =

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

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

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

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

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

= Suggested Project Ideas =

The following is a list of formal project suggestions, but do not feel limited to only these - some of our best contributions have been unique ideas that students had in mind from other sources!

See also [[Development Project Ideas]] and https://blueprints.launchpad.net/inkscape/

==P1. Better CSS Style Sheet Support==

Enhance Inkscape's support for CSS style sheets.

* Estimation of difficulty: Moderately hard
* Potential mentors: Tavmjong Bah
* Programming skills needed: C++
* Prerequisites: Experience with CSS style sheets.

Detailed Description

Currently Inkscape support of CSS style sheets is limited to the reading and parsing of one internal style sheet. The styles are immediately stored in the style attribute for each object thus changes to the style sheet (awkwardly possible now through the XML editor) are not recognized. This project will:

* Add to each object property a means to track the source of the property value.
* Create a dialog for editing internal style sheets. The dialog needs to:
** Support selectors based on object type, object id, and object class.
** Create selection sets based on the above selectors.
** Create and edit class names.

A dialog similar to (and perhaps merged with) the trunk Selection Set dialog might be a good model to follow.

Stretch goals include:

* Support external style sheets.
* Support multiple internal style sheets.
* Support CSS 3 selectors.
* Support parsing of 'font-face'.

Use Cases

* Support externally created SVGs.
* Producing better SVGs for the Web.
* Changing style on multiple objects at once (palettes).

Related Material

* [https://www.w3.org/TR/CSS2/ CSS 2 Specification]
* [https://www.w3.org/TR/css-2015/ CSS 2015 Snapshot]

==P2. Development Project Management System==

Enhance Inkscape's web tools for managing development projects.

* Estimation of difficulty: Moderately hard
* Potential mentors: Bryce Harrington
* Programming skills needed: Python
* Prerequisites: Working knowledge of Django web application development

Detailed Description

Design and implement tools to allow submitting and editing ideas for development projects. Create various project listing views that display projects that need further editing, lists of projects meeting various criteria (e.g. janitorial, new features, programming language, etc.), assigned projects, completed projects, and so forth.

This work would be part of a larger, ongoing effort to unify Inkscape's various collections of task ideas into a single system, to make them easier for potential contributors to review and select from. Some of this project has already been implemented, so you would be focusing on enhancing its user interfaces to make it more powerful and more broadly usable.

Use Cases
* "Janitorial" tasks suitable for new developers looking for easy ways to get involved in Inkscape development
* Google Summer of Code Project Ideas (this page!!)
* Funded development work, with funds supplied by various fundraisers
* User-supplied requests for feature enhancements

Related Material
* Current collections of tasks that we want to eventually migrate into this system:
** http://wiki.inkscape.org/wiki/index.php/Janitorial_tasks
** https://blueprints.launchpad.net/inkscape/
* [https://inkscape.org/en/support-us/funded-development/ High level specification for the system]
* [[FundedProjectSystemDevelopment]] related tasks

==P3. Slice toolbar items==
[[File:Cuttool.png|200px|thumb|right|Example of result of the cut/eraser tool]]
* Estimation of difficulty: Moderately hard
* Potential mentors: Jabier Arraiza (Spanish, some English)
* Programming skills needed: C++

Detailed Description
The goal is a toolbar item, called "slice" to slice items in a easy way.
We check to convert strokes to path previously to cut, to avoid continuing with stroke thought cut-out item fills. 
Maybe positioned in the path menu after bool operations, the selected items are sliced from topmost path, converting strokes to paths, duplicating fills and maybe apply to groups (there is some work in groups boolops from Martin Owens). 
A lot of helper code is done yet in flatten branch (Alexander Brock lp:~inkscape+alexander/inkscape/flatten). 
There are new Boolean operations, implemented but not used in trunk. We need to switch the division and flatten branch methods from Livarot to these new operations. 
Another feature interesting is a second toolbar item "slice from guides" to get the guides over the selected item and use it as cut-out. 

Use Cases
* Better item slicing.

==P4. SVG 2 Text Support==

* Estimation of difficulty: Hard
* Potential mentors: Tavmjong Bah
* Programming skills needed: C++
* Prerequisites: Familiarity with text layout. Knowledge of CSS.

Detailed Description

Inkscape currently has a non-compliant flowed text feature (based on SVG 1.2 which was never adopted) that needs to be made compatible with both SVG2 and SVG 1.1. This project is to re-implement the flowed text feature within Inkscape to be SVG2 compliant and to have a proper SVG 1.1 fallback. In addition to the flowed text itself as it exists within Inkscape, SVG2 adds new formatting features including shape-margin and shape-padding, shape-inside and shape-outside, exclusions, additional white-space control settings, pre-wrap, pre-line, etc.

Use Cases
* Proper text flow into rectangles and other shapes.

Related Material
* [https://svgwg.org/svg2-draft/text.html Current draft of SVG 2 text specification.]

==P5. Better data structure for selections==

* Estimation of difficulty: Medium
* Potential mentors: Krzysztof Kosiński
* Programming skills needed: C++
* Prerequisites: Familiarity with STL and/or Boost, knowledge of basic data structures and their performance properties, some knowledge of glib a plus.

Detailed Description

Many useful functions in Inkscape, such as grouping, Boolean operations, etc., work on a selection. However, there is only one selection object per window, and its state is shown in the user interface. It would be useful to have an object type that represents the same concept, but not tied to the user interface.

This project would involve implementing an <code>Inkscape::ObjectSet</code> object that would serve as a base for <code>Inkscape::Selection</code>. The internal data structure should support fast lookup (checking whether a given object belongs to the set) and preserve the order of insertion (so that we can still determine which object was selected first or last). Internally, <code>ObjectSet</code> can be based on a Boost multi-index container with a list index and a hash index.

Related Material
* [http://www.boost.org/doc/libs/1_60_0/libs/multi_index/doc/index.html Boost Multi-Index Containers Documentation]

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

[[Category:Developer Documentation]]

Google Summer of Code

2016-02-05T05:30:23Z

Tweenk: /* Suggested Project Ideas */

= Welcome to Inkscape! =

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

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

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

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

= Student Applications =

* Google program information:
** [https://www.google-melange.com/gsoc/homepage/google/gsoc2014 Home page].
** Summer of Code Application form. Applications open at 19:00 UTC on March 10th.

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

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

= The "two patches" rule =

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

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

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

= Performance Evaluation =

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

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

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

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

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

= Suggested Project Ideas =

The following is a list of formal project suggestions, but do not feel limited to only these - some of our best contributions have been unique ideas that students had in mind from other sources!

See also [[Development Project Ideas]] and https://blueprints.launchpad.net/inkscape/

==P1. Better CSS Style Sheet Support==

Enhance Inkscape's support for CSS style sheets.

* Estimation of difficulty: Moderately hard
* Potential mentors: Tavmjong Bah
* Programming skills needed: C++
* Prerequisites: Experience with CSS style sheets.

Detailed Description

Currently Inkscape support of CSS style sheets is limited to the reading and parsing of one internal style sheet. The styles are immediately stored in the style attribute for each object thus changes to the style sheet (awkwardly possible now through the XML editor) are not recognized. This project will:

* Add to each object property a means to track the source of the property value.
* Create a dialog for editing internal style sheets. The dialog needs to:
** Support selectors based on object type, object id, and object class.
** Create selection sets based on the above selectors.
** Create and edit class names.

A dialog similar to (and perhaps merged with) the trunk Selection Set dialog might be a good model to follow.

Stretch goals include:

* Support external style sheets.
* Support multiple internal style sheets.
* Support CSS 3 selectors.
* Support parsing of 'font-face'.

Use Cases

* Support externally created SVGs.
* Producing better SVGs for the Web.
* Changing style on multiple objects at once (palettes).

Related Material

* [https://www.w3.org/TR/CSS2/ CSS 2 Specification]
* [https://www.w3.org/TR/css-2015/ CSS 2015 Snapshot]

==P2. Development Project Management System==

Enhance Inkscape's web tools for managing development projects.

* Estimation of difficulty: Moderately hard
* Potential mentors: Bryce Harrington
* Programming skills needed: Python
* Prerequisites: Working knowledge of Django web application development

Detailed Description

Design and implement tools to allow submitting and editing ideas for development projects. Create various project listing views that display projects that need further editing, lists of projects meeting various criteria (e.g. janitorial, new features, programming language, etc.), assigned projects, completed projects, and so forth.

This work would be part of a larger, ongoing effort to unify Inkscape's various collections of task ideas into a single system, to make them easier for potential contributors to review and select from. Some of this project has already been implemented, so you would be focusing on enhancing its user interfaces to make it more powerful and more broadly usable.

Use Cases
* "Janitorial" tasks suitable for new developers looking for easy ways to get involved in Inkscape development
* Google Summer of Code Project Ideas (this page!!)
* Funded development work, with funds supplied by various fundraisers
* User-supplied requests for feature enhancements

Related Material
* Current collections of tasks that we want to eventually migrate into this system:
** http://wiki.inkscape.org/wiki/index.php/Janitorial_tasks
** https://blueprints.launchpad.net/inkscape/
* [https://inkscape.org/en/support-us/funded-development/ High level specification for the system]
* [[FundedProjectSystemDevelopment]] related tasks

==P3. Slice toolbar items==
[[File:Cuttool.png|200px|thumb|right|Example of result of the cut/eraser tool]]
* Estimation of difficulty: Moderately hard
* Potential mentors: Jabier Arraiza (Spanish, some English)
* Programming skills needed: C++

Detailed Description
The goal is a toolbar item, called "slice" to slice items in a easy way.
We check to convert strokes to path previously to cut, to avoid continuing with stroke thought cut-out item fills. 
Maybe positioned in the path menu after bool operations, the selected items are sliced from topmost path, converting strokes to paths, duplicating fills and maybe apply to groups (there is some work in groups boolops from Martin Owens). 
A lot of helper code is done yet in flatten branch (Alexander Brock lp:~inkscape+alexander/inkscape/flatten). 
There are new Boolean operations, implemented but not used in trunk. We need to switch the division and flatten branch methods from Livarot to these new operations. 
Another feature interesting is a second toolbar item "slice from guides" to get the guides over the selected item and use it as cut-out. 

Use Cases
* Better item slicing.

==P4. SVG 2 Text Support==

* Estimation of difficulty: Hard
* Potential mentors: Tavmjong Bah
* Programming skills needed: C++
* Prerequisites: Familiarity with text layout. Knowledge of CSS.

Detailed Description

Inkscape currently has a non-compliant flowed text feature (based on SVG 1.2 which was never adopted) that needs to be made compatible with both SVG2 and SVG 1.1. This project is to re-implement the flowed text feature within Inkscape to be SVG2 compliant and to have a proper SVG 1.1 fallback. In addition to the flowed text itself as it exists within Inkscape, SVG2 adds new formatting features including shape-margin and shape-padding, shape-inside and shape-outside, exclusions, additional white-space control settings, pre-wrap, pre-line, etc.

Use Cases
* Proper text flow into rectangles and other shapes.

Related Material
* [https://svgwg.org/svg2-draft/text.html Current draft of SVG 2 text specification.]

==P5. Better data structure for selections==

* Estimation of difficulty: Medium
* Potential mentors: Krzysztof Kosiński
* Programming skills needed: C++
* Prerequisites: Familiarity with STL and/or Boost, knowledge of basic data structures and their performance properties, some knowledge of glib a plus.

Detailed Description

Many useful functions in Inkscape, such as grouping, Boolean operations, etc., work on a selection. However, there is only one selection object per window, and its state is shown in the user interface. It would be useful to have an object type that represents the same concept, but not tied to the user interface.

This project would involve implementing an <code>Inkscape::ObjectSet</code> object that would serve as a base for <code>Inkscape::Selection</code>. The internal data structure should support fast lookup (checking whether a given object belongs to the set) and preserve the order of insertion (so that we can still determine which object was selected first or last). Internally, ObjectSet can be based on a Boost multi-index container with a list index and a hash index.

Related Material
* [http://www.boost.org/doc/libs/1_60_0/libs/multi_index/doc/index.html Boost Multi-Index Containers Documentation]

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

[[Category:Developer Documentation]]

Development Project Ideas

2016-02-05T05:28:26Z

Tweenk: /* 2Geom geometry library */

==General==

* Improve startup time and initialization performance (i.e. improve font cache).
* Improve icon cache: Convert the icon cache (widgets/icon.cpp) to create the PNGs with a directory structure and index file matching the icon theme specification. Use this to get rid of customized classes InkAction, SPIcon, and so on.
* Continue C++ migration:
** Use Glib::ustring for UTF-8 data and std::string for filenames and raw byte strings instead of C-strings (char*).
** Replace uses of GList and GSList with STL containers.
* Extension system improvements: Refactor the extension API. Clean up the kludgy class hierarchy, possibly using multiple inheritance. Use GInputStream and GOutputStream as parameters instead of file paths, so that things like the clipboard can write data to memory without going through a temporary file.

== XML tree ==

* SAX parser: Convert the current document parser from DOM to SAX, so that it creates our XML tree right away, instead of creating the libxml2 DOM tree, creating our tree to match it, then freeing the libxml2 tree. This should improve performance and allow more robust fixes for some problems.
* Typed XML tree: Improve XML tree so that it can store some attributes in parsed, binary form. The main target of this are the data URIs used to embed images, which could be stored as binary data only. This work should be done after completing the SAX parser, as this will make it easier.

== 2Geom geometry library ==

* Investigate whether it is possible to store subpath data in a more compact way and make the Curve objects only convenience facades. Right now, if the path has only linear segments, every point is stored twice.
* Remove SPCurve: SPCurve is a thin wrapper around Geom::PathVector which exists for historical reasons. Its functionality should be added to PathVector, and SPCurve should be purged.
* Provide a quick bounding box routine for stroked paths.
* Boolean operations and stroking: Add methods to PathVector objects:
** Set operators (& | - ^), which perform the relevant Boolean operation on the paths. <s>Use the algorithm from CGAL or devise a new robust algorithm.</s> The CGAL implementation is horribly broken and doesn't work; there is an implementation of the Greiner-Hormann algorithm in 2Geom now, but it's not robust and runs pretty slow.
** <tt>stroke(double line_width, LineJoin join, LineCap cap, double miter_limit)</tt>, which performs the stroke-to-path operation.
** <tt>dash(std::vector<double> const &dasharray)</tt>, which performs dashing.

== Object tree ==

* Improve the performance of layer visibility: Right now, toggling layer visibility causes massive changes in the display tree, because the entire toggled layer is invalidated at the XML level. This results in very bad performance for an action which should nearly instantaneous. Improve the control flow so that only the visibility of the object representing the layer is turned off, but the remainder of the display and object tree is leaved alone.
* Robust ID handling: Currently ID clash resolution is implemented as a giant switch over object types, listing every possible dependency. Replace this with virtual methods on objects, which provide information on what each object refers to. Improve behavior when a dependency of an object is deleted, and when IDs are changed / deleted from the XML editor.
* Replace the print functions in the SPxxx classes with a generic "Visitor" pattern and port at least one export type (e.g. EMF, PDF, PS) to the new routines.

== User interface ==
* Shape manipulators: The idea here is to rewrite shape tools in the same paradigm as the node tool. Instead of storing all information about the shape in knots which differ only by their callbacks, allow to store information in a higher-level manipulator object. This would enable things like dragging the side of a rectangle, consistent outlining / update preferences for all shapes, and editing more than one shape at once.
* [https://blueprints.launchpad.net/inkscape/+spec/transformation-anchors Transformation Anchors]
* Extend the Symbols dialog to include generic objects.
* [https://blueprints.launchpad.net/inkscape/+spec/inkscape-connectors Connector tool improvements] - Expose new libavoid functionality: orthogonal routing, connector ports, curved connectors. (Mentor: Michael Wybrow)
* [https://blueprints.launchpad.net/inkscape/+spec/fillet-tool Fillet/Chamfer tool]
* Provide more actions in the context menu depending on the content of the selection, e.g. show "Put on Path", "Flow into Frame" etc. when the selection contains the appropriate objects.
* When right-clicking a control point, show a transient dialog which would allow one to key in its coordinates.
* Provide a way to resize the page directly on the canvas, instead of keying in numbers in the Document Properties dialog.

== Project infrastructure and platform support ==

* Migrate argument parsing to GOption and remove the dependency on popt. Update the devlibs version of Glib to one where this bug is fixed: [https://bugzilla.gnome.org/show_bug.cgi?id=522131]. Once this is done, port argument parsing to GOption.
* Common build system for all platforms: Migrate the build system to CMake for all platforms and remove Autotools.
* GTK3 on Windows: Rebuild the Windows devlibs so that they contain GTK3. Make the Windows port work with them, possibly sending the appropriate patches to the GTK maintainers.

== Rendering Improvements ==

* [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. 
* Box blur: Currently we always use a very accurate method to compute the Gaussian blur filter. Add an alternate method which approximates Gaussian blur using three stacked box blurs (simple averages). This is detailed in the SVG 1.1 SE specification.
* Pluggable renderers - allow writing rendering backends which use something other than Cairo, e.g, OpenGL, Skia, Mozilla Azure or GEGL.
* OpenGL renderer - implement an OpenGL 3.x+ canvas which would render Beziers using this method: http://http.developer.nvidia.com/GPUGems3/gpugems3_ch25.html Investigate whether this generalizes to S-basis and circular arcs. Since the described method does not handle stroking, this work depends on implementing boolean operations and stroking. Also check how OpenGL path rendering is implemented in Qt, since apparently the performance there is very good. http://zrusin.blogspot.com/2011/09/nv-path-rendering.html

== Better SVG standard coverage ==

* Full SVG viewbox support
* [[multipage | Multiple Page support]]
* Improve SVG compliance. [http://tavmjong.free.fr/INKSCAPE/W3C_SVG_1.1F2/harness/htmlInkscapeApproved/index.html Current status of W3C test suite compliance].

=== SVG 2 and CSS3 ===

See: [[SVG2]].

This includes providing suitable GUI and SVG 1.1 fallbacks.

* Filling and Stroking
** [http://www.w3.org/Graphics/SVG/WG/wiki/Proposals/Stroke_position Stroke position]
** [http://www.w3.org/Graphics/SVG/WG/wiki/Proposals/Stroke_dash_adjustment Stroke dash adjustment]
** [https://svgwg.org/svg2-draft/painting.html#SpecifyingPaint Multiple fills]
** [https://svgwg.org/svg2-draft/painting.html#PaintOrder Paint order] (Rendering alread implemented, needs GUI and fallback.)
** Marker color matching stroke.
** Vector Effects (non-destructive boolean-ops would be a good start)
** [http://www.w3.org/TR/css3-color/ CSS3 color support]
** [http://dev.w3.org/fxtf/compositing-1/ CSS3 blend modes]

* Paint servers
** [https://svgwg.org/svg2-draft/pservers.html#SolidColors Solid-color support] (Named colors, would deprecate the single-stop gradient approach we currently use)
** [https://svgwg.org/svg2-draft/pservers.html#MeshGradients Mesh gradient] (Basic implementation done, needs refinement and fallback.)
** [https://svgwg.org/svg2-draft/pservers.html#Hatches Hatched patterns]

* Text
** [https://svgwg.org/svg2-draft/text.html CSS based text flow]

* Misc
** [http://www.w3.org/TR/css3-transforms/ CSS3 2d and 3d transforms]

Note: Some of the above items are somewhat low hanging fruit and would need a few of them to make a good proposal, others alone are worthy of a full GSoC project.

=== Improve Inkscape SVG for use on Web ===

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

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

== Slice toolbar items==
[[File:Cuttool.png|200px|thumb|right|Example of result of the cut/eraser tool]]

Detailed Description
The goal is a toolbar item, called "slice" to slice items in a easy way.
We check to convert strokes to path previously to cut, to avoid continuing with stroke thought cut-out item fills. 
Maybe positioned in the path menu after bool operations, the selected items are sliced from topmost path, converting strokes to paths, duplicating fills and maybe apply to groups (there is some work in groups boolops from Martin Owens). 
A lot of helper code is done yet in flatten branch (Alexander Brock lp:~inkscape+alexander/inkscape/flatten). 
There are new Boolean operations, implemented but not used in trunk. We need to switch the division and flatten branch methods from Livarot to these new operations. 
Another feature interesting is a second toolbar item "slice from guides" to get the guides over the selected item and use it as cut-out. 

== Live Path Effects related ==

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

== Import/export projects ==

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

== Generic ideas ==

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

[[Category:Developer Documentation]]

Hackfest2016

2015-11-06T21:26:08Z

Tweenk:

This page has some early planning information on a potential Inkscape hackfest in 2016.

==Venue==

LGM 2016 will be held in London. This means it would be the most convenient to have the hackfest in the UK or at least in Europe, to avoid long travels for developers who want to attend both the hackfest and the LGM.

The hackfest requires the following things:
* Quiet meeting space with several power outlets and reasonably fast internet access.
* WiFi is preferable, but can be provided via our own router.
* Whiteboard / blackboard for quick notes.
* Overhead projector or a big screen for demonstrations would be useful, but probably not essential.
* Accommodation which is easily reachable from the meeting space.
* Several food options near the meeting space.
* It should be possible to survive using only English.

===London===
Natural proposal due to LGM location.

====Pros====
* Same place as LGM
* English speaking country
* Lots of things to do after coding
* Good public transport

====Cons====
* Accommodation and food is very expensive

====Further information====
Public transport in London is one of the best in the world. Single fares are $4.47 peak / $3.54 off-peak to anywhere in Zone 1 if you have an Oyster card, available with a refundable $7.70 deposit, or $7.40 in cash. Cash fares cannot be used on buses. Transfer to/from Heathrow by tube (Piccadilly line) is $7.85 peak / $4.77 off-peak with an Oyster card or $9.24 with cash fare. Peak hours are 6:30 to 9:30 and 16:00 to 19:00.

London is a major international airline hub, and its five airports have connections to almost everywhere on Earth.

All prices after conversion to USD, using the exchange rate 1 GBP = 1.54 USD.

===Leeds===
Proposed by Alex Valavanis.

====Pros====
* Cheaper than London
* English speaking country
* Alex can arrange free meeting space
* London can be reached quickly by train (total 2-3 hours)

====Cons====
* Not a major airport

====Further information====

Transport from Manchester: Manchester Airport with a train to Leeds for £6 (50 mins)
Transport from London: Flight to Heathrow in London means the Piccadilly line (£8/45 mins) to Kings Cross and a 2 hour train ride for £22 to Leeds.

===Warsaw (former proposal)===
Proposed by Krzysztof Kosiński.

Unfortunately K.K. is moving to USA and so won't be local anymore. Information left for posterity.

====Pros====
* At least 50% cheaper than London
* Good public transport
* Krzysztof can probably arrange free meeting space

====Cons====
* Not an English speaking country, level of English proficiency is somewhere between Germany and France
* Requires a flight to get to London for LGM (total 4-5 hours)

====Further information====
A three-night midweek stay booked a month in advance at an aparthotel or a budget hotel will cost around $160-$200 (prices from booking.com for start of June, which is already during the tourist season; prices in April are typically lower). An equivalent five-star hotel stay will cost between $400 and $800.

Public transport has a [http://warszawa.jakdojade.pl/ very good navigation website] and a mobile application. Single tickets valid for 60 minutes and any number of transfers are $1.25, 24 hour passes are $4.20, 30-day passes are $31 - they are contactless cards and require a photo. The fares are good for all of Zone 1, which covers the whole city limits of Warsaw.

There are flights several times daily between Warsaw Chopin Airport (WAW) and major airline hubs London, Paris, Amsterdam, Vienna, Frankfurt, Brussels. The only direct U.S. destinations are Chicago O'Hare and New York JFK. There is a second low-cost airport in Modlin (WMI), served by Ryanair. WAW is close to the city and connected by buses and trains, while WMI is accessible by a shuttle bus from a nearby train station. There is also a train you can take from Berlin Hauptbahnhof every 3 hours, it takes about 6 hours to reach the main railway station Warszawa Centralna.

Food is cheap by European standards. The most popular foreign cuisine is Italian. Two XXL pizzas, enough to feed four people, are around $16. Footlong Sub combo is $6, McMenu is $5, restaurant meals are anywhere between $8 and $20. Possible after-coding activities are as varied as in any major European city. There are several good multi-tap beer parlors, where a craft beer will cost around $3.

All prices after conversion to USD, using the exchange rate 1 PLN = 0.28 USD.

===Phnom Penh===

Proposed by Sirko Kemter for an event in November 2015.

====Pros====
* Very cheap accommodation and food
* Friendly people

====Cons====
* Not an English speaking country
* Far away for US-based developers

====Further information====

Information from Sirko's e-mail:

Cambodia sounds far but flight costs are not more expensive as an flight from US to Europe, visa is not a problem there are only few countries excluded from the arrival one, so its pay get in. The hotels in Phnom Penh are extremly cheap, you get for 40$ an 5star hotel room but prices start with just 1$ a day (including breakfast and a bottle water a day). Same is for food, you get for 3-5$ a nice all you can eat khmer bbq.

Cambodias people are extremly welcoming and open, especially the youth who really likes to learn and work to change their lifes. Inkscape has already a lot of friends now there, I was last year twice in Phnom Penh and gave a lot of workshops how to use it.

Hackfest2016

2015-04-30T20:44:44Z

Tweenk:

This page has some early planning information on a potential Inkscape hackfest in 2016.

==Venue==

LGM 2016 will be held in London. This means it would be the most convenient to have the hackfest in the UK or at least in Europe, to avoid long travels for developers who want to attend both the hackfest and the LGM.

The hackfest requires the following things:
* Quiet meeting space with several power outlets and reasonably fast internet access.
* WiFi is preferable, but can be provided via our own router.
* Whiteboard / blackboard for quick notes.
* Overhead projector or a big screen for demonstrations would be useful, but probably not essential.
* Accommodation which is easily reachable from the meeting space.
* Several food options near the meeting space.
* It should be possible to survive using only English.

===London===
Natural proposal due to LGM location.

====Pros====
* Same place as LGM
* English speaking country
* Lots of things to do after coding
* Good public transport

====Cons====
* Accommodation and food is very expensive

====Further information====
Public transport in London is one of the best in the world. Single fares are $4.47 peak / $3.54 off-peak to anywhere in Zone 1 if you have an Oyster card, available with a refundable $7.70 deposit, or $7.40 in cash. Cash fares cannot be used on buses. Transfer to/from Heathrow by tube (Piccadilly line) is $7.85 peak / $4.77 off-peak with an Oyster card or $9.24 with cash fare. Peak hours are 6:30 to 9:30 and 16:00 to 19:00.

London is a major international airline hub, and its five airports have connections to almost everywhere on Earth.

All prices after conversion to USD, using the exchange rate 1 GBP = 1.54 USD.

===Leeds===
Proposed by Alex Valavanis.

====Pros====
* Cheaper than London
* English speaking country
* Alex can arrange free meeting space
* London can be reached quickly by train (total 2-3 hours)

====Cons====
* Not a major airport

====Further information====

Transport from Manchester: Manchester Airport with a train to Leeds for £6 (50 mins)
Transport from London: Flight to Heathrow in London means the Piccadilly line (£8/45 mins) to Kings Cross and a 2 hour train ride for £22 to Leeds.

===Warsaw===
Proposed by Krzysztof Kosiński.

====Pros====
* At least 50% cheaper than London
* Good public transport
* Krzysztof can probably arrange free meeting space

====Cons====
* Not an English speaking country, level of English proficiency is somewhere between Germany and France
* Requires a flight to get to London for LGM (total 4-5 hours)

====Further information====
A three-night midweek stay booked a month in advance at an aparthotel or a budget hotel will cost around $160-$200 (prices from booking.com for start of June, which is already during the tourist season; prices in April are typically lower). An equivalent five-star hotel stay will cost between $400 and $800.

Public transport has a [http://warszawa.jakdojade.pl/ very good navigation website] and a mobile application. Single tickets valid for 60 minutes and any number of transfers are $1.25, 24 hour passes are $4.20, 30-day passes are $31 - they are contactless cards and require a photo. The fares are good for all of Zone 1, which covers the whole city limits of Warsaw.

There are flights several times daily between Warsaw Chopin Airport (WAW) and major airline hubs London, Paris, Amsterdam, Vienna, Frankfurt, Brussels. The only direct U.S. destinations are Chicago O'Hare and New York JFK. There is a second low-cost airport in Modlin (WMI), served by Ryanair. WAW is close to the city and connected by buses and trains, while WMI is accessible by a shuttle bus from a nearby train station. There is also a train you can take from Berlin Hauptbahnhof every 3 hours, it takes about 6 hours to reach the main railway station Warszawa Centralna.

Food is cheap by European standards. The most popular foreign cuisine is Italian. Two XXL pizzas, enough to feed four people, are around $16. Footlong Sub combo is $6, McMenu is $5, restaurant meals are anywhere between $8 and $20. Possible after-coding activities are as varied as in any major European city. There are several good multi-tap beer parlors, where a craft beer will cost around $3.

All prices after conversion to USD, using the exchange rate 1 PLN = 0.28 USD.

===Phnom Penh===

Proposed by Sirko Kemter for an event in November 2015.

====Pros====
* Very cheap accommodation and food
* Friendly people

====Cons====
* Not an English speaking country
* Far away for US-based developers

====Further information====

Information from Sirko's e-mail:

Cambodia sounds far but flight costs are not more expensive as an flight from US to Europe, visa is not a problem there are only few countries excluded from the arrival one, so its pay get in. The hotels in Phnom Penh are extremly cheap, you get for 40$ an 5star hotel room but prices start with just 1$ a day (including breakfast and a bottle water a day). Same is for food, you get for 3-5$ a nice all you can eat khmer bbq.

Cambodias people are extremly welcoming and open, especially the youth who really likes to learn and work to change their lifes. Inkscape has already a lot of friends now there, I was last year twice in Phnom Penh and gave a lot of workshops how to use it.

Hackfest2016

2015-04-30T20:43:09Z

Tweenk: /* Warsaw */

This page has some early planning information on a potential Inkscape hackfest in 2016.

==Venue==

LGM 2016 will be held in London. This means it would be the most convenient to have the hackfest in the UK or at least in Europe, to avoid long travels for developers who want to attend both the hackfest and the LGM.

The hackfest requires the following things:
* Quiet meeting space with several power outlets and reasonably fast internet access.
* WiFi is preferable, but can be provided via our own router.
* Whiteboard / blackboard for quick notes.
* Overhead projector or a big screen for demonstrations would be useful, but probably not essential.
* Accommodation which is easily reachable from the meeting space.
* Several food options near the meeting space.
* It should be possible to survive using only English.

===London===
Natural proposal due to LGM location.

====Pros====
* Same place as LGM
* English speaking country
* Lots of things to do after coding
* Good public transport

====Cons====
* Accommodation and food is very expensive

====Further information====
Public transport in London is one of the best in the world. Single fares are $4.47 peak / $3.54 off-peak to anywhere in Zone 1 if you have an Oyster card, available with a refundable $7.70 deposit, or $7.40 in cash. Cash fares cannot be used on buses. Transfer to/from Heathrow by tube (Piccadilly line) is $7.85 peak / $4.77 off-peak with an Oyster card or $9.24 with cash fare. Peak hours are 6:30 to 9:30 and 16:00 to 19:00.

London is a major international airline hub, and its five airports have connections to almost everywhere on Earth.

All prices after conversion to USD, using the exchange rate 1 GBP = 1.54 USD.

===Leeds===
Proposed by Alex Valavanis.

====Pros====
* Cheaper than London
* English speaking country
* Alex can arrange free meeting space
* London can be reached quickly by train (total 2-3 hours)

====Cons====
* Not a major airport

====Further information====

Transport from Manchester: Manchester Airport with a train to Leeds for £6 (50 mins)
Transport from London: Flight to Heathrow in London means the Piccadilly line (£8/45 mins) to Kings Cross and a 2 hour train ride for £22 to Leeds.

===Warsaw===
Proposed by Krzysztof Kosiński.

====Pros====
* At least 50% cheaper than London
* Good public transport
* Krzysztof can probably arrange free meeting space

====Cons====
* Not an English speaking country, level of English proficiency is somewhere between Germany and France
* Requires a flight to get to London for LGM (total 4-5 hours)

====Further information====
A three-night midweek stay booked a month in advance at an aparthotel or a budget hotel will cost around $160-$200 (prices from booking.com for start of June, which is already during the tourist season; prices in April are typically lower). An equivalent five-star hotel stay will cost between $400 and $800.

Public transport has a [http://warszawa.jakdojade.pl/ very good navigation website] and a mobile application. Single tickets valid for 60 minutes and any number of transfers are $1.25, 24 hour passes are $4.20, 30-day passes are $31 - they are contactless cards and require a photo. The fares are good for all of Zone 1, which covers the whole city limits of Warsaw.

There are flights several times daily between Warsaw Chopin Airport (WAW) and major airline hubs London, Paris, Amsterdam, Vienna, Frankfurt, Brussels. The only direct U.S. destinations are Chicago O'Hare and New York JFK. There is a second low-cost airport in Modlin (WMI), served by Ryanair. WAW is close to the city and connected by buses and trains, while WMI is accessible by a shuttle bus from a nearby train station. There is also a train you can take from Berlin Hauptbahnhof every 3 hours, it takes about 6 hours to reach the main railway station Warszawa Centralna.

Food is cheap by European standards. The most popular foreign cuisine is Italian. Two XXL pizzas, enough to feed four people, are around $16. Footlong Sub combo is $6, McMenu is $5, restaurant meals are anywhere between $8 and $20. Possible after-coding activities are as varied as in any major European city. There are several good multi-tap beer parlors, where a craft beer will cost around $3.

All prices after conversion to USD, using the exchange rate 1 PLN = 0.28 USD.

==Phnom Penh==

Proposed by Sirko Kemter for an event in November 2015.

===Pros===
* Very cheap accommodation and food
* Friendly people

===Cons===
* Not an English speaking country
* Far away for US-based developers

====Further information====

Information from Sirko's e-mail:

Cambodia sounds far but flight costs are not more expensive as an flight from US to Europe, visa is not a problem there are only few countries excluded from the arrival one, so its pay get in. The hotels in Phnom Penh are extremly cheap, you get for 40$ an 5star hotel room but prices start with just 1$ a day (including breakfast and a bottle water a day). Same is for food, you get for 3-5$ a nice all you can eat khmer bbq.

Cambodias people are extremly welcoming and open, especially the youth who really likes to learn and work to change their lifes. Inkscape has already a lot of friends now there, I was last year twice in Phnom Penh and gave a lot of workshops how to use it.

Hackfest2016

2015-04-30T20:42:37Z

Tweenk:

This page has some early planning information on a potential Inkscape hackfest in 2016.

==Venue==

LGM 2016 will be held in London. This means it would be the most convenient to have the hackfest in the UK or at least in Europe, to avoid long travels for developers who want to attend both the hackfest and the LGM.

The hackfest requires the following things:
* Quiet meeting space with several power outlets and reasonably fast internet access.
* WiFi is preferable, but can be provided via our own router.
* Whiteboard / blackboard for quick notes.
* Overhead projector or a big screen for demonstrations would be useful, but probably not essential.
* Accommodation which is easily reachable from the meeting space.
* Several food options near the meeting space.
* It should be possible to survive using only English.

===London===
Natural proposal due to LGM location.

====Pros====
* Same place as LGM
* English speaking country
* Lots of things to do after coding
* Good public transport

====Cons====
* Accommodation and food is very expensive

====Further information====
Public transport in London is one of the best in the world. Single fares are $4.47 peak / $3.54 off-peak to anywhere in Zone 1 if you have an Oyster card, available with a refundable $7.70 deposit, or $7.40 in cash. Cash fares cannot be used on buses. Transfer to/from Heathrow by tube (Piccadilly line) is $7.85 peak / $4.77 off-peak with an Oyster card or $9.24 with cash fare. Peak hours are 6:30 to 9:30 and 16:00 to 19:00.

London is a major international airline hub, and its five airports have connections to almost everywhere on Earth.

All prices after conversion to USD, using the exchange rate 1 GBP = 1.54 USD.

===Leeds===
Proposed by Alex Valavanis.

====Pros====
* Cheaper than London
* English speaking country
* Alex can arrange free meeting space
* London can be reached quickly by train (total 2-3 hours)

====Cons====
* Not a major airport

====Further information====

Transport from Manchester: Manchester Airport with a train to Leeds for £6 (50 mins)
Transport from London: Flight to Heathrow in London means the Piccadilly line (£8/45 mins) to Kings Cross and a 2 hour train ride for £22 to Leeds.

===Warsaw===
Proposed by Krzysztof Kosiński.

====Pros====
* At least 50% cheaper than London
* Good public transport
* Krzysztof can probably arrange free meeting space

====Cons====
* Not an English speaking country, though level of English proficiency of the general population is higher than in France and Italy
* Requires a flight to get to London for LGM (total 4-5 hours)

====Further information====
A three-night midweek stay booked a month in advance at an aparthotel or a budget hotel will cost around $160-$200 (prices from booking.com for start of June, which is already during the tourist season; prices in April are typically lower). An equivalent five-star hotel stay will cost between $400 and $800.

Public transport has a [http://warszawa.jakdojade.pl/ very good navigation website] and a mobile application. Single tickets valid for 60 minutes and any number of transfers are $1.25, 24 hour passes are $4.20, 30-day passes are $31 - they are contactless cards and require a photo. The fares are good for all of Zone 1, which covers the whole city limits of Warsaw.

There are flights several times daily between Warsaw Chopin Airport (WAW) and major airline hubs London, Paris, Amsterdam, Vienna, Frankfurt, Brussels. The only direct U.S. destinations are Chicago O'Hare and New York JFK. There is a second low-cost airport in Modlin (WMI), served by Ryanair. WAW is close to the city and connected by buses and trains, while WMI is accessible by a shuttle bus from a nearby train station. There is also a train you can take from Berlin Hauptbahnhof every 3 hours, it takes about 6 hours to reach the main railway station Warszawa Centralna.

Food is cheap by European standards. The most popular foreign cuisine is Italian. Two XXL pizzas, enough to feed four people, are around $16. Footlong Sub combo is $6, McMenu is $5, restaurant meals are anywhere between $8 and $20. Possible after-coding activities are as varied as in any major European city. There are several good multi-tap beer parlors, where a craft beer will cost around $3.

All prices after conversion to USD, using the exchange rate 1 PLN = 0.28 USD.

==Phnom Penh==

Proposed by Sirko Kemter for an event in November 2015.

===Pros===
* Very cheap accommodation and food
* Friendly people

===Cons===
* Not an English speaking country
* Far away for US-based developers

====Further information====

Information from Sirko's e-mail:

Cambodia sounds far but flight costs are not more expensive as an flight from US to Europe, visa is not a problem there are only few countries excluded from the arrival one, so its pay get in. The hotels in Phnom Penh are extremly cheap, you get for 40$ an 5star hotel room but prices start with just 1$ a day (including breakfast and a bottle water a day). Same is for food, you get for 3-5$ a nice all you can eat khmer bbq.

Cambodias people are extremly welcoming and open, especially the youth who really likes to learn and work to change their lifes. Inkscape has already a lot of friends now there, I was last year twice in Phnom Penh and gave a lot of workshops how to use it.

Hackfest2016

2015-04-30T20:34:56Z

Tweenk:

This page has some early planning information on a potential Inkscape hackfest in 2016.

==Venue==

LGM 2016 will be held in London. This means it would be the most convenient to have the hackfest in the UK or at least in Europe, to avoid long travels for developers who want to attend both the hackfest and the LGM.

The hackfest requires the following things:
* Quiet meeting space with several power outlets and reasonably fast internet access.
* WiFi is preferable, but can be provided via our own router.
* Whiteboard / blackboard for quick notes.
* Overhead projector or a big screen for demonstrations would be useful, but probably not essential.
* Accommodation which is easily reachable from the meeting space.
* Several food options near the meeting space.
* It should be possible to survive using only English.

===London===
Natural proposal due to LGM location.

====Pros====
* Same place as LGM
* English speaking country
* Lots of things to do after coding
* Good public transport

====Cons====
* Accommodation and food is very expensive

====Further information====
Public transport in London is one of the best in the world. Single fares are $4.47 peak / $3.54 off-peak to anywhere in Zone 1 if you have an Oyster card, available with a refundable $7.70 deposit, or $7.40 in cash. Cash fares cannot be used on buses. Transfer to/from Heathrow by tube (Piccadilly line) is $7.85 peak / $4.77 off-peak with an Oyster card or $9.24 with cash fare. Peak hours are 6:30 to 9:30 and 16:00 to 19:00.

London is a major international airline hub, and its five airports have connections to almost everywhere on Earth.

All prices after conversion to USD, using the exchange rate 1 GBP = 1.54 USD.

===Leeds===
Proposed by Alex Valavanis.

====Pros====
* Cheaper than London
* English speaking country
* Alex can arrange free meeting space
* London can be reached quickly by train (total 2-3 hours)

====Cons====
* Not a major airport

====Further information====

Transport from Manchester: Manchester Airport with a train to Leeds for £6 (50 mins)
Transport from London: Flight to Heathrow in London means the Piccadilly line (£8/45 mins) to Kings Cross and a 2 hour train ride for £22 to Leeds.

===Warsaw===
Proposed by Krzysztof Kosiński.

====Pros====
* At least 50% cheaper than London
* Good public transport
* Krzysztof can probably arrange free meeting space

====Cons====
* Not an English-speaking country
* Requires a flight to get to London for LGM (total 4-5 hours)

====Further information====
A three-night midweek stay booked a month in advance at an aparthotel or a budget hotel will cost around $160-$200 (prices from booking.com for start of June, which is already during the tourist season; prices in April are typically lower). An equivalent five-star hotel stay will cost between $400 and $800.

Public transport has a [http://warszawa.jakdojade.pl/ very good navigation website] and a mobile application. Single tickets valid for 60 minutes and any number of transfers are $1.25, 24 hour passes are $4.20, 30-day passes are $31 - they are contactless cards and require a photo. The fares are good for all of Zone 1, which covers the whole city limits of Warsaw.

There are flights several times daily between Warsaw Chopin Airport (WAW) and major airline hubs London, Paris, Amsterdam, Vienna, Frankfurt, Brussels. The only direct U.S. destinations are Chicago O'Hare and New York JFK. There is a second low-cost airport in Modlin (WMI), served by Ryanair. WAW is close to the city and connected by buses and trains, while WMI is accessible by a shuttle bus from a nearby train station. There is also a train you can take from Berlin Hauptbahnhof every 3 hours, it takes about 6 hours to reach the main railway station Warszawa Centralna.

Food is cheap by European standards. The most popular foreign cuisine is Italian. Two XXL pizzas, enough to feed four people, are around $16. Footlong Sub combo is $6, McMenu is $5, restaurant meals are anywhere between $8 and $20. Possible after-coding activities are as varied as in any major European city. There are several good multi-tap beer parlors, where a craft beer will cost around $3.

All prices after conversion to USD, using the exchange rate 1 PLN = 0.28 USD.

Hackfest2016

2015-04-30T06:13:57Z

Tweenk:

Hackfest2016

2015-04-30T06:10:13Z

Tweenk: /* Further information */

Hackfest2016

2015-04-30T06:04:40Z

Tweenk: create page

Killing Livarot

2015-04-26T16:28:20Z

Tweenk: Created page with "This page details work items that need to be done to remove Livarot from the code base. ==Work items== * Boolean operations ** Initial code in 2Geom, needs more work. MSc th..."

This page details work items that need to be done to remove Livarot from the code base.

==Work items==

* Boolean operations
** Initial code in 2Geom, needs more work. MSc thesis subject of Krzysztof Kosiński
* Tweak tool
* Crazy libnrtype dependency
** libnrtype uses Livarot for line-breaking text in flow regions
* Offset tool
** Path outliner worked on by Liam will eventually be a direct replacement