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.
0.91 will be a longer cycle focused on refactoring and new features.
Merge GSoC 2010 work
Evaluate changing the numbering scheme to a date-based one, or setting more realistic goals for major (1.0, 2.0) releases
Port renderer to Cairo (Krzysztof - GSoC 2010)
Completely remove libnr
Random Ideas / Requests / Needs
Note this list is unordered, unapproved, and unofficial. Feel free to add new ideas worth considering for the roadmap.
- 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.
- 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)
- 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 (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 (Doxygen not available online according to old wiki page but 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.
Using the above mechanism, make flowed text SVG-compliant.
- 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 (Mailing list thread from October 2014)
- Take a holistic approach to UI design (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.