Inkscape Wiki - User contributions [en]

Tracking Dependencies

2024-05-02T02:12:23Z

ScislaC: /* Distros */ Added Ubuntu 24.04 LTS

== Compilers ==

* Version 1.0 requires a C++11 compiler.
* Version 1.1 requires a C++17 compiler.
* Version 1.4 requires a C++20 compiler.

See [[c++11]], [[c++17]], and [[C++20]].

== Libs ==

C++ bindings are not included, since their required versions match those of the C counterparts.

{| class="wikitable"
|-
! Library
! v 0.92
! v 1.0
! v 1.1
! v 1.2
! v 1.3
! master
! gtk4
|-
| Boehm-GC
| 7.2
| 7.2
| 7.2
|
|
|
|
|-
| Cairo
| 1.14
| 1.14 (1.15.4 required for PDF links)
| 1.16*
| 1.16
| 1.16
|
| 1.16**
|-
| double-conversion [https://github.com/google/double-conversion] ''(lib2geom dependency)''
| ''(not required)''
| any
|
|
|
|
|-
| FreeType
|
|
| 2.9* (Required for Variable fonts)
| 2.9
| 2.9
|
|
|-
| GDL
| N/A (3.4)
| 3.4
| Not Used
| Not Used
| Not Used
| Not Used
|-
| Glib
| 2.28
| 2.48
| 2.56 or 2.62*
| 2.64
| 2.64
|
| 2.68**
|-
| GTK+
| 2.24 (3.8)
| 3.22
| 3.24*
| 3.24
| 3.24
|
| 4.12+
|-
| GNU Scientific Library
| ?
| ?
|
|
|
|
|
|-
| HarfBuzz
| ?
| ?
| 2.2*
| 2.6
| 2.6
| 2.6.5*
|
|-
| libsigc++
| ''2.0.12*''
| ''2.0.12*''
| ''2.0.12*''
|
|
|
| 3.0**
|-
| libSoup
| ''(not required)''
| (any)
|
|
|
|
|
|-
| libpotrace
| ''(not required)''
| (any)
|
|
|
|
|
|-
| libxml
| ''2.6.11*''
| ''2.6.11*''
|
|
|
|
|
|-
| libxslt
| ''1.0.15*''
| ''1.0.15*''
|
|
|
|
|
|-
| lcms
| 1.13
| 2.2
| 2.2 (2.9*)
| 2.9*
| 2.9*
|
|
|-
| Pango
| 1.24
| 1.24 (1.41.1 required for variable fonts)
| 1.42*
| 1.44
| 1.44 (HarfBuzz shaping)
|
| 2.48**
|-
| Poppler
| 0.20.0
| 0.20.0
| 0.29 (0.71*)
| 0.29 (0.71*)
| 0.71*
|
|
|-
| [https://formulae.brew.sh/formula/gtk-mac-integration gtk-mac-integration] [https://www.macports.org/ports.php?by=library&substr=gtk-osx-application-gtk3 gtk-osx-application-gtk3]
| N/A
| 2.0.8 ([[CompilingMacOsX|macOS only]])
|
|
|
|
|
|}

''* Tentative dependency''

* Pango 1.42.2 requires Harfbuzz 1.4.2
* Pango 1.44.0 requires Glib 2.59.2 and Harfbuzz 2.0. 1.44 exposes hb_font directly.
* Pango 1.45.1 requires Glib 2.60
* Pango 1.48.4 has vertical upright marks fix.
* Harfbuzz 4.1 changes glyph positioning for upright vertical text when font does not have vertical metrics (from glyph touching to of cell to being centered in cell).

''** Gtkmm4 requires API changed Glibmm, Cairomm, and Pangomm. In particular, enums use child namespaces in newer libraries (Cairo::FORMAT_ARGB32 -> Cairo::Surface::Format::ARGB32).''

''+ Decision at 5 Nov 2023 developer's meeting. Gtk4 4.10.1 has an important scrolling bug fix.''

== Distros ==

Note: This table is not relevant to (non-fink) MacOS X, where we ship the desired version with Inkscape.

"Inkscape" column is default or distro version / oldest that builds - latest that builds. If no latest is given then that means trunk is expected to build on the given platform.

e.g. for a distro that ships with 0.48 but should support building of trunk you might get:
0.48 / 0.47-

'''General rules:'''
* Support latest Debian Stable (as of feature freeze) [https://www.debian.org/distrib/packages Debian packages]
* Support latest Ubuntu LTS (as of feature freeze) [https://packages.ubuntu.com/ Ubuntu packages]
**e.g. Considering Inkscape 1.2, the latest Ubuntu LTS at '''feature freeze time''' (around February 2022) would have been Ubuntu 20.04. The latest LTS at release time (around May 2022), though, will be Ubuntu 22.04. Therefore, according to the rule, we should support Ubuntu 20.04 LTS as the minimum version.
** ''Note: For gtkmm4: Jammy: no package, Kinetic: 4.8, Lunar: 4.10, Mantic: 4.10''

* Support last two Fedora releases (as of feature freeze) [https://packages.fedoraproject.org/ Fedora packages]
* Don't break ''point'' releases.

{| class="wikitable"
|-
! Distro
! Inkscape
! gcc#
! clang#
! cairo
! cairomm
! freetype
! glib
! glibmm
! gtk+
! gtkmm
! harfbuzz
! pango
! poppler
! gdl
! lcms2
! libsigc++
! libgc 
! libsoup
|-
| Windows MSYS2 (2021-04-14) ([https://github.com/Alexpux/MINGW-packages mingw-w64 packages] from MSYS2 project)

| 1.0.2
| 10.2.0
| 11.0.0
| 1.17.4
| 1.12.2
| 2.10.4
| 2.68.1
| 2.66.0
| 3.24.27
| 3.24.3
| 2.8.0
| 1.48.4
| 20.12.1
| 3.34.0
| 2.12
| 2.10.6
| 8.0.4 
| 2.72.0
|-
| Debian 11 (Bullseye, oldstable) EOL 2026
| 1.0.2
| 10.2.1
| 13.0.1
| 1.16
| 1.12.2
| 2.10.4
| 2.66.8
| 2.64.2
| 3.24.24
| 3.24.2
| 2.7.4
| 1.46.2
| 20.09.0
| 3.34.0
| 2.12
| 2.10.4
| 8.0.4
| 2.72.0
|-
| Debian 12 (Bookworm, stable) EOL 2028?
| 1.2.2
| 12.2.0
| 15.0.6
| 1.16.0
| 1.12.1
| 2.10.4
| 2.74.5
| 2.74.0
| 3.24.36 4.8.3
| 3.24.7 4.8.0
| 6.0.0
| 1.50.12
| 22.12.0
| 3.40.0
| 2.14.1
| 2.12.0 3.4.0
| 8.2.2
| 2.74.03 3.2.2
|-
| Ubuntu 22.04 LTS (Jammy Jellyfish) EOL 2027-04
| 1.1.2
| 12.3.0
| 15.0.7
| 1.16.0
| 1.12.2
| 2.11.1
| 2.72.1
| 2.66.2
| 3.24.33 4.6.2
| 3.24.5 no libgtkmm-4.0
| 2.7.4
| 1.50.6
| 22.02.0
| 3.40.0
| 2.12-rc1
| 2.10.4
| 8.0.6
| 2.74.2 3.0.5
|-
| Ubuntu 23.10 (Mantic)
| 1.2.2
| 13.2.0
| 16.0.0 (17.0.2)
| 1.14.4 1.16.0
| 1.14.4 1.16.2
| 2.13.1
| 2.78.0
| 2.66.6 2.78.0
| 3.24.38 4.12.2
| 3.24.8 4.10.0
| 8.0.1
| 1.51.0 2.50.1
| 23.08.0
| 3.40.0
| 2.14.2
| 2.12.0 3.4.0
| 8.2.4
| 2.74.3 3.4.2
|-
| Ubuntu 24.04 LTS (Noble) EOL 2029-04
| 1.2.2
| 13.2.0
| 18.0.0 (18.1.3)
| 1.18.0
| 1.14.5 1.18.0
| 2.13.2
| 2.80.0
| 2.66.7 2.78.1
| 3.24.41 4.14.2
| 3.24.9 4.10.0
| 8.3.0
| 1.52.1 2.52.0
| 24.02.0
| 3.40.0
| 2.14.2
| 2.12.1 3.6.0
| 8.2.6
| 2.74.3 3.4.4
|}
#Debian and Ubuntu offer multiple gcc and clang versions, latest available version listed.

* Agreed to at Saarbrücken hackfest.

== Getting and Installing Source packages ==

See [https://inkscape.org/develop/getting-started/ Getting Started]

== Optional Dependencies ==

Inkscape will still compile without these, but some features may be missing if they are absent during compilation:

{| class="wikitable"
|-
! scope="col"| Library
! scope="col"| Needed for
! scope="col"| Default
|-
|aspell
|Dictionaries for spell checking
|On
|-
|libcdr
|Open Corel Draw files
|On
|-
|gettext/msgformat
|Translation support
|On
|-
|gtest/gmock
|Automatted testing
|Off
|-
|gspell
|Spell checking
|On
|-
|imagemagick
|Bitmap editing extensions, bitmap import resolution
|On
|-
|jpeg
|jpeg import?
|On
|-
|OpenMP
|Multi-threaded filter rendering
|On
|-
|scour
|Save as Optimized SVG
|(not needed during compiling, Python)
|-
|libvisio
|Open Visio Files, use Visio stencils
|On
|-
|libwpg
|Open WordPerfect Graphics
|On
|-
|}

[[Category:About Inkscape]]
[[Category:Developer Documentation]]

Hackfest2019 SCALE Attendees

2019-02-12T19:01:18Z

ScislaC: /* Unconfirmed but Likely 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/4, 3/5, 3/6, 3/7, 3/8, 3/9, 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
|-
| Josh Andler
| 3/4 - 3/11
|
|
|
|
|
|
|}

== Unconfirmed but Likely Attendees ==

* Tavmjong Bah
* Marc Jeanmougin
* Krzysztof Kosiński

== Maybe or Unknown ==

* Alex
* Jabier

Hackfest2019 SCALE Attendees

2019-02-12T19:00:27Z

ScislaC: /* 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/4, 3/5, 3/6, 3/7, 3/8, 3/9, 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
|-
| Josh Andler
| 3/4 - 3/11
|
|
|
|
|
|
|}

== Unconfirmed but Likely Attendees ==

* Tavmjong Bah
* Marc Jeanmougin
* Josh Andler
* Krzysztof Kosiński

== Maybe or Unknown ==

* Alex
* Jabier

Hackfest2019 SCALE Attendees

2019-01-14T03:14:38Z

ScislaC: /* Unconfirmed but Likely Attendees */

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

== Confirmed Attendees ==

== Unconfirmed but Likely Attendees ==

* Bryce Harrington
* Ryan Gorley
* Ted Gould
* Tavmjong Bah
* Marc Jeanmougin
* Josh Andler

== People to Invite ==

KK
Alex
Jabier

Hackfest2019 SCALE Attendees

2019-01-14T03:14:06Z

ScislaC: /* People to Invite */

Google Summer of Code

2017-02-10T01:23:56Z

ScislaC: /* Student Applications */

= 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.]

==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
** [[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]]

Tracking Dependencies

2016-11-10T02:11:58Z

ScislaC: Update dependencies removing Wiley as EOL and added Yakkety

== Overview ==

We need help getting our basic lib dependencies listed out and kept up to date. Also we need to track which versions of which distros have the needed dependencies.

To get glib and GTK+ dependencies figured out, people can go through the API documentation and look for the 'since' entries saying when calls were added. Then look for those calls in our source. Voila! we'll have base minimum dependencies figured out.

== Compilers ==

For C++11 features, see [[C++11]]

=== gcc ===
=== clang ===

== Libs ==

C++ bindings are not included, since their required versions match those of the C counterparts. Versions in parentheses refer to the dependencies for experimental Gtk+ 3 builds.

{| class="wikitable"
|-
! Library
! v 0.91
! trunk
|-
| Boehm-GC
| 7.1
| 7.2
|-
| Cairo
| 1.10
| 1.10
|-
| GDL
| N/A (3.34)
| N/A (3.4)
|-
| Glib
| 2.28
| 2.28
|-
| GTK+
| 2.24 (3.2)
| 2.24 (3.8)
|-
| GNU Scientific Library
| ?
| ?
|-
| LittleCMS
| 1.13
| 1.13
|-
| libxml
| ''2.6.11*''
| ''2.6.11*''
|-
| libxslt
| ''1.0.15*''
| ''1.0.15*''
|-
| Pango
| ?
| 1.24
|-
| Poppler
| ''0.5.9*''
| 0.20.0
|-
| libsigc++
| ''2.0.12*''
| ''2.0.12*''
|}

''* Tentative dependency''

== Distros ==

Note: This table is not relevant to (non-fink) MacOS X, where we ship the desired version with Inkscape.

"Inkscape" column is default or distro version / oldest that builds - latest that builds. If no latest is given then that means trunk is expected to build on the given platform.

e.g. for a distro that ships with 0.48 but should support building of trunk you might get:
0.48 / 0.47-

{| class="wikitable"
|-
! Distro
! Inkscape
! gcc
! clang
! cairo
! cairomm
! glib
! glibmm
! gtk+
! gtkmm
! pango
! poppler
! gdl
! lcms
! libsigc++
! libgc 
|-
| style="background:Violet;"|Windows Devlibs (32bit) [https://code.launchpad.net/~inkscape.dev/inkscape-devlibs/trunk] (r53)
|
|
|
| 1.11.2
| 1.10.0
| 2.28.8
| 2.28.2
| style="background:Violet;"| 2.24.10
| style="background:Violet;"| 2.24.2
| 1.28.3
| 0.39.0
| style="background:Violet;"| (none)
| 1.17 2.4
| 2.2.11
| 7.4.2
|-
| Windows Devlibs Gtk+ 3 branch [https://code.launchpad.net/~inkscape.dev/inkscape-devlibs/devlibs-gtk3] (r34)
|
|
|
| 1.10.2
| 1.10.0
| 2.38.0
| 2.36.0
| 2.24.18 3.8.1
| 2.24.2 3.8.0
| 1.34.0
| 0.22.5
| 3.4.2
| 1.19 2.4
| 2.2.10
| 7.2d
|-
| Windows Devlibs 64bit [https://code.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk] (r17)
|
|
|
| 1.14.1
| 1.11.2
| 2.40.0
| 2.40.0
| 2.24.23 3.13.1
| 2.24.4 3.12.0
| 1.36.3
| 0.24.2
| 3.12.0
| - 2.6
| 2.3.1
| 7.2
|-
| Debian 8.2.0 (Jessie, stable)
| 0.48.5
| 4.9.2
| 3.5
| 1.14.0
| 1.10.0
| 2.42.1
| 2.42.0
| 2.24.25 3.14.5
| 2.24.4 3.14.0
| 1.36.8
| 0.26.5
| 3.14.0
| 2.6
| 2.4.0
| 7.2d
|-
| style="background:Violet;"|RHEL / CentOS / Scientific Linux 7.x
| 0.48
| 4.8.3
| X
| 1.12.14
| 1.10.0
| 2.40.0
| 2.36.2
| 2.24.22 3.8.8
| 2.24.2 3.8.1
| 1.34.1
| 0.22.5
| style="background:Violet;"|X
| 2.5.4
| 2.3.1
| 7.2d
|-
| style="background:Red;"|Ubuntu 12.04 LTS (Precise) EOL 2017-04
| 0.48.3
| 4.6.3
| (U 3.4)
| 1.10.2
| 1.10.0
| 2.32.4
| 2.32.0
| 2.24.10 3.4.2
| 2.24.2 3.4.0
| 1.30.0
| style="background:Red;"|0.18.4
| 3.3.91
| 1.19 2.2
| 2.2.10
| style="background:Red;"|7.1
|-
| Ubuntu 14.04 (Trusty) EOL 2019-04
| 0.48.4
| 4.8.2
| (U 3.5)
| 1.13.0
| 1.10.0
| 2.40.2
| 2.39.93
| 2.24.23 3.10.8
| 2.24.4 3.10.1
| 1.36.3
| 0.24.5
| 3.8.1
| 1.19 2.5
| 2.2.10
| 7.2d
|-
| Ubuntu 16.04 (Xenial) EOL 2021-04)
| 0.91.0
| 5.3.1
| 3.8
| 1.14.6
| 1.12.0
| 2.48.0
| 2.46.3
| 2.24.30 3.18.9
| 2.24.4 3.18.0
| 1.38.1
| 0.41.0
| 3.18.0
| 2.6
| 2.6.2
| 7.4.2
|-
| Ubuntu 16.10 (Yakkety) EOL 2017-07)
| 0.91.0
| 5.4.1
| 3.8
| 1.14.6
| 1.12.0
| 2.50.0
| 2.48.1
| 2.24.30 3.20.9
| 2.24.5 3.20.1
| 1.40.1
| 0.44.0
| 3.22.0
| 2.7
| 2.8.0
| 7.4.2
|}

{| class="wikitable"
|-
! Legend
|-
| style="background:Red;"| Inkscape stable unsupported
|-
| style="background:Orange;"| Inkscape trunk unsupported
|-
| style="background:Violet;"| GTK+ 3 builds unsupported
|}

== Getting and Installing Source packages ==

If your distro does not have some packages available (like many don't, ie, Fedora Core 2), you must often download
source packages and build and install them yourself. Actually this is not that hard, and is similar to
doing a Gentoo 'emerge.'

* Usually you download a file with a name like somepackage-1.0.tar.gz. Unpack it with

$ tar zxf somepackage-1.0.tar.gz
or
$ tar jxf somepackage-1.0.tar.bz2

* Then 'cd' into the new directory.

* Configure it with the command:

$ ./configure

* Build it with:

$ make

* As the 'root' user, install it with:

# make install

=== Boehm-GC ===

Source: http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source

* Download this file:
** http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/gc6.8.tar.gz
* Unpack it
** tar zxf gc6.8.tar.gz
* Configure and build it
** cd gc6.8
** ./configure --disable-shared --enable-static
** make
* Install it
** su (or however else you become root)
** make install

Binaries: If searching for a package for GC, the name of it is sometimes:

* gc
* libgc
* gc-devel
* libgc-devel
* boehm-gc (on Gentoo)
* debian/ubuntu: sudo apt-get install libgc-dev

=== libSigc++ ===

Source: http://ftp.gnome.org/pub/GNOME/sources/libsigc++/2.2/libsigc++-2.2.3.tar.bz2

With this file, and for GlibMM and GtkMM below, it is usually desirable for us developers to
build this C++ library statically. This removes a dependency that might be difficult for an
end-user during installation. Configure it with:

./configure --enable-static --disable-shared

=== GlibMM ===
Try to match your Glib2 version with GlibMM's version. For example, if your Glib2 is 2.16.6, download glibmm-2.16.4.tar.bz2.

Latest source: http://ftp.gnome.org/pub/GNOME/sources/glibmm/

=== GtkMM ===
Usually you can try the latest version of GtkMM, but if you get version mismatch errors, try older releases.

Source: http://ftp.gnome.org/pub/GNOME/sources/gtkmm/2.12/gtkmm-2.12.7.tar.bz2

=== cairomm ===

if you got prompted about cairomm, try first solve your cairo version, so you can grab [http://www.cairographics.org/releases/ there] a compatible version.

=== Boost ===

Many users have reported when building from source that after installing the above dependencies, the configure script still requires a "boost" package. It can be found below, but even after installing, you will need to create a symlink to allow the configure script to find it:

ln -s /usr/local/include/boost_1_xx_x/boost /usr/local/include/boost

Source: http://www.boost.org/users/download/

=== Poppler ===

Source: http://poppler.freedesktop.org/

Poppler is required for PDF import. There are several potential issues:
* Some Linux distributions do not ship the Xpdf headers required by Inkscape. In such cases, you need to recompile Poppler, passing --enable-xpdf-headers on the configure line or install the libpoppler-private-dev package. See [https://bugs.launchpad.net/inkscape/+bug/254849 this wishlist bug]. This typically manifests in error messages like this:
<pre>In file included from extension/internal/pdfinput/svg-builder.cpp:19:
extension/internal/pdfinput/svg-builder.h:32:23: error: CharTypes.h: No such file or directory
...
make[2]: *** [extension/internal/pdfinput/svg-builder.o] Error 1
make[2]: Leaving directory `/tmp/build/inkscape-0.46/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/build/inkscape-0.46'
make: *** [all] Error 2</pre>
* Inkscape 0.47 does not compile with Poppler >= 0.12.2. If you need to compile Inkscape on such systems, use the development version from Bazaar, where this bug is fixed. See [https://bugs.launchpad.net/inkscape/+bug/487038 the bug report] for details and a minimal patch.
* Inkscape compiled with Poppler <= 0.12.1 will run on systems with Poppler >= 0.12.2, but the PDF import function will crash instantly. This problem does not concern Windows users, since the correct Poppler version is contained in the Windows installer package. This cannot be fixed on Inkscape's side: those two versions of Poppler are not ABI compatible, yet share the same soname. See [https://bugs.launchpad.net/inkscape/+bug/258504 this bug] for more details.
* Poppler's Xpdf headers are not guaranteed to be API-compatible between releases. It's likely that future Poppler versions will break PDF import in some way. PDF import works at least up to 0.12.4 but might not work with later versions.

[[Category:About Inkscape]]
[[Category:Developer Documentation]]

Tracking Dependencies

2016-05-12T00:55:20Z

ScislaC: /* Distros */ - Update Xenial deps

== Overview ==

We need help getting our basic lib dependencies listed out and kept up to date. Also we need to track which versions of which distros have the needed dependencies.

To get glib and GTK+ dependencies figured out, people can go through the API documentation and look for the 'since' entries saying when calls were added. Then look for those calls in our source. Voila! we'll have base minimum dependencies figured out.

== Compilers ==

For C++11 features, see [[C++11]]

=== gcc ===
=== clang ===

== Libs ==

C++ bindings are not included, since their required versions match those of the C counterparts. Versions in parentheses refer to the dependencies for experimental Gtk+ 3 builds.

{| class="wikitable"
|-
! Library
! v 0.91
! trunk
|-
| Boehm-GC
| 7.1
| 7.2
|-
| Cairo
| 1.10
| 1.10
|-
| GDL
| N/A (3.34)
| N/A (3.4)
|-
| Glib
| 2.28
| 2.28
|-
| GTK+
| 2.24 (3.2)
| 2.24 (3.8)
|-
| GNU Scientific Library
| ?
| ?
|-
| LittleCMS
| 1.13
| 1.13
|-
| libxml
| ''2.6.11*''
| ''2.6.11*''
|-
| libxslt
| ''1.0.15*''
| ''1.0.15*''
|-
| Pango
| ?
| 1.24
|-
| Poppler
| ''0.5.9*''
| 0.20.0
|-
| libsigc++
| ''2.0.12*''
| ''2.0.12*''
|}

''* Tentative dependency''

== Distros ==

Note: This table is not relevant to (non-fink) MacOS X, where we ship the desired version with Inkscape.

"Inkscape" column is default or distro version / oldest that builds - latest that builds. If no latest is given then that means trunk is expected to build on the given platform.

e.g. for a distro that ships with 0.48 but should support building of trunk you might get:
0.48 / 0.47-

{| class="wikitable"
|-
! Distro
! Inkscape
! gcc
! clang
! cairo
! cairomm
! glib
! glibmm
! gtk+
! gtkmm
! pango
! poppler
! gdl
! lcms
! libsigc++
! libgc 
|-
| style="background:Violet;"|Windows Devlibs (32bit) [https://code.launchpad.net/~inkscape.dev/inkscape-devlibs/trunk] (r53)
|
|
|
| 1.11.2
| 1.10.0
| 2.28.8
| 2.28.2
| style="background:Violet;"| 2.24.10
| style="background:Violet;"| 2.24.2
| 1.28.3
| 0.39.0
| style="background:Violet;"| (none)
| 1.17 2.4
| 2.2.11
| 7.4.2
|-
| Windows Devlibs Gtk+ 3 branch [https://code.launchpad.net/~inkscape.dev/inkscape-devlibs/devlibs-gtk3] (r34)
|
|
|
| 1.10.2
| 1.10.0
| 2.38.0
| 2.36.0
| 2.24.18 3.8.1
| 2.24.2 3.8.0
| 1.34.0
| 0.22.5
| 3.4.2
| 1.19 2.4
| 2.2.10
| 7.2d
|-
| Windows Devlibs 64bit [https://code.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk] (r17)
|
|
|
| 1.14.1
| 1.11.2
| 2.40.0
| 2.40.0
| 2.24.23 3.13.1
| 2.24.4 3.12.0
| 1.36.3
| 0.24.2
| 3.12.0
| - 2.6
| 2.3.1
| 7.2
|-
| Debian 8.2.0 (Jessie, stable)
| 0.48.5
| 4.9.2
| 3.5
| 1.14.0
| 1.10.0
| 2.42.1
| 2.42.0
| 2.24.25 3.14.5
| 2.24.4 3.14.0
| 1.36.8
| 0.26.5
| 3.14.0
| 2.6
| 2.4.0
| 7.2d
|-
| style="background:Violet;"|RHEL / CentOS / Scientific Linux 7.x
| 0.48
| 4.8.3
| X
| 1.12.14
| 1.10.0
| 2.40.0
| 2.36.2
| 2.24.22 3.8.8
| 2.24.2 3.8.1
| 1.34.1
| 0.22.5
| style="background:Violet;"|X
| 2.5.4
| 2.3.1
| 7.2d
|-
| style="background:Red;"|Ubuntu 12.04 LTS (Precise) EOL 2017-04
| 0.48.3
| 4.6.3
| (U 3.4)
| 1.10.2
| 1.10.0
| 2.32.4
| 2.32.0
| 2.24.10 3.4.2
| 2.24.2 3.4.0
| 1.30.0
| style="background:Red;"|0.18.4
| 3.3.91
| 1.19 2.2
| 2.2.10
| style="background:Red;"|7.1
|-
| Ubuntu 14.04 (Trusty) EOL 2019-04
| 0.48.4
| 4.8.2
| (U 3.5)
| 1.13.0
| 1.10.0
| 2.40.2
| 2.39.93
| 2.24.23 3.10.8
| 2.24.4 3.10.1
| 1.36.3
| 0.24.5
| 3.8.1
| 1.19 2.5
| 2.2.10
| 7.2d
|-
| Ubuntu 15.10 (Wiley) EOL 2016-07
| 0.91.0
| 5.2.1
| 3.6
| 1.14.2
| 1.11.2
| 2.46.1
| 2.45.41
| 2.24.28 3.16.7
| 2.24.4 3.16.0
| 1.36.8
| 0.33.0
| 3.16.0
| 2.6
| 2.4.1
| 7.2d
|-
| Ubuntu 16.04 (Xenial) EOL 2021-04)
| 0.91.0
| 5.3.1
| 3.8
| 1.14.6
| 1.12.0
| 2.48.0
| 2.46.3
| 2.24.30 3.18.9
| 2.24.4 3.18.0
| 1.38.1
| 0.41.0
| 3.18.0
| 2.6
| 2.6.2
| 7.4.2
|}

{| class="wikitable"
|-
! Legend
|-
| style="background:Red;"| Inkscape stable unsupported
|-
| style="background:Orange;"| Inkscape trunk unsupported
|-
| style="background:Violet;"| GTK+ 3 builds unsupported
|}

== Getting and Installing Source packages ==

If your distro does not have some packages available (like many don't, ie, Fedora Core 2), you must often download
source packages and build and install them yourself. Actually this is not that hard, and is similar to
doing a Gentoo 'emerge.'

* Usually you download a file with a name like somepackage-1.0.tar.gz. Unpack it with

$ tar zxf somepackage-1.0.tar.gz
or
$ tar jxf somepackage-1.0.tar.bz2

* Then 'cd' into the new directory.

* Configure it with the command:

$ ./configure

* Build it with:

$ make

* As the 'root' user, install it with:

# make install

=== Boehm-GC ===

Source: http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source

* Download this file:
** http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/gc6.8.tar.gz
* Unpack it
** tar zxf gc6.8.tar.gz
* Configure and build it
** cd gc6.8
** ./configure --disable-shared --enable-static
** make
* Install it
** su (or however else you become root)
** make install

Binaries: If searching for a package for GC, the name of it is sometimes:

* gc
* libgc
* gc-devel
* libgc-devel
* boehm-gc (on Gentoo)
* debian/ubuntu: sudo apt-get install libgc-dev

=== libSigc++ ===

Source: http://ftp.gnome.org/pub/GNOME/sources/libsigc++/2.2/libsigc++-2.2.3.tar.bz2

With this file, and for GlibMM and GtkMM below, it is usually desirable for us developers to
build this C++ library statically. This removes a dependency that might be difficult for an
end-user during installation. Configure it with:

./configure --enable-static --disable-shared

=== GlibMM ===
Try to match your Glib2 version with GlibMM's version. For example, if your Glib2 is 2.16.6, download glibmm-2.16.4.tar.bz2.

Latest source: http://ftp.gnome.org/pub/GNOME/sources/glibmm/

=== GtkMM ===
Usually you can try the latest version of GtkMM, but if you get version mismatch errors, try older releases.

Source: http://ftp.gnome.org/pub/GNOME/sources/gtkmm/2.12/gtkmm-2.12.7.tar.bz2

=== cairomm ===

if you got prompted about cairomm, try first solve your cairo version, so you can grab [http://www.cairographics.org/releases/ there] a compatible version.

=== Boost ===

Many users have reported when building from source that after installing the above dependencies, the configure script still requires a "boost" package. It can be found below, but even after installing, you will need to create a symlink to allow the configure script to find it:

ln -s /usr/local/include/boost_1_xx_x/boost /usr/local/include/boost

Source: http://www.boost.org/users/download/

=== Poppler ===

Source: http://poppler.freedesktop.org/

Poppler is required for PDF import. There are several potential issues:
* Some Linux distributions do not ship the Xpdf headers required by Inkscape. In such cases, you need to recompile Poppler, passing --enable-xpdf-headers on the configure line or install the libpoppler-private-dev package. See [https://bugs.launchpad.net/inkscape/+bug/254849 this wishlist bug]. This typically manifests in error messages like this:
<pre>In file included from extension/internal/pdfinput/svg-builder.cpp:19:
extension/internal/pdfinput/svg-builder.h:32:23: error: CharTypes.h: No such file or directory
...
make[2]: *** [extension/internal/pdfinput/svg-builder.o] Error 1
make[2]: Leaving directory `/tmp/build/inkscape-0.46/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/build/inkscape-0.46'
make: *** [all] Error 2</pre>
* Inkscape 0.47 does not compile with Poppler >= 0.12.2. If you need to compile Inkscape on such systems, use the development version from Bazaar, where this bug is fixed. See [https://bugs.launchpad.net/inkscape/+bug/487038 the bug report] for details and a minimal patch.
* Inkscape compiled with Poppler <= 0.12.1 will run on systems with Poppler >= 0.12.2, but the PDF import function will crash instantly. This problem does not concern Windows users, since the correct Poppler version is contained in the Windows installer package. This cannot be fixed on Inkscape's side: those two versions of Poppler are not ABI compatible, yet share the same soname. See [https://bugs.launchpad.net/inkscape/+bug/258504 this bug] for more details.
* Poppler's Xpdf headers are not guaranteed to be API-compatible between releases. It's likely that future Poppler versions will break PDF import in some way. PDF import works at least up to 0.12.4 but might not work with later versions.

[[Category:About Inkscape]]
[[Category:Developer Documentation]]

Google Summer of Code

2016-02-19T01:11:18Z

ScislaC: /* Student Applications */

= 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 2014 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
* 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]]

Leadership Committee Status Updates

2016-01-09T00:07:59Z

ScislaC: /* Minutes */

== Place and Time ==

We meet in #inkscape-devel on [https://freenode.net/ freenode].

Everybody in the Inkscape community is invited to participate.

Next meeting: [http://www.timeanddate.com/worldclock/fixedtime.html?month=12&day=4&year=2015&hour=20&min=00&sec=0&p1=0 Noon PDT/21:00 CEST], Fri, Dec 4th.

Meetings should be announced in advance on [https://lists.sourceforge.net/lists/listinfo/inkscape-devel inkscape-devel] and [https://lists.sourceforge.net/lists/listinfo/inkscape-board inkscape-board] mailing lists.

== Agenda ==

=== Action Items from December Meeting ===
* Ensure KK and Alex discuss sponsor recognition [Tav]
* Invite Alex to make a proposal for Leeds [bryce]
* Get Project Suggestions list ready for GSoC [bryce]
* Draft budget [bryce]
** Increase Hackfest by 50%
** Increase funds for Other Events
* Do a vote for another OSUOSL donation [bryce]
√ Post meeting minutes [bryce]
* New agenda for next month [bryce]

=== For January 8th ===

* Code of Conduct (final review)
* Budget 2016 [bryce]
* Sponsorship levels [kk]
* [[Hackfest2016|Hackfest 2016]]: Leeds [alex]
* [https://inkscape.org/en/support-us/funded-development/ Funded development] [bryce]
* GSoC 2016 [scislac]
* Other Business

=== Past Agenda Items Still Open ===

* Privacy Policy [drmo]

=== Proposed New Agenda Items ===

* C++11 [alex]
* Licensing issues (GPL v2+) [kk]

== Minutes ==

* Meeting 2014-09-15: notes https://inkscape.org/gallery/item/392/
* Meeting 2014-09-29: notes https://inkscape.org/gallery/item/854/
* Meeting 2014-10-08: notes https://inkscape.org/gallery/item/950/
* Meeting 2014-10-15: notes https://inkscape.org/gallery/item/1436/
* Meeting 2014-11-05: notes https://inkscape.org/gallery/item/2204/
* Meeting 2014-11-12: notes https://inkscape.org/gallery/item/2210/
* Meeting 2014-11-19: notes https://inkscape.org/gallery/item/2216/
* Meeting 2014-11-26: notes https://inkscape.org/gallery/item/2498/
* Meeting 2015-10-02: notes https://inkscape.org/gallery/item/6701/
* Meeting 2015-11-06: notes https://inkscape.org/gallery/item/6886/
* Meeting 2015-12-04: notes https://inkscape.org/gallery/item/7056/
* Meeting 2016-01-08: notes https://inkscape.org/gallery/item/7276/

Leadership Committee Status Updates

2015-11-06T22:32:37Z

ScislaC: /* Minutes */

Tracking Dependencies

2015-09-28T19:01:12Z

ScislaC: /* Distros */

== Overview ==

We need help getting our basic lib dependencies listed out and kept up to date. Also we need to track which versions of which distros have the needed dependencies.

To get glib and GTK+ dependencies figured out, people can go through the API documentation and look for the 'since' entries saying when calls were added. Then look for those calls in our source. Voila! we'll have base minimum dependencies figured out.

== Compilers ==

For C++11 features, see [[C++11]]

=== gcc ===
=== clang ===

== Libs ==

C++ bindings are not included, since their required versions match those of the C counterparts.

{| class="wikitable"
|-
! Library
! v 0.91
! trunk
! trunk (GTK+ 3.0 build)
|-
| Boehm-GC
| 7.1
| 7.1
| 7.1
|-
| Cairo
| 1.10
| 1.10
| 1.10
|-
| GDL
| N/A
| N/A
| 3.3.4
|-
| Glib
| 2.28
| 2.28
| 2.28
|-
| GTK+
| 2.24
| 2.24
| 3.2
|-
| GNU Scientific Library
| ?
| ?
| ?
|-
| LittleCMS
| 1.13
| 1.13
| 1.13
|-
| libxml
| ''2.6.11*''
| ''2.6.11*''
| ''2.6.11*''
|-
| libxslt
| ''1.0.15*''
| ''1.0.15*''
| ''1.0.15*''
|-
| Pango
| ?
| ?
| 1.24
|-
| Poppler
| ''0.5.9*''
| 0.8.3
| 0.8.3
|-
| libsigc++
| ''2.0.12*''
| ''2.0.12*''
| ''2.0.12*''
|}

''* Tentative dependency''

== Distros ==

Note: This table is not relevant to (non-fink) MacOS X, where we ship the desired version with Inkscape.

"Inkscape" column is default or distro version / oldest that builds - latest that builds. If no latest is given then that means trunk is expected to build on the given platform.

e.g. for a distro that ships with 0.48 but should support building of trunk you might get:
0.48 / 0.47-

{| class="wikitable"
|-
! Distro
! Inkscape
! gcc
! clang
! cairo
! cairomm
! glib
! glibmm
! gtk+
! gtkmm
! pango
! poppler
! gdl
! lcms
! libsigc++
! libgc 
|-
| style="background:Violet;"|Windows Devlibs (32bit) [https://code.launchpad.net/~inkscape.dev/inkscape-devlibs/trunk] (r53)
|
|
|
| 1.11.2
| 1.10.0
| 2.28.8
| 2.28.2
| style="background:Violet;"| 2.24.10
| style="background:Violet;"| 2.24.2
| 1.28.3
| 0.12.1
| style="background:Violet;"| (none)
| 1.17 2.4
| 2.2.11
| 7.1
|-
| Windows Devlibs Gtk+ 3 branch [https://code.launchpad.net/~inkscape.dev/inkscape-devlibs/devlibs-gtk3] (r34)
|
|
|
| 1.10.2
| 1.10.0
| 2.38.0
| 2.36.0
| 2.24.18 3.8.1
| 2.24.2 3.8.0
| 1.34.0
| 0.22.5
| 3.4.2
| 1.19 2.4
| 2.2.10
| 7.2d
|-
| Windows Devlibs 64bit [https://code.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk] (r17)
|
|
|
| 1.14.1
| 1.11.2
| 2.40.0
| 2.40.0
| 2.24.23 3.13.1
| 2.24.4 3.12.0
| 1.36.3
| 0.24.2
| 3.12.0
| - 2.6
| 2.3.1
| 7.2
|-
| Debian 7.0 (Wheezy, stable)
|
|
|
| 1.12.2
| 1.10.0
| 2.33.12
| 2.32.1
| 2.24.10 3.4.2
| 2.24.2 3.4.2
| 1.32.5
| 0.18.4
| 3.4.2
| 1.19 2.2
| 2.2.10
| 7.1
|-
| style="background:Red;" | RHEL / CentOS / Scientific Linux 5.x
|
| 4.1.2
| X
| 1.2.4
| X
| 2.12.3
| X
| 2.10.4
| X
| 1.14.9
| 0.5.4
| X
| 1.18
| X
| X
|-
| RHEL / CentOS / Scientific Linux 6.x
| 0.47
| 4.4.7
| X
| 1.8.8
| 1.8.0
| 2.28.8
| 2.22
| 2.24.23
| 2.18.2
| 1.28.1
| 0.12.4
| X
| 1.19
| 2.2.4.2
| 7.1
|-
| RHEL / CentOS / Scientific Linux 7.x
| 0.48
| 4.8.3
| X
| 1.12.14
| 1.10.0
| 2.40.0
| 2.36.2
| 2.24.22 3.8.8
| 2.24.2 3.8.1
| 1.34.1
| 0.22.5
| X
| 2.5.4
| 2.3.1
| 7.2d
|-
| Fedora 20
| 0.91
| 4.8.3
| 3.4
| 1.13.1+git
| 1.10.0
| 2.38.2
| 2.38.1
| 2.24.22 3.10.6
| 2.24.4 3.10.1
| 1.36.1
| 0.24.3
| 3.10.0
| 1.19 2.5
| 2.3.1
| 7.2d
|-
| OpenSuSE 13.1 EOL 2015-05-01[http://en.opensuse.org/Lifetime]
| 0.48.4
| 4.8.2
| 3.3
| 1.12.16
| 1.10.0
| 2.38.1
| 2.38.0
| 2.24.22 3.10.2
| 2.24.4 3.10.0
| 1.36.0
| 0.24.3
| 3.10.0
| 1.19 2.5
| 2.3.1
| 7.2d
|-
| Ubuntu 12.04 LTS (Precise) EOL 2017-04
| 0.48.3
| 4.6.3
| (U 3.4)
| 1.10.2
| 1.10.0
| 2.32.4
| 2.32.0
| 2.24.10 3.4.2
| 2.24.2 3.4.0
| 1.30.0
| 0.18.4
| 3.3.91
| 1.19 2.2
| 2.2.10
| 7.1
|-
| Ubuntu 14.04 (Trusty) EOL 2019-04
| 0.48.4
| 4.8.2
| (U 3.5)
| 1.13.0
| 1.10.0
| 2.40.2
| 2.39.93
| 2.24.23 3.10.8
| 2.24.4 3.10.1
| 1.36.3
| 0.24.5
| 3.8.1
| 1.19 2.5
| 2.2.10
| 7.2d
|-
| Ubuntu 15.04 (Vivid) EOL 2016-01
| 0.91.0
| 4.9.2
| 3.6
| 1.14.2
| 1.11.2
| 2.44.1
| 2.42.0
| 2.24.27 3.14.13
| 2.24.4 3.14.0
| 1.36.8
| 0.30.0
| 3.14.0
| 2.6
| 2.4.0
| 7.2d
|-
| Ubuntu 15.10 (Wiley) (As of 2015-09-28), EOL 2016-07
| 0.91.0
| 5.2.1
| 3.6
| 1.14.2
| 1.11.2
| 2.46.0
| 2.44.0
| 2.24.28 3.16.7
| 2.24.4 3.16.0
| 1.36.8
| 0.33.0
| 3.16.0
| 2.6
| 2.4.1
| 7.2d
|}

{| class="wikitable"
|-
! Legend
|-
| style="background:Red;"| Inkscape stable unsupported
|-
| style="background:Orange;"| Inkscape trunk unsupported
|-
| style="background:Violet;"| GTK+ 3 builds unsupported
|}

== Getting and Installing Source packages ==

If your distro does not have some packages available (like many don't, ie, Fedora Core 2), you must often download
source packages and build and install them yourself. Actually this is not that hard, and is similar to
doing a Gentoo 'emerge.'

* Usually you download a file with a name like somepackage-1.0.tar.gz. Unpack it with

$ tar zxf somepackage-1.0.tar.gz
or
$ tar jxf somepackage-1.0.tar.bz2

* Then 'cd' into the new directory.

* Configure it with the command:

$ ./configure

* Build it with:

$ make

* As the 'root' user, install it with:

# make install

=== Boehm-GC ===

Source: http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source

* Download this file:
** http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/gc6.8.tar.gz
* Unpack it
** tar zxf gc6.8.tar.gz
* Configure and build it
** cd gc6.8
** ./configure --disable-shared --enable-static
** make
* Install it
** su (or however else you become root)
** make install

Binaries: If searching for a package for GC, the name of it is sometimes:

* gc
* libgc
* gc-devel
* libgc-devel
* boehm-gc (on Gentoo)
* debian/ubuntu: sudo apt-get install libgc-dev

=== libSigc++ ===

Source: http://ftp.gnome.org/pub/GNOME/sources/libsigc++/2.2/libsigc++-2.2.3.tar.bz2

With this file, and for GlibMM and GtkMM below, it is usually desirable for us developers to
build this C++ library statically. This removes a dependency that might be difficult for an
end-user during installation. Configure it with:

./configure --enable-static --disable-shared

=== GlibMM ===
Try to match your Glib2 version with GlibMM's version. For example, if your Glib2 is 2.16.6, download glibmm-2.16.4.tar.bz2.

Latest source: http://ftp.gnome.org/pub/GNOME/sources/glibmm/

=== GtkMM ===
Usually you can try the latest version of GtkMM, but if you get version mismatch errors, try older releases.

Source: http://ftp.gnome.org/pub/GNOME/sources/gtkmm/2.12/gtkmm-2.12.7.tar.bz2

=== cairomm ===

if you got prompted about cairomm, try first solve your cairo version, so you can grab [http://www.cairographics.org/releases/ there] a compatible version.

=== Boost ===

Many users have reported when building from source that after installing the above dependencies, the configure script still requires a "boost" package. It can be found below, but even after installing, you will need to create a symlink to allow the configure script to find it:

ln -s /usr/local/include/boost_1_xx_x/boost /usr/local/include/boost

Source: http://www.boost.org/users/download/

=== Poppler ===

Source: http://poppler.freedesktop.org/

Poppler is required for PDF import. There are several potential issues:
* Some Linux distributions do not ship the Xpdf headers required by Inkscape. In such cases, you need to recompile Poppler, passing --enable-xpdf-headers on the configure line or install the libpoppler-private-dev package. See [https://bugs.launchpad.net/inkscape/+bug/254849 this wishlist bug]. This typically manifests in error messages like this:
<pre>In file included from extension/internal/pdfinput/svg-builder.cpp:19:
extension/internal/pdfinput/svg-builder.h:32:23: error: CharTypes.h: No such file or directory
...
make[2]: *** [extension/internal/pdfinput/svg-builder.o] Error 1
make[2]: Leaving directory `/tmp/build/inkscape-0.46/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/build/inkscape-0.46'
make: *** [all] Error 2</pre>
* Inkscape 0.47 does not compile with Poppler >= 0.12.2. If you need to compile Inkscape on such systems, use the development version from Bazaar, where this bug is fixed. See [https://bugs.launchpad.net/inkscape/+bug/487038 the bug report] for details and a minimal patch.
* Inkscape compiled with Poppler <= 0.12.1 will run on systems with Poppler >= 0.12.2, but the PDF import function will crash instantly. This problem does not concern Windows users, since the correct Poppler version is contained in the Windows installer package. This cannot be fixed on Inkscape's side: those two versions of Poppler are not ABI compatible, yet share the same soname. See [https://bugs.launchpad.net/inkscape/+bug/258504 this bug] for more details.
* Poppler's Xpdf headers are not guaranteed to be API-compatible between releases. It's likely that future Poppler versions will break PDF import in some way. PDF import works at least up to 0.12.4 but might not work with later versions.

[[Category:About Inkscape]]
[[Category:Developer Documentation]]

Hackfest2015 Attendees

2015-04-09T22:11:27Z

ScislaC: /* Who is Attending? */

Information about and for Hackfest2015 Attendees

Other pages: [[Hackfest2015|Hackfest 2015]], [[Hackfest2015 Topics]].

== Who is Attending? ==

{| class="wikitable"
|+ List of Attendees
Hackfest
|-
! rowspan="2" | Who
! colspan="2" | Dates
! colspan="2" | Allocation
! colspan="2" | Flights
! rowspan="2" | Hotel
|-
! Hackfest
! LGM
! Hackfest
! LGM
! Arrival
! Departure
|-
| Bryce Harrington
| 4/26, 4/27, 4/28
| 4/29, 4/30, 5/1, 5/2
| Sponsored1
| Sponsored1
| UA0843 YYZ @ 8:13pm
| UA5165 YYZ @ 10:10am
| Courtyard Downtown Marriott
|-
| Tavmjong Bah
| 4/26, 4/27, 4/28
| 4/29, 4/30, 5/1
| $2000
| $500
| AF356 YYZ @ 4:10pm
| AF352 YYZ @ 6:35pm (on 1st)
| AirBnB (126 Harbord St.)
|-
| Jon Cruz
| --
| 4/29, 4/30, 5/1, 5/2
| N/A
| Sponsored1
|
|
|
|-
| Josh Andler
| 4/26, 4/27, 4/28
| 4/29, 4/30, 5/1, 5/2
| $5002
| $500
| AC1038 YYZ @ 4:24pm
| AC755 YYZ @ 12:05pm
| AirBnB (13 Glenbaillie Pl.)
|-
| Martin Owens
| 4/26, 4/27, 4/28
| 4/29, 4/30, 5/1, 5/2
| $2000
| $500
| PD942 YTZ @ 2:50PM
| PD945 YTZ @ 2:35PM
| None Yet
|-
| Jabiertxo Arraiza Cenoz
| 4/26, 4/27, 4/28
| 4/29, 4/30, 5/1, 5/2
| $1000
| $500
| KLM695 YYZ @ 8:05PM
| DL2320 YYZ @ 3:00PM
|-
| Krzysztof Kosiński
| 4/26, 4/27, 4/28
| --
| $2000
| N/A
| LH470 YYZ @ 4:40PM, 4/23
| OS72 YYZ @ 5:55PM, 4/28
| Canadiana Backpackers Inn
|-
| Alex Valavanis
| 4/26, 4/27, 4/28
|
| $2000
| N/A
|
|
|
|-
| Inkscaper
|
|
|
|
|
|
|
|-
! Total
!
!
! $9500
! $2000
!
!
!
|}

1 Sponsered by outside organization.
2 Flight sponsered 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, 2015.

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

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 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.

Most international flights arrive at Pearson International Airport (YYZ). Some Canadian and US flights arrive at Billy Bishop Toronto City Airport (YTZ).

See also: [http://libregraphicsmeeting.org/2015/travel/ LGM Travel page].

=== Hotel ===

The [http://libregraphicsmeeting.org/2015/travel/accommodation/ LGM Accommodation page] is pretty sparse. The AirBnB suggestion is worth looking into (I paid 1/3 of what a hotel would cost in Sydney using AirBnB). If you are interested in sharing a room (US/Canadian hotel rooms are usually quite big, often with two queen size beds) leave a note here:

=== Venue ===

The hackfest will take place in room 1150 on the first floor of [http://www.openstreetmap.org/#map=19/43.66439/-79.39981 Robarts Library] (130 St. George St.).

A map of the U. of Toronto campus can be found on the [http://libregraphicsmeeting.org/2015/venue/ LGM Venue page].

== 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).

Tracking Dependencies

2015-04-06T17:29:49Z

ScislaC: /* Distros */

== Overview ==

We need help getting our basic lib dependencies listed out and kept up to date. Also we need to track which versions of which distros have the needed dependencies.

To get glib and GTK+ dependencies figured out, people can go through the API documentation and look for the 'since' entries saying when calls were added. Then look for those calls in our source. Voila! we'll have base minimum dependencies figured out.

== Compilers ==

For C++11 features, see [[C++11]]

=== gcc ===
=== clang ===

== Libs ==

C++ bindings are not included, since their required versions match those of the C counterparts.

{| class="wikitable"
|-
! Library
! v 0.91
! trunk
! trunk (GTK+ 3.0 build)
|-
| Boehm-GC
| 7.1
| 7.1
| 7.1
|-
| Cairo
| 1.10
| 1.10
| 1.10
|-
| GDL
| N/A
| N/A
| 3.3.4
|-
| Glib
| 2.28
| 2.28
| 2.28
|-
| GTK+
| 2.24
| 2.24
| 3.2
|-
| GNU Scientific Library
| ?
| ?
| ?
|-
| LittleCMS
| 1.13
| 1.13
| 1.13
|-
| libxml
| ''2.6.11*''
| ''2.6.11*''
| ''2.6.11*''
|-
| libxslt
| ''1.0.15*''
| ''1.0.15*''
| ''1.0.15*''
|-
| Pango
| ?
| ?
| 1.24
|-
| Poppler
| ''0.5.9*''
| 0.8.3
| 0.8.3
|-
| libsigc++
| ''2.0.12*''
| ''2.0.12*''
| ''2.0.12*''
|}

''* Tentative dependency''

== Distros ==

Note: This table is not relevant to (non-fink) MacOS X, where we ship the desired version with Inkscape.

"Inkscape" column is default or distro version / oldest that builds - latest that builds. If no latest is given then that means trunk is expected to build on the given platform.

e.g. for a distro that ships with 0.48 but should support building of trunk you might get:
0.48 / 0.47-

{| class="wikitable"
|-
! Distro
! Inkscape
! gcc
! clang
! cairo
! cairomm
! glib
! glibmm
! gtk+
! gtkmm
! pango
! poppler
! gdl
! lcms
! libsigc++
! libgc 
|-
| style="background:Violet;"|Windows Devlibs (32bit) [https://code.launchpad.net/~inkscape.dev/inkscape-devlibs/trunk] (r53)
|
|
|
| 1.11.2
| 1.10.0
| 2.28.8
| 2.28.2
| style="background:Violet;"| 2.24.10
| style="background:Violet;"| 2.24.2
| 1.28.3
| 0.12.1
| style="background:Violet;"| (none)
| 1.17 2.4
| 2.2.11
| 7.1
|-
| Windows Devlibs Gtk+ 3 branch [https://code.launchpad.net/~inkscape.dev/inkscape-devlibs/devlibs-gtk3] (r34)
|
|
|
| 1.10.2
| 1.10.0
| 2.38.0
| 2.36.0
| 2.24.18 3.8.1
| 2.24.2 3.8.0
| 1.34.0
| 0.22.5
| 3.4.2
| 1.19 2.4
| 2.2.10
| 7.2d
|-
| Windows Devlibs 64bit [https://code.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk] (r17)
|
|
|
| 1.14.1
| 1.11.2
| 2.40.0
| 2.40.0
| 2.24.23 3.13.1
| 2.24.4 3.12.0
| 1.36.3
| 0.24.2
| 3.12.0
| - 2.6
| 2.3.1
| 7.2
|-
| Debian 7.0 (Wheezy, stable)
|
|
|
| 1.12.2
| 1.10.0
| 2.33.12
| 2.32.1
| 2.24.10 3.4.2
| 2.24.2 3.4.2
| 1.32.5
| 0.18.4
| 3.4.2
| 1.19 2.2
| 2.2.10
| 7.1
|-
| style="background:Red;" | RHEL / CentOS / Scientific Linux 5.x
|
| 4.1.2
| X
| 1.2.4
| X
| 2.12.3
| X
| 2.10.4
| X
| 1.14.9
| 0.5.4
| X
| 1.18
| X
| X
|-
| RHEL / CentOS / Scientific Linux 6.x
| 0.47
| 4.4.7
| X
| 1.8.8
| 1.8.0
| 2.28.8
| 2.22
| 2.24.23
| 2.18.2
| 1.28.1
| 0.12.4
| X
| 1.19
| 2.2.4.2
| 7.1
|-
| RHEL / CentOS / Scientific Linux 7.x
| 0.48
| 4.8.3
| X
| 1.12.14
| 1.10.0
| 2.40.0
| 2.36.2
| 2.24.22 3.8.8
| 2.24.2 3.8.1
| 1.34.1
| 0.22.5
| X
| 2.5.4
| 2.3.1
| 7.2d
|-
| Fedora 20
| 0.91
| 4.8.3
| 3.4
| 1.13.1+git
| 1.10.0
| 2.38.2
| 2.38.1
| 2.24.22 3.10.6
| 2.24.4 3.10.1
| 1.36.1
| 0.24.3
| 3.10.0
| 1.19 2.5
| 2.3.1
| 7.2d
|-
| OpenSuSE 13.1 EOL 2015-05-01[http://en.opensuse.org/Lifetime]
| 0.48.4
| 4.8.2
| 3.3
| 1.12.16
| 1.10.0
| 2.38.1
| 2.38.0
| 2.24.22 3.10.2
| 2.24.4 3.10.0
| 1.36.0
| 0.24.3
| 3.10.0
| 1.19 2.5
| 2.3.1
| 7.2d
|-
| Ubuntu 12.04 LTS (Precise) EOL 2017-04
| 0.48.3
| 4.6.3
| (U 3.4)
| 1.10.2
| 1.10.0
| 2.32.4
| 2.32.0
| 2.24.10 3.4.2
| 2.24.2 3.4.0
| 1.30.0
| 0.18.4
| 3.3.91
| 1.19 2.2
| 2.2.10
| 7.1
|-
| Ubuntu 14.04 (Trusty) EOL 2019-04
| 0.48.4
| 4.8.2
| (U 3.5)
| 1.13.0
| 1.10.0
| 2.40.2
| 2.39.93
| 2.24.23 3.10.8
| 2.24.4 3.10.1
| 1.36.3
| 0.24.5
| 3.8.1
| 1.19 2.5
| 2.2.10
| 7.2d
|-
| Ubuntu 14.10 (Utopic), EOL 2015-07
| 0.48.5
| 4.9.1
| (U 3.5)
| 1.13.0
| 1.10.0
| 2.42.1
| 2.42.0
| 2.24.25 3.12.2
| 2.24.4 3.12.0
| 1.36.6
| 0.26.5
| 3.12.0
| 1.19 2.6
| 2.2.11
| 7.2d
|-
| Ubuntu 15.04 (Vivid) (As of 2015-04-03), EOL 2016-01
| 0.91.0
| 4.9.2
| 3.6
| 1.14.0
| 1.11.2
| 2.44.0
| 2.42.0
| 2.24.27 3.14.11
| 2.24.4 3.14.0
| 1.36.8
| 0.30.0
| 3.14.0
| - 2.6
| 2.4.0
| 7.2d
|}

{| class="wikitable"
|-
! Legend
|-
| style="background:Red;"| Inkscape stable unsupported
|-
| style="background:Orange;"| Inkscape trunk unsupported
|-
| style="background:Violet;"| GTK+ 3 builds unsupported
|}

== Getting and Installing Source packages ==

If your distro does not have some packages available (like many don't, ie, Fedora Core 2), you must often download
source packages and build and install them yourself. Actually this is not that hard, and is similar to
doing a Gentoo 'emerge.'

* Usually you download a file with a name like somepackage-1.0.tar.gz. Unpack it with

$ tar zxf somepackage-1.0.tar.gz
or
$ tar jxf somepackage-1.0.tar.bz2

* Then 'cd' into the new directory.

* Configure it with the command:

$ ./configure

* Build it with:

$ make

* As the 'root' user, install it with:

# make install

=== Boehm-GC ===

Source: http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source

* Download this file:
** http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/gc6.8.tar.gz
* Unpack it
** tar zxf gc6.8.tar.gz
* Configure and build it
** cd gc6.8
** ./configure --disable-shared --enable-static
** make
* Install it
** su (or however else you become root)
** make install

Binaries: If searching for a package for GC, the name of it is sometimes:

* gc
* libgc
* gc-devel
* libgc-devel
* boehm-gc (on Gentoo)
* debian/ubuntu: sudo apt-get install libgc-dev

=== libSigc++ ===

Source: http://ftp.gnome.org/pub/GNOME/sources/libsigc++/2.2/libsigc++-2.2.3.tar.bz2

With this file, and for GlibMM and GtkMM below, it is usually desirable for us developers to
build this C++ library statically. This removes a dependency that might be difficult for an
end-user during installation. Configure it with:

./configure --enable-static --disable-shared

=== GlibMM ===
Try to match your Glib2 version with GlibMM's version. For example, if your Glib2 is 2.16.6, download glibmm-2.16.4.tar.bz2.

Latest source: http://ftp.gnome.org/pub/GNOME/sources/glibmm/

=== GtkMM ===
Usually you can try the latest version of GtkMM, but if you get version mismatch errors, try older releases.

Source: http://ftp.gnome.org/pub/GNOME/sources/gtkmm/2.12/gtkmm-2.12.7.tar.bz2

=== cairomm ===

if you got prompted about cairomm, try first solve your cairo version, so you can grab [http://www.cairographics.org/releases/ there] a compatible version.

=== Boost ===

Many users have reported when building from source that after installing the above dependencies, the configure script still requires a "boost" package. It can be found below, but even after installing, you will need to create a symlink to allow the configure script to find it:

ln -s /usr/local/include/boost_1_xx_x/boost /usr/local/include/boost

Source: http://www.boost.org/users/download/

=== Poppler ===

Source: http://poppler.freedesktop.org/

Poppler is required for PDF import. There are several potential issues:
* Some Linux distributions do not ship the Xpdf headers required by Inkscape. In such cases, you need to recompile Poppler, passing --enable-xpdf-headers on the configure line or install the libpoppler-private-dev package. See [https://bugs.launchpad.net/inkscape/+bug/254849 this wishlist bug]. This typically manifests in error messages like this:
<pre>In file included from extension/internal/pdfinput/svg-builder.cpp:19:
extension/internal/pdfinput/svg-builder.h:32:23: error: CharTypes.h: No such file or directory
...
make[2]: *** [extension/internal/pdfinput/svg-builder.o] Error 1
make[2]: Leaving directory `/tmp/build/inkscape-0.46/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/build/inkscape-0.46'
make: *** [all] Error 2</pre>
* Inkscape 0.47 does not compile with Poppler >= 0.12.2. If you need to compile Inkscape on such systems, use the development version from Bazaar, where this bug is fixed. See [https://bugs.launchpad.net/inkscape/+bug/487038 the bug report] for details and a minimal patch.
* Inkscape compiled with Poppler <= 0.12.1 will run on systems with Poppler >= 0.12.2, but the PDF import function will crash instantly. This problem does not concern Windows users, since the correct Poppler version is contained in the Windows installer package. This cannot be fixed on Inkscape's side: those two versions of Poppler are not ABI compatible, yet share the same soname. See [https://bugs.launchpad.net/inkscape/+bug/258504 this bug] for more details.
* Poppler's Xpdf headers are not guaranteed to be API-compatible between releases. It's likely that future Poppler versions will break PDF import in some way. PDF import works at least up to 0.12.4 but might not work with later versions.

[[Category:About Inkscape]]
[[Category:Developer Documentation]]

Tracking Dependencies

2015-04-03T21:47:40Z

ScislaC: Update Vivid libs

== Overview ==

We need help getting our basic lib dependencies listed out and kept up to date. Also we need to track which versions of which distros have the needed dependencies.

To get glib and GTK+ dependencies figured out, people can go through the API documentation and look for the 'since' entries saying when calls were added. Then look for those calls in our source. Voila! we'll have base minimum dependencies figured out.

== Compilers ==

For C++11 features, see [[C++11]]

=== gcc ===
=== clang ===

== Libs ==

C++ bindings are not included, since their required versions match those of the C counterparts.

{| class="wikitable"
|-
! Library
! v 0.91
! trunk
! trunk (GTK+ 3.0 build)
|-
| Boehm-GC
| 7.1
| 7.1
| 7.1
|-
| Cairo
| 1.10
| 1.10
| 1.10
|-
| GDL
| N/A
| N/A
| 3.3.4
|-
| Glib
| 2.28
| 2.28
| 2.28
|-
| GTK+
| 2.24
| 2.24
| 3.2
|-
| GNU Scientific Library
| ?
| ?
| ?
|-
| LittleCMS
| 1.13
| 1.13
| 1.13
|-
| libxml
| ''2.6.11*''
| ''2.6.11*''
| ''2.6.11*''
|-
| libxslt
| ''1.0.15*''
| ''1.0.15*''
| ''1.0.15*''
|-
| Pango
| ?
| ?
| 1.24
|-
| Poppler
| ''0.5.9*''
| 0.8.3
| 0.8.3
|-
| libsigc++
| ''2.0.12*''
| ''2.0.12*''
| ''2.0.12*''
|}

''* Tentative dependency''

== Distros ==

Note: This table is not relevant to (non-fink) MacOS X, where we ship the desired version with Inkscape.

"Inkscape" column is default or distro version / oldest that builds - latest that builds. If no latest is given then that means trunk is expected to build on the given platform.

e.g. for a distro that ships with 0.48 but should support building of trunk you might get:
0.48 / 0.47-

{| class="wikitable"
|-
! Distro
! Inkscape
! gcc
! clang
! cairo
! cairomm
! glib
! glibmm
! gtk+
! gtkmm
! pango
! poppler
! gdl
! lcms
! libsigc++
! libgc 
|-
| style="background:Violet;"|Windows Devlibs (32bit) [https://code.launchpad.net/~inkscape.dev/inkscape-devlibs/trunk] (r53)
|
|
|
| 1.11.2
| 1.10.0
| 2.28.8
| 2.28.2
| style="background:Violet;"| 2.24.10
| style="background:Violet;"| 2.24.2
| 1.28.3
| 0.12.1
| style="background:Violet;"| (none)
| 1.17 2.4
| 2.2.11
| 7.1
|-
| Windows Devlibs Gtk+ 3 branch [https://code.launchpad.net/~inkscape.dev/inkscape-devlibs/devlibs-gtk3] (r34)
|
|
|
| 1.10.2
| 1.10.0
| 2.38.0
| 2.36.0
| 2.24.18 3.8.1
| 2.24.2 3.8.0
| 1.34.0
| 0.22.5
| 3.4.2
| 1.19 2.4
| 2.2.10
| 7.2d
|-
| Windows Devlibs 64bit [https://code.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk] (r17)
|
|
|
| 1.14.1
| 1.11.2
| 2.40.0
| 2.40.0
| 2.24.23 3.13.1
| 2.24.4 3.12.0
| 1.36.3
| 0.24.2
| 3.12.0
| - 2.6
| 2.3.1
| 7.2
|-
| Debian 7.0 (Wheezy, stable)
|
|
|
| 1.12.2
| 1.10.0
| 2.33.12
| 2.32.1
| 2.24.10 3.4.2
| 2.24.2 3.4.2
| 1.32.5
| 0.18.4
| 3.4.2
| 1.19 2.2
| 2.2.10
| 7.1
|-
| style="background:Red;" | RHEL / CentOS / Scientific Linux 5.x
|
| 4.1.2
| X
| 1.2.4
| X
| 2.12.3
| X
| 2.10.4
| X
| 1.14.9
| 0.5.4
| X
| 1.18
| X
| X
|-
| RHEL / CentOS / Scientific Linux 6.x
| 0.47
| 4.4.7
| X
| 1.8.8
| 1.8.0
| 2.28.8
| 2.22
| 2.24.23
| 2.18.2
| 1.28.1
| 0.12.4
| X
| 1.19
| 2.2.4.2
| 7.1
|-
| RHEL / CentOS / Scientific Linux 7.x
| 0.48
| 4.8.3
| X
| 1.12.14
| 1.10.0
| 2.40.0
| 2.36.2
| 2.24.22 3.8.8
| 2.24.2 3.8.1
| 1.34.1
| 0.22.5
| X
| 2.5.4
| 2.3.1
| 7.2d
|-
| Fedora 20
| 0.91
| 4.8.3
| 3.4
| 1.13.1+git
| 1.10.0
| 2.38.2
| 2.38.1
| 2.24.22 3.10.6
| 2.24.4 3.10.1
| 1.36.1
| 0.24.3
| 3.10.0
| 1.19 2.5
| 2.3.1
| 7.2d
|-
| OpenSuSE 13.1 EOL 2015-05-01[http://en.opensuse.org/Lifetime]
| 0.48.4
| 4.8.2
| 3.3
| 1.12.16
| 1.10.0
| 2.38.1
| 2.38.0
| 2.24.22 3.10.2
| 2.24.4 3.10.0
| 1.36.0
| 0.24.3
| 3.10.0
| 1.19 2.5
| 2.3.1
| 7.2d
|-
| Ubuntu 12.04 LTS (Precise) EOL 2017-04
| 0.48.3
| 4.6.3
| (U 3.4)
| 1.10.2
| 1.10.0
| 2.32.4
| 2.32.0
| 2.24.10 3.4.2
| 2.24.2 3.4.0
| 1.30.0
| 0.18.4
| 3.3.91
| 1.19 2.2
| 2.2.10
| 7.1
|-
| Ubuntu 14.04 (Trusty) EOL 2019-04
| 0.48.4
| 4.8.2
| (U 3.5)
| 1.13.0
| 1.10.0
| 2.40.2
| 2.39.93
| 2.24.23 3.10.8
| 2.24.4 3.10.1
| 1.36.3
| 0.24.5
| 3.8.1
| 1.19 2.5
| 2.2.10
| 7.2d
|-
| Ubuntu 14.10 (Utopic), EOL 2015-07
| 0.48.5
| 4.9.1
| (U 3.5)
| 1.13.0
| 1.10.0
| 2.42.1
| 2.42.0
| 2.24.25 3.12.2
| 2.24.4 3.12.0
| 1.36.6
| 0.26.5
| 3.12.0
| 1.19 2.6
| 2.2.11
| 7.2d
|-
| Ubuntu 15.04 (Vivid) (As of 2015-04-03), EOL 2016-01
|
|
|
| 1.14.0
| 1.11.2
| 2.44.0
| 2.42.0
| 2.24.27 3.14.11
| 2.24.4 3.14.0
| 1.36.8
| 0.30.0
| 3.14.0
| - 2.6
| 2.4.0
| 7.2d
|}

{| class="wikitable"
|-
! Legend
|-
| style="background:Red;"| Inkscape stable unsupported
|-
| style="background:Orange;"| Inkscape trunk unsupported
|-
| style="background:Violet;"| GTK+ 3 builds unsupported
|}

== Getting and Installing Source packages ==

If your distro does not have some packages available (like many don't, ie, Fedora Core 2), you must often download
source packages and build and install them yourself. Actually this is not that hard, and is similar to
doing a Gentoo 'emerge.'

* Usually you download a file with a name like somepackage-1.0.tar.gz. Unpack it with

$ tar zxf somepackage-1.0.tar.gz
or
$ tar jxf somepackage-1.0.tar.bz2

* Then 'cd' into the new directory.

* Configure it with the command:

$ ./configure

* Build it with:

$ make

* As the 'root' user, install it with:

# make install

=== Boehm-GC ===

Source: http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source

* Download this file:
** http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/gc6.8.tar.gz
* Unpack it
** tar zxf gc6.8.tar.gz
* Configure and build it
** cd gc6.8
** ./configure --disable-shared --enable-static
** make
* Install it
** su (or however else you become root)
** make install

Binaries: If searching for a package for GC, the name of it is sometimes:

* gc
* libgc
* gc-devel
* libgc-devel
* boehm-gc (on Gentoo)
* debian/ubuntu: sudo apt-get install libgc-dev

=== libSigc++ ===

Source: http://ftp.gnome.org/pub/GNOME/sources/libsigc++/2.2/libsigc++-2.2.3.tar.bz2

With this file, and for GlibMM and GtkMM below, it is usually desirable for us developers to
build this C++ library statically. This removes a dependency that might be difficult for an
end-user during installation. Configure it with:

./configure --enable-static --disable-shared

=== GlibMM ===
Try to match your Glib2 version with GlibMM's version. For example, if your Glib2 is 2.16.6, download glibmm-2.16.4.tar.bz2.

Latest source: http://ftp.gnome.org/pub/GNOME/sources/glibmm/

=== GtkMM ===
Usually you can try the latest version of GtkMM, but if you get version mismatch errors, try older releases.

Source: http://ftp.gnome.org/pub/GNOME/sources/gtkmm/2.12/gtkmm-2.12.7.tar.bz2

=== cairomm ===

if you got prompted about cairomm, try first solve your cairo version, so you can grab [http://www.cairographics.org/releases/ there] a compatible version.

=== Boost ===

Many users have reported when building from source that after installing the above dependencies, the configure script still requires a "boost" package. It can be found below, but even after installing, you will need to create a symlink to allow the configure script to find it:

ln -s /usr/local/include/boost_1_xx_x/boost /usr/local/include/boost

Source: http://www.boost.org/users/download/

=== Poppler ===

Source: http://poppler.freedesktop.org/

Poppler is required for PDF import. There are several potential issues:
* Some Linux distributions do not ship the Xpdf headers required by Inkscape. In such cases, you need to recompile Poppler, passing --enable-xpdf-headers on the configure line or install the libpoppler-private-dev package. See [https://bugs.launchpad.net/inkscape/+bug/254849 this wishlist bug]. This typically manifests in error messages like this:
<pre>In file included from extension/internal/pdfinput/svg-builder.cpp:19:
extension/internal/pdfinput/svg-builder.h:32:23: error: CharTypes.h: No such file or directory
...
make[2]: *** [extension/internal/pdfinput/svg-builder.o] Error 1
make[2]: Leaving directory `/tmp/build/inkscape-0.46/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/build/inkscape-0.46'
make: *** [all] Error 2</pre>
* Inkscape 0.47 does not compile with Poppler >= 0.12.2. If you need to compile Inkscape on such systems, use the development version from Bazaar, where this bug is fixed. See [https://bugs.launchpad.net/inkscape/+bug/487038 the bug report] for details and a minimal patch.
* Inkscape compiled with Poppler <= 0.12.1 will run on systems with Poppler >= 0.12.2, but the PDF import function will crash instantly. This problem does not concern Windows users, since the correct Poppler version is contained in the Windows installer package. This cannot be fixed on Inkscape's side: those two versions of Poppler are not ABI compatible, yet share the same soname. See [https://bugs.launchpad.net/inkscape/+bug/258504 this bug] for more details.
* Poppler's Xpdf headers are not guaranteed to be API-compatible between releases. It's likely that future Poppler versions will break PDF import in some way. PDF import works at least up to 0.12.4 but might not work with later versions.

[[Category:About Inkscape]]
[[Category:Developer Documentation]]

Hackfest2015 Topics

2015-03-24T00:01:26Z

ScislaC: /* Refactoring */

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

Other pages: [[Hackfest2015|Hackfest 2015]], [[Hackfest2015 Attendees]].

== Discussions ==

=== SVG 2 strategy (Tav) ===

* Overview/rundown of relevant new SVG2 features. What are they, what will need done to implement them?
* How do we handle fallbacks?
* When do we add things to the GUI? (When three browsers offers support?)

=== Program flow (Tav) ===

* Diagram how Inkscape behaves/should behave on:
** Opening a file.
** Changing a style item (e.g. 'fill').
** Moving a node.
** Deleting an item.
*** Comment: Deleting an item causes Inkscape to create a new SVG document with containing the deleted item to allow pasting.

==== Motivation ====

Add a few random print statements in Inkscape and you'll see that Inkscape visits certain functions more often than one would think it should. Having well defined diagrams will allow developers to clean up existing code and to better understand what needs to be done to add new features. I've noticed that we suffer from "cargo cult programming" where people add functions without fully understanding if they are truly needed.

* Ideas
** Better, easily referenced API documentation
** Code reviews
** `linux perf` can be used to identify performance critical functions

==== Comments from Krzysztof ====

This is a pretty big problem right now. The flow looks like this:

Something is updated in the SP tree
# updateRepr() is called
# new XML is written
# XML modification listeners fire
# SP tree is re-read from the XML
# A recursive call to update() is made
# Each of those update calls updates the rendering tree in turn.

As a result, changing the document height triggers a full update of
the rendering tree, even though almost nothing changes.

The current approach makes it impossible to introduce errors that
cause the XML and the SP tree to go out of sync, at the cost of
performance. We could discuss what to do about this.

=== Refactoring ===

Can we decide on a roadmap to work with new APIs and compilers? How do we minimize breakages for downstream users? Can we balance risk with reward? How does each migration benefit the developers, package maintainers and end users?

Some possible changes to discuss:

* Moving to C++11 (AV)
** code cleanup/maintainability
** improved data structures/templating
* Adding a hard Cairo 1.14 dependency (AV)
** Fix bitmap downscaling issue
* Gtk+ 3 migration (AV)
** Get rid of lots of conditional code
** Get rid of embedded GDK library fork
** Some "cleaner" API available
** How do we handle canvas flickering/rendering issues?
* C++ification (AV)
** Migrate widgets/dialogs to Gtkmm
** Get rid of popt
** Get rid of GObject usage
* Removing 3rd party Library dependencies from version control (AV)
* Change how we're utilizing 3rd party libraries (Josh)
** Stop using Poppler internals, use the proper API via poppler-glib (https://bugs.launchpad.net/inkscape/+bug/239544)
** Use newer Pango-Cairo text/glyph APIs (https://bugs.launchpad.net/inkscape/+bug/420822)
* Unnecessary profileration of namespaces (Krzysztof)Things like Inkscape::UI::View::View are excessive. I cannot imagine a scenario where we would need more than 2 levels of namespaces. Everything UI-related should sit in Inkscape::UI, without separate namespaces for widgets and dialogs which only serve to increase typing.
* Directory structure. Let's make a directory for the SP tree, and namespace it as Inkscape::SVG (or maybe Inkscape::DOM). (Krzysztof)
* Identify clever geometry code which can be cleaned up and moved to 2Geom. (Krzysztof)

=== Testing (Johan) ===

* Discuss Jenkins/unittesting/rendertesting.

=== Website (DoctorMO) ===

* How do people feel about it's current functions
* How should we move it forwards?
* Plans for mailing list migrations.
* Getting developers set up with local copies for hacking.

=== Roadmap Planning (Bryce) ===

Prioritize feature and infrastructure development work for next several releases.

=== Fundraisers (Bryce) ===

Brainstorm future fundraising ideas.

=== Community Development (Bryce) ===

* Championing FOSS ideals generally
* Expanding userbase
* Building up a strong evangelist user community
* Recruiting newbie developers, encouraging involvement, and mentoring
* Re-connecting with old timers
* Promoting existing developers into leadership roles

== Hacking ==

=== Invert coordinate system (Tav) ===

If there was ever a good moment to do the coordinate system flip, this is it. (should coordinates be configurable in relation to the canvas?)

==== Comment from Krzysztof ====

We need to decide whether we want to keep the 3D Box at all costs, or is the coordinate system inversion a more important goal than having 3D Box. Being unable to fix 3D Box was the main reason I didn't commit this change when I initially made it. FWIW, I think the 3D Box tool is nearly unusable and needs to be rewritten from scratch. It also pollutes the entire codebase with special handling for its perspective elements, indicating faulty
design.

=== Make Systems ===

==== CMake (Bryce) ====

A while back someone made a valiant attempt to get Inkscape built with cmake, but if this ever worked it's bitrotted to where it doesn't work presently. Hack it back into working shape on Linux, Mac, and Windows. Write up evaluation.

==== WAF (Krzysztof) ====

I would rather use Waf. CMake has its own, sloppy scripting language; writing anything moderately complex in it is an exercise in frustration. By contrast, Waf scripts can leverage all the mighty power of Python.

Killer feature: since Waf stores a database of what was compiled, it support wildcards correctly. As in, when the set of files matched by a wildcard in the build script changes, it will automatically recompiles the correct files, without the need to modify build scripts. CMake cannot do this, because it just generates makefiles, and Make cannot support wildcards in this manner because it does not have any persistence beyond what is stored in the file system.

Other things we could easily do with Waf are:
* render test integration
* automatically updating the AUTHORS file and the authors tab in the About dialog from Bazaar logs
* creating a completely standalone executable (using e.g. GResource to store data files in the executable itself)

=== Hardware Acceleration Experimentation (Bryce) ===

Create experimental branch using Cairo-GLX as the rendering backend. Evaluate rendering performance. Brainstorm follow up work.

Hackfest2015 Topics

2015-03-20T19:05:27Z

ScislaC: /* Refactoring */

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

Other pages: [[Hackfest2015|Hackfest 2015]], [[Hackfest2015 Attendees]].

== Discussions ==

=== SVG 2 strategy (Tav) ===

* Overview/rundown of relevant new SVG2 features. What are they, what will need done to implement them?
* How do we handle fallbacks?
* When do we add things to the GUI? (When three browsers offers support?)

=== Program flow (Tav) ===

* Diagram how Inkscape behaves/should behave on:
** Opening a file.
** Changing a style item (e.g. 'fill').
** Moving a node.
** Deleting an item.
*** Comment: Deleting an item causes Inkscape to create a new SVG document with containing the deleted item to allow pasting.

==== Motivation ====

Add a few random print statements in Inkscape and you'll see that Inkscape visits certain functions more often than one would think it should. Having well defined diagrams will allow developers to clean up existing code and to better understand what needs to be done to add new features. I've noticed that we suffer from "cargo cult programming" where people add functions without fully understanding if they are truly needed.

* Ideas
** Better, easily referenced API documentation
** Code reviews
** `linux perf` can be used to identify performance critical functions

==== Comments from Krzysztof ====

This is a pretty big problem right now. The flow looks like this:

Something is updated in the SP tree
# updateRepr() is called
# new XML is written
# XML modification listeners fire
# SP tree is re-read from the XML
# A recursive call to update() is made
# Each of those update calls updates the rendering tree in turn.

As a result, changing the document height triggers a full update of
the rendering tree, even though almost nothing changes.

The current approach makes it impossible to introduce errors that
cause the XML and the SP tree to go out of sync, at the cost of
performance. We could discuss what to do about this.

=== Refactoring ===

Can we decide on a roadmap to work with new APIs and compilers? How do we minimize breakages for downstream users? Can we balance risk with reward? How does each migration benefit the developers, package maintainers and end users?

Some possible changes to discuss:

* Moving to C++11 (AV)
** code cleanup/maintainability
** improved data structures/templating
* Adding a hard Cairo 1.14 dependency (AV)
** Fix bitmap downscaling issue
* Gtk+ 3 migration (AV)
** Get rid of lots of conditional code
** Get rid of embedded GDK library fork
** Some "cleaner" API available
** How do we handle canvas flickering/rendering issues?
* C++ification (AV)
** Migrate widgets/dialogs to Gtkmm
** Get rid of popt
** Get rid of GObject usage
* Removing 3rd party Library dependencies from version control (Josh)
* Change how we're utilizing 3rd party libraries (Josh)
** Stop using Poppler internals, use the proper API via poppler-glib (https://bugs.launchpad.net/inkscape/+bug/239544)
** Use newer Pango-Cairo text/glyph APIs (https://bugs.launchpad.net/inkscape/+bug/420822)
* Unnecessary profileration of namespaces (Krzysztof)Things like Inkscape::UI::View::View are excessive. I cannot imagine a scenario where we would need more than 2 levels of namespaces. Everything UI-related should sit in Inkscape::UI, without separate namespaces for widgets and dialogs which only serve to increase typing.
* Directory structure. Let's make a directory for the SP tree, and namespace it as Inkscape::SVG (or maybe Inkscape::DOM). (Krzysztof)
* Identify clever geometry code which can be cleaned up and moved to 2Geom. (Krzysztof)

=== Testing (Johan) ===

* Discuss Jenkins/unittesting/rendertesting.

=== Website (DoctorMO) ===

* How do people feel about it's current functions
* How should we move it forwards?
* Plans for mailing list migrations.
* Getting developers set up with local copies for hacking.

=== Roadmap Planning (Bryce) ===

Prioritize feature and infrastructure development work for next several releases.

=== Fundraisers (Bryce) ===

Brainstorm future fundraising ideas.

=== Community Development (Bryce) ===

* Championing FOSS ideals generally
* Expanding userbase
* Building up a strong evangelist user community
* Recruiting newbie developers, encouraging involvement, and mentoring
* Re-connecting with old timers
* Promoting existing developers into leadership roles

== Hacking ==

=== Invert coordinate system (Tav) ===

If there was ever a good moment to do the coordinate system flip, this is it. (should coordinates be configurable in relation to the canvas?)

==== Comment from Krzysztof ====

We need to decide whether we want to keep the 3D Box at all costs, or is the coordinate system inversion a more important goal than having 3D Box. Being unable to fix 3D Box was the main reason I didn't commit this change when I initially made it. FWIW, I think the 3D Box tool is nearly unusable and needs to be rewritten from scratch. It also pollutes the entire codebase with special handling for its perspective elements, indicating faulty
design.

=== Make Systems ===

==== CMake (Bryce) ====

A while back someone made a valiant attempt to get Inkscape built with cmake, but if this ever worked it's bitrotted to where it doesn't work presently. Hack it back into working shape on Linux, Mac, and Windows. Write up evaluation.

==== WAF (Krzysztof) ====

I would rather use Waf. CMake has its own, sloppy scripting language; writing anything moderately complex in it is an exercise in frustration. By contrast, Waf scripts can leverage all the mighty power of Python.

Killer feature: since Waf stores a database of what was compiled, it support wildcards correctly. As in, when the set of files matched by a wildcard in the build script changes, it will automatically recompiles the correct files, without the need to modify build scripts. CMake cannot do this, because it just generates makefiles, and Make cannot support wildcards in this manner because it does not have any persistence beyond what is stored in the file system.

Other things we could easily do with Waf are:
* render test integration
* automatically updating the AUTHORS file and the authors tab in the About dialog from Bazaar logs
* creating a completely standalone executable (using e.g. GResource to store data files in the executable itself)

=== Hardware Acceleration Experimentation (Bryce) ===

Create experimental branch using Cairo-GLX as the rendering backend. Evaluate rendering performance. Brainstorm follow up work.

Hackfest2015 Topics

2015-03-20T19:04:46Z

ScislaC: /* Refactoring */

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

Other pages: [[Hackfest2015|Hackfest 2015]], [[Hackfest2015 Attendees]].

== Discussions ==

=== SVG 2 strategy (Tav) ===

* Overview/rundown of relevant new SVG2 features. What are they, what will need done to implement them?
* How do we handle fallbacks?
* When do we add things to the GUI? (When three browsers offers support?)

=== Program flow (Tav) ===

* Diagram how Inkscape behaves/should behave on:
** Opening a file.
** Changing a style item (e.g. 'fill').
** Moving a node.
** Deleting an item.
*** Comment: Deleting an item causes Inkscape to create a new SVG document with containing the deleted item to allow pasting.

==== Motivation ====

Add a few random print statements in Inkscape and you'll see that Inkscape visits certain functions more often than one would think it should. Having well defined diagrams will allow developers to clean up existing code and to better understand what needs to be done to add new features. I've noticed that we suffer from "cargo cult programming" where people add functions without fully understanding if they are truly needed.

* Ideas
** Better, easily referenced API documentation
** Code reviews
** `linux perf` can be used to identify performance critical functions

==== Comments from Krzysztof ====

This is a pretty big problem right now. The flow looks like this:

Something is updated in the SP tree
# updateRepr() is called
# new XML is written
# XML modification listeners fire
# SP tree is re-read from the XML
# A recursive call to update() is made
# Each of those update calls updates the rendering tree in turn.

As a result, changing the document height triggers a full update of
the rendering tree, even though almost nothing changes.

The current approach makes it impossible to introduce errors that
cause the XML and the SP tree to go out of sync, at the cost of
performance. We could discuss what to do about this.

=== Refactoring ===

Can we decide on a roadmap to work with new APIs and compilers? How do we minimize breakages for downstream users? Can we balance risk with reward? How does each migration benefit the developers, package maintainers and end users?

Some possible changes to discuss:

* Moving to C++11 (AV)
** code cleanup/maintainability
** improved data structures/templating
* Adding a hard Cairo 1.14 dependency (AV)
** Fix bitmap downscaling issue
* Gtk+ 3 migration (AV)
** Get rid of lots of conditional code
** Get rid of embedded GDK library fork
** Some "cleaner" API available
** How do we handle canvas flickering/rendering issues?
* C++ification (AV)
** Migrate widgets/dialogs to Gtkmm
** Get rid of popt
** Get rid of GObject usage
* Removing 3rd party Library dependencies from version control (JA)
* Change how we're utilizing 3rd party libraries (JA)
** Stop using Poppler internals, use the proper API via poppler-glib (https://bugs.launchpad.net/inkscape/+bug/239544)
** Use newer Pango-Cairo text/glyph APIs (https://bugs.launchpad.net/inkscape/+bug/420822)
* Unnecessary profileration of namespaces (Krzysztof)Things like Inkscape::UI::View::View are excessive. I cannot imagine a scenario where we would need more than 2 levels of namespaces. Everything UI-related should sit in Inkscape::UI, without separate namespaces for widgets and dialogs which only serve to increase typing.
* Directory structure. Let's make a directory for the SP tree, and namespace it as Inkscape::SVG (or maybe Inkscape::DOM). (Krzysztof)
* Identify clever geometry code which can be cleaned up and moved to 2Geom. (Krzysztof)

=== Testing (Johan) ===

* Discuss Jenkins/unittesting/rendertesting.

=== Website (DoctorMO) ===

* How do people feel about it's current functions
* How should we move it forwards?
* Plans for mailing list migrations.
* Getting developers set up with local copies for hacking.

=== Roadmap Planning (Bryce) ===

Prioritize feature and infrastructure development work for next several releases.

=== Fundraisers (Bryce) ===

Brainstorm future fundraising ideas.

=== Community Development (Bryce) ===

* Championing FOSS ideals generally
* Expanding userbase
* Building up a strong evangelist user community
* Recruiting newbie developers, encouraging involvement, and mentoring
* Re-connecting with old timers
* Promoting existing developers into leadership roles

== Hacking ==

=== Invert coordinate system (Tav) ===

If there was ever a good moment to do the coordinate system flip, this is it. (should coordinates be configurable in relation to the canvas?)

==== Comment from Krzysztof ====

We need to decide whether we want to keep the 3D Box at all costs, or is the coordinate system inversion a more important goal than having 3D Box. Being unable to fix 3D Box was the main reason I didn't commit this change when I initially made it. FWIW, I think the 3D Box tool is nearly unusable and needs to be rewritten from scratch. It also pollutes the entire codebase with special handling for its perspective elements, indicating faulty
design.

=== Make Systems ===

==== CMake (Bryce) ====

A while back someone made a valiant attempt to get Inkscape built with cmake, but if this ever worked it's bitrotted to where it doesn't work presently. Hack it back into working shape on Linux, Mac, and Windows. Write up evaluation.

==== WAF (Krzysztof) ====

I would rather use Waf. CMake has its own, sloppy scripting language; writing anything moderately complex in it is an exercise in frustration. By contrast, Waf scripts can leverage all the mighty power of Python.

Killer feature: since Waf stores a database of what was compiled, it support wildcards correctly. As in, when the set of files matched by a wildcard in the build script changes, it will automatically recompiles the correct files, without the need to modify build scripts. CMake cannot do this, because it just generates makefiles, and Make cannot support wildcards in this manner because it does not have any persistence beyond what is stored in the file system.

Other things we could easily do with Waf are:
* render test integration
* automatically updating the AUTHORS file and the authors tab in the About dialog from Bazaar logs
* creating a completely standalone executable (using e.g. GResource to store data files in the executable itself)

=== Hardware Acceleration Experimentation (Bryce) ===

Create experimental branch using Cairo-GLX as the rendering backend. Evaluate rendering performance. Brainstorm follow up work.

Hackfest2015 Topics

2015-03-20T00:53:34Z

ScislaC:

Hackfest2015 Topics

2015-03-20T00:52:06Z

ScislaC:

Tracking Dependencies

2015-03-04T23:00:32Z

ScislaC: /* Distros */

== Overview ==

We need help getting our basic lib dependencies listed out and kept up to date. Also we need to track which versions of which distros have the needed dependencies.

To get glib and GTK+ dependencies figured out, people can go through the API documentation and look for the 'since' entries saying when calls were added. Then look for those calls in our source. Voila! we'll have base minimum dependencies figured out.

== Libs ==

C++ bindings are not included, since their required versions match those of the C counterparts.

{| class="wikitable"
|-
! Library
! v 0.91
! trunk
! trunk (GTK+ 3.0 build)
|-
| Boehm-GC
| 7.1
| 7.1
| 7.1
|-
| Cairo
| 1.10
| 1.10
| 1.10
|-
| GDL
| N/A
| N/A
| 3.3.4
|-
| Glib
| 2.28
| 2.28
| 2.28
|-
| GTK+
| 2.24
| 2.24
| 3.2
|-
| GNU Scientific Library
| ?
| ?
| ?
|-
| LittleCMS
| 1.13
| 1.13
| 1.13
|-
| libxml
| ''2.6.11*''
| ''2.6.11*''
| ''2.6.11*''
|-
| libxslt
| ''1.0.15*''
| ''1.0.15*''
| ''1.0.15*''
|-
| Pango
| ?
| ?
| 1.24
|-
| Poppler
| ''0.5.9*''
| 0.8.3
| 0.8.3
|-
| libsigc++
| ''2.0.12*''
| ''2.0.12*''
| ''2.0.12*''
|}

''* Tentative dependency''

== Distros ==

Note: This table is not relevant to (non-fink) MacOS X, where we ship the desired version with Inkscape.

{| class="wikitable"
|-
! Distro
! cairo
! cairomm
! glib
! glibmm
! gtk+
! gtkmm
! pango
! poppler
! gdl
! lcms
! libsigc++
! libgc 
|-
| style="background:Violet;"|Windows Devlibs (32bit) [https://code.launchpad.net/~inkscape.dev/inkscape-devlibs/trunk] (r53)
| 1.11.2
| 1.10.0
| 2.28.8
| 2.28.2
| style="background:Violet;"| 2.24.10
| style="background:Violet;"| 2.24.2
| 1.28.3
| 0.12.1
| style="background:Violet;"| (none)
| 1.17 2.4
| 2.2.11
| 7.1
|-
| Windows Devlibs Gtk+ 3 branch [https://code.launchpad.net/~inkscape.dev/inkscape-devlibs/devlibs-gtk3] (r34)
| 1.10.2
| 1.10.0
| 2.38.0
| 2.36.0
| 2.24.18 3.8.1
| 2.24.2 3.8.0
| 1.34.0
| 0.22.5
| 3.4.2
| 1.19 2.4
| 2.2.10
| 7.2d
|-
| Windows Devlibs 64bit [https://code.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk] (r17)
| 1.14.1
| 1.11.2
| 2.40.0
| 2.40.0
| 2.24.23 3.13.1
| 2.24.4 3.12.0
| 1.36.3
| 0.24.2
| 3.12.0
| - 2.6
| 2.3.1
| 7.2
|-
| Debian 7.0 (Wheezy, stable)
| 1.12.2
| 1.10.0
| 2.33.12
| 2.32.1
| 2.24.10 3.4.2
| 2.24.2 3.4.2
| 1.32.5
| 0.18.4
| 3.4.2
| 1.19 2.2
| 2.2.10
| 7.1
|-
| Fedora 20
| 1.13.1+git
| 1.10.0
| 2.38.2
| 2.38.1
| 2.24.22 3.10.6
| 2.24.4 3.10.1
| 1.36.1
| 0.24.3
| 3.10.0
| 1.19 2.5
| 2.3.1
| 7.2d
|-
| OpenSuSE 13.1 EOL 2015-05-01[http://en.opensuse.org/Lifetime]
| 1.12.16
| 1.10.0
| 2.38.1
| 2.38.0
| 2.24.22 3.10.2
| 2.24.4 3.10.0
| 1.36.0
| 0.24.3
| 3.10.0
| 1.19 2.5
| 2.3.1
| 7.2d
|-
| Ubuntu 12.04 LTS (Precise) EOL 2017-04
| 1.10.2
| 1.10.0
| 2.32.4
| 2.32.0
| 2.24.10 3.4.2
| 2.24.2 3.4.0
| 1.30.0
| 0.18.4
| 3.3.91
| 1.19 2.2
| 2.2.10
| 7.1
|-
| Ubuntu 14.04 (Trusty) EOL 2019-04
| 1.13.0
| 1.10.0
| 2.40.2
| 2.39.93
| 2.24.23 3.10.8
| 2.24.4 3.10.1
| 1.36.3
| 0.24.5
| 3.8.1
| 1.19 2.5
| 2.2.10
| 7.2d
|-
| Ubuntu 14.10 (Utopic), EOL 2015-07
| 1.13.0
| 1.10.0
| 2.42.1
| 2.42.0
| 2.24.25 3.12.2
| 2.24.4 3.12.0
| 1.36.6
| 0.26.5
| 3.12.0
| 1.19 2.6
| 2.2.11
| 7.2d
|-
| Ubuntu 15.04 (Vivid) (As of 2015-03-04), EOL 2016-01
| 1.14.0
| 1.11.2
| 2.43.91
| 2.42.0
| 2.24.27 3.14.8
| 2.24.4 3.14.0
| 1.36.8
| 0.30.0
| 3.14.0
| - 2.6
| 2.4.0
| 7.2d
|}

{| class="wikitable"
|-
! Legend
|-
| style="background:Red;"| Inkscape stable unsupported
|-
| style="background:Orange;"| Inkscape trunk unsupported
|-
| style="background:Violet;"| GTK+ 3 builds unsupported
|}

== Getting and Installing Source packages ==

If your distro does not have some packages available (like many don't, ie, Fedora Core 2), you must often download
source packages and build and install them yourself. Actually this is not that hard, and is similar to
doing a Gentoo 'emerge.'

* Usually you download a file with a name like somepackage-1.0.tar.gz. Unpack it with

$ tar zxf somepackage-1.0.tar.gz
or
$ tar jxf somepackage-1.0.tar.bz2

* Then 'cd' into the new directory.

* Configure it with the command:

$ ./configure

* Build it with:

$ make

* As the 'root' user, install it with:

# make install

=== Boehm-GC ===

Source: http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source

* Download this file:
** http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/gc6.8.tar.gz
* Unpack it
** tar zxf gc6.8.tar.gz
* Configure and build it
** cd gc6.8
** ./configure --disable-shared --enable-static
** make
* Install it
** su (or however else you become root)
** make install

Binaries: If searching for a package for GC, the name of it is sometimes:

* gc
* libgc
* gc-devel
* libgc-devel
* boehm-gc (on Gentoo)
* debian/ubuntu: sudo apt-get install libgc-dev

=== libSigc++ ===

Source: http://ftp.gnome.org/pub/GNOME/sources/libsigc++/2.2/libsigc++-2.2.3.tar.bz2

With this file, and for GlibMM and GtkMM below, it is usually desirable for us developers to
build this C++ library statically. This removes a dependency that might be difficult for an
end-user during installation. Configure it with:

./configure --enable-static --disable-shared

=== GlibMM ===
Try to match your Glib2 version with GlibMM's version. For example, if your Glib2 is 2.16.6, download glibmm-2.16.4.tar.bz2.

Latest source: http://ftp.gnome.org/pub/GNOME/sources/glibmm/

=== GtkMM ===
Usually you can try the latest version of GtkMM, but if you get version mismatch errors, try older releases.

Source: http://ftp.gnome.org/pub/GNOME/sources/gtkmm/2.12/gtkmm-2.12.7.tar.bz2

=== cairomm ===

if you got prompted about cairomm, try first solve your cairo version, so you can grab [http://www.cairographics.org/releases/ there] a compatible version.

=== Boost ===

Many users have reported when building from source that after installing the above dependencies, the configure script still requires a "boost" package. It can be found below, but even after installing, you will need to create a symlink to allow the configure script to find it:

ln -s /usr/local/include/boost_1_xx_x/boost /usr/local/include/boost

Source: http://www.boost.org/users/download/

=== Poppler ===

Source: http://poppler.freedesktop.org/

Poppler is required for PDF import. There are several potential issues:
* Some Linux distributions do not ship the Xpdf headers required by Inkscape. In such cases, you need to recompile Poppler, passing --enable-xpdf-headers on the configure line or install the libpoppler-private-dev package. See [https://bugs.launchpad.net/inkscape/+bug/254849 this wishlist bug]. This typically manifests in error messages like this:
<pre>In file included from extension/internal/pdfinput/svg-builder.cpp:19:
extension/internal/pdfinput/svg-builder.h:32:23: error: CharTypes.h: No such file or directory
...
make[2]: *** [extension/internal/pdfinput/svg-builder.o] Error 1
make[2]: Leaving directory `/tmp/build/inkscape-0.46/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/build/inkscape-0.46'
make: *** [all] Error 2</pre>
* Inkscape 0.47 does not compile with Poppler >= 0.12.2. If you need to compile Inkscape on such systems, use the development version from Bazaar, where this bug is fixed. See [https://bugs.launchpad.net/inkscape/+bug/487038 the bug report] for details and a minimal patch.
* Inkscape compiled with Poppler <= 0.12.1 will run on systems with Poppler >= 0.12.2, but the PDF import function will crash instantly. This problem does not concern Windows users, since the correct Poppler version is contained in the Windows installer package. This cannot be fixed on Inkscape's side: those two versions of Poppler are not ABI compatible, yet share the same soname. See [https://bugs.launchpad.net/inkscape/+bug/258504 this bug] for more details.
* Poppler's Xpdf headers are not guaranteed to be API-compatible between releases. It's likely that future Poppler versions will break PDF import in some way. PDF import works at least up to 0.12.4 but might not work with later versions.

[[Category:About Inkscape]]
[[Category:Developer Documentation]]

Hackfest2015 Attendees

2015-03-03T16:08:17Z

ScislaC: /* Who is Attending? */

Information about and for Hackfest2015 Attendees

== Who is Attending? ==

{| class="wikitable"
|+ List of Attendees
Hackfest
|-
! rowspan="2" | Who
! colspan="2" | Dates
! colspan="2" | Allocation
! colspan="2" | Flights
! rowspan="2" | Hotel
|-
! Hackfest
! LGM
! Hackfest
! LGM
! Arrival
! Departure
|-
| Bryce Harrington
| 4/26, 4/27, 4/28
| 4/29, 4/30, 5/1, 5/2
| Sponsored
| Sponsored
| UA0843 YYZ @ 8:13pm
| UA5165 YYZ @ 10:10am
| Courtyard Downtown Marriott
|-
| Tavmjong Bah
| 4/26, 4/27, 4/28
| 4/29, 4/30, 5/1
| $2000
| $500
|
|
|
|-
| Jon Cruz
| --
| 4/29, 4/30, 5/1, 5/2
| N/A
| Sponsored
|
|
|
|-
| Josh Andler
| 4/26, 4/27, 4/28
| 4/29, 4/30, 5/1, 5/2
| Sponsored?
|
| AC1038 YYZ @ 4:24pm
| AC755 YYZ @ 12:05pm
|
|-
| Martin Owen
| 4/26, 4/27, 4/28
| 4/29, 4/30, 5/1, 5/2
| $2000
| $500
| PD942 YTZ @ 2:50PM
| PD945 YTZ @ 2:35PM
| None Yet
|-
| Jabiertxo Cenoz
| 4/26, 4/27, 4/28
| 4/29, 4/30, 5/1, 5/2
| $1000
| $500
|
|
|-
| Krzysztof Kosiński
| 4/26, 4/27, 4/28
| --
| $2000
| N/A
|
|
|
|-
| Inkscaper
|
|
|
|
|
|
|-
| Inkscaper
|
|
|
|
|
|
|-
! Total
!
!
! $7000
! $1500
!
!
|}

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, 2015.

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

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 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.

Most international flights arrive at Pearson International Airport (YYZ). Some Canadian and US flights arrive at Billy Bishop Toronto City Airport (YTZ).

See also: [http://libregraphicsmeeting.org/2015/travel/ LGM Travel page].

=== Hotel ===

The [http://libregraphicsmeeting.org/2015/travel/accommodation/ LGM Accommodation page] is pretty sparse. The AirBnB suggestion is worth looking into (I paid 1/3 of what a hotel would cost in Sydney using AirBnB). If you are interested in sharing a room (US/Canadian hotel rooms are usually quite big, often with two queen size beds) leave a note here:

=== Venue ===

The hackfest will be held in [to be filled in].

A map of the U. of Toronto campus can be found on the [http://libregraphicsmeeting.org/2015/venue/ LGM Venue page].

== 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).

Hackfest2015 Attendees

2015-03-03T15:54:42Z

ScislaC: /* Who is Attending? */

Information about and for Hackfest2015 Attendees

== Who is Attending? ==

{| class="wikitable"
|+ List of Attendees
Hackfest
|-
! rowspan="2" | Who
! colspan="2" | Dates
! colspan="2" | Allocation
! colspan="2" | Flights
! rowspan="2" | Hotel
|-
! Hackfest
! LGM
! Hackfest
! LGM
! Arrival
! Departure
|-
| Bryce Harrington
| 4/26, 4/27, 4/28
| 4/29, 4/30, 5/1, 5/2
| Sponsored
| Sponsored
| UA0843 YYZ @ 8:13pm
| UA5165 YYZ @ 10:10am
| Courtyard Downtown Marriott
|-
| Tavmjong Bah
| 4/26, 4/27, 4/28
| 4/29, 4/30, 5/1
| $2000
| $500
|
|
|
|-
| Jon Cruz
| --
| 4/29, 4/30, 5/1, 5/2
| N/A
| Sponsored
|
|
|
|-
| Josh Andler
| 4/26, 4/27, 4/28
| 4/29, 4/30, 5/1, 5/2
| Sponsored?
|
|
|
|
|-
| Martin Owen
| 4/26, 4/27, 4/28
| 4/29, 4/30, 5/1, 5/2
| $2000
| $500
| PD942 YTZ @ 2:50PM
| PD945 YTZ @ 2:35PM
| None Yet
|-
| Jabiertxo Cenoz
| 4/26, 4/27, 4/28
| 4/29, 4/30, 5/1, 5/2
| $1000
| $500
|
|
|-
| Krzysztof Kosiński
| 4/26, 4/27, 4/28
| --
| $2000
| N/A
|
|
|
|-
| Inkscaper
|
|
|
|
|
|
|-
| Inkscaper
|
|
|
|
|
|
|-
! Total
!
!
! $7000
! $1500
!
!
|}

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, 2015.

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

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 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.

Most international flights arrive at Pearson International Airport (YYZ). Some Canadian and US flights arrive at Billy Bishop Toronto City Airport (YTZ).

See also: [http://libregraphicsmeeting.org/2015/travel/ LGM Travel page].

=== Hotel ===

The [http://libregraphicsmeeting.org/2015/travel/accommodation/ LGM Accommodation page] is pretty sparse. The AirBnB suggestion is worth looking into (I paid 1/3 of what a hotel would cost in Sydney using AirBnB). If you are interested in sharing a room (US/Canadian hotel rooms are usually quite big, often with two queen size beds) leave a note here:

=== Venue ===

The hackfest will be held in [to be filled in].

A map of the U. of Toronto campus can be found on the [http://libregraphicsmeeting.org/2015/venue/ LGM Venue page].

== 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).

Hackfest2015

2015-02-27T23:05:01Z

ScislaC: /* Tasks to tackle */

This page details the planning of an Inkscape Hackfest in April 2015

== Discusson ==

See the [[Board_Meetings]] page for minutes of past discussions and the time and place of the next discussion.

== 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.

Maybe even some Gtk+ issues: http://wiki.inkscape.org/wiki/index.php/GTK%2B_Issues

== The Pitch ==

Inkscape is a free, fully open source, community-developed, socially owned software program that allows everyone to explore their creativity. Digital artists use it to produce professional quality work. Engineers and scientists use it to create clear drawings to explain their ideas. Everyday people use it to create simple drawings, develop their design skills, and just have fun.

We need your help to further improve the program so many people love, and make sure it has a bright future!

Our dedicated volunteer Inkscape developers are spread across the globe and rarely have the chance to meet face-to-face. Thanks to technology, we are able to work remotely on most things, but we've noticed that in-person meetings bring about stronger relationships, quicker solutions, and more creative results.

Being together in one room also allows us to work on things that are harder to do on-line: designing a new plugin/extension system, teaming up to squash particularly nasty bugs, authoring better user documentation, and planning where to take Inkscape development in the future.

We will be meeting before the [http://libregraphicsmeeting.org/2014/ Libre Graphics Meeting] (April 29 to May 2, 2015) in Toronto for three days of intense hacking.

Please consider donating a few bucks to help cover travel, room, and board so our available volunteer developers can attend the hackfest in person? It's an investment in Inkscape which should produce big benefits for all its users and help us make the product the very best it can be.

* Organizations that use Inkscape to draw testimonials from: http://wiki.inkscape.org/wiki/index.php/UsedBy
* Some of the nifty new features: http://inkscapetutorials.wordpress.com/category/0-91-new-features/
* TODO: Needs some photos of our developers, or images of what we'll be working on

All donations are fully tax deductable to the extent permitted by law. Suggested donation amounts:
* $5 –
* $50 – Covers meals & incidentals for one developer
* $120 – Equivalent to half of a year's subscription to a proprietary drawing program.
* $500 – Business level. Named as sponsor on the Hackfest website.
* $1000 - Sponsors a nearby US/Canada developer.
* $2000 – Sponsors a developer from afar.
* $5000 - Corporate level. Named as a Corporate Sponsor on both the Hackfest website and in news items about the event. [Extra perks?]
* Other – Whatever you can spare. Every donation helps!

To make your donation, (insert here how they do that)

Thanks so much for being an investor in Inkscape and contributing to help bring the developers together in Toronto. We appreciate your commitment to free, fully open source, community-developed, socially owned software, and your vision for Inkscape. We are grateful to have you on our team!

== Date ==

Sunday, April 26th through Tuesday, April 28th; just before the [http://libregraphicsmeeting.org/2014/ Libre Graphics Meeting 2015] (LGM2015) which takes place from [http://lists.freedesktop.org/archives/create/2014-May/004961.html April 29th through May 2nd 2015] (note: email states 30th through 2nd but an email on libre-graphics-meeting states that one day has been added at the beginning).

== Schedule ==

A sketch of what might happen on hackfest days, 2 or 3 days of things should be planned.

a) Social meeting
b) Pre-lunch presentations
c) Lunch
d) Pure hacking
e) Dinner
f) Late night hacking

== Location ==

Toronto at the same venue as LGM. We have a room reserved for us that can hold up to 30 people. It has movable tables with built in power outlets and a 40" TV in lieu of a projector.

== Budget ==

We had 8 attendees at the last LGM, and are hoping for perhaps 12 people this time.
Roughly, assuming costs will be in the $1000-2000 range per person for travel, room, and board, that gives a budget of $9-18k

To get more specific we'll need to:
* Estimate of hotel costs per night: $50 per person for shared double in two star hotel, $30 per person in hostel
* Estimate of airfare costs from Europe ($900), West Coast ($750), East Coast ($300), etc.
* Plan a daily food/incidentals stipend amount (~$30)

Cost estimate for 3 days pre-LGM in Toronto:
* From Paris: airfare $900 + $200 hotel + $100 food = $1200
* From Boston: airfare $300 + $200 hotel + $100 food = $600
* From Zurich: airfare $900 + $200 hotel + $100 food = $1200
* From Los Angeles: airfare $750 + $200 hotel + $100 food = $1150

We're considering a model similar to what we did with reimbursement limits for the GSoC reunion:

* Up to $2000 each for Inkscape developers who have contributed for 3+ years and > 200 commits (About 18 developers qualify, not all currently active)
* Up to $1500 each for Inkscape developers who have contributed for 2+ years and > 100 commits (About 17 additional qualify)
* Up to $1000 each for Inkscape developers who have contributed for 1+ year and > 50 commits (About 24 additional qualify)
* Up to $500 each for any Inkscape contributor listed in AUTHORS file with at least 10 commits by Jan 1, 2015 (About 50 additional qualify)

We should also consider sponsoring Inkscape contributors who are not developers (translators,etc.).

== Sponsors ==

Finding local companies who might like to sponsor the event, help out with feeding people or bringing them to attend can be documented here.

maybe if we had some kind of form letter folks could give to their employer
i save you this much $$ per year in adobe whatever license fees. would you support my work for this company by contributing some percentage of that back to the inkscape project

* http://wiki.inkscape.org/wiki/index.php/UsedBy

=== Sponsors' interests ===
It would help a lot if we have specific ideas about how to compensate sponsors, what they would be "buying".

Interests and offerings
* PR among users
** News item with clear marking of who sponsored the event
* Improving a product that they ship
** Work on specific bugs may be very tricky
** offer to work on general code improvement (focussing on refactoring/ease for devs to develop new things, for example) seems good
* Improving a product that many of their employees use
** Work on specific bugs may be very tricky
** offer to work on general code improvement (focussing on stability, for example) seems good
* PR among coders
** Clear PR during event
** Making contacts with development team
** News item with clear marking of who sponsored the event

== Action items ==

{| border="1" cellspacing="0" cellpadding="5" align="center"
|-
! Date
! Owner
! Item
|-
| 15 sep 2014
| Karen Sandler (SFC)
| [DONE] Could inquire if RH and Google can sponsor
|-
| 15 sep 2014
| Bryce
| [DONE] Get the fundraising doc posted on our website
|-
| 15 sep 2014
| Bryce
| Once we have things more nailed down: inquire with samsung for hackfest sponsorship
|-
| 15 sep 2014
| Martin Owens
| Hear back from LGM about Torronto co-sponsorship
|-
| 15 sep 2014
| ScislaC
| Contact userbase for interest in the hackfest
|-
| 15 sep 2014
| ScislaC
| [DONE] Get a list of [[http://wiki.inkscape.org/wiki/index.php/UsedBy companies using inkscape]]
|-
| 15 sep 2014
| Tav
| [DONE] Summarize and mail devlist
|-
| 20 sep 2014
| Tav
| [DONE] Set up a new wiki page for planning second Hackfest w/ RedHat
|-
| 20 sep 2014
| Bryce
| [DONE] Draft a preliminary promotional fundraising blurb
|-
| 20 sep 2014
| ryanlerch
| Work on a video for fundraiser
|-
| 20 sep 2014
| everyone
| [DONE] Consider indiegogo vs. hosting our own paypal donation page
|-
| 15 oct 2014
| everyone
| [DONE] Decide plan for implementing website/db support for fundraiser campaigns
|-
| 15 oct 2014
| karen
| Can we use Inkscape's existing paypal account or should we set up a separate one for fundraising
|-
| 15 oct 2014
| karen
| If we set the product_id on the donation page, can SFC provide us with a summary (or the raw data) with this info, so we can tally hackfest contribs?
|-
| 15 oct 2014
|
| Mockup layout on Staging for a fundraiser/donation page (using text from Pitch)
|-
| 12 nov 2014
|
| Decide where in inkscape.org's site menu to place Hackfest related pages
|-
| 12 nov 2014
|
| Create a Hackfest page in the main website
|-
| 12 nov 2014
|
| Write a page for Toronto transportation for A) how to get to/from airport, and B) how to get around the city
|-
| 12 nov 2014
|
| Write a set of posts for Inkscape blog / news feed (to be finalized + published as the event nears)
|-
| 12 nov 2014
|
| Find someone local to Toronto to help with local logistics
|-
| 12 nov 2014
|
| Translate the Hackfest Donation page to French
|-
| 12 nov 2014
|
| Translate the Hackfest Donation page to Spanish (and/or other major languages)

|}

== Brainstorm area ==
Put things here that you think could use a bit of discussion/thought.

Places to announce the fundraiser, once it's set up?
* Inkscape's g+ page
* inkscape-users@
* twitter
* dA
* the website
* <karenesq> I bet LWN would be interested
* <doctormon> Possible interest: http://zipfelchappe.readthedocs.org/en/latest/
* <ryanlerch> i can promote on inkscapetuts and fedoramagazine too

=== Tasks to tackle ===
What can we hack on? To me (Johan) what seems nice are tasks that become more managable/fun/... and with higher chance of completion (maximum one day) when done in a group. Before determining specific tasks, what kind of tasks should we try to tackle?
* Fleshing out documentation
** Code documentation
** Architecture docs
** Coding howtos
** Tutorials
** User documentation
** Translation of same
* A bug that requires knowledge of large part of codebase.
* Writing test cases
* Simple repetitive refactoring or code clean up that can be parallelized and may not be so much fun alone. Examples:
** make sure every file contains standardized and correct copyright notice,
** eradicate all use of gboolean/TRUE/FALSE,
** move towards C++11 by =delete on copy-constructors instead of making them private+undefined).
* A more complicated refactoring that requires discussion.
** Conversion of build system
** Performance optimizations
** Coordinate flip.
* Canvas issues [https://inkscape.org/en/gallery/6314/ https://inkscape.org/en/gallery/6314/ - videos by s_uv]
** Canvas flickering on GTK3
** GTK2/Quartz canvas issues
* A feature that can be split into parallelizable tasks possibly with different skills required, for example:
** combination of UI, backline math stuff, usability/behavior stuff.
** Infrastructure setup
* Design / strategy collaboration
** SVG 2 fallbacks
** New plugin/extension system
* Planning
** Post-1.0 roadmap definition
** Conference attendance for upcoming year
** Future hackfests :-)
* Pictures pictures pictures
** Try to make nice pictures that show what has happened. Can then also be used for PR for next edition.

For the evening libation hacking sessions:
* Fun stuff, obviously. So perhaps a quirky feature, and see next day if it lead to something usable.

=== Participants ===

We aim for around 10 people.

Who do we expect to join (not remote), what kind of people?

* Seasoned Inkscape developers? Yes.
* More recently joined Inkscape developers? Yes.
* Coders unfamiliar with Inkscape? Possibly one or two. Local students, e.g.
** Good programmers with experience?
** New programmers with little experience?
* Users? Probably none that don't fall in other categories
** Graphic designers?
** Technical drawers?
** 'Powerpoint' figure drawers?
We can make a list of possible tasks for each of these groups.

For the first hackfest, I (Tav) would keep it open to anyone, but only promote it to people already familiar with the Inkscape code base.

=== Help for newcomers ===
* Provide a VM image with: Inkscape's trunk ready to compile. Preferably with clang so one can run clang's static analyzer and quickly get a nicely formatted report of potential bugs that are generally easy to fix (i.e. null-ptr checking, etc).
* List of simple tasks

=== Non-coding stuff ===
Some ideas for socializing and getting away from PC screen
* Karaoke :)
* Board/card games
* Run around town
* Movie
* Pub
* Take a group picture!!!

Hackfest2015

2015-02-27T23:04:05Z

ScislaC: /* Tasks to tackle */

This page details the planning of an Inkscape Hackfest in April 2015

== Discusson ==

See the [[Board_Meetings]] page for minutes of past discussions and the time and place of the next discussion.

== 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.

Maybe even some Gtk+ issues: http://wiki.inkscape.org/wiki/index.php/GTK%2B_Issues

== The Pitch ==

Inkscape is a free, fully open source, community-developed, socially owned software program that allows everyone to explore their creativity. Digital artists use it to produce professional quality work. Engineers and scientists use it to create clear drawings to explain their ideas. Everyday people use it to create simple drawings, develop their design skills, and just have fun.

We need your help to further improve the program so many people love, and make sure it has a bright future!

Our dedicated volunteer Inkscape developers are spread across the globe and rarely have the chance to meet face-to-face. Thanks to technology, we are able to work remotely on most things, but we've noticed that in-person meetings bring about stronger relationships, quicker solutions, and more creative results.

Being together in one room also allows us to work on things that are harder to do on-line: designing a new plugin/extension system, teaming up to squash particularly nasty bugs, authoring better user documentation, and planning where to take Inkscape development in the future.

We will be meeting before the [http://libregraphicsmeeting.org/2014/ Libre Graphics Meeting] (April 29 to May 2, 2015) in Toronto for three days of intense hacking.

Please consider donating a few bucks to help cover travel, room, and board so our available volunteer developers can attend the hackfest in person? It's an investment in Inkscape which should produce big benefits for all its users and help us make the product the very best it can be.

* Organizations that use Inkscape to draw testimonials from: http://wiki.inkscape.org/wiki/index.php/UsedBy
* Some of the nifty new features: http://inkscapetutorials.wordpress.com/category/0-91-new-features/
* TODO: Needs some photos of our developers, or images of what we'll be working on

All donations are fully tax deductable to the extent permitted by law. Suggested donation amounts:
* $5 –
* $50 – Covers meals & incidentals for one developer
* $120 – Equivalent to half of a year's subscription to a proprietary drawing program.
* $500 – Business level. Named as sponsor on the Hackfest website.
* $1000 - Sponsors a nearby US/Canada developer.
* $2000 – Sponsors a developer from afar.
* $5000 - Corporate level. Named as a Corporate Sponsor on both the Hackfest website and in news items about the event. [Extra perks?]
* Other – Whatever you can spare. Every donation helps!

To make your donation, (insert here how they do that)

Thanks so much for being an investor in Inkscape and contributing to help bring the developers together in Toronto. We appreciate your commitment to free, fully open source, community-developed, socially owned software, and your vision for Inkscape. We are grateful to have you on our team!

== Date ==

Sunday, April 26th through Tuesday, April 28th; just before the [http://libregraphicsmeeting.org/2014/ Libre Graphics Meeting 2015] (LGM2015) which takes place from [http://lists.freedesktop.org/archives/create/2014-May/004961.html April 29th through May 2nd 2015] (note: email states 30th through 2nd but an email on libre-graphics-meeting states that one day has been added at the beginning).

== Schedule ==

A sketch of what might happen on hackfest days, 2 or 3 days of things should be planned.

a) Social meeting
b) Pre-lunch presentations
c) Lunch
d) Pure hacking
e) Dinner
f) Late night hacking

== Location ==

Toronto at the same venue as LGM. We have a room reserved for us that can hold up to 30 people. It has movable tables with built in power outlets and a 40" TV in lieu of a projector.

== Budget ==

We had 8 attendees at the last LGM, and are hoping for perhaps 12 people this time.
Roughly, assuming costs will be in the $1000-2000 range per person for travel, room, and board, that gives a budget of $9-18k

To get more specific we'll need to:
* Estimate of hotel costs per night: $50 per person for shared double in two star hotel, $30 per person in hostel
* Estimate of airfare costs from Europe ($900), West Coast ($750), East Coast ($300), etc.
* Plan a daily food/incidentals stipend amount (~$30)

Cost estimate for 3 days pre-LGM in Toronto:
* From Paris: airfare $900 + $200 hotel + $100 food = $1200
* From Boston: airfare $300 + $200 hotel + $100 food = $600
* From Zurich: airfare $900 + $200 hotel + $100 food = $1200
* From Los Angeles: airfare $750 + $200 hotel + $100 food = $1150

We're considering a model similar to what we did with reimbursement limits for the GSoC reunion:

* Up to $2000 each for Inkscape developers who have contributed for 3+ years and > 200 commits (About 18 developers qualify, not all currently active)
* Up to $1500 each for Inkscape developers who have contributed for 2+ years and > 100 commits (About 17 additional qualify)
* Up to $1000 each for Inkscape developers who have contributed for 1+ year and > 50 commits (About 24 additional qualify)
* Up to $500 each for any Inkscape contributor listed in AUTHORS file with at least 10 commits by Jan 1, 2015 (About 50 additional qualify)

We should also consider sponsoring Inkscape contributors who are not developers (translators,etc.).

== Sponsors ==

Finding local companies who might like to sponsor the event, help out with feeding people or bringing them to attend can be documented here.

maybe if we had some kind of form letter folks could give to their employer
i save you this much $$ per year in adobe whatever license fees. would you support my work for this company by contributing some percentage of that back to the inkscape project

* http://wiki.inkscape.org/wiki/index.php/UsedBy

=== Sponsors' interests ===
It would help a lot if we have specific ideas about how to compensate sponsors, what they would be "buying".

Interests and offerings
* PR among users
** News item with clear marking of who sponsored the event
* Improving a product that they ship
** Work on specific bugs may be very tricky
** offer to work on general code improvement (focussing on refactoring/ease for devs to develop new things, for example) seems good
* Improving a product that many of their employees use
** Work on specific bugs may be very tricky
** offer to work on general code improvement (focussing on stability, for example) seems good
* PR among coders
** Clear PR during event
** Making contacts with development team
** News item with clear marking of who sponsored the event

== Action items ==

{| border="1" cellspacing="0" cellpadding="5" align="center"
|-
! Date
! Owner
! Item
|-
| 15 sep 2014
| Karen Sandler (SFC)
| [DONE] Could inquire if RH and Google can sponsor
|-
| 15 sep 2014
| Bryce
| [DONE] Get the fundraising doc posted on our website
|-
| 15 sep 2014
| Bryce
| Once we have things more nailed down: inquire with samsung for hackfest sponsorship
|-
| 15 sep 2014
| Martin Owens
| Hear back from LGM about Torronto co-sponsorship
|-
| 15 sep 2014
| ScislaC
| Contact userbase for interest in the hackfest
|-
| 15 sep 2014
| ScislaC
| [DONE] Get a list of [[http://wiki.inkscape.org/wiki/index.php/UsedBy companies using inkscape]]
|-
| 15 sep 2014
| Tav
| [DONE] Summarize and mail devlist
|-
| 20 sep 2014
| Tav
| [DONE] Set up a new wiki page for planning second Hackfest w/ RedHat
|-
| 20 sep 2014
| Bryce
| [DONE] Draft a preliminary promotional fundraising blurb
|-
| 20 sep 2014
| ryanlerch
| Work on a video for fundraiser
|-
| 20 sep 2014
| everyone
| [DONE] Consider indiegogo vs. hosting our own paypal donation page
|-
| 15 oct 2014
| everyone
| [DONE] Decide plan for implementing website/db support for fundraiser campaigns
|-
| 15 oct 2014
| karen
| Can we use Inkscape's existing paypal account or should we set up a separate one for fundraising
|-
| 15 oct 2014
| karen
| If we set the product_id on the donation page, can SFC provide us with a summary (or the raw data) with this info, so we can tally hackfest contribs?
|-
| 15 oct 2014
|
| Mockup layout on Staging for a fundraiser/donation page (using text from Pitch)
|-
| 12 nov 2014
|
| Decide where in inkscape.org's site menu to place Hackfest related pages
|-
| 12 nov 2014
|
| Create a Hackfest page in the main website
|-
| 12 nov 2014
|
| Write a page for Toronto transportation for A) how to get to/from airport, and B) how to get around the city
|-
| 12 nov 2014
|
| Write a set of posts for Inkscape blog / news feed (to be finalized + published as the event nears)
|-
| 12 nov 2014
|
| Find someone local to Toronto to help with local logistics
|-
| 12 nov 2014
|
| Translate the Hackfest Donation page to French
|-
| 12 nov 2014
|
| Translate the Hackfest Donation page to Spanish (and/or other major languages)

|}

== Brainstorm area ==
Put things here that you think could use a bit of discussion/thought.

Places to announce the fundraiser, once it's set up?
* Inkscape's g+ page
* inkscape-users@
* twitter
* dA
* the website
* <karenesq> I bet LWN would be interested
* <doctormon> Possible interest: http://zipfelchappe.readthedocs.org/en/latest/
* <ryanlerch> i can promote on inkscapetuts and fedoramagazine too

=== Tasks to tackle ===
What can we hack on? To me (Johan) what seems nice are tasks that become more managable/fun/... and with higher chance of completion (maximum one day) when done in a group. Before determining specific tasks, what kind of tasks should we try to tackle?
* Fleshing out documentation
** Code documentation
** Architecture docs
** Coding howtos
** Tutorials
** User documentation
** Translation of same
* A bug that requires knowledge of large part of codebase.
* Writing test cases
* Simple repetitive refactoring or code clean up that can be parallelized and may not be so much fun alone. Examples:
** make sure every file contains standardized and correct copyright notice,
** eradicate all use of gboolean/TRUE/FALSE,
** move towards C++11 by =delete on copy-constructors instead of making them private+undefined).
* A more complicated refactoring that requires discussion.
** Conversion of build system
** Performance optimizations
** Coordinate flip.
* Canvas issues [https://inkscape.org/en/gallery/6314/ https://inkscape.org/en/gallery/6314/ videos by s_uv]
** Canvas flickering on GTK3
** GTK2/Quartz canvas issues
* A feature that can be split into parallelizable tasks possibly with different skills required, for example:
** combination of UI, backline math stuff, usability/behavior stuff.
** Infrastructure setup
* Design / strategy collaboration
** SVG 2 fallbacks
** New plugin/extension system
* Planning
** Post-1.0 roadmap definition
** Conference attendance for upcoming year
** Future hackfests :-)
* Pictures pictures pictures
** Try to make nice pictures that show what has happened. Can then also be used for PR for next edition.

For the evening libation hacking sessions:
* Fun stuff, obviously. So perhaps a quirky feature, and see next day if it lead to something usable.

=== Participants ===

We aim for around 10 people.

Who do we expect to join (not remote), what kind of people?

* Seasoned Inkscape developers? Yes.
* More recently joined Inkscape developers? Yes.
* Coders unfamiliar with Inkscape? Possibly one or two. Local students, e.g.
** Good programmers with experience?
** New programmers with little experience?
* Users? Probably none that don't fall in other categories
** Graphic designers?
** Technical drawers?
** 'Powerpoint' figure drawers?
We can make a list of possible tasks for each of these groups.

For the first hackfest, I (Tav) would keep it open to anyone, but only promote it to people already familiar with the Inkscape code base.

=== Help for newcomers ===
* Provide a VM image with: Inkscape's trunk ready to compile. Preferably with clang so one can run clang's static analyzer and quickly get a nicely formatted report of potential bugs that are generally easy to fix (i.e. null-ptr checking, etc).
* List of simple tasks

=== Non-coding stuff ===
Some ideas for socializing and getting away from PC screen
* Karaoke :)
* Board/card games
* Run around town
* Movie
* Pub
* Take a group picture!!!

Tracking Dependencies

2015-02-24T00:12:37Z

ScislaC: Update Utopic libs

== Overview ==

We need help getting our basic lib dependencies listed out and kept up to date. Also we need to track which versions of which distros have the needed dependencies.

To get glib and GTK+ dependencies figured out, people can go through the API documentation and look for the 'since' entries saying when calls were added. Then look for those calls in our source. Voila! we'll have base minimum dependencies figured out.

== Libs ==

C++ bindings are not included, since their required versions match those of the C counterparts.

{| class="wikitable"
|-
! Library
! v 0.91
! trunk
! trunk (GTK+ 3.0 build)
|-
| Boehm-GC
| 7.1
| 7.1
| 7.1
|-
| Cairo
| 1.10
| 1.10
| 1.10
|-
| GDL
| N/A
| N/A
| 3.3.4
|-
| Glib
| 2.28
| 2.28
| 2.28
|-
| GTK+
| 2.24
| 2.24
| 3.2
|-
| GNU Scientific Library
| ?
| ?
| ?
|-
| LittleCMS
| 1.13
| 1.13
| 1.13
|-
| libxml
| ''2.6.11*''
| ''2.6.11*''
| ''2.6.11*''
|-
| libxslt
| ''1.0.15*''
| ''1.0.15*''
| ''1.0.15*''
|-
| Pango
| ?
| ?
| 1.24
|-
| Poppler
| ''0.5.9*''
| 0.8.3
| 0.8.3
|-
| libsigc++
| ''2.0.12*''
| ''2.0.12*''
| ''2.0.12*''
|}

''* Tentative dependency''

== Distros ==

Note: This table is not relevant to (non-fink) MacOS X, where we ship the desired version with Inkscape.

{| class="wikitable"
|-
! Distro
! cairo
! cairomm
! glib
! glibmm
! gtk+
! gtkmm
! pango
! poppler
! gdl
! lcms
! libsigc++
! libgc 
|-
| style="background:Violet;"|Windows Devlibs (32bit) [https://code.launchpad.net/~inkscape.dev/inkscape-devlibs/trunk] (r53)
| 1.11.2
| 1.10.0
| 2.28.8
| 2.28.2
| style="background:Violet;"| 2.24.10
| style="background:Violet;"| 2.24.2
| 1.28.3
| 0.12.1
| style="background:Violet;"| (none)
| 1.17 2.4
| 2.2.11
| 7.1
|-
| Windows Devlibs Gtk+ 3 branch [https://code.launchpad.net/~inkscape.dev/inkscape-devlibs/devlibs-gtk3] (r34)
| 1.10.2
| 1.10.0
| 2.38.0
| 2.36.0
| 2.24.18 3.8.1
| 2.24.2 3.8.0
| 1.34.0
| 0.22.5
| 3.4.2
| 1.19 2.4
| 2.2.10
| 7.2d
|-
| Windows Devlibs 64bit [https://code.launchpad.net/~inkscape.dev/inkscape-devlibs64/trunk] (r17)
| 1.14.1
| 1.11.2
| 2.40.0
| 2.40.0
| 2.24.23 3.13.1
| 2.24.4 3.12.0
| 1.36.3
| 0.24.2
| 3.12.0
| - 2.6
| 2.3.1
| 7.2
|-
| Debian 7.0 (Wheezy, stable)
| 1.12.2
| 1.10.0
| 2.33.12
| 2.32.1
| 2.24.10 3.4.2
| 2.24.2 3.4.2
| 1.32.5
| 0.18.4
| 3.4.2
| 1.19 2.2
| 2.2.10
| 7.1
|-
| Fedora 20
| 1.13.1+git
| 1.10.0
| 2.38.2
| 2.38.1
| 2.24.22 3.10.6
| 2.24.4 3.10.1
| 1.36.1
| 0.24.3
| 3.10.0
| 1.19 2.5
| 2.3.1
| 7.2d
|-
| OpenSuSE 13.1 EOL 2015-05-01[http://en.opensuse.org/Lifetime]
| 1.12.16
| 1.10.0
| 2.38.1
| 2.38.0
| 2.24.22 3.10.2
| 2.24.4 3.10.0
| 1.36.0
| 0.24.3
| 3.10.0
| 1.19 2.5
| 2.3.1
| 7.2d
|-
| Ubuntu 12.04 LTS (Precise) EOL 2017-04
| 1.10.2
| 1.10.0
| 2.32.4
| 2.32.0
| 2.24.10 3.4.2
| 2.24.2 3.4.0
| 1.30.0
| 0.18.4
| 3.3.91
| 1.19 2.2
| 2.2.10
| 7.1
|-
| Ubuntu 14.04 (Trusty) EOL 2019-04
| 1.13.0
| 1.10.0
| 2.40.2
| 2.39.93
| 2.24.23 3.10.8
| 2.24.4 3.10.1
| 1.36.3
| 0.24.5
| 3.8.1
| 1.19 2.5
| 2.2.10
| 7.2d
|-
| Ubuntu 14.10 (Utopic), EOL 2015-07
| 1.13.0
| 1.10.0
| 2.42.1
| 2.42.0
| 2.24.25 3.12.2
| 2.24.4 3.12.0
| 1.36.6
| 0.26.5
| 3.12.0
| 1.19 2.6
| 2.2.11
| 7.2d
|-
| Ubuntu 15.04 (Vivid) (As of 2015-02-23), EOL 2016-01
| 1.14.0
| 1.11.2
| 2.43.90
| 2.42.0
| 2.24.26 3.14.8
| 2.24.4 3.14.0
| 1.36.8
| 0.30.0
| 3.14.0
| - 2.6
| 2.4.0
| 7.2d
|}

{| class="wikitable"
|-
! Legend
|-
| style="background:Red;"| Inkscape stable unsupported
|-
| style="background:Orange;"| Inkscape trunk unsupported
|-
| style="background:Violet;"| GTK+ 3 builds unsupported
|}

== Getting and Installing Source packages ==

If your distro does not have some packages available (like many don't, ie, Fedora Core 2), you must often download
source packages and build and install them yourself. Actually this is not that hard, and is similar to
doing a Gentoo 'emerge.'

* Usually you download a file with a name like somepackage-1.0.tar.gz. Unpack it with

$ tar zxf somepackage-1.0.tar.gz
or
$ tar jxf somepackage-1.0.tar.bz2

* Then 'cd' into the new directory.

* Configure it with the command:

$ ./configure

* Build it with:

$ make

* As the 'root' user, install it with:

# make install

=== Boehm-GC ===

Source: http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source

* Download this file:
** http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/gc6.8.tar.gz
* Unpack it
** tar zxf gc6.8.tar.gz
* Configure and build it
** cd gc6.8
** ./configure --disable-shared --enable-static
** make
* Install it
** su (or however else you become root)
** make install

Binaries: If searching for a package for GC, the name of it is sometimes:

* gc
* libgc
* gc-devel
* libgc-devel
* boehm-gc (on Gentoo)
* debian/ubuntu: sudo apt-get install libgc-dev

=== libSigc++ ===

Source: http://ftp.gnome.org/pub/GNOME/sources/libsigc++/2.2/libsigc++-2.2.3.tar.bz2

With this file, and for GlibMM and GtkMM below, it is usually desirable for us developers to
build this C++ library statically. This removes a dependency that might be difficult for an
end-user during installation. Configure it with:

./configure --enable-static --disable-shared

=== GlibMM ===
Try to match your Glib2 version with GlibMM's version. For example, if your Glib2 is 2.16.6, download glibmm-2.16.4.tar.bz2.

Latest source: http://ftp.gnome.org/pub/GNOME/sources/glibmm/

=== GtkMM ===
Usually you can try the latest version of GtkMM, but if you get version mismatch errors, try older releases.

Source: http://ftp.gnome.org/pub/GNOME/sources/gtkmm/2.12/gtkmm-2.12.7.tar.bz2

=== cairomm ===

if you got prompted about cairomm, try first solve your cairo version, so you can grab [http://www.cairographics.org/releases/ there] a compatible version.

=== Boost ===

Many users have reported when building from source that after installing the above dependencies, the configure script still requires a "boost" package. It can be found below, but even after installing, you will need to create a symlink to allow the configure script to find it:

ln -s /usr/local/include/boost_1_xx_x/boost /usr/local/include/boost

Source: http://www.boost.org/users/download/

=== Poppler ===

Source: http://poppler.freedesktop.org/

Poppler is required for PDF import. There are several potential issues:
* Some Linux distributions do not ship the Xpdf headers required by Inkscape. In such cases, you need to recompile Poppler, passing --enable-xpdf-headers on the configure line or install the libpoppler-private-dev package. See [https://bugs.launchpad.net/inkscape/+bug/254849 this wishlist bug]. This typically manifests in error messages like this:
<pre>In file included from extension/internal/pdfinput/svg-builder.cpp:19:
extension/internal/pdfinput/svg-builder.h:32:23: error: CharTypes.h: No such file or directory
...
make[2]: *** [extension/internal/pdfinput/svg-builder.o] Error 1
make[2]: Leaving directory `/tmp/build/inkscape-0.46/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/build/inkscape-0.46'
make: *** [all] Error 2</pre>
* Inkscape 0.47 does not compile with Poppler >= 0.12.2. If you need to compile Inkscape on such systems, use the development version from Bazaar, where this bug is fixed. See [https://bugs.launchpad.net/inkscape/+bug/487038 the bug report] for details and a minimal patch.
* Inkscape compiled with Poppler <= 0.12.1 will run on systems with Poppler >= 0.12.2, but the PDF import function will crash instantly. This problem does not concern Windows users, since the correct Poppler version is contained in the Windows installer package. This cannot be fixed on Inkscape's side: those two versions of Poppler are not ABI compatible, yet share the same soname. See [https://bugs.launchpad.net/inkscape/+bug/258504 this bug] for more details.
* Poppler's Xpdf headers are not guaranteed to be API-compatible between releases. It's likely that future Poppler versions will break PDF import in some way. PDF import works at least up to 0.12.4 but might not work with later versions.

[[Category:About Inkscape]]
[[Category:Developer Documentation]]

Roadmap

2014-12-05T23:27:06Z

ScislaC: /* Maintenance */

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 ===

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 ===

=== Inkscape 0.93 ===

=== Inkscape 0.94 ===

=== Inkscape 0.9x ===

=== Inkscape 1.0 ===

=== Inkscape 1.x ===

=== Milestone [Future] ===

=== Random Ideas / Requests / Needs ===

Note this list is unordered, unapproved, and unofficial. Feel free to add new ideas worth considering for the roadmap.

===== Maintenance =====
* C++11. Initially focus on widely supported C++11 features, then later adopt remaining features as they become widespread.
* Better modularization
** Switch to using libcroco as a regular dependency (not embedded in our codebase)
** Switch to using libgdl as a regular dependency
** Break libavoid out to its own library
** Break libcola out to its own library
** Break libdepixelize out to its own library
** Break libnrtype out to its own library
** Break libuemf out to its own library
** Break libvpsc out to its own library
* 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.
* [[GtkMMification]]
* XML refactoring: Remove direct manipulation of XML from as many places as possible and replace it with SP tree methods.
* 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).
* Switch to using Poppler's API rather than using internals (the current situation causes regular breakage with new releases of Poppler)

===== Infrastructure =====
* Replace VCS.
* Replace Automake Build System.
* Make the Windows uninstaller work (reevaluate this, we now have msi installer for win32 and Win64)
* make msi Windows install multilingual
* 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])
** Greatly expand Unit test framework.
** Set up workflow (passing tests, test coverage, code review) for getting code into trunk.
* Set up autogeneration of Inkcape 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)])
** Put it publically somewhere on the inkscape domain for "official" access.
* 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.

===== New features / Improvements to existing features =====
* Multi-page documents and parent/child document references
* [[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.
* <strike>Using the above mechanism, make flowed text SVG-compliant.</strike>
* Implement SVG 2 flowed text which has a natural SVG 1.1 fallback.
* Improve support for changing the name of the XML element node in response to SP tree changes.
* Flip y-coordinate to match SVG.
* 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.
* CSS support
* Animation support.
* D-Bus scripting API. (Merge GSoC work from 0.48 timeframe?)
* 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])
* 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 redesign existing dialogs/docks.

===== Documentation =====
===== Community =====

[[Category:Developer Documentation]]

AnnouncePlanning091

2014-11-27T22:27:27Z

ScislaC: /* Receive small overview */

This announce planning page is based on [[AnnouncePlanning047]] - What you see below has been copied from there and edited. Refer to the [[Release notes/0.91]] for details on what's new, different and improved.

== Tasks ==
{| class="wikitable"
|-
! Task
! Performer
! Projected Date of completion
! Status
|- style="background:#eeeeee;"
| Informal PR text - DRAFT
|
|
| 0%
|- style="background:#eeeeee;"
| Informal PR text
|
|
| 0%
|- style="background:#eeeeee;"
| Translated Informal PR text
|
|
| 0%
|- style="background:#dddddd;"
| Formal PR text - DRAFT
|
|
| 0%
|- style="background:#dddddd;"
| Formal PR text
|
|
| 0%
|- style="background:#dddddd;"
| Translated Formal PR text
|
|
| 0%
|-
| Contacts & Sources
| Collaborated on this wiki page
| 5th June
| 15%
|}

=Announcement Process=
# Create News posts (using the small overview below) on all the relevant social sites: reddit, twitter, facebook, Google+, hacker news, slashdot, etc.
# Create a new Page on the Inkscape website that has the Formal Announcement on it (for linking purposes) have links back to the social bookmarking stories for the release.
# Post the official announcement to the Inkscape News on the website, and on all the relevant Inkscape lists (eg. announce, user, developer)
# Send out the informal announcement (include a link to the web page with the formal announcement)
# Send out the formal announcement. (include a link to the web page with the formal announcement)

=Press Release Translations=
Once the English Press Release text has been finalized, translation can start into other languages.

The current goal for this PR text is to have the English version finished by DATE.

Please Create a new Wiki page for planning / translating the 0.91 PR in your language here:
* [[Inkscape091-PRannounce-fr]]
* [[Inkscape091-PRannounce-de]]
* [[Inkscape091-PRannounce-es]]
* [[Inkscape091-PRannounce-pt]]
* [[Inkscape091-PRannounce-zh]]
etc...

=Press Release Text=
==Small Overview==
The Inkscape project proudly announces a new release of its outstanding open source vector graphics editor. Version 0.91 includes ...

====For More Information====

Complete Release Notes for 0.91
http://wiki.inkscape.org/wiki/index.php/Release_notes/0.91

Community Contributed Screenshots
http://inkscape.org/screenshots/

====About Inkscape====

Inkscape is an open source drawing tool that uses the World Wide Web Consortium's (W3C) scalable vector graphics format (SVG). Some supported SVG features include basic shapes, paths, text, markers, clones, alpha blending, transforms, gradients, and grouping. In addition, Inkscape supports Creative Commons' metadata, node-editing, layers, complex path operations, text-on-path, text-in-shape, and SVG XML editing. It can also import EPS, PostScript, and most bitmap formats, and exports PNG, PS, PDF and various vector formats. Inkscape's main motivation is to provide the Open Source community with a fully W3C compliant XML, SVG, and CSS2 drawing tool. Additional work includes conversion of the codebase from C/Gtk to C++/Gtkmm, emphasizing a lightweight core with powerful features added through an extension mechanism, and maintaining a friendly, open, community-oriented development process.

===Announcement Text===
====The Inkscape Community Announces 0.91 Release :: http://www.inkscape.org :: Draw Freely.====

After over a year of intensive development and refactoring, Inkscape 0.91 is out. This version of the SVG-based vector graphics editor brings improved performance and tons of new features, some of which are as follows: New Live Path Effects (including Powerstroke), and much more. There are over X bug reports and feature requests closed with this release. Check out the full release notes for more information about what has changed, enjoy the screenshots, or just jump right to downloading your package for Windows, Linux or Mac OS X.

http://inkscape.org/download/

==Places to Announce==
=== Receive small overview===
{|style="background:#f2f2f2;"
!style="text-align:left;background-color:#d3d7cf;width:20%;"|Web Site / Media
!style="text-align:left;background-color:#d3d7cf;width:30%;"|Who will contact / post
!style="text-align:left;background-color:#d3d7cf;width:50%;"|Notes...
|-style="border-bottom:white 2px solid;"
|http://reddit.com
|?
|someone needs to post a short excerpt announcing the release, and link it to inkscape.org.
|-style="border-bottom:white 2px solid;"
|http://digg.com
|?
|digg.com someone needs to post a short excerpt announcing the release, and link it to inkscape.org.
|-style="border-bottom:white 2px solid;"
|http://slashdot.org
|?
|submit a new news item.
|-style="border-bottom:white 2px solid;"
|http://newsvine.com
|?
|submit a new news item.
|-style="border-bottom:white 2px solid;"
|1
|2
|3
|-style="border-bottom:white 2px solid;"
|(1 Web Site / Media)
|(2 Who will contact / post)
|(3 Notes...)
|-style="border-bottom:white 2px solid;"
|}

== Receive Informal PR ==
=== Open Source Community ===
{| style="background:#f2f2f2;"
!style="text-align:left;background-color:#d3d7cf;width:20%;"|Contact Name
!style="text-align:left;background-color:#d3d7cf;width:30%;"|Who will contact / post
!style="text-align:left;background-color:#d3d7cf;width:50%;"|Notes...
|- style="border-bottom:white 2px solid;"
|gnome office list
| who?
|gnome-office-list at gnome dot org
|-style="border-bottom:white 2px solid;"
|svg developers yahoo group
|
|svg-developers at yahoo dot com must join the list to send (rejon is on)
|-style="border-bottom:white 2px solid;"
|SVG.org
|
|antoine at graougraou dot com, svg at steltenpower dot com
|-style="border-bottom:white 2px solid;"
|svgfaq.org
|
|maxdunn at siliconpublishing dot com
|-style="border-bottom:white 2px solid;"
|svgfoundation.org
|
|michael (at) svgfoundation.org
|-style="border-bottom:white 2px solid;"
|cairo list
|
|cairo at cairographics dot org
|-style="border-bottom:white 2px solid;"
|gnome-list
|
|gnome-announce-list at gnome dot org
|-style="border-bottom:white 2px solid;"
|Scribus List (mrdocs)
|
|scribus at nashi dot altmuehlnet dot de
|-style="border-bottom:white 2px solid;"
|osnews.com
|
|http://osnews.com/submit.php
|-style="border-bottom:white 2px solid;"
|desktoplinux.com
|
|http://desktoplinux.com/contactus.html
|-style="border-bottom:white 2px solid;"
|Freshmeat.net
|
|a new release has to be added to inkscape's freshmeat profile
|-style="border-bottom:white 2px solid;"
|gnome footnotes
|
|http://gnomedesktop.org/node/add/story
|-style="border-bottom:white 2px solid;"
|scale-a-vector
|
|kukofka at scale-a-vector dot de http://www.scale-a-vector.de/cont.htm
|-style="border-bottom:white 2px solid;"
|http://dot.kde.org
|
|http://dot.kde.org/addPostingForm
|-style="border-bottom:white 2px solid;"
|revelinux.com
|
|theobroma at revelinux dot com
|-style="border-bottom:white 2px solid;"
|}

=== Broader Inkscape & Art Community ===
{|style="background:#f2f2f2;"
!style="text-align:left;background-color:#d3d7cf;width:20%;"|Contact Name
!style="text-align:left;background-color:#d3d7cf;width:30%;"|Who will contact / post?
!style="text-align:left;background-color:#d3d7cf;width:50%;"|Notes...
|-style="border-bottom:white 2px solid;"
|Inkscape deviantart group
|ScislaC
|http://inkscape.deviantart.com/
|
|-style="border-bottom:white 2px solid;"
|the inkscape forum
|ScislaC
|http://www.inkscapeforum.com/ run by microUgly
|-style="border-bottom:white 2px solid;"
|inkscape tutorials blog
|
|http://inkscapetutorials.wordpress.com/
|-
|-style="border-bottom:white 2px solid;"
|open clip art library list
|
|clipart@freedesktop.org
|-style="border-bottom:white 2px solid;"
|open clip art library news
|
|
|-style="border-bottom:white 2px solid;"
|artdc.org forum
|
|http://www.artdc.org/
|-style="border-bottom:white 2px solid;"
|bittbox.com - vector art blog
|
|contact(at)bittbox.com
|-style="border-bottom:white 2px solid;"
|The Daily Ubuntu - Daily Ubuntu Applications
|
|http://www.contactify.com/35b54
|-style="border-bottom:white 2px solid;"
|
|
|
|-style="border-bottom:white 2px solid;"
|
|
|
|-
|}

=== Other Inkscape Users ===
Inkscape is attracting growing numbers of users in different fields such as scrapbooking, craft-makers, fabric designers and people creating a range of technical drawings. How can we get the word out to these groups?

{|style="background:#f2f2f2;"
!style="text-align:left;background-color:#d3d7cf;width:30%;"|website / magazine / list
!style="text-align:left;background-color:#d3d7cf;width:20%;"|Who will contact / post?
!style="text-align:left;background-color:#d3d7cf;width:50%;"|Notes...
|-style="border-bottom:white 2px solid;"
|
|
|
|-style="border-bottom:white 2px solid;"
|
|
|
|-style="border-bottom:white 2px solid;"
|
|
|
|-style="border-bottom:white 2px solid;"
|
|
|
|-
|}

== Receive Formal PR ==
{|style="background:#f2f2f2;"
!style="text-align:left;background-color:#d3d7cf;width:20%;"|Contact Name
!style="text-align:left;background-color:#d3d7cf;width:30%;"|Who will contact / post?
!style="text-align:left;background-color:#d3d7cf;width:50%;"|Notes...
|-style="border-bottom:white 2px solid;"
|http://linuxformat.co.uk/
|
|login and submit news via top of page link
|-style="border-bottom:white 2px solid;"
|http://linux-magazine.com/
|
|pr(at)linux - magazine (dot) com
|-style="border-bottom:white 2px solid;"
|http://linuxmagazine.com/
|
|jbrockmeier at linux hyphen mag DOT com.
|-style="border-bottom:white 2px solid;"
|http://www.tuxmagazine.com/
|
|editor at tuxmagazine dot com
|-style="border-bottom:white 2px solid;"
|http://cmykmag.com/
|
|
|-style="border-bottom:white 2px solid;"
|http://www.computerarts.co.uk/
|
|dom dot hall at futurenet dot co dot uk http://www.computerarts.co.uk/contacts
|-style="border-bottom:white 2px solid;"
|http://www.theopensourcereport.com/
|
|contact at theopensourcereport dot com
|-style="border-bottom:white 2px solid;"
|http://www.builderau.com.au/
|
|Chris Duckett, editor at builderau dot com dot au
|-style="border-bottom:white 2px solid;"
|http://www.zdnet.com.au
|
|edit at zdnet dot com dot au
|-style="border-bottom:white 2px solid;"
|http://lwn.net
|
|
|-style="border-bottom:white 2px solid;"
|
|
|
|-style="border-bottom:white 2px solid;"
|
|
|
|-
|}

=== Other ===

* Smashing Magazine - http://www.smashingmagazine.com/
* [http://openpr.com openpr] - http://openpr.com/news/submit.html
* nettime-ann - http://www.nettime.org/
* See Kansas City infoZine: http://www.infozine.com/news/stories/op/storiesView/sid/5080/
* http://graphicdesign.about.com
* http://graphicssoft.about.com
* http://desktoppublishing.about.com

AnnouncePlanning091

2014-11-27T22:25:20Z

ScislaC: Create page based on the 0.47 version

This announce planning page is based on [[AnnouncePlanning047]] - What you see below has been copied from there and edited. Refer to the [[Release notes/0.91]] for details on what's new, different and improved.

== Tasks ==
{| class="wikitable"
|-
! Task
! Performer
! Projected Date of completion
! Status
|- style="background:#eeeeee;"
| Informal PR text - DRAFT
|
|
| 0%
|- style="background:#eeeeee;"
| Informal PR text
|
|
| 0%
|- style="background:#eeeeee;"
| Translated Informal PR text
|
|
| 0%
|- style="background:#dddddd;"
| Formal PR text - DRAFT
|
|
| 0%
|- style="background:#dddddd;"
| Formal PR text
|
|
| 0%
|- style="background:#dddddd;"
| Translated Formal PR text
|
|
| 0%
|-
| Contacts & Sources
| Collaborated on this wiki page
| 5th June
| 15%
|}

=Announcement Process=
# Create News posts (using the small overview below) on all the relevant social sites: reddit, twitter, facebook, Google+, hacker news, slashdot, etc.
# Create a new Page on the Inkscape website that has the Formal Announcement on it (for linking purposes) have links back to the social bookmarking stories for the release.
# Post the official announcement to the Inkscape News on the website, and on all the relevant Inkscape lists (eg. announce, user, developer)
# Send out the informal announcement (include a link to the web page with the formal announcement)
# Send out the formal announcement. (include a link to the web page with the formal announcement)

=Press Release Translations=
Once the English Press Release text has been finalized, translation can start into other languages.

The current goal for this PR text is to have the English version finished by DATE.

Please Create a new Wiki page for planning / translating the 0.91 PR in your language here:
* [[Inkscape091-PRannounce-fr]]
* [[Inkscape091-PRannounce-de]]
* [[Inkscape091-PRannounce-es]]
* [[Inkscape091-PRannounce-pt]]
* [[Inkscape091-PRannounce-zh]]
etc...

=Press Release Text=
==Small Overview==
The Inkscape project proudly announces a new release of its outstanding open source vector graphics editor. Version 0.91 includes ...

====For More Information====

Complete Release Notes for 0.91
http://wiki.inkscape.org/wiki/index.php/Release_notes/0.91

Community Contributed Screenshots
http://inkscape.org/screenshots/

====About Inkscape====

Inkscape is an open source drawing tool that uses the World Wide Web Consortium's (W3C) scalable vector graphics format (SVG). Some supported SVG features include basic shapes, paths, text, markers, clones, alpha blending, transforms, gradients, and grouping. In addition, Inkscape supports Creative Commons' metadata, node-editing, layers, complex path operations, text-on-path, text-in-shape, and SVG XML editing. It can also import EPS, PostScript, and most bitmap formats, and exports PNG, PS, PDF and various vector formats. Inkscape's main motivation is to provide the Open Source community with a fully W3C compliant XML, SVG, and CSS2 drawing tool. Additional work includes conversion of the codebase from C/Gtk to C++/Gtkmm, emphasizing a lightweight core with powerful features added through an extension mechanism, and maintaining a friendly, open, community-oriented development process.

===Announcement Text===
====The Inkscape Community Announces 0.91 Release :: http://www.inkscape.org :: Draw Freely.====

After over a year of intensive development and refactoring, Inkscape 0.91 is out. This version of the SVG-based vector graphics editor brings improved performance and tons of new features, some of which are as follows: New Live Path Effects (including Powerstroke), and much more. There are over X bug reports and feature requests closed with this release. Check out the full release notes for more information about what has changed, enjoy the screenshots, or just jump right to downloading your package for Windows, Linux or Mac OS X.

http://inkscape.org/download/

==Places to Announce==
=== Receive small overview===
{|style="background:#f2f2f2;"
!style="text-align:left;background-color:#d3d7cf;width:20%;"|Web Site / Media
!style="text-align:left;background-color:#d3d7cf;width:30%;"|Who will contact / post
!style="text-align:left;background-color:#d3d7cf;width:50%;"|Notes...
|-style="border-bottom:white 2px solid;"
|http://digg.com
|?
|digg.com someone needs to post a short excerpt announcing the release, and link it to inkscape.org.
|-style="border-bottom:white 2px solid;"
|http://slashdot.org
|?
|submit a new news item.
|-style="border-bottom:white 2px solid;"
|http://newsvine.com
|?
|submit a new news item.
|-style="border-bottom:white 2px solid;"
|http://reddit.com
|?
|someone needs to post a short excerpt announcing the release, and link it to inkscape.org.
|-style="border-bottom:white 2px solid;"
|1
|2
|3
|-style="border-bottom:white 2px solid;"
|(1 Web Site / Media)
|(2 Who will contact / post)
|(3 Notes...)
|-style="border-bottom:white 2px solid;"
|}

== Receive Informal PR ==
=== Open Source Community ===
{| style="background:#f2f2f2;"
!style="text-align:left;background-color:#d3d7cf;width:20%;"|Contact Name
!style="text-align:left;background-color:#d3d7cf;width:30%;"|Who will contact / post
!style="text-align:left;background-color:#d3d7cf;width:50%;"|Notes...
|- style="border-bottom:white 2px solid;"
|gnome office list
| who?
|gnome-office-list at gnome dot org
|-style="border-bottom:white 2px solid;"
|svg developers yahoo group
|
|svg-developers at yahoo dot com must join the list to send (rejon is on)
|-style="border-bottom:white 2px solid;"
|SVG.org
|
|antoine at graougraou dot com, svg at steltenpower dot com
|-style="border-bottom:white 2px solid;"
|svgfaq.org
|
|maxdunn at siliconpublishing dot com
|-style="border-bottom:white 2px solid;"
|svgfoundation.org
|
|michael (at) svgfoundation.org
|-style="border-bottom:white 2px solid;"
|cairo list
|
|cairo at cairographics dot org
|-style="border-bottom:white 2px solid;"
|gnome-list
|
|gnome-announce-list at gnome dot org
|-style="border-bottom:white 2px solid;"
|Scribus List (mrdocs)
|
|scribus at nashi dot altmuehlnet dot de
|-style="border-bottom:white 2px solid;"
|osnews.com
|
|http://osnews.com/submit.php
|-style="border-bottom:white 2px solid;"
|desktoplinux.com
|
|http://desktoplinux.com/contactus.html
|-style="border-bottom:white 2px solid;"
|Freshmeat.net
|
|a new release has to be added to inkscape's freshmeat profile
|-style="border-bottom:white 2px solid;"
|gnome footnotes
|
|http://gnomedesktop.org/node/add/story
|-style="border-bottom:white 2px solid;"
|scale-a-vector
|
|kukofka at scale-a-vector dot de http://www.scale-a-vector.de/cont.htm
|-style="border-bottom:white 2px solid;"
|http://dot.kde.org
|
|http://dot.kde.org/addPostingForm
|-style="border-bottom:white 2px solid;"
|revelinux.com
|
|theobroma at revelinux dot com
|-style="border-bottom:white 2px solid;"
|}

=== Broader Inkscape & Art Community ===
{|style="background:#f2f2f2;"
!style="text-align:left;background-color:#d3d7cf;width:20%;"|Contact Name
!style="text-align:left;background-color:#d3d7cf;width:30%;"|Who will contact / post?
!style="text-align:left;background-color:#d3d7cf;width:50%;"|Notes...
|-style="border-bottom:white 2px solid;"
|Inkscape deviantart group
|ScislaC
|http://inkscape.deviantart.com/
|
|-style="border-bottom:white 2px solid;"
|the inkscape forum
|ScislaC
|http://www.inkscapeforum.com/ run by microUgly
|-style="border-bottom:white 2px solid;"
|inkscape tutorials blog
|
|http://inkscapetutorials.wordpress.com/
|-
|-style="border-bottom:white 2px solid;"
|open clip art library list
|
|clipart@freedesktop.org
|-style="border-bottom:white 2px solid;"
|open clip art library news
|
|
|-style="border-bottom:white 2px solid;"
|artdc.org forum
|
|http://www.artdc.org/
|-style="border-bottom:white 2px solid;"
|bittbox.com - vector art blog
|
|contact(at)bittbox.com
|-style="border-bottom:white 2px solid;"
|The Daily Ubuntu - Daily Ubuntu Applications
|
|http://www.contactify.com/35b54
|-style="border-bottom:white 2px solid;"
|
|
|
|-style="border-bottom:white 2px solid;"
|
|
|
|-
|}

=== Other Inkscape Users ===
Inkscape is attracting growing numbers of users in different fields such as scrapbooking, craft-makers, fabric designers and people creating a range of technical drawings. How can we get the word out to these groups?

{|style="background:#f2f2f2;"
!style="text-align:left;background-color:#d3d7cf;width:30%;"|website / magazine / list
!style="text-align:left;background-color:#d3d7cf;width:20%;"|Who will contact / post?
!style="text-align:left;background-color:#d3d7cf;width:50%;"|Notes...
|-style="border-bottom:white 2px solid;"
|
|
|
|-style="border-bottom:white 2px solid;"
|
|
|
|-style="border-bottom:white 2px solid;"
|
|
|
|-style="border-bottom:white 2px solid;"
|
|
|
|-
|}

== Receive Formal PR ==
{|style="background:#f2f2f2;"
!style="text-align:left;background-color:#d3d7cf;width:20%;"|Contact Name
!style="text-align:left;background-color:#d3d7cf;width:30%;"|Who will contact / post?
!style="text-align:left;background-color:#d3d7cf;width:50%;"|Notes...
|-style="border-bottom:white 2px solid;"
|http://linuxformat.co.uk/
|
|login and submit news via top of page link
|-style="border-bottom:white 2px solid;"
|http://linux-magazine.com/
|
|pr(at)linux - magazine (dot) com
|-style="border-bottom:white 2px solid;"
|http://linuxmagazine.com/
|
|jbrockmeier at linux hyphen mag DOT com.
|-style="border-bottom:white 2px solid;"
|http://www.tuxmagazine.com/
|
|editor at tuxmagazine dot com
|-style="border-bottom:white 2px solid;"
|http://cmykmag.com/
|
|
|-style="border-bottom:white 2px solid;"
|http://www.computerarts.co.uk/
|
|dom dot hall at futurenet dot co dot uk http://www.computerarts.co.uk/contacts
|-style="border-bottom:white 2px solid;"
|http://www.theopensourcereport.com/
|
|contact at theopensourcereport dot com
|-style="border-bottom:white 2px solid;"
|http://www.builderau.com.au/
|
|Chris Duckett, editor at builderau dot com dot au
|-style="border-bottom:white 2px solid;"
|http://www.zdnet.com.au
|
|edit at zdnet dot com dot au
|-style="border-bottom:white 2px solid;"
|http://lwn.net
|
|
|-style="border-bottom:white 2px solid;"
|
|
|
|-style="border-bottom:white 2px solid;"
|
|
|
|-
|}

=== Other ===

* Smashing Magazine - http://www.smashingmagazine.com/
* [http://openpr.com openpr] - http://openpr.com/news/submit.html
* nettime-ann - http://www.nettime.org/
* See Kansas City infoZine: http://www.infozine.com/news/stories/op/storiesView/sid/5080/
* http://graphicdesign.about.com
* http://graphicssoft.about.com
* http://desktoppublishing.about.com

Tracking Dependencies

2014-11-24T01:12:34Z

ScislaC: /* Libs */

== Overview ==

We need help getting our basic lib dependencies listed out and kept up to date. Also we need to track which versions of which distros have the needed dependencies.

To get glib and GTK+ dependencies figured out, people can go through the API documentation and look for the 'since' entries saying when calls were added. Then look for those calls in our source. Voila! we'll have base minimum dependencies figured out.

== Libs ==

C++ bindings are not included, since their required versions match those of the C counterparts.

{| class="wikitable"
|-
! Library
! v 0.48.5
! v 0.91
! trunk
! trunk (GTK+ 3.0 build)
|-
| Boehm-GC
| >= 6.4
| 7.1
| 7.1
| 7.1
|-
| Cairo
| ?
| 1.10
| 1.10
| 1.10
|-
| GDL
| N/A
| N/A
| N/A
| 3.3.4
|-
| Glib
| ''2.16*''
| 2.28
| 2.28
| 2.28
|-
| GTK+
| ''2.12*''
| 2.24
| 2.24
| 3.2
|-
| GNU Scientific Library
| ?
| ?
| ?
| ?
|-
| LittleCMS
| 1.13
| 1.13
| 1.13
| 1.13
|-
| libxml
| ''2.6.11*''
| ''2.6.11*''
| ''2.6.11*''
| ''2.6.11*''
|-
| libxslt
| ''1.0.15*''
| ''1.0.15*''
| ''1.0.15*''
| ''1.0.15*''
|-
| Pango
| ?
| ?
| ?
| 1.24
|-
| Poppler
| ''0.5.9*''
| ''0.5.9*''
| ''0.5.9*''
| ''0.5.9*''
|-
| libsigc++
| ''2.0.12*''
| ''2.0.12*''
| ''2.0.12*''
| ''2.0.12*''
|}

''* Tentative dependency''

== Distros ==

Note: This table is not relevant to (non-fink) MacOS X, where we ship the desired version with Inkscape.

{| class="wikitable"
|-
! Distro
! cairo
! cairomm
! glib
! glibmm
! gtk+
! gtkmm
! pango
! poppler
! gdl
! lcms
! libsigc++
! libgc 
|-
| style="background:Violet;"|Windows Devlibs (r46)
| 1.11.2
| 1.10.0
| 2.28.8
| 2.28.2
| style="background:Violet;"| 2.24.10
| style="background:Violet;"| 2.24.2
| 1.28.3
| 0.12.1
| style="background:Violet;"| (none)
| 1.17
| 2.2.11
| 7.1
|-
| Windows Devlibs Gtk+ 3 branch (r28)
| 1.10.2
| 1.10.0
| 2.38.0
| 2.36.0
| 2.24.18 3.8.1
| 2.24.2 3.8.0
| 1.34.0
| 0.22.5
| 3.4.2
| 1.19 2.4
| 2.2.10
| 7.2d
|-
| Debian 7.0 (Wheezy, stable)
| 1.12.2
| 1.10.0
| 2.33.12
| 2.32.1
| 2.24.10 3.4.2
| 2.24.2 3.4.2
| 1.32.5
| 0.18.4
| 3.4.2
| 1.19 2.2
| 2.2.10
| 7.1
|-
| Fedora 19
| 1.12.14
| 1.10.0
| 2.36.3
| 2.36.2
| 2.24.19 3.8.2
| 2.24.3 3.8.1
| 1.34.1
| 0.22.1
| 3.8.1
| 1.19 2.5
| 2.3.1
| 7.2d
|-
| Fedora 20
| 1.13.1+git
| 1.10.0
| 2.38.2
| 2.38.1
| 2.24.22 3.10.6
| 2.24.4 3.10.1
| 1.36.1
| 0.24.3
| 3.10.0
| 1.19 2.5
| 2.3.1
| 7.2d
|-
| OpenSuSE 12.3 EOL 2015-01-04[http://en.opensuse.org/Lifetime]
| 1.12.8
| 1.10.0
| 2.34.3
| 2.34.1
| 2.24.14 3.6.4
| 2.24.2 3.6.0
| 1.32.5
| 0.22.0
| 3.6.2
| 1.19 2.4
| 2.2.11
| 7.1.9.6
|-
| OpenSuSE 13.1 EOL 2015-05-01[http://en.opensuse.org/Lifetime]
| 1.12.16
| 1.10.0
| 2.38.1
| 2.38.0
| 2.24.22 3.10.2
| 2.24.4 3.10.0
| 1.36.0
| 0.24.3
| 3.10.0
| 1.19 2.5
| 2.3.1
| 7.2d
|-
| Ubuntu 12.04 LTS (Precise) EOL 2017-04
| 1.10.2
| 1.10.0
| 2.32.3
| 2.32.0
| 2.24.10 3.4.2
| 2.24.2 3.4.0
| 1.30.0
| 0.18.4
| 3.3.91
| 1.19 2.2
| 2.2.10
| 7.1
|-
| Ubuntu 14.04 (Trusty) EOL 2019-04
| 1.13.0
| 1.10.0
| 2.40.0
| 2.39.93
| 2.24.23 3.10.8
| 2.24.4 3.10.1
| 1.36.3
| 0.24.5
| 3.8.1
| 1.19 2.5
| 2.2.10
| 7.2d
|-
| Ubuntu 14.10 (Utopic) (As of 2014-10-16), EOL 2015-07
| 1.13.0
| 1.10.0
| 2.42.0
| 2.42.0
| 2.24.25 3.12.2
| 2.24.4 3.12.0
| 1.36.6
| 0.26.5
| 3.12.0
| 1.19 2.6
| 2.2.11
| 7.2d
|}

{| class="wikitable"
|-
! Legend
|-
| style="background:Red;"| Inkscape stable unsupported
|-
| style="background:Orange;"| Inkscape trunk unsupported
|-
| style="background:Violet;"| GTK+ 3 builds unsupported
|}

== Getting and Installing Source packages ==

If your distro does not have some packages available (like many don't, ie, Fedora Core 2), you must often download
source packages and build and install them yourself. Actually this is not that hard, and is similar to
doing a Gentoo 'emerge.'

* Usually you download a file with a name like somepackage-1.0.tar.gz. Unpack it with

$ tar zxf somepackage-1.0.tar.gz
or
$ tar jxf somepackage-1.0.tar.bz2

* Then 'cd' into the new directory.

* Configure it with the command:

$ ./configure

* Build it with:

$ make

* As the 'root' user, install it with:

# make install

=== Boehm-GC ===

Source: http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source

* Download this file:
** http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/gc6.8.tar.gz
* Unpack it
** tar zxf gc6.8.tar.gz
* Configure and build it
** cd gc6.8
** ./configure --disable-shared --enable-static
** make
* Install it
** su (or however else you become root)
** make install

Binaries: If searching for a package for GC, the name of it is sometimes:

* gc
* libgc
* gc-devel
* libgc-devel
* boehm-gc (on Gentoo)
* debian/ubuntu: sudo apt-get install libgc-dev

=== libSigc++ ===

Source: http://ftp.gnome.org/pub/GNOME/sources/libsigc++/2.2/libsigc++-2.2.3.tar.bz2

With this file, and for GlibMM and GtkMM below, it is usually desirable for us developers to
build this C++ library statically. This removes a dependency that might be difficult for an
end-user during installation. Configure it with:

./configure --enable-static --disable-shared

=== GlibMM ===
Try to match your Glib2 version with GlibMM's version. For example, if your Glib2 is 2.16.6, download glibmm-2.16.4.tar.bz2.

Latest source: http://ftp.gnome.org/pub/GNOME/sources/glibmm/

=== GtkMM ===
Usually you can try the latest version of GtkMM, but if you get version mismatch errors, try older releases.

Source: http://ftp.gnome.org/pub/GNOME/sources/gtkmm/2.12/gtkmm-2.12.7.tar.bz2

=== cairomm ===

if you got prompted about cairomm, try first solve your cairo version, so you can grab [http://www.cairographics.org/releases/ there] a compatible version.

=== Boost ===

Many users have reported when building from source that after installing the above dependencies, the configure script still requires a "boost" package. It can be found below, but even after installing, you will need to create a symlink to allow the configure script to find it:

ln -s /usr/local/include/boost_1_xx_x/boost /usr/local/include/boost

Source: http://www.boost.org/users/download/

=== Poppler ===

Source: http://poppler.freedesktop.org/

Poppler is required for PDF import. There are several potential issues:
* Some Linux distributions do not ship the Xpdf headers required by Inkscape. In such cases, you need to recompile Poppler, passing --enable-xpdf-headers on the configure line or install the libpoppler-private-dev package. See [https://bugs.launchpad.net/inkscape/+bug/254849 this wishlist bug]. This typically manifests in error messages like this:
<pre>In file included from extension/internal/pdfinput/svg-builder.cpp:19:
extension/internal/pdfinput/svg-builder.h:32:23: error: CharTypes.h: No such file or directory
...
make[2]: *** [extension/internal/pdfinput/svg-builder.o] Error 1
make[2]: Leaving directory `/tmp/build/inkscape-0.46/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/build/inkscape-0.46'
make: *** [all] Error 2</pre>
* Inkscape 0.47 does not compile with Poppler >= 0.12.2. If you need to compile Inkscape on such systems, use the development version from Bazaar, where this bug is fixed. See [https://bugs.launchpad.net/inkscape/+bug/487038 the bug report] for details and a minimal patch.
* Inkscape compiled with Poppler <= 0.12.1 will run on systems with Poppler >= 0.12.2, but the PDF import function will crash instantly. This problem does not concern Windows users, since the correct Poppler version is contained in the Windows installer package. This cannot be fixed on Inkscape's side: those two versions of Poppler are not ABI compatible, yet share the same soname. See [https://bugs.launchpad.net/inkscape/+bug/258504 this bug] for more details.
* Poppler's Xpdf headers are not guaranteed to be API-compatible between releases. It's likely that future Poppler versions will break PDF import in some way. PDF import works at least up to 0.12.4 but might not work with later versions.

[[Category:About Inkscape]]
[[Category:Developer Documentation]]

Tracking Dependencies

2014-11-24T01:07:59Z

ScislaC: /* Libs */

== Overview ==

We need help getting our basic lib dependencies listed out and kept up to date. Also we need to track which versions of which distros have the needed dependencies.

To get glib and GTK+ dependencies figured out, people can go through the API documentation and look for the 'since' entries saying when calls were added. Then look for those calls in our source. Voila! we'll have base minimum dependencies figured out.

== Libs ==

C++ bindings are not included, since their required versions match those of the C counterparts.

{| class="wikitable"
|-
! Library
! v 0.48.5
! v 0.91
! trunk
! trunk (GTK+ 3.0 build)
|-
| Boehm-GC
| >= 6.4
| 7.1
| 7.1
| 7.1
|-
| Cairo
| ''1.10*''
| 1.14
| 1.14
| 1.14
|-
| GDL
| N/A
| N/A
| N/A
| 3.3.4
|-
| Glib
| ''2.16*''
| 2.28
| 2.28
| 2.28
|-
| GTK+
| ''2.12*''
| 2.24
| 2.24
| 3.2
|-
| GNU Scientific Library
| ?
| ?
| ?
| ?
|-
| LittleCMS
| 1.13
| 1.13
| 1.13
| 1.13
|-
| libxml
| ''2.6.11*''
| ''2.6.11*''
| ''2.6.11*''
| ''2.6.11*''
|-
| libxslt
| ''1.0.15*''
| ''1.0.15*''
| ''1.0.15*''
| ''1.0.15*''
|-
| Pango
| ?
| ?
| ?
| 1.24
|-
| Poppler
| ''0.5.9*''
| ''0.5.9*''
| ''0.5.9*''
| ''0.5.9*''
|-
| libsigc++
| ''2.0.12*''
| ''2.0.12*''
| ''2.0.12*''
| ''2.0.12*''
|}

''* Tentative dependency''

== Distros ==

Note: This table is not relevant to (non-fink) MacOS X, where we ship the desired version with Inkscape.

{| class="wikitable"
|-
! Distro
! cairo
! cairomm
! glib
! glibmm
! gtk+
! gtkmm
! pango
! poppler
! gdl
! lcms
! libsigc++
! libgc 
|-
| style="background:Violet;"|Windows Devlibs (r46)
| 1.11.2
| 1.10.0
| 2.28.8
| 2.28.2
| style="background:Violet;"| 2.24.10
| style="background:Violet;"| 2.24.2
| 1.28.3
| 0.12.1
| style="background:Violet;"| (none)
| 1.17
| 2.2.11
| 7.1
|-
| Windows Devlibs Gtk+ 3 branch (r28)
| 1.10.2
| 1.10.0
| 2.38.0
| 2.36.0
| 2.24.18 3.8.1
| 2.24.2 3.8.0
| 1.34.0
| 0.22.5
| 3.4.2
| 1.19 2.4
| 2.2.10
| 7.2d
|-
| Debian 7.0 (Wheezy, stable)
| 1.12.2
| 1.10.0
| 2.33.12
| 2.32.1
| 2.24.10 3.4.2
| 2.24.2 3.4.2
| 1.32.5
| 0.18.4
| 3.4.2
| 1.19 2.2
| 2.2.10
| 7.1
|-
| Fedora 19
| 1.12.14
| 1.10.0
| 2.36.3
| 2.36.2
| 2.24.19 3.8.2
| 2.24.3 3.8.1
| 1.34.1
| 0.22.1
| 3.8.1
| 1.19 2.5
| 2.3.1
| 7.2d
|-
| Fedora 20
| 1.13.1+git
| 1.10.0
| 2.38.2
| 2.38.1
| 2.24.22 3.10.6
| 2.24.4 3.10.1
| 1.36.1
| 0.24.3
| 3.10.0
| 1.19 2.5
| 2.3.1
| 7.2d
|-
| OpenSuSE 12.3 EOL 2015-01-04[http://en.opensuse.org/Lifetime]
| 1.12.8
| 1.10.0
| 2.34.3
| 2.34.1
| 2.24.14 3.6.4
| 2.24.2 3.6.0
| 1.32.5
| 0.22.0
| 3.6.2
| 1.19 2.4
| 2.2.11
| 7.1.9.6
|-
| OpenSuSE 13.1 EOL 2015-05-01[http://en.opensuse.org/Lifetime]
| 1.12.16
| 1.10.0
| 2.38.1
| 2.38.0
| 2.24.22 3.10.2
| 2.24.4 3.10.0
| 1.36.0
| 0.24.3
| 3.10.0
| 1.19 2.5
| 2.3.1
| 7.2d
|-
| Ubuntu 12.04 LTS (Precise) EOL 2017-04
| 1.10.2
| 1.10.0
| 2.32.3
| 2.32.0
| 2.24.10 3.4.2
| 2.24.2 3.4.0
| 1.30.0
| 0.18.4
| 3.3.91
| 1.19 2.2
| 2.2.10
| 7.1
|-
| Ubuntu 14.04 (Trusty) EOL 2019-04
| 1.13.0
| 1.10.0
| 2.40.0
| 2.39.93
| 2.24.23 3.10.8
| 2.24.4 3.10.1
| 1.36.3
| 0.24.5
| 3.8.1
| 1.19 2.5
| 2.2.10
| 7.2d
|-
| Ubuntu 14.10 (Utopic) (As of 2014-10-16), EOL 2015-07
| 1.13.0
| 1.10.0
| 2.42.0
| 2.42.0
| 2.24.25 3.12.2
| 2.24.4 3.12.0
| 1.36.6
| 0.26.5
| 3.12.0
| 1.19 2.6
| 2.2.11
| 7.2d
|}

{| class="wikitable"
|-
! Legend
|-
| style="background:Red;"| Inkscape stable unsupported
|-
| style="background:Orange;"| Inkscape trunk unsupported
|-
| style="background:Violet;"| GTK+ 3 builds unsupported
|}

== Getting and Installing Source packages ==

If your distro does not have some packages available (like many don't, ie, Fedora Core 2), you must often download
source packages and build and install them yourself. Actually this is not that hard, and is similar to
doing a Gentoo 'emerge.'

* Usually you download a file with a name like somepackage-1.0.tar.gz. Unpack it with

$ tar zxf somepackage-1.0.tar.gz
or
$ tar jxf somepackage-1.0.tar.bz2

* Then 'cd' into the new directory.

* Configure it with the command:

$ ./configure

* Build it with:

$ make

* As the 'root' user, install it with:

# make install

=== Boehm-GC ===

Source: http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source

* Download this file:
** http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/gc6.8.tar.gz
* Unpack it
** tar zxf gc6.8.tar.gz
* Configure and build it
** cd gc6.8
** ./configure --disable-shared --enable-static
** make
* Install it
** su (or however else you become root)
** make install

Binaries: If searching for a package for GC, the name of it is sometimes:

* gc
* libgc
* gc-devel
* libgc-devel
* boehm-gc (on Gentoo)
* debian/ubuntu: sudo apt-get install libgc-dev

=== libSigc++ ===

Source: http://ftp.gnome.org/pub/GNOME/sources/libsigc++/2.2/libsigc++-2.2.3.tar.bz2

With this file, and for GlibMM and GtkMM below, it is usually desirable for us developers to
build this C++ library statically. This removes a dependency that might be difficult for an
end-user during installation. Configure it with:

./configure --enable-static --disable-shared

=== GlibMM ===
Try to match your Glib2 version with GlibMM's version. For example, if your Glib2 is 2.16.6, download glibmm-2.16.4.tar.bz2.

Latest source: http://ftp.gnome.org/pub/GNOME/sources/glibmm/

=== GtkMM ===
Usually you can try the latest version of GtkMM, but if you get version mismatch errors, try older releases.

Source: http://ftp.gnome.org/pub/GNOME/sources/gtkmm/2.12/gtkmm-2.12.7.tar.bz2

=== cairomm ===

if you got prompted about cairomm, try first solve your cairo version, so you can grab [http://www.cairographics.org/releases/ there] a compatible version.

=== Boost ===

Many users have reported when building from source that after installing the above dependencies, the configure script still requires a "boost" package. It can be found below, but even after installing, you will need to create a symlink to allow the configure script to find it:

ln -s /usr/local/include/boost_1_xx_x/boost /usr/local/include/boost

Source: http://www.boost.org/users/download/

=== Poppler ===

Source: http://poppler.freedesktop.org/

Poppler is required for PDF import. There are several potential issues:
* Some Linux distributions do not ship the Xpdf headers required by Inkscape. In such cases, you need to recompile Poppler, passing --enable-xpdf-headers on the configure line or install the libpoppler-private-dev package. See [https://bugs.launchpad.net/inkscape/+bug/254849 this wishlist bug]. This typically manifests in error messages like this:
<pre>In file included from extension/internal/pdfinput/svg-builder.cpp:19:
extension/internal/pdfinput/svg-builder.h:32:23: error: CharTypes.h: No such file or directory
...
make[2]: *** [extension/internal/pdfinput/svg-builder.o] Error 1
make[2]: Leaving directory `/tmp/build/inkscape-0.46/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/build/inkscape-0.46'
make: *** [all] Error 2</pre>
* Inkscape 0.47 does not compile with Poppler >= 0.12.2. If you need to compile Inkscape on such systems, use the development version from Bazaar, where this bug is fixed. See [https://bugs.launchpad.net/inkscape/+bug/487038 the bug report] for details and a minimal patch.
* Inkscape compiled with Poppler <= 0.12.1 will run on systems with Poppler >= 0.12.2, but the PDF import function will crash instantly. This problem does not concern Windows users, since the correct Poppler version is contained in the Windows installer package. This cannot be fixed on Inkscape's side: those two versions of Poppler are not ABI compatible, yet share the same soname. See [https://bugs.launchpad.net/inkscape/+bug/258504 this bug] for more details.
* Poppler's Xpdf headers are not guaranteed to be API-compatible between releases. It's likely that future Poppler versions will break PDF import in some way. PDF import works at least up to 0.12.4 but might not work with later versions.

[[Category:About Inkscape]]
[[Category:Developer Documentation]]

Tracking Dependencies

2014-11-24T01:06:45Z

ScislaC: /* Libs */

== Overview ==

We need help getting our basic lib dependencies listed out and kept up to date. Also we need to track which versions of which distros have the needed dependencies.

To get glib and GTK+ dependencies figured out, people can go through the API documentation and look for the 'since' entries saying when calls were added. Then look for those calls in our source. Voila! we'll have base minimum dependencies figured out.

== Libs ==

C++ bindings are not included, since their required versions match those of the C counterparts.

{| class="wikitable"
|-
! Library
! v 0.48.5
! v 0.91
! trunk
! trunk (GTK+ 3.0 build)
|-
| Boehm-GC
| >= 6.4
| 7.1
| 7.1
| 7.1
|-
| Cairo
| ''1.10*''
| 1.14
| 1.14
| 1.14
|-
| GDL
| N/A
| N/A
| N/A
| 3.3.4
|-
| Glib
| ''2.16*''
| 2.28
| 2.28
| 2.28
|-
| GTK+
| ''2.12*''
| 2.24
| 3.2
|-
| GNU Scientific Library
| ?
| ?
| ?
|-
| LittleCMS
| 1.13
| 1.13
| 1.13
| 1.13
|-
| libxml
| ''2.6.11*''
| ''2.6.11*''
| ''2.6.11*''
| ''2.6.11*''
|-
| libxslt
| ''1.0.15*''
| ''1.0.15*''
| ''1.0.15*''
| ''1.0.15*''
|-
| Pango
| ?
| ?
| ?
| 1.24
|-
| Poppler
| ''0.5.9*''
| ''0.5.9*''
| ''0.5.9*''
| ''0.5.9*''
|-
| libsigc++
| ''2.0.12*''
| ''2.0.12*''
| ''2.0.12*''
| ''2.0.12*''
|}

''* Tentative dependency''

== Distros ==

Note: This table is not relevant to (non-fink) MacOS X, where we ship the desired version with Inkscape.

{| class="wikitable"
|-
! Distro
! cairo
! cairomm
! glib
! glibmm
! gtk+
! gtkmm
! pango
! poppler
! gdl
! lcms
! libsigc++
! libgc 
|-
| style="background:Violet;"|Windows Devlibs (r46)
| 1.11.2
| 1.10.0
| 2.28.8
| 2.28.2
| style="background:Violet;"| 2.24.10
| style="background:Violet;"| 2.24.2
| 1.28.3
| 0.12.1
| style="background:Violet;"| (none)
| 1.17
| 2.2.11
| 7.1
|-
| Windows Devlibs Gtk+ 3 branch (r28)
| 1.10.2
| 1.10.0
| 2.38.0
| 2.36.0
| 2.24.18 3.8.1
| 2.24.2 3.8.0
| 1.34.0
| 0.22.5
| 3.4.2
| 1.19 2.4
| 2.2.10
| 7.2d
|-
| Debian 7.0 (Wheezy, stable)
| 1.12.2
| 1.10.0
| 2.33.12
| 2.32.1
| 2.24.10 3.4.2
| 2.24.2 3.4.2
| 1.32.5
| 0.18.4
| 3.4.2
| 1.19 2.2
| 2.2.10
| 7.1
|-
| Fedora 19
| 1.12.14
| 1.10.0
| 2.36.3
| 2.36.2
| 2.24.19 3.8.2
| 2.24.3 3.8.1
| 1.34.1
| 0.22.1
| 3.8.1
| 1.19 2.5
| 2.3.1
| 7.2d
|-
| Fedora 20
| 1.13.1+git
| 1.10.0
| 2.38.2
| 2.38.1
| 2.24.22 3.10.6
| 2.24.4 3.10.1
| 1.36.1
| 0.24.3
| 3.10.0
| 1.19 2.5
| 2.3.1
| 7.2d
|-
| OpenSuSE 12.3 EOL 2015-01-04[http://en.opensuse.org/Lifetime]
| 1.12.8
| 1.10.0
| 2.34.3
| 2.34.1
| 2.24.14 3.6.4
| 2.24.2 3.6.0
| 1.32.5
| 0.22.0
| 3.6.2
| 1.19 2.4
| 2.2.11
| 7.1.9.6
|-
| OpenSuSE 13.1 EOL 2015-05-01[http://en.opensuse.org/Lifetime]
| 1.12.16
| 1.10.0
| 2.38.1
| 2.38.0
| 2.24.22 3.10.2
| 2.24.4 3.10.0
| 1.36.0
| 0.24.3
| 3.10.0
| 1.19 2.5
| 2.3.1
| 7.2d
|-
| Ubuntu 12.04 LTS (Precise) EOL 2017-04
| 1.10.2
| 1.10.0
| 2.32.3
| 2.32.0
| 2.24.10 3.4.2
| 2.24.2 3.4.0
| 1.30.0
| 0.18.4
| 3.3.91
| 1.19 2.2
| 2.2.10
| 7.1
|-
| Ubuntu 14.04 (Trusty) EOL 2019-04
| 1.13.0
| 1.10.0
| 2.40.0
| 2.39.93
| 2.24.23 3.10.8
| 2.24.4 3.10.1
| 1.36.3
| 0.24.5
| 3.8.1
| 1.19 2.5
| 2.2.10
| 7.2d
|-
| Ubuntu 14.10 (Utopic) (As of 2014-10-16), EOL 2015-07
| 1.13.0
| 1.10.0
| 2.42.0
| 2.42.0
| 2.24.25 3.12.2
| 2.24.4 3.12.0
| 1.36.6
| 0.26.5
| 3.12.0
| 1.19 2.6
| 2.2.11
| 7.2d
|}

{| class="wikitable"
|-
! Legend
|-
| style="background:Red;"| Inkscape stable unsupported
|-
| style="background:Orange;"| Inkscape trunk unsupported
|-
| style="background:Violet;"| GTK+ 3 builds unsupported
|}

== Getting and Installing Source packages ==

If your distro does not have some packages available (like many don't, ie, Fedora Core 2), you must often download
source packages and build and install them yourself. Actually this is not that hard, and is similar to
doing a Gentoo 'emerge.'

* Usually you download a file with a name like somepackage-1.0.tar.gz. Unpack it with

$ tar zxf somepackage-1.0.tar.gz
or
$ tar jxf somepackage-1.0.tar.bz2

* Then 'cd' into the new directory.

* Configure it with the command:

$ ./configure

* Build it with:

$ make

* As the 'root' user, install it with:

# make install

=== Boehm-GC ===

Source: http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source

* Download this file:
** http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/gc6.8.tar.gz
* Unpack it
** tar zxf gc6.8.tar.gz
* Configure and build it
** cd gc6.8
** ./configure --disable-shared --enable-static
** make
* Install it
** su (or however else you become root)
** make install

Binaries: If searching for a package for GC, the name of it is sometimes:

* gc
* libgc
* gc-devel
* libgc-devel
* boehm-gc (on Gentoo)
* debian/ubuntu: sudo apt-get install libgc-dev

=== libSigc++ ===

Source: http://ftp.gnome.org/pub/GNOME/sources/libsigc++/2.2/libsigc++-2.2.3.tar.bz2

With this file, and for GlibMM and GtkMM below, it is usually desirable for us developers to
build this C++ library statically. This removes a dependency that might be difficult for an
end-user during installation. Configure it with:

./configure --enable-static --disable-shared

=== GlibMM ===
Try to match your Glib2 version with GlibMM's version. For example, if your Glib2 is 2.16.6, download glibmm-2.16.4.tar.bz2.

Latest source: http://ftp.gnome.org/pub/GNOME/sources/glibmm/

=== GtkMM ===
Usually you can try the latest version of GtkMM, but if you get version mismatch errors, try older releases.

Source: http://ftp.gnome.org/pub/GNOME/sources/gtkmm/2.12/gtkmm-2.12.7.tar.bz2

=== cairomm ===

if you got prompted about cairomm, try first solve your cairo version, so you can grab [http://www.cairographics.org/releases/ there] a compatible version.

=== Boost ===

Many users have reported when building from source that after installing the above dependencies, the configure script still requires a "boost" package. It can be found below, but even after installing, you will need to create a symlink to allow the configure script to find it:

ln -s /usr/local/include/boost_1_xx_x/boost /usr/local/include/boost

Source: http://www.boost.org/users/download/

=== Poppler ===

Source: http://poppler.freedesktop.org/

Poppler is required for PDF import. There are several potential issues:
* Some Linux distributions do not ship the Xpdf headers required by Inkscape. In such cases, you need to recompile Poppler, passing --enable-xpdf-headers on the configure line or install the libpoppler-private-dev package. See [https://bugs.launchpad.net/inkscape/+bug/254849 this wishlist bug]. This typically manifests in error messages like this:
<pre>In file included from extension/internal/pdfinput/svg-builder.cpp:19:
extension/internal/pdfinput/svg-builder.h:32:23: error: CharTypes.h: No such file or directory
...
make[2]: *** [extension/internal/pdfinput/svg-builder.o] Error 1
make[2]: Leaving directory `/tmp/build/inkscape-0.46/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/build/inkscape-0.46'
make: *** [all] Error 2</pre>
* Inkscape 0.47 does not compile with Poppler >= 0.12.2. If you need to compile Inkscape on such systems, use the development version from Bazaar, where this bug is fixed. See [https://bugs.launchpad.net/inkscape/+bug/487038 the bug report] for details and a minimal patch.
* Inkscape compiled with Poppler <= 0.12.1 will run on systems with Poppler >= 0.12.2, but the PDF import function will crash instantly. This problem does not concern Windows users, since the correct Poppler version is contained in the Windows installer package. This cannot be fixed on Inkscape's side: those two versions of Poppler are not ABI compatible, yet share the same soname. See [https://bugs.launchpad.net/inkscape/+bug/258504 this bug] for more details.
* Poppler's Xpdf headers are not guaranteed to be API-compatible between releases. It's likely that future Poppler versions will break PDF import in some way. PDF import works at least up to 0.12.4 but might not work with later versions.

[[Category:About Inkscape]]
[[Category:Developer Documentation]]

Tracking Dependencies

2014-11-24T01:02:57Z

ScislaC: Undo revision 93722 by ScislaC (talk)

== Overview ==

We need help getting our basic lib dependencies listed out and kept up to date. Also we need to track which versions of which distros have the needed dependencies.

To get glib and GTK+ dependencies figured out, people can go through the API documentation and look for the 'since' entries saying when calls were added. Then look for those calls in our source. Voila! we'll have base minimum dependencies figured out.

== Libs ==

C++ bindings are not included, since their required versions match those of the C counterparts.

{| class="wikitable"
|-
! Library
! v 0.48.5
! trunk
! trunk (GTK+ 3.0 build)
|-
| Boehm-GC
| >= 6.4
| 7.1
| 7.1
|-
| Cairo
| ?
| 1.10
| 1.10
|-
| GDL
| N/A
| N/A
| 3.3.4
|-
| Glib
| ''2.16*''
| 2.28
| 2.28
|-
| GTK+
| ''2.12*''
| 2.24
| 3.2
|-
| GNU Scientific Library
| ?
| ?
| ?
|-
| LittleCMS
| 1.13
| 1.13
| 1.13
|-
| libxml
| ''2.6.11*''
| ''2.6.11*''
| ''2.6.11*''
|-
| libxslt
| ''1.0.15*''
| ''1.0.15*''
| ''1.0.15*''
|-
| Pango
| ?
| ?
| 1.24
|-
| Poppler
| ''0.5.9*''
| ''0.5.9*''
| ''0.5.9*''
|-
| libsigc++
| ''2.0.12*''
| ''2.0.12*''
| ''2.0.12*''
|}

''* Tentative dependency''

== Distros ==

Note: This table is not relevant to (non-fink) MacOS X, where we ship the desired version with Inkscape.

{| class="wikitable"
|-
! Distro
! cairo
! cairomm
! glib
! glibmm
! gtk+
! gtkmm
! pango
! poppler
! gdl
! lcms
! libsigc++
! libgc 
|-
| style="background:Violet;"|Windows Devlibs (r46)
| 1.11.2
| 1.10.0
| 2.28.8
| 2.28.2
| style="background:Violet;"| 2.24.10
| style="background:Violet;"| 2.24.2
| 1.28.3
| 0.12.1
| style="background:Violet;"| (none)
| 1.17
| 2.2.11
| 7.1
|-
| Windows Devlibs Gtk+ 3 branch (r28)
| 1.10.2
| 1.10.0
| 2.38.0
| 2.36.0
| 2.24.18 3.8.1
| 2.24.2 3.8.0
| 1.34.0
| 0.22.5
| 3.4.2
| 1.19 2.4
| 2.2.10
| 7.2d
|-
| Debian 7.0 (Wheezy, stable)
| 1.12.2
| 1.10.0
| 2.33.12
| 2.32.1
| 2.24.10 3.4.2
| 2.24.2 3.4.2
| 1.32.5
| 0.18.4
| 3.4.2
| 1.19 2.2
| 2.2.10
| 7.1
|-
| Fedora 19
| 1.12.14
| 1.10.0
| 2.36.3
| 2.36.2
| 2.24.19 3.8.2
| 2.24.3 3.8.1
| 1.34.1
| 0.22.1
| 3.8.1
| 1.19 2.5
| 2.3.1
| 7.2d
|-
| Fedora 20
| 1.13.1+git
| 1.10.0
| 2.38.2
| 2.38.1
| 2.24.22 3.10.6
| 2.24.4 3.10.1
| 1.36.1
| 0.24.3
| 3.10.0
| 1.19 2.5
| 2.3.1
| 7.2d
|-
| OpenSuSE 12.3 EOL 2015-01-04[http://en.opensuse.org/Lifetime]
| 1.12.8
| 1.10.0
| 2.34.3
| 2.34.1
| 2.24.14 3.6.4
| 2.24.2 3.6.0
| 1.32.5
| 0.22.0
| 3.6.2
| 1.19 2.4
| 2.2.11
| 7.1.9.6
|-
| OpenSuSE 13.1 EOL 2015-05-01[http://en.opensuse.org/Lifetime]
| 1.12.16
| 1.10.0
| 2.38.1
| 2.38.0
| 2.24.22 3.10.2
| 2.24.4 3.10.0
| 1.36.0
| 0.24.3
| 3.10.0
| 1.19 2.5
| 2.3.1
| 7.2d
|-
| Ubuntu 12.04 LTS (Precise) EOL 2017-04
| 1.10.2
| 1.10.0
| 2.32.3
| 2.32.0
| 2.24.10 3.4.2
| 2.24.2 3.4.0
| 1.30.0
| 0.18.4
| 3.3.91
| 1.19 2.2
| 2.2.10
| 7.1
|-
| Ubuntu 14.04 (Trusty) EOL 2019-04
| 1.13.0
| 1.10.0
| 2.40.0
| 2.39.93
| 2.24.23 3.10.8
| 2.24.4 3.10.1
| 1.36.3
| 0.24.5
| 3.8.1
| 1.19 2.5
| 2.2.10
| 7.2d
|-
| Ubuntu 14.10 (Utopic) (As of 2014-10-16), EOL 2015-07
| 1.13.0
| 1.10.0
| 2.42.0
| 2.42.0
| 2.24.25 3.12.2
| 2.24.4 3.12.0
| 1.36.6
| 0.26.5
| 3.12.0
| 1.19 2.6
| 2.2.11
| 7.2d
|}

{| class="wikitable"
|-
! Legend
|-
| style="background:Red;"| Inkscape stable unsupported
|-
| style="background:Orange;"| Inkscape trunk unsupported
|-
| style="background:Violet;"| GTK+ 3 builds unsupported
|}

== Getting and Installing Source packages ==

If your distro does not have some packages available (like many don't, ie, Fedora Core 2), you must often download
source packages and build and install them yourself. Actually this is not that hard, and is similar to
doing a Gentoo 'emerge.'

* Usually you download a file with a name like somepackage-1.0.tar.gz. Unpack it with

$ tar zxf somepackage-1.0.tar.gz
or
$ tar jxf somepackage-1.0.tar.bz2

* Then 'cd' into the new directory.

* Configure it with the command:

$ ./configure

* Build it with:

$ make

* As the 'root' user, install it with:

# make install

=== Boehm-GC ===

Source: http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source

* Download this file:
** http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/gc6.8.tar.gz
* Unpack it
** tar zxf gc6.8.tar.gz
* Configure and build it
** cd gc6.8
** ./configure --disable-shared --enable-static
** make
* Install it
** su (or however else you become root)
** make install

Binaries: If searching for a package for GC, the name of it is sometimes:

* gc
* libgc
* gc-devel
* libgc-devel
* boehm-gc (on Gentoo)
* debian/ubuntu: sudo apt-get install libgc-dev

=== libSigc++ ===

Source: http://ftp.gnome.org/pub/GNOME/sources/libsigc++/2.2/libsigc++-2.2.3.tar.bz2

With this file, and for GlibMM and GtkMM below, it is usually desirable for us developers to
build this C++ library statically. This removes a dependency that might be difficult for an
end-user during installation. Configure it with:

./configure --enable-static --disable-shared

=== GlibMM ===
Try to match your Glib2 version with GlibMM's version. For example, if your Glib2 is 2.16.6, download glibmm-2.16.4.tar.bz2.

Latest source: http://ftp.gnome.org/pub/GNOME/sources/glibmm/

=== GtkMM ===
Usually you can try the latest version of GtkMM, but if you get version mismatch errors, try older releases.

Source: http://ftp.gnome.org/pub/GNOME/sources/gtkmm/2.12/gtkmm-2.12.7.tar.bz2

=== cairomm ===

if you got prompted about cairomm, try first solve your cairo version, so you can grab [http://www.cairographics.org/releases/ there] a compatible version.

=== Boost ===

Many users have reported when building from source that after installing the above dependencies, the configure script still requires a "boost" package. It can be found below, but even after installing, you will need to create a symlink to allow the configure script to find it:

ln -s /usr/local/include/boost_1_xx_x/boost /usr/local/include/boost

Source: http://www.boost.org/users/download/

=== Poppler ===

Source: http://poppler.freedesktop.org/

Poppler is required for PDF import. There are several potential issues:
* Some Linux distributions do not ship the Xpdf headers required by Inkscape. In such cases, you need to recompile Poppler, passing --enable-xpdf-headers on the configure line or install the libpoppler-private-dev package. See [https://bugs.launchpad.net/inkscape/+bug/254849 this wishlist bug]. This typically manifests in error messages like this:
<pre>In file included from extension/internal/pdfinput/svg-builder.cpp:19:
extension/internal/pdfinput/svg-builder.h:32:23: error: CharTypes.h: No such file or directory
...
make[2]: *** [extension/internal/pdfinput/svg-builder.o] Error 1
make[2]: Leaving directory `/tmp/build/inkscape-0.46/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/build/inkscape-0.46'
make: *** [all] Error 2</pre>
* Inkscape 0.47 does not compile with Poppler >= 0.12.2. If you need to compile Inkscape on such systems, use the development version from Bazaar, where this bug is fixed. See [https://bugs.launchpad.net/inkscape/+bug/487038 the bug report] for details and a minimal patch.
* Inkscape compiled with Poppler <= 0.12.1 will run on systems with Poppler >= 0.12.2, but the PDF import function will crash instantly. This problem does not concern Windows users, since the correct Poppler version is contained in the Windows installer package. This cannot be fixed on Inkscape's side: those two versions of Poppler are not ABI compatible, yet share the same soname. See [https://bugs.launchpad.net/inkscape/+bug/258504 this bug] for more details.
* Poppler's Xpdf headers are not guaranteed to be API-compatible between releases. It's likely that future Poppler versions will break PDF import in some way. PDF import works at least up to 0.12.4 but might not work with later versions.

[[Category:About Inkscape]]
[[Category:Developer Documentation]]

Tracking Dependencies

2014-11-24T01:00:15Z

ScislaC: /* Distros */ Add GCC

== Overview ==

We need help getting our basic lib dependencies listed out and kept up to date. Also we need to track which versions of which distros have the needed dependencies.

To get glib and GTK+ dependencies figured out, people can go through the API documentation and look for the 'since' entries saying when calls were added. Then look for those calls in our source. Voila! we'll have base minimum dependencies figured out.

== Libs ==

C++ bindings are not included, since their required versions match those of the C counterparts.

{| class="wikitable"
|-
! Library
! v 0.48.5
! trunk
! trunk (GTK+ 3.0 build)
|-
| Boehm-GC
| >= 6.4
| 7.1
| 7.1
|-
| Cairo
| ?
| 1.10
| 1.10
|-
| GDL
| N/A
| N/A
| 3.3.4
|-
| Glib
| ''2.16*''
| 2.28
| 2.28
|-
| GTK+
| ''2.12*''
| 2.24
| 3.2
|-
| GNU Scientific Library
| ?
| ?
| ?
|-
| LittleCMS
| 1.13
| 1.13
| 1.13
|-
| libxml
| ''2.6.11*''
| ''2.6.11*''
| ''2.6.11*''
|-
| libxslt
| ''1.0.15*''
| ''1.0.15*''
| ''1.0.15*''
|-
| Pango
| ?
| ?
| 1.24
|-
| Poppler
| ''0.5.9*''
| ''0.5.9*''
| ''0.5.9*''
|-
| libsigc++
| ''2.0.12*''
| ''2.0.12*''
| ''2.0.12*''
|}

''* Tentative dependency''

== Distros ==

Note: This table is not relevant to (non-fink) MacOS X, where we ship the desired version with Inkscape.

{| class="wikitable"
|-
! Distro
! cairo
! cairomm
! glib
! glibmm
! gtk+
! gtkmm
! pango
! poppler
! gdl
! lcms
! libsigc++
! libgc 
! gcc
|-
| style="background:Violet;"|Windows Devlibs (r46)
| 1.11.2
| 1.10.0
| 2.28.8
| 2.28.2
| style="background:Violet;"| 2.24.10
| style="background:Violet;"| 2.24.2
| 1.28.3
| 0.12.1
| style="background:Violet;"| (none)
| 1.17
| 2.2.11
| 7.1
| (not in devlibs)
|-
| Windows Devlibs Gtk+ 3 branch (r28)
| 1.10.2
| 1.10.0
| 2.38.0
| 2.36.0
| 2.24.18 3.8.1
| 2.24.2 3.8.0
| 1.34.0
| 0.22.5
| 3.4.2
| 1.19 2.4
| 2.2.10
| 7.2d
| (not in devlibs)
|-
| Debian 7.0 (Wheezy, stable)
| 1.12.2
| 1.10.0
| 2.33.12
| 2.32.1
| 2.24.10 3.4.2
| 2.24.2 3.4.2
| 1.32.5
| 0.18.4
| 3.4.2
| 1.19 2.2
| 2.2.10
| 7.1
| ?
|-
| Fedora 19
| 1.12.14
| 1.10.0
| 2.36.3
| 2.36.2
| 2.24.19 3.8.2
| 2.24.3 3.8.1
| 1.34.1
| 0.22.1
| 3.8.1
| 1.19 2.5
| 2.3.1
| 7.2d
| ?
|-
| Fedora 20
| 1.13.1+git
| 1.10.0
| 2.38.2
| 2.38.1
| 2.24.22 3.10.6
| 2.24.4 3.10.1
| 1.36.1
| 0.24.3
| 3.10.0
| 1.19 2.5
| 2.3.1
| 7.2d
| ?
|-
| OpenSuSE 12.3 EOL 2015-01-04[http://en.opensuse.org/Lifetime]
| 1.12.8
| 1.10.0
| 2.34.3
| 2.34.1
| 2.24.14 3.6.4
| 2.24.2 3.6.0
| 1.32.5
| 0.22.0
| 3.6.2
| 1.19 2.4
| 2.2.11
| 7.1.9.6
| ?
|-
| OpenSuSE 13.1 EOL 2015-05-01[http://en.opensuse.org/Lifetime]
| 1.12.16
| 1.10.0
| 2.38.1
| 2.38.0
| 2.24.22 3.10.2
| 2.24.4 3.10.0
| 1.36.0
| 0.24.3
| 3.10.0
| 1.19 2.5
| 2.3.1
| 7.2d
| ?
|-
| Ubuntu 12.04 LTS (Precise) EOL 2017-04
| 1.10.2
| 1.10.0
| 2.32.3
| 2.32.0
| 2.24.10 3.4.2
| 2.24.2 3.4.0
| 1.30.0
| 0.18.4
| 3.3.91
| 1.19 2.2
| 2.2.10
| 7.1
| ?
|-
| Ubuntu 14.04 (Trusty) EOL 2019-04
| 1.13.0
| 1.10.0
| 2.40.0
| 2.39.93
| 2.24.23 3.10.8
| 2.24.4 3.10.1
| 1.36.3
| 0.24.5
| 3.8.1
| 1.19 2.5
| 2.2.10
| 7.2d
| ?
|-
| Ubuntu 14.10 (Utopic)
| 1.13.0
| 1.10.0
| 2.42.0
| 2.42.0
| 2.24.25 3.12.2
| 2.24.4 3.12.0
| 1.36.6
| 0.26.5
| 3.12.0
| 1.19 2.6
| 2.2.11
| 7.2d
| 4.9.1
|}

{| class="wikitable"
|-
! Legend
|-
| style="background:Red;"| Inkscape stable unsupported
|-
| style="background:Orange;"| Inkscape trunk unsupported
|-
| style="background:Violet;"| GTK+ 3 builds unsupported
|}

== Getting and Installing Source packages ==

If your distro does not have some packages available (like many don't, ie, Fedora Core 2), you must often download
source packages and build and install them yourself. Actually this is not that hard, and is similar to
doing a Gentoo 'emerge.'

* Usually you download a file with a name like somepackage-1.0.tar.gz. Unpack it with

$ tar zxf somepackage-1.0.tar.gz
or
$ tar jxf somepackage-1.0.tar.bz2

* Then 'cd' into the new directory.

* Configure it with the command:

$ ./configure

* Build it with:

$ make

* As the 'root' user, install it with:

# make install

=== Boehm-GC ===

Source: http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source

* Download this file:
** http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/gc6.8.tar.gz
* Unpack it
** tar zxf gc6.8.tar.gz
* Configure and build it
** cd gc6.8
** ./configure --disable-shared --enable-static
** make
* Install it
** su (or however else you become root)
** make install

Binaries: If searching for a package for GC, the name of it is sometimes:

* gc
* libgc
* gc-devel
* libgc-devel
* boehm-gc (on Gentoo)
* debian/ubuntu: sudo apt-get install libgc-dev

=== libSigc++ ===

Source: http://ftp.gnome.org/pub/GNOME/sources/libsigc++/2.2/libsigc++-2.2.3.tar.bz2

With this file, and for GlibMM and GtkMM below, it is usually desirable for us developers to
build this C++ library statically. This removes a dependency that might be difficult for an
end-user during installation. Configure it with:

./configure --enable-static --disable-shared

=== GlibMM ===
Try to match your Glib2 version with GlibMM's version. For example, if your Glib2 is 2.16.6, download glibmm-2.16.4.tar.bz2.

Latest source: http://ftp.gnome.org/pub/GNOME/sources/glibmm/

=== GtkMM ===
Usually you can try the latest version of GtkMM, but if you get version mismatch errors, try older releases.

Source: http://ftp.gnome.org/pub/GNOME/sources/gtkmm/2.12/gtkmm-2.12.7.tar.bz2

=== cairomm ===

if you got prompted about cairomm, try first solve your cairo version, so you can grab [http://www.cairographics.org/releases/ there] a compatible version.

=== Boost ===

Many users have reported when building from source that after installing the above dependencies, the configure script still requires a "boost" package. It can be found below, but even after installing, you will need to create a symlink to allow the configure script to find it:

ln -s /usr/local/include/boost_1_xx_x/boost /usr/local/include/boost

Source: http://www.boost.org/users/download/

=== Poppler ===

Source: http://poppler.freedesktop.org/

Poppler is required for PDF import. There are several potential issues:
* Some Linux distributions do not ship the Xpdf headers required by Inkscape. In such cases, you need to recompile Poppler, passing --enable-xpdf-headers on the configure line or install the libpoppler-private-dev package. See [https://bugs.launchpad.net/inkscape/+bug/254849 this wishlist bug]. This typically manifests in error messages like this:
<pre>In file included from extension/internal/pdfinput/svg-builder.cpp:19:
extension/internal/pdfinput/svg-builder.h:32:23: error: CharTypes.h: No such file or directory
...
make[2]: *** [extension/internal/pdfinput/svg-builder.o] Error 1
make[2]: Leaving directory `/tmp/build/inkscape-0.46/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/build/inkscape-0.46'
make: *** [all] Error 2</pre>
* Inkscape 0.47 does not compile with Poppler >= 0.12.2. If you need to compile Inkscape on such systems, use the development version from Bazaar, where this bug is fixed. See [https://bugs.launchpad.net/inkscape/+bug/487038 the bug report] for details and a minimal patch.
* Inkscape compiled with Poppler <= 0.12.1 will run on systems with Poppler >= 0.12.2, but the PDF import function will crash instantly. This problem does not concern Windows users, since the correct Poppler version is contained in the Windows installer package. This cannot be fixed on Inkscape's side: those two versions of Poppler are not ABI compatible, yet share the same soname. See [https://bugs.launchpad.net/inkscape/+bug/258504 this bug] for more details.
* Poppler's Xpdf headers are not guaranteed to be API-compatible between releases. It's likely that future Poppler versions will break PDF import in some way. PDF import works at least up to 0.12.4 but might not work with later versions.

[[Category:About Inkscape]]
[[Category:Developer Documentation]]

Roadmap

2014-11-23T20:32:01Z

ScislaC: /* Random Ideas / Requests / Needs */

Roadmap

2014-11-23T19:32:05Z

ScislaC:

Roadmap

2014-11-23T17:35:21Z

ScislaC: /* Random Ideas / Requests / Needs */

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 ===

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 ===

=== Inkscape 0.93 ===

=== Inkscape 0.94 ===

=== Inkscape 0.9x ===

=== Inkscape 1.0 ===

=== Inkscape 1.x ===

=== Milestone [Future] ===

=== Random Ideas / Requests / Needs ===

Note this list is unordered, unapproved, and unofficial. Feel free to add new ideas worth considering for the roadmap.

* Replace VCS.
* Replace Automake Build System.
* Greatly expand Unit test framework.
* C++11. Initially focus on widely supported C++11 features, then later adopt remaining features as they become widespread.
* Multi-page documents and parent/child document references
* Better modularization
** Switch to using libcroco as a regular dependency (not embedded in our codebase)
** Switch to using libgdl as a regular dependency
** Break libavoid out to its own library
** Break libcola out to its own library
** Break libdepixelize out to its own library
** Break libnrtype out to its own library
** Break libuemf out to its own library
** Break libvpsc out to its own library
* [[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.
** Using the above mechanism, make flowed text SVG-compliant.
* Improve support for changing the name of the XML element node in response to SP tree changes.
* 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.
* Make the Windows uninstaller work
* [[GtkMMification]]
* XML refactoring: Remove direct manipulation of XML from as many places as possible and replace it with SP tree methods.
* 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.
* CSS support?
* Animation support.
* D-Bus scripting API. (Merge GSoC work from 0.48 timeframe?)

[[Category:Developer Documentation]]

Release notes/0.48.1

2014-11-22T18:09:44Z

ScislaC: /* Release highlights */

==Release highlights==
Released on '''4 March 2011'''.

Inkscape 0.48.1 is a stability and bugfix release. For a complete list of bugs fixed in 0.48.1, see the [https://launchpad.net/inkscape/+milestone/0.48.1 Launchpad milestone page].

==Regression fixes==
Many small regressions in the node tool were fixed. Here are some examples:
* Shift will turn off snapping in the node tool. [https://bugs.launchpad.net/bugs/588628 Bug #588628]
* Duplication of nodes in the node tool using Shift+D works again. [https://bugs.launchpad.net/bugs/555449 Bug #555449]
* Changing all selected segments into straight lines in the node tool using Shift+L works again. [https://bugs.launchpad.net/bugs/532905 Bug #532905]
* Changing the type of nodes to cusp will retract their handles only if all selected nodes are already cusp. This improves usability when working with selections that contain both cusp and smooth nodes.

==Important bugfixes==

* Exporting of masks has been substantially improved in all Cairo-based output formats.
* Several crash bugs in the node tool have been fixed. [https://bugs.launchpad.net/bugs/544599 Bug #544599], [https://bugs.launchpad.net/bugs/591986 Bug #591986], [https://bugs.launchpad.net/bugs/605575 Bug #605575]
* Rulers are redrawn properly with recent versions of GTK. [https://bugs.launchpad.net/bugs/627134 Bug #627134]
* Unlinking an orphaned clone no longer causes a crash. [https://bugs.launchpad.net/bugs/675309 Bug #675309]
* Problems with extensions sometimes not working at all on Mac OS X have been fixed. [https://bugs.launchpad.net/bugs/482993 Bug #482993]
* Inkscape should no longer crash due to missing icons at startup or when opening the document properties dialog. [https://bugs.launchpad.net/bugs/658055 Bug #658055], [https://bugs.launchpad.net/bugs/651678 Bug #651678]
* Shift-clicking on the top rounding handle of a rectangle will no longer cause a crash. [https://bugs.launchpad.net/inkscape/+bug/680520 Bug #680520]
* Inkscape builds correctly with recent versions of Poppler. [https://bugs.launchpad.net/bugs/676271 Bug #676271]

==Known issues==

* Stamping in the node tool does not work.
* Closing an unchanged document that contains connectors might ask to save, as if the document was modified. Pressing Ctrl+Z before closing will avoid bringing up the dialog.

==Previous releases==
*[[Release notes/0.48]]
*[[Release notes/0.47]]
*[[Release notes/0.46]]

Release notes/0.48

2014-11-22T18:09:02Z

ScislaC: /* Release highlights */

{{Other languages|en=Release notes/0.48}}

==Inkscape 0.48==
'''[[AnnouncePlanning048]]'''

==Release highlights==
Released on '''23 August 2010'''.

The release marks returning to shorter release cycles to speed up availability of new technologies often developed as part of Google Summer of Code projects.

The highlights of this release are:

* '''multipath''' editing
* improved text tool: subscript, superscript, numerical input for text kerning, tracking and more
* new '''Spray''' tool
* '''LaTeX export''' with PDF/PS/EPS
* '''JessyInk''' extension to create presentations
* numerous bugfixes

==Tools==

===Node Tool===

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

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

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

===Text Tool===

The text toolbar has been overhauled with many bug fixes and improvements. One can now directly access a number of text layout parameters:

*"Line Spacing:" Distance between baselines of adjacent lines.
*"Letter Spacing:" Spacing between letters.
*"Word Spacing:" Spacing between words.
*"Horizontal kerning"
*"Vertical shift"
*"Character rotation"

In addition, support has been added for superscripts and subscripts.

This work was sponsored in part by Inkscape users through LinuxFund.org.

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

Three modes are available.

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

'''Spray options'''

*Amount : spray more or less items.

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

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

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

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


===Connector Tool===

The connector tool can now produce orthogonal connectors (those made up from vertical and horizontal line segments, e.g. as seen in circuit diagrams). There is an additional button on the connector toolbar that can toggle selected connector types between "polyline" and "orthogonal".

Also included are several bug and crash fixes to the connector routing code.

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

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

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

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

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

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

A more thorough description of how to use the new feature (and automate the exporting/inclusion of the image in LaTeX) is given in this document: [http://tug.ctan.org/tex-archive/info/svg-inkscape/ svg-inkscape on CTAN].

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

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

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

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

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

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



==SVG Support==

The baseline-shift attribute is supported! The Text toolbar uses the "super" and "sub" values for implementing superscripts and subscripts. At the moment there is no other GUI access to the attribute.



==Other features==

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

===Extended input device configuration===

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

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

==User interface==

===Adaptive UI===

Initial implementation of adaptive user interface has been introduced. This has internal work done to collect system and runtime information on the user and allow for decisions on how best to assist the user in working. The visible control is a menu to pick from different arrangements, including one optimized for wide-screen computers such as netbooks. Currently the system will detect the screen layout and set the appropriate default. Other minor internals are also run by this.

===Custom Swatches===

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

This iteration has been implemented via single-stop gradients. This results in fully SVG 1.1 compliant files that remain editable.

===CMYK and ICC support===

Support for using icc-color has been extended to more areas of the UI, including the use in gradient stops. This helps preserve custom colors, including CMYK.

===Icon Dialog===

The icon preview dialog has gone through a round of refinement. The newer functionality has been set to the most common defaults, but some behavior can be modified via preference settings.

* Auto Refresh. The icon preview dialog will now auto-refresh as the document is edited.
* Holding initial selection. When the "Selection" checkbox is enabled, the currently selected item selected will be remembered and tracked. Inkscape will use this item's bounding box as an area to be included in the Icon Preview dialog. To change the preview to track a new selection, uncheck and recheck the "Selection" checkbox.
* Layout refinements. The icon previews have been updated, including the addition of visual frames and defaulting to a more compact arrangement.

====Preferences====

You can change the following attributes in <code>group id="iconpreview"</code> in your preferences.xml file:

* <code>autoRefresh</code> (default 1) to enable (1) or disable (0) automatic refresh of preview.
* <code>pack</code> (default 1) to arrange preview thumbnails in a more compact manner (1) to to force the previous vertical stacking (0)
* <code>selectionHold</code> (default 1) to keep preview locked to the initial selection (1) or switch to each newly selected item (0)
* <code>showFrames</code> (default 1) to paint outlines around thumbnails (1) or to suppress them (0)

===Glyphs Dialog===

A basic glyph selection dialog has been added. This allows for viewing which Unicode codepoints are represented in a given font, and to allow individual glyphs to be selected and included. Characters can be selected and inserted via copy and paste or inserted directly using the append button in the dialog. Text will be appended to the currently selected text object on the active canvas.

The range of glyphs/characters being viewed can be filtered by Unicode range and/or language 'script'. When an individual glyph is selected, the dialog status area shows the glyph's Unicode value and script name.

There is a known limitation where the list of glyphs in the dialog are not yet rendered in the selected font, but still in the system font (this mainly is an issue for fonts non-standard characters). When a font with a large character repertoire is selected for viewing, such as a CJK font set to show 'all', the display may pause momentarily as previews are generated.

===New cursors in Selector===

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

===Translations===

New Farsi (fa) and Telugu (te_IN) translations (in progress).

==Tutorials==

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

==Windows port improvements==

The quality of the Windows port was improved substantially.

===Command line interface===

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

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

===Stability improvements===

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

===Unicode compatibility===

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

==Notable bug fixes==

* The 3D tool no longer inserts an inkscape:perspective element into SVG when it is not needed (i.e. when the document has no 3D box objects).
* Wrong clippaths and masks with cyclic recursion (i.e. clippaths or masks that refer to themselves via other clippaths or masks) no longer crash Inkscape.
* Default unit setting for the XY grid is now respected when creating a new grid.
* Pasting Live Path Effect stacks now works. It adds the stack of the copied object to the end of the LPE stack (if present) of the object it is pasted to.
* The accuracy of the bounding box calculation has been significantly improved when converting objects to patterns or markers. This should make it much easier to create patterns where the tiles should 'connect' to each other, e.g. a tile with a plus sign to create a hatched pattern.
* The default font has been changed to ''Sans'', eliminating problems when the former default font, ''Bitstream Vera Sans'', is not available. (''Sans'' is a Pango pseudo-font.)
* The Text toolbar bold and italic/oblique buttons are more likely to work as expected.
* Bitmaps with transparency are now shown (and exported) correctly.
* The emergency save function no longer mangles the file names (which used to make it fail quite often).

==Known issues==

===Floating Toolbars===

Floating toolbars had been found to present problems on a few window managers. By default floating has been turned off in response on MS Windows and the default KDE window manager. To re-enable, the <code>preferences.xml</code> file has an <code>options</code> group called <code>workarounds</code> with a setting called <code>floatallowed</code>. Setting this to <code>"1"</code> will re-enable floating on these problematic systems. Valid values are <code>"0"</code> and <code>"1"</code>.

==Previous releases==

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

[[Category:Marketing]]

Hackfest2015

2014-11-21T07:44:01Z

ScislaC: /* The Pitch */ minor edit from karen during irc meeting

This page details the planning of an Inkscape Hackfest in April 2015

== Discusson ==

See the [[Board_Meetings]] page for minutes of past discussions and the time and place of the next discussion.

== 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.

Maybe even some Gtk+ issues: http://wiki.inkscape.org/wiki/index.php/GTK%2B_Issues

== The Pitch ==

Inkscape enables digital artists to produce professional quality work and beginners to create simple drawings or just noodle a bit. It allows everyone to explore their creativity. Inkscape is also used by engineers and scientists to create clear drawings to explain their ideas.
The Inkscape software is provided for free to all, as a fully open source, community-developed, socially owned project.

We need your help to further improve the program so many people love, and make sure it has a bright future!

Our developers work remotely in all corners of the world and rarely have the chance to work together in person. We've noticed that in-person meetings bring about stronger relationships and more creative results. Being together in one room allows us to work on things that are harder to do remotely: designing a new plugin/extension system, teaming up to squash particularly nasty bugs, authoring better user documentation, and planning where to take Inkscape development in the future.

We will be meeting before the [http://libregraphicsmeeting.org/2014/ Libre Graphics Meeting] (April 29 to May 2, 2015) in Toronto for three days of intense hacking.

Please consider donating to cover travel, room, and board so our volunteer developers can attend the hackfest in person.

* Organizations that use Inkscape to draw testimonials from: http://wiki.inkscape.org/wiki/index.php/UsedBy

* Some of the nifty new features: http://inkscapetutorials.wordpress.com/category/0-91-new-features/

# TODO: Needs some photos of our developers, or images of what we'll be working on

Suggested donation amounts:
* $5 - If you would buy an Inkscape developer a beverage
* $50 - Food & Incidentals for one developer
* $500 - Lunch for the hackfest
* $2000 - Sponsor a developer

== Alternate Pitch language ==

Inkscape is a free, fully open source, community-developed, socially owned software program that allows everyone to explore their creativity. Digital artists use it to produce professional quality work. Engineers and scientists use it to create clear drawings to explain their ideas. And everyday people use it to create simple drawings, develop their design skills, and just have fun.

As good as Inkscape is and as proud as we are of it, it could be even better. But to make that happen, we need your help.

Our dedicated volunteer Inkscape developers are spread across the globe and rarely have the chance to meet face-to-face. Thanks to the miracles of technology, we are able to work remote on many things, but we've noticed that in-person meetings bring about stronger relationships, quicker solutions, and more creative results.

Being together in one room also allows us to work on things that are harder to do remotely: designing a new plugin/extension system, teaming up to squash particularly nasty bugs, authoring better user documentation, and planning where to take Inkscape development in the future.

Our goal is for all available Inkscape developers to be able to meet before the [http://libregraphicsmeeting.org/2014/ Libre Graphics Meeting] (April 29 to May 2, 2015) in Toronto for three days of intense, in-person hacking.

So will you please consider donating a few bucks to help cover travel, room, and board so our available volunteer developers can attend the hackfest in person? It's an investment in Inkscape which should produce big benefits for all its users and help us make the product the very best it can be.

Suggested donation amounts:
* $5 – Buys an Inkscape developer a beverage
* $50 – Provides meals & incidentals for one developer
* $500 – Buys lunch for the hackfest
* $2000 – Sponsors a developer
* Other – Whatever you can spare. Every donation helps!

To make your donation, (insert here how they do that)

Thanks so much for being an investor in Inkscape and contributing to help bring the developers together in Toronto. We appreciate your commitment to free, fully open source, community-developed, socially owned software, and your vision for what Inkscape can become. We are grateful to have you on our team!

== Date ==

Sunday, April 26th through Tuesday, April 28th; just before the [http://libregraphicsmeeting.org/2014/ Libre Graphics Meeting 2015] (LGM2015) which takes place from [http://lists.freedesktop.org/archives/create/2014-May/004961.html April 29th through May 2nd 2015] (note: email states 30th through 2nd but an email on libre-graphics-meeting states that one day has been added at the beginning).

== Schedule ==

A sketch of what might happen on hackfest days, 2 or 3 days of things should be planned.

a) Social meeting
b) Pre-lunch presentations
c) Lunch
d) Pure hacking
e) Dinner
f) Late night hacking

== Location ==

Toronto at the same venue as LGM. We have a room reserved for us that can hold up to 30 people. It has movable tables with built in power outlets and a 40" TV in lieu of a projector.

== Budget ==

We had 8 attendees at the last LGM, and are hoping for perhaps 12 people this time.
Roughly, assuming costs will be in the $1000-2000 range per person for travel, room, and board, that gives a budget of $9-18k

To get more specific we'll need to:
* Estimate of hotel costs per night: $50 per person for shared double in two star hotel, $30 per person in hostel
* Estimate of airfare costs from Europe ($900), West Coast ($750), East Coast ($300), etc.
* Plan a daily food/incidentals stipend amount (~$30)

Cost estimate for 3 days pre-LGM in Toronto:
* From Paris: airfare $900 + $200 hotel + $100 food = $1200
* From Boston: airfare $300 + $200 hotel + $100 food = $600
* From Zurich: airfare $900 + $200 hotel + $100 food = $1200
* From Los Angeles: airfare $750 + $200 hotel + $100 food = $1150

We're considering a model similar to what we did with reimbursement limits for the GSoC reunion:

* Up to $2000 each for Inkscape developers who have contributed for 3+ years and > 200 commits (About 18 developers qualify, not all currently active)
* Up to $1500 each for Inkscape developers who have contributed for 2+ years and > 100 commits (About 17 additional qualify)
* Up to $1000 each for Inkscape developers who have contributed for 1+ year and > 50 commits (About 24 additional qualify)
* Up to $500 each for any Inkscape contributor listed in AUTHORS file with at least 10 commits by Jan 1, 2015 (About 50 additional qualify)

== Sponsors ==

Finding local companies who might like to sponsor the event, help out with feeding people or bringing them to attend can be documented here.

maybe if we had some kind of form letter folks could give to their employer
i save you this much $$ per year in adobe whatever license fees. would you support my work for this company by contributing some percentage of that back to the inkscape project

* http://wiki.inkscape.org/wiki/index.php/UsedBy

=== Sponsors' interests ===
It would help a lot if we have specific ideas about how to compensate sponsors, what they would be "buying".

Interests and offerings
* PR among users
** News item with clear marking of who sponsored the event
* Improving a product that they ship
** Work on specific bugs may be very tricky
** offer to work on general code improvement (focussing on refactoring/ease for devs to develop new things, for example) seems good
* Improving a product that many of their employees use
** Work on specific bugs may be very tricky
** offer to work on general code improvement (focussing on stability, for example) seems good
* PR among coders
** Clear PR during event
** Making contacts with development team
** News item with clear marking of who sponsored the event

== Action items ==

{| border="1" cellspacing="0" cellpadding="5" align="center"
|-
! Date
! Owner
! Item
|-
| 15 sep 2014
| Karen Sandler (SFC)
| [DONE] Could inquire if RH and Google can sponsor
|-
| 15 sep 2014
| Bryce
| [DONE] Get the fundraising doc posted on our website
|-
| 15 sep 2014
| Bryce
| Once we have things more nailed down: inquire with samsung for hackfest sponsorship
|-
| 15 sep 2014
| Martin Owens
| Hear back from LGM about Torronto co-sponsorship
|-
| 15 sep 2014
| ScislaC
| Contact userbase for interest in the hackfest
|-
| 15 sep 2014
| ScislaC
| [DONE] Get a list of [[http://wiki.inkscape.org/wiki/index.php/UsedBy companies using inkscape]]
|-
| 15 sep 2014
| Tav
| [DONE] Summarize and mail devlist
|-
| 20 sep 2014
| Tav
| [DONE] Set up a new wiki page for planning second Hackfest w/ RedHat
|-
| 20 sep 2014
| Bryce
| [DONE] Draft a preliminary promotional fundraising blurb
|-
| 20 sep 2014
| ryanlerch
| Work on a video for fundraiser
|-
| 20 sep 2014
| everyone
| [DONE] Consider indiegogo vs. hosting our own paypal donation page
|-
| 15 oct 2014
| everyone
| [DONE] Decide plan for implementing website/db support for fundraiser campaigns
|-
| 15 oct 2014
| karen
| Can we use Inkscape's existing paypal account or should we set up a separate one for fundraising
|-
| 15 oct 2014
| karen
| If we set the product_id on the donation page, can SFC provide us with a summary (or the raw data) with this info, so we can tally hackfest contribs?
|-
| 15 oct 2014
|
| Mockup layout on Staging for a fundraiser/donation page (using text from Pitch)
|-
| 12 nov 2014
|
| Decide where in inkscape.org's site menu to place Hackfest related pages
|-
| 12 nov 2014
|
| Create a Hackfest page in the main website
|-
| 12 nov 2014
|
| Write a page for Toronto transportation for A) how to get to/from airport, and B) how to get around the city
|-
| 12 nov 2014
|
| Write a set of posts for Inkscape blog / news feed (to be finalized + published as the event nears)
|-
| 12 nov 2014
|
| Find someone local to Toronto to help with local logistics
|-
| 12 nov 2014
|
| Translate the Hackfest Donation page to French
|-
| 12 nov 2014
|
| Translate the Hackfest Donation page to Spanish (and/or other major languages)

|}

== Brainstorm area ==
Put things here that you think could use a bit of discussion/thought.

Places to announce the fundraiser, once it's set up?
* Inkscape's g+ page
* inkscape-users@
* twitter
* dA
* the website
* <karenesq> I bet LWN would be interested
* <doctormon> Possible interest: http://zipfelchappe.readthedocs.org/en/latest/
* <ryanlerch> i can promote on inkscapetuts and fedoramagazine too

=== Tasks to tackle ===
What can we hack on? To me (Johan) what seems nice are tasks that become more managable/fun/... and with higher chance of completion (maximum one day) when done in a group. Before determining specific tasks, what kind of tasks should we try to tackle?
* Fleshing out documentation
** Code documentation
** Architecture docs
** Coding howtos
** Tutorials
** User documentation
** Translation of same
* A bug that requires knowledge of large part of codebase.
* Writing test cases
* Simple repetitive refactoring or code clean up that can be parallelized and may not be so much fun alone. Examples:
** make sure every file contains standardized and correct copyright notice,
** eradicate all use of gboolean/TRUE/FALSE,
** move towards C++11 by =delete on copy-constructors instead of making them private+undefined).
* A more complicated refactoring that requires discussion.
** Conversion of build system
** Performance optimizations
** Coordinate flip.
* A feature that can be split into parallelizable tasks possibly with different skills required, for example:
** combination of UI, backline math stuff, usability/behavior stuff.
** Infrastructure setup
* Design / strategy collaboration
** SVG 2 fallbacks
** New plugin/extension system
* Planning
** Post-1.0 roadmap definition
** Conference attendance for upcoming year
** Future hackfests :-)
* Pictures pictures pictures
** Try to make nice pictures that show what has happened. Can then also be used for PR for next edition.

For the drunk hacking sessions:
* Fun stuff, obviously. So perhaps a quirky feature, and see next day if it lead to something usable.

=== Participants ===

We aim for around 10 people.

Who do we expect to join (not remote), what kind of people?

* Seasoned Inkscape developers? Yes.
* More recently joined Inkscape developers? Yes.
* Coders unfamiliar with Inkscape? Possibly one or two. Local students, e.g.
** Good programmers with experience?
** New programmers with little experience?
* Users? Probably none that don't fall in other categories
** Graphic designers?
** Technical drawers?
** 'Powerpoint' figure drawers?
We can make a list of possible tasks for each of these groups.

For the first hackfest, I (Tav) would keep it open to anyone, but only promote it to people already familiar with the Inkscape code base.

=== Help for newcomers ===
* Provide a VM image with: Inkscape's trunk ready to compile. Preferably with clang so one can run clang's static analyzer and quickly get a nicely formatted report of potential bugs that are generally easy to fix (i.e. null-ptr checking, etc).
* List of simple tasks

=== Non-coding stuff ===
Some ideas for socializing and getting away from PC screen
* Karaoke :)
* Board/card games
* Run around town
* Movie
* Pub
* Take a group picture!!!

Hackfest2015

2014-11-21T03:36:40Z

ScislaC: /* Alternate Pitch language */

This page details the planning of an Inkscape Hackfest in April 2015

== Discusson ==

See the [[Board_Meetings]] page for minutes of past discussions and the time and place of the next discussion.

== 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.

Maybe even some Gtk+ issues: http://wiki.inkscape.org/wiki/index.php/GTK%2B_Issues

== The Pitch ==

Inkscape enables digital artists to produce professional quality work and beginners to create simple drawings or just noodle a bit. It allows everyone to explore their creativity. Inkscape is also used by engineers and scientists to create clear drawings to explain their ideas.
The Inkscape software is provided for free to all, as a fully open source, community-developed, socially owned project.

We need your help to further improve the program so many people love, and make sure it has a bright future!

Our developers work remotely in all corners of the world and rarely have the chance to work together in person. We've noticed that in-person meetings bring about stronger relationships and more creative results. Being together in one room allows us to work on things that are harder to do remotely: designing a new plugin/extension system, teaming up to squash particularly nasty bugs, authoring better user documentation, and planning where to take Inkscape development in the future.

We will be meeting before the [http://libregraphicsmeeting.org/2014/ Libre Graphics Meeting] (April 29 to May 2, 2015) in Toronto for three days of intense hacking.

Please consider donating to cover travel, room, and board so our volunteer developers can attend the hackfest in person.

* Organizations that use Inkscape to draw testimonials from: http://wiki.inkscape.org/wiki/index.php/UsedBy

* Some of the nifty new features: http://inkscapetutorials.wordpress.com/category/0-91-new-features/

# TODO: Needs some photos of our developers, or images of what we'll be working on

Suggested donation amounts:
* $5 - Buy an Inkscape developer a beverage
* $50 - Food & Incidentals for one developer
* $500 - Lunch for the hackfest
* $2000 - Sponsor a developer

== Alternate Pitch language ==

Inkscape is a free, fully open source, community-developed, socially owned software program that allows everyone to explore their creativity. Digital artists use it to produce professional quality work. Engineers and scientists use it to create clear drawings to explain their ideas. And everyday people use it to create simple drawings, develop their design skills, and just have fun.

As good as Inkscape is and as proud as we are of it, it could be even better. But to make that happen, we need your help.

Our dedicated volunteer Inkscape developers are spread across the globe and rarely have the chance to meet face-to-face. Thanks to the miracles of technology, we are able to work remote on many things, but we've noticed that in-person meetings bring about stronger relationships, quicker solutions, and more creative results.

Being together in one room also allows us to work on things that are harder to do remotely: designing a new plugin/extension system, teaming up to squash particularly nasty bugs, authoring better user documentation, and planning where to take Inkscape development in the future.

Our goal is for all available Inkscape developers to be able to meet before the [http://libregraphicsmeeting.org/2014/ Libre Graphics Meeting] (April 29 to May 2, 2015) in Toronto for three days of intense, in-person hacking.

So will you please consider donating a few bucks to help cover travel, room, and board so our available volunteer developers can attend the hackfest in person? It's an investment in Inkscape which should produce big benefits for all its users and help us make the product the very best it can be.

Suggested donation amounts:
* $5 – Buys an Inkscape developer a beverage
* $50 – Provides meals & incidentals for one developer
* $500 – Buys lunch for the hackfest
* $2000 – Sponsors a developer
* Other – Whatever you can spare. Every donation helps!

To make your donation, (insert here how they do that)

Thanks so much for being an investor in Inkscape and contributing to help bring the developers together in Toronto. We appreciate your commitment to free, fully open source, community-developed, socially owned software, and your vision for what Inkscape can become. We are grateful to have you on our team!

== Date ==

Sunday, April 26th through Tuesday, April 28th; just before the [http://libregraphicsmeeting.org/2014/ Libre Graphics Meeting 2015] (LGM2015) which takes place from [http://lists.freedesktop.org/archives/create/2014-May/004961.html April 29th through May 2nd 2015] (note: email states 30th through 2nd but an email on libre-graphics-meeting states that one day has been added at the beginning).

== Schedule ==

A sketch of what might happen on hackfest days, 2 or 3 days of things should be planned.

a) Social meeting
b) Pre-lunch presentations
c) Lunch
d) Pure hacking
e) Dinner
f) Late night hacking

== Location ==

Toronto at the same venue as LGM. We have a room reserved for us that can hold up to 30 people. It has movable tables with built in power outlets and a 40" TV in lieu of a projector.

== Budget ==

We had 8 attendees at the last LGM, and are hoping for perhaps 12 people this time.
Roughly, assuming costs will be in the $1000-2000 range per person for travel, room, and board, that gives a budget of $9-18k

To get more specific we'll need to:
* Estimate of hotel costs per night: $50 per person for shared double in two star hotel, $30 per person in hostel
* Estimate of airfare costs from Europe ($900), West Coast ($750), East Coast ($300), etc.
* Plan a daily food/incidentals stipend amount (~$30)

Cost estimate for 3 days pre-LGM in Toronto:
* From Paris: airfare $900 + $200 hotel + $100 food = $1200
* From Boston: airfare $300 + $200 hotel + $100 food = $600
* From Zurich: airfare $900 + $200 hotel + $100 food = $1200
* From Los Angeles: airfare $750 + $200 hotel + $100 food = $1150

We're considering a model similar to what we did with reimbursement limits for the GSoC reunion:

* Up to $2000 each for Inkscape developers who have contributed for 3+ years and > 200 commits (About 18 developers qualify, not all currently active)
* Up to $1500 each for Inkscape developers who have contributed for 2+ years and > 100 commits (About 17 additional qualify)
* Up to $1000 each for Inkscape developers who have contributed for 1+ year and > 50 commits (About 24 additional qualify)
* Up to $500 each for any Inkscape contributor listed in AUTHORS file with at least 10 commits by Jan 1, 2015 (About 50 additional qualify)

== Sponsors ==

Finding local companies who might like to sponsor the event, help out with feeding people or bringing them to attend can be documented here.

maybe if we had some kind of form letter folks could give to their employer
i save you this much $$ per year in adobe whatever license fees. would you support my work for this company by contributing some percentage of that back to the inkscape project

* http://wiki.inkscape.org/wiki/index.php/UsedBy

=== Sponsors' interests ===
It would help a lot if we have specific ideas about how to compensate sponsors, what they would be "buying".

Interests and offerings
* PR among users
** News item with clear marking of who sponsored the event
* Improving a product that they ship
** Work on specific bugs may be very tricky
** offer to work on general code improvement (focussing on refactoring/ease for devs to develop new things, for example) seems good
* Improving a product that many of their employees use
** Work on specific bugs may be very tricky
** offer to work on general code improvement (focussing on stability, for example) seems good
* PR among coders
** Clear PR during event
** Making contacts with development team
** News item with clear marking of who sponsored the event

== Action items ==

{| border="1" cellspacing="0" cellpadding="5" align="center"
|-
! Date
! Owner
! Item
|-
| 15 sep 2014
| Karen Sandler (SFC)
| [DONE] Could inquire if RH and Google can sponsor
|-
| 15 sep 2014
| Bryce
| [DONE] Get the fundraising doc posted on our website
|-
| 15 sep 2014
| Bryce
| Once we have things more nailed down: inquire with samsung for hackfest sponsorship
|-
| 15 sep 2014
| Martin Owens
| Hear back from LGM about Torronto co-sponsorship
|-
| 15 sep 2014
| ScislaC
| Contact userbase for interest in the hackfest
|-
| 15 sep 2014
| ScislaC
| [DONE] Get a list of [[http://wiki.inkscape.org/wiki/index.php/UsedBy companies using inkscape]]
|-
| 15 sep 2014
| Tav
| [DONE] Summarize and mail devlist
|-
| 20 sep 2014
| Tav
| [DONE] Set up a new wiki page for planning second Hackfest w/ RedHat
|-
| 20 sep 2014
| Bryce
| [DONE] Draft a preliminary promotional fundraising blurb
|-
| 20 sep 2014
| ryanlerch
| Work on a video for fundraiser
|-
| 20 sep 2014
| everyone
| [DONE] Consider indiegogo vs. hosting our own paypal donation page
|-
| 15 oct 2014
| everyone
| [DONE] Decide plan for implementing website/db support for fundraiser campaigns
|-
| 15 oct 2014
| karen
| Can we use Inkscape's existing paypal account or should we set up a separate one for fundraising
|-
| 15 oct 2014
| karen
| If we set the product_id on the donation page, can SFC provide us with a summary (or the raw data) with this info, so we can tally hackfest contribs?
|-
| 15 oct 2014
|
| Mockup layout on Staging for a fundraiser/donation page (using text from Pitch)
|-
| 12 nov 2014
|
| Decide where in inkscape.org's site menu to place Hackfest related pages
|-
| 12 nov 2014
|
| Create a Hackfest page in the main website
|-
| 12 nov 2014
|
| Write a page for Toronto transportation for A) how to get to/from airport, and B) how to get around the city
|-
| 12 nov 2014
|
| Write a set of posts for Inkscape blog / news feed (to be finalized + published as the event nears)
|-
| 12 nov 2014
|
| Find someone local to Toronto to help with local logistics
|-
| 12 nov 2014
|
| Translate the Hackfest Donation page to French
|-
| 12 nov 2014
|
| Translate the Hackfest Donation page to Spanish (and/or other major languages)

|}

== Brainstorm area ==
Put things here that you think could use a bit of discussion/thought.

Places to announce the fundraiser, once it's set up?
* Inkscape's g+ page
* inkscape-users@
* twitter
* dA
* the website
* <karenesq> I bet LWN would be interested
* <doctormon> Possible interest: http://zipfelchappe.readthedocs.org/en/latest/
* <ryanlerch> i can promote on inkscapetuts and fedoramagazine too

=== Tasks to tackle ===
What can we hack on? To me (Johan) what seems nice are tasks that become more managable/fun/... and with higher chance of completion (maximum one day) when done in a group. Before determining specific tasks, what kind of tasks should we try to tackle?
* Fleshing out documentation
** Code documentation
** Architecture docs
** Coding howtos
** Tutorials
** User documentation
** Translation of same
* A bug that requires knowledge of large part of codebase.
* Writing test cases
* Simple repetitive refactoring or code clean up that can be parallelized and may not be so much fun alone. Examples:
** make sure every file contains standardized and correct copyright notice,
** eradicate all use of gboolean/TRUE/FALSE,
** move towards C++11 by =delete on copy-constructors instead of making them private+undefined).
* A more complicated refactoring that requires discussion.
** Conversion of build system
** Performance optimizations
** Coordinate flip.
* A feature that can be split into parallelizable tasks possibly with different skills required, for example:
** combination of UI, backline math stuff, usability/behavior stuff.
** Infrastructure setup
* Design / strategy collaboration
** SVG 2 fallbacks
** New plugin/extension system
* Planning
** Post-1.0 roadmap definition
** Conference attendance for upcoming year
** Future hackfests :-)
* Pictures pictures pictures
** Try to make nice pictures that show what has happened. Can then also be used for PR for next edition.

For the drunk hacking sessions:
* Fun stuff, obviously. So perhaps a quirky feature, and see next day if it lead to something usable.

=== Participants ===

We aim for around 10 people.

Who do we expect to join (not remote), what kind of people?

* Seasoned Inkscape developers? Yes.
* More recently joined Inkscape developers? Yes.
* Coders unfamiliar with Inkscape? Possibly one or two. Local students, e.g.
** Good programmers with experience?
** New programmers with little experience?
* Users? Probably none that don't fall in other categories
** Graphic designers?
** Technical drawers?
** 'Powerpoint' figure drawers?
We can make a list of possible tasks for each of these groups.

For the first hackfest, I (Tav) would keep it open to anyone, but only promote it to people already familiar with the Inkscape code base.

=== Help for newcomers ===
* Provide a VM image with: Inkscape's trunk ready to compile. Preferably with clang so one can run clang's static analyzer and quickly get a nicely formatted report of potential bugs that are generally easy to fix (i.e. null-ptr checking, etc).
* List of simple tasks

=== Non-coding stuff ===
Some ideas for socializing and getting away from PC screen
* Karaoke :)
* Board/card games
* Run around town
* Movie
* Pub
* Take a group picture!!!

Hackfest2015

2014-11-21T03:30:54Z

ScislaC: Alternate pitch wording

This page details the planning of an Inkscape Hackfest in April 2015

== Discusson ==

See the [[Board_Meetings]] page for minutes of past discussions and the time and place of the next discussion.

== 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.

Maybe even some Gtk+ issues: http://wiki.inkscape.org/wiki/index.php/GTK%2B_Issues

== The Pitch ==

Inkscape enables digital artists to produce professional quality work and beginners to create simple drawings or just noodle a bit. It allows everyone to explore their creativity. Inkscape is also used by engineers and scientists to create clear drawings to explain their ideas.
The Inkscape software is provided for free to all, as a fully open source, community-developed, socially owned project.

We need your help to further improve the program so many people love, and make sure it has a bright future!

Our developers work remotely in all corners of the world and rarely have the chance to work together in person. We've noticed that in-person meetings bring about stronger relationships and more creative results. Being together in one room allows us to work on things that are harder to do remotely: designing a new plugin/extension system, teaming up to squash particularly nasty bugs, authoring better user documentation, and planning where to take Inkscape development in the future.

We will be meeting before the [http://libregraphicsmeeting.org/2014/ Libre Graphics Meeting] (April 29 to May 2, 2015) in Toronto for three days of intense hacking.

Please consider donating to cover travel, room, and board so our volunteer developers can attend the hackfest in person.

* Organizations that use Inkscape to draw testimonials from: http://wiki.inkscape.org/wiki/index.php/UsedBy

* Some of the nifty new features: http://inkscapetutorials.wordpress.com/category/0-91-new-features/

# TODO: Needs some photos of our developers, or images of what we'll be working on

Suggested donation amounts:
* $5 - Buy an Inkscape developer a beverage
* $50 - Food & Incidentals for one developer
* $500 - Lunch for the hackfest
* $2000 - Sponsor a developer

== Alternate Pitch language ==

Inkscape is a free, fully open source, community-developed, socially owned software program that allows everyone to explore their creativity. Digital artists use it to produce prefessional quality work. Engineers and scientists use it to create clear drawings to explain their ideas. And everyday people use it to create simple drawings, develop their design skills, and just have fun.

As good as Inkscape is and as proud as we are of it, it could be even better. But to make that happen, we need your help.

Our dedicated volunteer Inkscape developers are spread across the globe and rarely have the chance to meet face-to-face. Thanks to the miracles of technology, we are able to work remote on many things, but we've noticed that in-person meetings bring about stronger relationships, quicker solutions, and more creative results.

Being together in one room also allows us to work on things that are harder to do remotely: designing a new plugin/extension system, teaming up to squash particularly nasty bugs, authoring better user documentation, and planning where to take Inkscape development in the future.

Our goal is for all available Inkascape developers to be able to meet before the [http://libregraphicsmeeting.org/2014/ Libre Graphics Meeting] (April 29 to May 2, 2015) in Toronto for three days of intense, in-person hacking.

So will you please consider donating a few bucks to help cover travel, room, and board so our available volunteer developers can attend the hackfest in person? It's an investment in Inkscape which should produce big benefits for all its users and help us make the product the very best it can be.

Suggested donation amounts:
* $5 – Buys an Inkscape developer a beverage
* $50 – Provides meals & incidentals for one developer
* $500 – Buys lunch for the hackfest
* $2000 – Sponsors a developer
* Other – Whatever you can spare. Every donation helps!

To make your donation, (insert here how they do that)

Thanks so much for being an investor in Inkscape and contributing to help bring the developers together in Toronto. We appreciate your commitment to free, fully open source, community-developed, socially owned software, and your vision for what Inkscape can become. We are grateful to have you on our team!

== Date ==

Sunday, April 26th through Tuesday, April 28th; just before the [http://libregraphicsmeeting.org/2014/ Libre Graphics Meeting 2015] (LGM2015) which takes place from [http://lists.freedesktop.org/archives/create/2014-May/004961.html April 29th through May 2nd 2015] (note: email states 30th through 2nd but an email on libre-graphics-meeting states that one day has been added at the beginning).

== Schedule ==

A sketch of what might happen on hackfest days, 2 or 3 days of things should be planned.

a) Social meeting
b) Pre-lunch presentations
c) Lunch
d) Pure hacking
e) Dinner
f) Late night hacking

== Location ==

Toronto at the same venue as LGM. We have a room reserved for us that can hold up to 30 people. It has movable tables with built in power outlets and a 40" TV in lieu of a projector.

== Budget ==

We had 8 attendees at the last LGM, and are hoping for perhaps 12 people this time.
Roughly, assuming costs will be in the $1000-2000 range per person for travel, room, and board, that gives a budget of $9-18k

To get more specific we'll need to:
* Estimate of hotel costs per night: $50 per person for shared double in two star hotel, $30 per person in hostel
* Estimate of airfare costs from Europe ($900), West Coast ($750), East Coast ($300), etc.
* Plan a daily food/incidentals stipend amount (~$30)

Cost estimate for 3 days pre-LGM in Toronto:
* From Paris: airfare $900 + $200 hotel + $100 food = $1200
* From Boston: airfare $300 + $200 hotel + $100 food = $600
* From Zurich: airfare $900 + $200 hotel + $100 food = $1200
* From Los Angeles: airfare $750 + $200 hotel + $100 food = $1150

We're considering a model similar to what we did with reimbursement limits for the GSoC reunion:

* Up to $2000 each for Inkscape developers who have contributed for 3+ years and > 200 commits (About 18 developers qualify, not all currently active)
* Up to $1500 each for Inkscape developers who have contributed for 2+ years and > 100 commits (About 17 additional qualify)
* Up to $1000 each for Inkscape developers who have contributed for 1+ year and > 50 commits (About 24 additional qualify)
* Up to $500 each for any Inkscape contributor listed in AUTHORS file with at least 10 commits by Jan 1, 2015 (About 50 additional qualify)

== Sponsors ==

Finding local companies who might like to sponsor the event, help out with feeding people or bringing them to attend can be documented here.

maybe if we had some kind of form letter folks could give to their employer
i save you this much $$ per year in adobe whatever license fees. would you support my work for this company by contributing some percentage of that back to the inkscape project

* http://wiki.inkscape.org/wiki/index.php/UsedBy

=== Sponsors' interests ===
It would help a lot if we have specific ideas about how to compensate sponsors, what they would be "buying".

Interests and offerings
* PR among users
** News item with clear marking of who sponsored the event
* Improving a product that they ship
** Work on specific bugs may be very tricky
** offer to work on general code improvement (focussing on refactoring/ease for devs to develop new things, for example) seems good
* Improving a product that many of their employees use
** Work on specific bugs may be very tricky
** offer to work on general code improvement (focussing on stability, for example) seems good
* PR among coders
** Clear PR during event
** Making contacts with development team
** News item with clear marking of who sponsored the event

== Action items ==

{| border="1" cellspacing="0" cellpadding="5" align="center"
|-
! Date
! Owner
! Item
|-
| 15 sep 2014
| Karen Sandler (SFC)
| [DONE] Could inquire if RH and Google can sponsor
|-
| 15 sep 2014
| Bryce
| [DONE] Get the fundraising doc posted on our website
|-
| 15 sep 2014
| Bryce
| Once we have things more nailed down: inquire with samsung for hackfest sponsorship
|-
| 15 sep 2014
| Martin Owens
| Hear back from LGM about Torronto co-sponsorship
|-
| 15 sep 2014
| ScislaC
| Contact userbase for interest in the hackfest
|-
| 15 sep 2014
| ScislaC
| [DONE] Get a list of [[http://wiki.inkscape.org/wiki/index.php/UsedBy companies using inkscape]]
|-
| 15 sep 2014
| Tav
| [DONE] Summarize and mail devlist
|-
| 20 sep 2014
| Tav
| [DONE] Set up a new wiki page for planning second Hackfest w/ RedHat
|-
| 20 sep 2014
| Bryce
| [DONE] Draft a preliminary promotional fundraising blurb
|-
| 20 sep 2014
| ryanlerch
| Work on a video for fundraiser
|-
| 20 sep 2014
| everyone
| [DONE] Consider indiegogo vs. hosting our own paypal donation page
|-
| 15 oct 2014
| everyone
| [DONE] Decide plan for implementing website/db support for fundraiser campaigns
|-
| 15 oct 2014
| karen
| Can we use Inkscape's existing paypal account or should we set up a separate one for fundraising
|-
| 15 oct 2014
| karen
| If we set the product_id on the donation page, can SFC provide us with a summary (or the raw data) with this info, so we can tally hackfest contribs?
|-
| 15 oct 2014
|
| Mockup layout on Staging for a fundraiser/donation page (using text from Pitch)
|-
| 12 nov 2014
|
| Decide where in inkscape.org's site menu to place Hackfest related pages
|-
| 12 nov 2014
|
| Create a Hackfest page in the main website
|-
| 12 nov 2014
|
| Write a page for Toronto transportation for A) how to get to/from airport, and B) how to get around the city
|-
| 12 nov 2014
|
| Write a set of posts for Inkscape blog / news feed (to be finalized + published as the event nears)
|-
| 12 nov 2014
|
| Find someone local to Toronto to help with local logistics
|-
| 12 nov 2014
|
| Translate the Hackfest Donation page to French
|-
| 12 nov 2014
|
| Translate the Hackfest Donation page to Spanish (and/or other major languages)

|}

== Brainstorm area ==
Put things here that you think could use a bit of discussion/thought.

Places to announce the fundraiser, once it's set up?
* Inkscape's g+ page
* inkscape-users@
* twitter
* dA
* the website
* <karenesq> I bet LWN would be interested
* <doctormon> Possible interest: http://zipfelchappe.readthedocs.org/en/latest/
* <ryanlerch> i can promote on inkscapetuts and fedoramagazine too

=== Tasks to tackle ===
What can we hack on? To me (Johan) what seems nice are tasks that become more managable/fun/... and with higher chance of completion (maximum one day) when done in a group. Before determining specific tasks, what kind of tasks should we try to tackle?
* Fleshing out documentation
** Code documentation
** Architecture docs
** Coding howtos
** Tutorials
** User documentation
** Translation of same
* A bug that requires knowledge of large part of codebase.
* Writing test cases
* Simple repetitive refactoring or code clean up that can be parallelized and may not be so much fun alone. Examples:
** make sure every file contains standardized and correct copyright notice,
** eradicate all use of gboolean/TRUE/FALSE,
** move towards C++11 by =delete on copy-constructors instead of making them private+undefined).
* A more complicated refactoring that requires discussion.
** Conversion of build system
** Performance optimizations
** Coordinate flip.
* A feature that can be split into parallelizable tasks possibly with different skills required, for example:
** combination of UI, backline math stuff, usability/behavior stuff.
** Infrastructure setup
* Design / strategy collaboration
** SVG 2 fallbacks
** New plugin/extension system
* Planning
** Post-1.0 roadmap definition
** Conference attendance for upcoming year
** Future hackfests :-)
* Pictures pictures pictures
** Try to make nice pictures that show what has happened. Can then also be used for PR for next edition.

For the drunk hacking sessions:
* Fun stuff, obviously. So perhaps a quirky feature, and see next day if it lead to something usable.

=== Participants ===

We aim for around 10 people.

Who do we expect to join (not remote), what kind of people?

* Seasoned Inkscape developers? Yes.
* More recently joined Inkscape developers? Yes.
* Coders unfamiliar with Inkscape? Possibly one or two. Local students, e.g.
** Good programmers with experience?
** New programmers with little experience?
* Users? Probably none that don't fall in other categories
** Graphic designers?
** Technical drawers?
** 'Powerpoint' figure drawers?
We can make a list of possible tasks for each of these groups.

For the first hackfest, I (Tav) would keep it open to anyone, but only promote it to people already familiar with the Inkscape code base.

=== Help for newcomers ===
* Provide a VM image with: Inkscape's trunk ready to compile. Preferably with clang so one can run clang's static analyzer and quickly get a nicely formatted report of potential bugs that are generally easy to fix (i.e. null-ptr checking, etc).
* List of simple tasks

=== Non-coding stuff ===
Some ideas for socializing and getting away from PC screen
* Karaoke :)
* Board/card games
* Run around town
* Movie
* Pub
* Take a group picture!!!

Release notes/0.92

2014-10-30T22:10:57Z

ScislaC: /* Live Path Effects */

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

==Inkscape 0.92==

'''(definitely not released yet - [[AnnouncePlanning092]])'''

==Release highlights==

Released on '''«YYYY-MM-DD»'''.

== Dialogs, etc. ==

=== Objects ===
Hierarchy of document

=== Selection Sets ===
Create selection sets that are not affected document structure

=== Live Path Effects ===
==== Fillet/Chamfer ====
* Fillet/Chamfer knots are green diamonds
* '''Change Fillet/Chamfer types:''' <kbd>Ctrl+click</kbd> green knot

==== Roughen ====
==== Simplify ====
==== Perspective Envelope ====
==== Lattice Deformation 2 ====
==== Show Handles ====

== Other user interface ==

Release notes/0.92

2014-10-30T21:50:20Z

ScislaC: /* Chamfer/Fillet */

Release notes/0.92

2014-10-30T21:37:13Z

ScislaC: /* Live Path Effects */

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

==Inkscape 0.92==

'''(definitely not released yet - [[AnnouncePlanning092]])'''

==Release highlights==

Released on '''«YYYY-MM-DD»'''.

== Dialogs, etc. ==

=== Objects ===
Hierarchy of document

=== Selection Sets ===
Create selection sets that are not affected document structure

=== Live Path Effects ===
==== Chamfer/Fillet ====
==== Roughen ====
==== Simplify ====
==== Perspective Envelope ====
==== Lattice 2 ====

== Other user interface ==

Release notes/0.92

2014-10-30T20:31:01Z

ScislaC:

Release notes

2014-10-30T20:25:06Z

ScislaC:

Here are the release notes for all versions of Inkscape. The list of release notes ''in all languages'' is at [[Special:PrefixIndex/Release notes/]].

* [[Release notes/0.92]] (next major release)
* [[Release notes/0.91]] (upcoming major release)
* [[Release notes/0.48.5]] (current release)
* [[Release notes/0.48.4]]
* [[Release notes/0.48.3]]
* [[Release notes/0.48.2]]
* [[Release notes/0.48.1]]
* [[Release notes/0.48]]
* [[Release notes/0.47]]
* [[Release notes/0.46]]
* [[Release notes/0.45]]
* [[Release notes/0.44]]
* [[Release notes/0.43]]
* [[Release notes/0.42]]
* [[Release notes/0.41]]
* [[Release notes/0.40]]
* [[Release notes/0.39]]
* [[Release notes/0.38]]
* [[Release notes/0.37]]
* [[Release notes/0.36]]
* [[Release notes/0.35]]

[[Category:About Inkscape]]

Release notes/0.92

2014-10-30T20:24:08Z

ScislaC:

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

==Inkscape 0.92==

'''(definitely not released yet - [[AnnouncePlanning092]])'''

==Release highlights==

Released on '''«YYYY-MM-DD»'''.

Release notes/0.92

2014-10-30T20:23:57Z

ScislaC: Created page with "{{Other languages|en=Release_notes/0.91}} ==Inkscape 0.92== '''(definitely not released yet - AnnouncePlanning092)''' ==Release highlights== Released on '''«YYYY-MM-D..."

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

==Inkscape 0.92==

'''(definitely not released yet - [[AnnouncePlanning092]])'''

==Release highlights==

Released on '''«YYYY-MM-DD»'''.

Tracking Dependencies

2014-10-16T19:55:49Z

ScislaC: Update Utopic libs

== Overview ==

We need help getting our basic lib dependencies listed out and kept up to date. Also we need to track which versions of which distros have the needed dependencies.

To get glib and GTK+ dependencies figured out, people can go through the API documentation and look for the 'since' entries saying when calls were added. Then look for those calls in our source. Voila! we'll have base minimum dependencies figured out.

== Libs ==

C++ bindings are not included, since their required versions match those of the C counterparts.

{| class="wikitable"
|-
! Library
! v 0.48.5
! trunk
! trunk (GTK+ 3.0 build)
|-
| Boehm-GC
| >= 6.4
| 7.1
| 7.1
|-
| Cairo
| ?
| 1.10
| 1.10
|-
| GDL
| N/A
| N/A
| 3.3.4
|-
| Glib
| ''2.16*''
| 2.28
| 2.28
|-
| GTK+
| ''2.12*''
| 2.24
| 3.2
|-
| GNU Scientific Library
| ?
| ?
| ?
|-
| LittleCMS
| 1.13
| 1.13
| 1.13
|-
| libxml
| ''2.6.11*''
| ''2.6.11*''
| ''2.6.11*''
|-
| libxslt
| ''1.0.15*''
| ''1.0.15*''
| ''1.0.15*''
|-
| Pango
| ?
| ?
| 1.24
|-
| Poppler
| ''0.5.9*''
| ''0.5.9*''
| ''0.5.9*''
|-
| libsigc++
| ''2.0.12*''
| ''2.0.12*''
| ''2.0.12*''
|}

''* Tentative dependency''

== Distros ==

Note: This table is not relevant to (non-fink) MacOS X, where we ship the desired version with Inkscape.

{| class="wikitable"
|-
! Distro
! cairo
! cairomm
! glib
! glibmm
! gtk+
! gtkmm
! pango
! poppler
! gdl
! lcms
! libsigc++
! libgc 
|-
| style="background:Violet;"|Windows Devlibs (r46)
| 1.11.2
| 1.10.0
| 2.28.8
| 2.28.2
| style="background:Violet;"| 2.24.10
| style="background:Violet;"| 2.24.2
| 1.28.3
| 0.12.1
| style="background:Violet;"| (none)
| 1.17
| 2.2.11
| 7.1
|-
| Windows Devlibs Gtk+ 3 branch (r28)
| 1.10.2
| 1.10.0
| 2.38.0
| 2.36.0
| 2.24.18 3.8.1
| 2.24.2 3.8.0
| 1.34.0
| 0.22.5
| 3.4.2
| 1.19 2.4
| 2.2.10
| 7.2d
|-
| Debian 7.0 (Wheezy, stable)
| 1.12.2
| 1.10.0
| 2.33.12
| 2.32.1
| 2.24.10 3.4.2
| 2.24.2 3.4.2
| 1.32.5
| 0.18.4
| 3.4.2
| 1.19 2.2
| 2.2.10
| 7.1
|-
| Fedora 19
| 1.12.14
| 1.10.0
| 2.36.3
| 2.36.2
| 2.24.19 3.8.2
| 2.24.3 3.8.1
| 1.34.1
| 0.22.1
| 3.8.1
| 1.19 2.5
| 2.3.1
| 7.2d
|-
| Fedora 20
| 1.13.1+git
| 1.10.0
| 2.38.2
| 2.38.1
| 2.24.22 3.10.6
| 2.24.4 3.10.1
| 1.36.1
| 0.24.3
| 3.10.0
| 1.19 2.5
| 2.3.1
| 7.2d
|-
| OpenSuSE 12.3 EOL 2015-01-04[http://en.opensuse.org/Lifetime]
| 1.12.8
| 1.10.0
| 2.34.3
| 2.34.1
| 2.24.14 3.6.4
| 2.24.2 3.6.0
| 1.32.5
| 0.22.0
| 3.6.2
| 1.19 2.4
| 2.2.11
| 7.1.9.6
|-
| OpenSuSE 13.1 EOL 2015-05-01[http://en.opensuse.org/Lifetime]
| 1.12.16
| 1.10.0
| 2.38.1
| 2.38.0
| 2.24.22 3.10.2
| 2.24.4 3.10.0
| 1.36.0
| 0.24.3
| 3.10.0
| 1.19 2.5
| 2.3.1
| 7.2d
|-
| Ubuntu 12.04 LTS (Precise) EOL 2017-04
| 1.10.2
| 1.10.0
| 2.32.3
| 2.32.0
| 2.24.10 3.4.2
| 2.24.2 3.4.0
| 1.30.0
| 0.18.4
| 3.3.91
| 1.19 2.2
| 2.2.10
| 7.1
|-
| Ubuntu 14.04 (Trusty) EOL 2019-04
| 1.13.0
| 1.10.0
| 2.40.0
| 2.39.93
| 2.24.23 3.10.8
| 2.24.4 3.10.1
| 1.36.3
| 0.24.5
| 3.8.1
| 1.19 2.5
| 2.2.10
| 7.2d
|-
| Ubuntu 14.10 (Utopic) (As of 2014-10-16), EOL 2015-07
| 1.13.0
| 1.10.0
| 2.42.0
| 2.42.0
| 2.24.25 3.12.2
| 2.24.4 3.12.0
| 1.36.6
| 0.26.5
| 3.12.0
| 1.19 2.6
| 2.2.11
| 7.2d
|}

{| class="wikitable"
|-
! Legend
|-
| style="background:Red;"| Inkscape stable unsupported
|-
| style="background:Orange;"| Inkscape trunk unsupported
|-
| style="background:Violet;"| GTK+ 3 builds unsupported
|}

== Getting and Installing Source packages ==

If your distro does not have some packages available (like many don't, ie, Fedora Core 2), you must often download
source packages and build and install them yourself. Actually this is not that hard, and is similar to
doing a Gentoo 'emerge.'

* Usually you download a file with a name like somepackage-1.0.tar.gz. Unpack it with

$ tar zxf somepackage-1.0.tar.gz
or
$ tar jxf somepackage-1.0.tar.bz2

* Then 'cd' into the new directory.

* Configure it with the command:

$ ./configure

* Build it with:

$ make

* As the 'root' user, install it with:

# make install

=== Boehm-GC ===

Source: http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source

* Download this file:
** http://www.hpl.hp.com/personal/Hans_Boehm/gc/gc_source/gc6.8.tar.gz
* Unpack it
** tar zxf gc6.8.tar.gz
* Configure and build it
** cd gc6.8
** ./configure --disable-shared --enable-static
** make
* Install it
** su (or however else you become root)
** make install

Binaries: If searching for a package for GC, the name of it is sometimes:

* gc
* libgc
* gc-devel
* libgc-devel
* boehm-gc (on Gentoo)
* debian/ubuntu: sudo apt-get install libgc-dev

=== libSigc++ ===

Source: http://ftp.gnome.org/pub/GNOME/sources/libsigc++/2.2/libsigc++-2.2.3.tar.bz2

With this file, and for GlibMM and GtkMM below, it is usually desirable for us developers to
build this C++ library statically. This removes a dependency that might be difficult for an
end-user during installation. Configure it with:

./configure --enable-static --disable-shared

=== GlibMM ===
Try to match your Glib2 version with GlibMM's version. For example, if your Glib2 is 2.16.6, download glibmm-2.16.4.tar.bz2.

Latest source: http://ftp.gnome.org/pub/GNOME/sources/glibmm/

=== GtkMM ===
Usually you can try the latest version of GtkMM, but if you get version mismatch errors, try older releases.

Source: http://ftp.gnome.org/pub/GNOME/sources/gtkmm/2.12/gtkmm-2.12.7.tar.bz2

=== cairomm ===

if you got prompted about cairomm, try first solve your cairo version, so you can grab [http://www.cairographics.org/releases/ there] a compatible version.

=== Boost ===

Many users have reported when building from source that after installing the above dependencies, the configure script still requires a "boost" package. It can be found below, but even after installing, you will need to create a symlink to allow the configure script to find it:

ln -s /usr/local/include/boost_1_xx_x/boost /usr/local/include/boost

Source: http://www.boost.org/users/download/

=== Poppler ===

Source: http://poppler.freedesktop.org/

Poppler is required for PDF import. There are several potential issues:
* Some Linux distributions do not ship the Xpdf headers required by Inkscape. In such cases, you need to recompile Poppler, passing --enable-xpdf-headers on the configure line or install the libpoppler-private-dev package. See [https://bugs.launchpad.net/inkscape/+bug/254849 this wishlist bug]. This typically manifests in error messages like this:
<pre>In file included from extension/internal/pdfinput/svg-builder.cpp:19:
extension/internal/pdfinput/svg-builder.h:32:23: error: CharTypes.h: No such file or directory
...
make[2]: *** [extension/internal/pdfinput/svg-builder.o] Error 1
make[2]: Leaving directory `/tmp/build/inkscape-0.46/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/tmp/build/inkscape-0.46'
make: *** [all] Error 2</pre>
* Inkscape 0.47 does not compile with Poppler >= 0.12.2. If you need to compile Inkscape on such systems, use the development version from Bazaar, where this bug is fixed. See [https://bugs.launchpad.net/inkscape/+bug/487038 the bug report] for details and a minimal patch.
* Inkscape compiled with Poppler <= 0.12.1 will run on systems with Poppler >= 0.12.2, but the PDF import function will crash instantly. This problem does not concern Windows users, since the correct Poppler version is contained in the Windows installer package. This cannot be fixed on Inkscape's side: those two versions of Poppler are not ABI compatible, yet share the same soname. See [https://bugs.launchpad.net/inkscape/+bug/258504 this bug] for more details.
* Poppler's Xpdf headers are not guaranteed to be API-compatible between releases. It's likely that future Poppler versions will break PDF import in some way. PDF import works at least up to 0.12.4 but might not work with later versions.

[[Category:About Inkscape]]
[[Category:Developer Documentation]]