Difference between revisions of "Roadmap"

From Inkscape Wiki
Jump to navigation Jump to search
Line 50: Line 50:
** SPItem, SPObject and other variables have names from the early versions of Sodipodi, these names no longer makes sense (especially for new developers).
** 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
* Drop Autotools support
* Migrate potrace to be an external dependency
* Create a test program for checking for some basic C++-11 capabilities.  We will add more to this as we go post 1.0.


=== Inkscape 0.94 ~ New Features Focus ===
=== Inkscape 0.94 ~ New Features Focus ===

Revision as of 21:10, 26 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

Following is a WIP draft of the 0.92 and future release goals; this is not yet finalized, and should not be taken as official yet

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
  • Migrate potrace to be an external dependency
  • Create a test program for checking for some basic C++-11 capabilities. We will add more to this as we go post 1.0.

Inkscape 0.94 ~ New Features Focus

  • Multi-page documents and parent/child document references
  • SVG Flowed Text
    • Fix flowtext
    • Implement SVG 2 flowed text which has a natural SVG 1.1 fallback.
  • Improve support for CMYK/spot colors
    • Minor UI streamlining
    • Eliminate the CMS tab
    • Change the CMYK tab to allow selecting the CMYK colors directly
    • Allow setting the document to CMYK, which sets a global CMYK profile
    • Stores RGB colors as RGB, CMYK colors as CMYK
  • Solicit community-contributed tutorial contributions

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
    • Switch to using Adaptagrams (libvpsc, libcola & libavoid) as a regular dependency (see https://bugs.launchpad.net/inkscape/+bug/1353833)
    • Break libdepixelize out to its own library
    • Break libnrtype out to its own library
    • Break libuemf out to its own library
  • Switch to using Poppler's API rather than using internals (the current situation causes regular breakage with new releases of Poppler)
  • GtkMMification
  • XML refactoring: Remove direct manipulation of XML from as many places as possible and replace it with SP tree methods.
  • Improved performance
    • Working with large files
    • Working with files with lots of filters

Inkscape 1.4 ~ Major Features

  • 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
Retrieved from "https://wiki.inkscape.org/wiki/index.php?title=Roadmap&oldid=96576"