Difference between revisions of "Roadmap"

From Inkscape Wiki
Jump to navigation Jump to search
Line 3: Line 3:
 
''See [[OldRoadmap]] for milestones that have already been achieved.''
 
''See [[OldRoadmap]] for milestones that have already been achieved.''
  
=== Inkscape 0.91 ===
+
=== Inkscape 0.91 ~ Refactoring ===
  
 
0.91 will be a longer cycle focused on refactoring and new features.
 
0.91 will be a longer cycle focused on refactoring and new features.
Line 13: Line 13:
  
 
=== Inkscape 0.92 ~ Infrastructure Focus ===
 
=== Inkscape 0.92 ~ Infrastructure Focus ===
* Build system: migrate away from Autotools, either to CMake or Waf
+
* <s>Set up autogeneration of Inkscape source code documentation ([http://wiki.inkscape.org/wiki/index.php/Doxygen_documentation Doxygen not available online according to old wiki page] but [http://fossies.org/dox/inkscape-0.91pre2/ available here (fossies.org)])</s> (http://jenkins.inkscape.org/job/Inkscape_trunk_doxygen/doxygen/)
 +
** <s>Put it publicly somewhere on the inkscape domain for "official" access.</s> (http://jenkins.inkscape.org/job/Inkscape_trunk_doxygen/doxygen/)
 +
* Build system: migrate away from Autotools
 +
** Decide between CMake and Waf
 +
** Get decided system working
 +
** Switch release tools to use new build system
 +
** Switch packaging tools to use new build system
 +
** Retain Autotools support one final release (legacy support), then drop next release.
 +
* Decide which Unit testing framework to use ([http://inkscape.13.x6.nabble.com/Unit-testing-td4967386.html Discussion July 2013 didn't get much traction])
 +
* Improved mailing list archive
 +
** Move existing archive to inkscape.org or add an archive mirror at inkscape.org ("official" inkscape information is spread out wide between different domains), this would be an improvement.
 +
** Consider also bringing lib2geom mailing lists?
 +
** inkscape: We need postmaster@inkscape.org and abuse@inkscape.org set up.  Maybe as part of a mailing list refresh?
 +
* Make the Windows uninstaller work (reevaluate this, we now have msi installer for win32 and Win64)
  
=== Inkscape 0.93 ~ Maintenance Focus ===
+
=== Inkscape 0.93 ~ Maintenance and Optimization Focus ===
 +
* Improved performance
 +
** with an empty start
 +
** when starting up with an existing file
 +
* Flip y-coordinate to match SVG.
 +
** Introduce a backwards compatibility mechanism that will allow us to modify the XML representation of editing info. This is needed to bring the desktop coordinate system in line with SVG due to guideline and 3D box problems (they save desktop coordinates in the XML). This can be done either at the SP tree level or by moving to a SAX-based parser which updates the editing information as the document is parsed.
 +
* 2geom maintenance
 +
** Clean up and move generally useful geometry code to 2Geom
 +
** Stop embedding 2Geom in Inkscape's codebase; handle it as a regular dependency
 +
** Possibly start doing lib2geom releases in conjunction with Inkscape's releases?
 +
* Split tutorials and other content from the main executable, to enable them to be updated independently of our main release process
 +
* Split out less well maintained extensions to an 'extras' package
 +
** Add a test suite that runs each extension against a collection of test documents
 +
** Possibly start doing inkscape-extras releases in conjunction with Inkscape's releases?
 +
* Refactor out "Sodipodi" history
 +
** SPItem, SPObject and other variables have names from the early versions of Sodipodi, these names no longer makes sense (especially for new developers).
 +
* Drop Autotools support
  
=== Inkscape 0.94 ~ Feature Focus ===
+
=== Inkscape 0.94 ~ New Features Focus ===
 +
* Multi-page documents and parent/child document references
 +
* SVG Flowed Text
 +
** Fix flowtext
 +
** Implement SVG 2 flowed text which has a natural SVG 1.1 fallback.
 +
* Improve support for CMYK/spot colors
 +
* Solicit community-contributed tutorial contributions
  
=== Inkscape 0.95 ~ Stability Focus ===
+
=== Inkscape 0.95 ~ Stabilization Focus ===
 +
* Update all core plugins to handle multi-page documents
 +
* Special focus on bugs relating to multi-page, flowed text, 2geom, and coordinate system flip
 +
* Introduce new tutorials
  
 
=== Inkscape 1.0 ~ Documentation Focus ===
 
=== Inkscape 1.0 ~ Documentation Focus ===
 +
* Review, update, and expand existing documentation
 +
** code documentation
 +
** tutorials
 +
** man page
 +
** kickoff manual effort?
 +
* Better translations - keep track of % translations for all languages.  Drive to 95% on all major languages.
 +
* Cleanup website and wiki
 +
** Move pages of value to users from wiki to the main website
 +
** Trim down amount of legacy material presented in the wiki
  
 +
=== Inkscape 1.1 ~ Refactoring ===
 +
* Adoption of C++11 features that will benefit Inkscape and are widely supported
 +
** http://en.cppreference.com/w/cpp/compiler_support
 +
* Take a holistic approach to UI design ([http://sourceforge.net/p/inkscape/mailman/message/33080043/ Original email])
 +
*# Analyze the existing UI, make a list of UI decisions that are inconsistent between each other.
 +
*# Look around, see how other project solves these things, figure out what's good/applicable for Inkscape (like designing particular custom widgets that are less pixel-hungry etc.).
 +
*# Design some sort of HIG (Human Interface Guidelines) for Inkscape
 +
*# Use it to plan redesigns existing dialogs/docks.
 +
*# Preserve dialog layouts between sessions
  
=== Milestone [Future] ===
+
=== Inkscape 1.2 ~ Infrastructure ===
 +
* Replace VCS
 +
* Greatly expand Unit test framework.
 +
* Consider setting up workflow (passing tests, test coverage, code review) for getting code into trunk.
 +
* make msi Windows install multilingual
  
 
+
=== Inkscape 1.3 ~ Maintenance and Optimization ===
=== 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
 
* Better modularization
 
** Switch to using libcroco as a regular dependency (not embedded in our codebase)
 
** Switch to using libcroco as a regular dependency (not embedded in our codebase)
Line 42: Line 96:
 
** Break libuemf out to its own library
 
** Break libuemf out to its own library
 
** Break libvpsc 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.
+
* Switch to using Poppler's API rather than using internals (the current situation causes regular breakage with new releases of Poppler)
 
* [[GtkMMification]]
 
* [[GtkMMification]]
 
* XML refactoring: Remove direct manipulation of XML from as many places as possible and replace it with SP tree methods.
 
* XML refactoring: Remove direct manipulation of XML from as many places as possible and replace it with SP tree methods.
* Refactor out "Sodipodi" history
+
* Improved performance
** SPItem, SPObject and other variables have names from the early versions of Sodipodi, these names no longer makes sense (especially for new developers).
+
** Working with large files
* Switch to using Poppler's API rather than using internals (the current situation causes regular breakage with new releases of Poppler)
+
** Working with files with lots of filters
* Split backend / GUI frontend
+
 
* Split out less well maintained extensions to an 'extras' package
+
=== Inkscape 1.4 ~ Major Features ===
 +
* New plugin / extension system
 +
** Easy to create
 +
** Powerful enough to do LPEs
 +
 
 +
=== Inkscape 1.5 ~ Stabilization ===
 +
 
 +
 
 +
 
 +
 
 +
=== Milestone [Future] ===
 +
 
 +
 
  
 
===== Infrastructure =====
 
===== 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.
 
* <s>Set up autogeneration of Inkscape source code documentation ([http://wiki.inkscape.org/wiki/index.php/Doxygen_documentation Doxygen not available online according to old wiki page] but [http://fossies.org/dox/inkscape-0.91pre2/ available here (fossies.org)])</s> (http://jenkins.inkscape.org/job/Inkscape_trunk_doxygen/doxygen/)
 
** <s>Put it publicly somewhere on the inkscape domain for "official" access.</s> (http://jenkins.inkscape.org/job/Inkscape_trunk_doxygen/doxygen/)
 
* 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.
 
* inkscape: We need postmaster@inkscape.org and abuse@inkscape.org set up.  Maybe as part of a mailing list refresh?
 
  
 +
 +
===== Maintenance =====
 +
* Split backend / GUI frontend
  
 
===== New features / Improvements to existing features =====
 
===== New features / Improvements to existing features =====
* Improve support for CMYK/spot colors
+
* <strike>Make flowed text SVG-compliant.</strike>
* Multi-page documents and parent/child document references
 
 
* [[SVG2]] support (with proper SVG 1.1 fallbacks)
 
* [[SVG2]] support (with proper SVG 1.1 fallbacks)
 
* Improve support for SVG switches: the first recognized element in a switch should appear directly in the SP tree, not as a child of the switch element.
 
* Improve support for 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.
 
* 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.
 
* 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.
 
* 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.
Line 88: Line 141:
 
* Evaluate pdf exporter to join features from scribus Export
 
* 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])
 
** 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.
 
*# Preserve dialog layouts between sessions
 
 
* For animation and css, a functionality to remove ALL transformations from an SVG
 
* For animation and css, a functionality to remove ALL transformations from an SVG
 
* PDF cleanup function - ungroup everything, remove all unnecessary clipping and masking
 
* PDF cleanup function - ungroup everything, remove all unnecessary clipping and masking
* Improved performance
 
** Start up empty
 
** Opening an existing file
 
** Working with large files
 
** Working with files with lots of filters
 
 
* Better marker support
 
* Better marker support
 
* Object navigator (like in ponyscape)
 
* Object navigator (like in ponyscape)
* New plugin / extension system
 
** Easy to create
 
** Powerful enough to do LPEs
 
 
* Inkscape for Android
 
* Inkscape for Android
 
* CAD drawing functionality
 
* CAD drawing functionality
Line 115: Line 154:
  
 
===== Documentation =====
 
===== Documentation =====
* Introduce new tutorials
 
* Split tutorials and other content from the main executable, to enable them to be updated independently of our main release process
 
* Better translations - keep track of % translations for all languages.  Drive to 95% on all major languages.
 
  
 
===== Community =====
 
===== Community =====
  
 
[[Category:Developer Documentation]]
 
[[Category:Developer Documentation]]

Revision as of 20:49, 8 April 2015

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

See OldRoadmap for milestones that have already been achieved.

Inkscape 0.91 ~ Refactoring

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

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

Inkscape 0.92 ~ Infrastructure Focus

Inkscape 0.93 ~ Maintenance and Optimization Focus

  • Improved performance
    • with an empty start
    • when starting up with an existing file
  • Flip y-coordinate to match SVG.
    • Introduce a backwards compatibility mechanism that will allow us to modify the XML representation of editing info. This is needed to bring the desktop coordinate system in line with SVG due to guideline and 3D box problems (they save desktop coordinates in the XML). This can be done either at the SP tree level or by moving to a SAX-based parser which updates the editing information as the document is parsed.
  • 2geom maintenance
    • Clean up and move generally useful geometry code to 2Geom
    • Stop embedding 2Geom in Inkscape's codebase; handle it as a regular dependency
    • Possibly start doing lib2geom releases in conjunction with Inkscape's releases?
  • Split tutorials and other content from the main executable, to enable them to be updated independently of our main release process
  • Split out less well maintained extensions to an 'extras' package
    • Add a test suite that runs each extension against a collection of test documents
    • Possibly start doing inkscape-extras releases in conjunction with Inkscape's releases?
  • Refactor out "Sodipodi" history
    • SPItem, SPObject and other variables have names from the early versions of Sodipodi, these names no longer makes sense (especially for new developers).
  • Drop Autotools support

Inkscape 0.94 ~ New Features Focus

  • Multi-page documents and parent/child document references
  • SVG Flowed Text
    • Fix flowtext
    • Implement SVG 2 flowed text which has a natural SVG 1.1 fallback.
  • Improve support for CMYK/spot colors
  • Solicit community-contributed tutorial contributions

Inkscape 0.95 ~ Stabilization Focus

  • Update all core plugins to handle multi-page documents
  • Special focus on bugs relating to multi-page, flowed text, 2geom, and coordinate system flip
  • Introduce new tutorials

Inkscape 1.0 ~ Documentation Focus

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

Inkscape 1.1 ~ Refactoring

  • Adoption of C++11 features that will benefit Inkscape and are widely supported
  • Take a holistic approach to UI design (Original email)
    1. Analyze the existing UI, make a list of UI decisions that are inconsistent between each other.
    2. 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.).
    3. Design some sort of HIG (Human Interface Guidelines) for Inkscape
    4. Use it to plan redesigns existing dialogs/docks.
    5. Preserve dialog layouts between sessions

Inkscape 1.2 ~ Infrastructure

  • Replace VCS
  • Greatly expand Unit test framework.
  • Consider setting up workflow (passing tests, test coverage, code review) for getting code into trunk.
  • make msi Windows install multilingual

Inkscape 1.3 ~ Maintenance and Optimization

  • 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
  • Switch to using Poppler's API rather than using internals (the current situation causes regular breakage with new releases of Poppler)
  • GtkMMification
  • XML refactoring: Remove direct manipulation of XML from as many places as possible and replace it with SP tree methods.
  • Improved performance
    • Working with large files
    • Working with files with lots of filters

Inkscape 1.4 ~ Major Features

  • New plugin / extension system
    • Easy to create
    • Powerful enough to do LPEs

Inkscape 1.5 ~ Stabilization

Milestone [Future]

Infrastructure
Maintenance
  • Split backend / GUI frontend
New features / Improvements to existing features
  • Make flowed text SVG-compliant.
  • SVG2 support (with proper SVG 1.1 fallbacks)
  • Improve support for SVG switches: the first recognized element in a switch should appear directly in the SP tree, not as a child of the switch element.
  • Improve support for changing the name of the XML element node in response to SP tree changes.
  • Hardware acceleration: make use of modern GPUs to speed up rendering.
  • Live path effects: investigate extending to cover generic vector transformations (vector effects). Provide live versions of several destructive operations: boolean ops, stroke to path, text to path, etc.
  • Mesh gradient support
  • CSS support
  • Javascript support
  • Animation support.
    • frame-by-frame interpolations?
    • SMIL?
    • Javascripts?
    • Something else?
  • D-Bus scripting API. (Merge GSoC work from 0.48 timeframe?)
  • Evaluate pdf exporter to join features from scribus Export
  • For animation and css, a functionality to remove ALL transformations from an SVG
  • PDF cleanup function - ungroup everything, remove all unnecessary clipping and masking
  • Better marker support
  • Object navigator (like in ponyscape)
  • Inkscape for Android
  • CAD drawing functionality
  • More file format import compatibility
    • TopDraw
  • OCR of bitmap traces
  • Rewrite / reintroduce 3D box.
    • 3-dimensional grid, perspective deformed, with snapping
Documentation
Community