Difference between revisions of "Projects"
(Removed cruft) |
|||
| (10 intermediate revisions by 3 users not shown) | |||
| Line 5: | Line 5: | ||
== General Codebase == | == General Codebase == | ||
=== Object Printing === | === Object Printing === | ||
| Line 27: | Line 14: | ||
Clean up all unnecessary castings in C++ classes. Remove unnecessary use of "this". Etc. | Clean up all unnecessary castings in C++ classes. Remove unnecessary use of "this". Etc. | ||
=== | === Rename s/SP/Ink/ === | ||
Various functions and variables have names from the early versions of Sodipodi, these names no longer makes sense (especially for new developers). Renaming s/SP/Ink/ would be ok if there aren't better ideas. This is most prevalent in the object tree, which may or may not be worth changing, but everything that is not part of the object tree should definitely be converted. | |||
=== Retire Garbage Collector === | |||
We use the Boehm garbage collector, but for smart pointers we can use | |||
support in C++-11 now, so most likely any Inkscape-specific gc code can | |||
probably go. Analyze where this code is, what uses it, and how to port | |||
it to use standard code, then delete our gc bits | |||
| Line 47: | Line 38: | ||
Inkscape update all references. It should also not be automatically | Inkscape update all references. It should also not be automatically | ||
created for all objects. Tav</span> | created for all objects. Tav</span> | ||
priority: Longer term | priority: Longer term | ||
| Line 69: | Line 51: | ||
priority: Longer term | priority: Longer term | ||
=== | === XML Refactoring === | ||
Remove direct manipulation of XML from as many places as possible and replace it with SP tree methods. | |||
== Interface == | == Interface == | ||
=== On-canvas tool controls === | === On-canvas tool controls === | ||
| Line 144: | Line 92: | ||
priority: Longer term | priority: Longer term | ||
== SVG Support == | == SVG Support == | ||
| Line 220: | Line 144: | ||
<span style="color:blue">Mesh gradients, hatches, etc. See [[SVG2|SVG2 page]]. Tav</span> | <span style="color:blue">Mesh gradients, hatches, etc. See [[SVG2|SVG2 page]]. Tav</span> | ||
* 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. | |||
== Paths == | == Paths == | ||
=== Boolean operations and stroking === | === Boolean operations and stroking === | ||
| Line 266: | Line 172: | ||
priority: Medium term term | priority: Medium term term | ||
== Fonts == | |||
=== | === variable fonts usability/UX === | ||
=== filters UI usability/UX === | |||
== Print == | == Print == | ||
| Line 288: | Line 188: | ||
what can or must be done in Inkscape itself. Outline project(s) to implement | what can or must be done in Inkscape itself. Outline project(s) to implement | ||
the needed changes. | the needed changes. | ||
See [[Color_management]] | See [[Color_management]] and [[Color Management Planning]] (which represents a head start into this task) | ||
* Improve support for CMYK/spot colors | * Improve support for CMYK/spot colors | ||
| Line 304: | Line 204: | ||
There are several distinct types of animation workflows and objectives, such as: | There are several distinct types of animation workflows and objectives, such as: | ||
* CSS animation - tweening/easing formulas for individual elements, aiming at e.g web display. | * CSS/SMIL animation - tweening/easing formulas for individual elements, aiming at e.g web display. | ||
* Sequential animation - each layer is a static frame that can be played back with a time delay, and recorded to a video stream | * Sequential animation - each layer is a static frame that can be played back with a time delay, and recorded to a video stream | ||
* Keyframe animation - layers represent points on a timeline with objects whose states change through some interpolation mechanism | * Keyframe animation - layers represent points on a timeline with objects whose states change through some interpolation mechanism | ||
* Javascript? | |||
While the intent, output, and UI for these may vary, the underlying machinery supporting them may have commonality, so the following projects may apply to one or more of the above types of animation. | While the intent, output, and UI for these may vary, the underlying machinery supporting them may have commonality, so the following projects may apply to one or more of the above types of animation. | ||
| Line 347: | Line 248: | ||
Review all the projects in this list. Cleanup grammar or phrasing to make the descriptions clearer. Expand on points that are vague. Add links to relevant bug reports, feature requests, blueprints, etc. Add "[Please fill in]" to items that need more information; identify particular questions needing addressed where possible. | Review all the projects in this list. Cleanup grammar or phrasing to make the descriptions clearer. Expand on points that are vague. Add links to relevant bug reports, feature requests, blueprints, etc. Add "[Please fill in]" to items that need more information; identify particular questions needing addressed where possible. | ||
=== Inkscape Widgets Doxygen === | === Inkscape Widgets Doxygen === | ||
| Line 364: | Line 261: | ||
Ensure all functions declared in header files have doxygen-compatible documentation. See items in [[Janitorial tasks]] for the style we're going for. All doxygen of the core Inkscape code (i.e. excluding 3rd party libraries included in src/*/) should have consistently written and formatted doxygen, which should include descriptions of input, output, and return parameters, identification of potential errors, a one-line brief statement and a more detailed explanation of the routine's purpose. | Ensure all functions declared in header files have doxygen-compatible documentation. See items in [[Janitorial tasks]] for the style we're going for. All doxygen of the core Inkscape code (i.e. excluding 3rd party libraries included in src/*/) should have consistently written and formatted doxygen, which should include descriptions of input, output, and return parameters, identification of potential errors, a one-line brief statement and a more detailed explanation of the routine's purpose. | ||
== Tutorials == | == User-facing documentation == | ||
=== Release Notes Improvement === | |||
Review the release notes for the next major Inkscape release. Update wording and phrasing to be more comprehensible for end users. Fill in missing items where possible. Create and add explanatory graphics (c.f as done in past release notes). Add Known Issues from the previous release that are still relevant. | |||
=== Tutorials === | |||
* Review existing tutorials and update as appropriate | |||
* Finish or remove unfinished tutorials | |||
* Solicit community-contributed tutorial contributions | * Solicit community-contributed tutorial contributions | ||
* Introduce new tutorials | * Introduce new tutorials | ||
=== Man page === | |||
* Update man page | |||
** transcribe the examples to the new command line structure | |||
* Add more helpful examples | |||
=== Manual === | |||
Create a comprehensive, community-owned Inkscape manual: As a first step, devise a plan for how / where it will be created / hosted, and how versioning is going to work. Define its structure, and a set of editing guidelines. Recruit writers and proofreaders. Write the documentation. Keep the documentation up-to-date with the released Inkscape versions (ongoing task). | |||
| Line 455: | Line 370: | ||
Do a query on bugs marked Incomplete with no response, and sort by age. All bugs older than 1 month with no reply can be closed as out of date. | Do a query on bugs marked Incomplete with no response, and sort by age. All bugs older than 1 month with no reply can be closed as out of date. | ||
=== [https://inkscape.org/en/projects/box-blur/ Box blur (FPRJ-001)] === | === [https://inkscape.org/en/projects/box-blur/ Box blur (FPRJ-001)] === | ||
| Line 508: | Line 387: | ||
contact: Tav | contact: Tav | ||
priority: Nearer term | priority: Nearer term | ||
=== Restore Ancient Change History === | |||
Inkscape's earliest development history is missing, with the first commit being "bzr r1" when we migrated to bzr. Prior history was in CVS and is missing. While not a huge priority, it would be nice to have this pre-bzr history resurrected and prepended to our git history. | |||
=== Rewrite / reintroduce 3D box === | |||
** 3-dimensional grid, perspective deformed, with snapping | |||
=== Git Integration === | |||
Due to the nature of SVG (text files), versioning might offer a really good way to effectively manage local historical changes even when inkscape is closed. [[https://git-scm.com/ Git]] is a popular versioning software, and is well known among open source contributors. I imagine a versioning system could be "enabled" through the user interface, and allow a user to tag "releases", branch copies if need be, and maintain a historical log of changes. Git could also have been a great way to maintain a branch of different versions of the svg file when the Inkscape project made the change of default dpi for old files recently. | |||
=== | |||
=== Other Misc. Ideas === | |||
* Improve support for changing the name of the XML element node in response to SP tree changes | |||
* Inkscape for Android | |||
* CAD drawing functionality | |||
* OCR of bitmap traces | |||
* Excentric radial gradients, see e.g. samples/orav.svg in the distribution. --bb | |||
= Finished Projects = | = Finished Projects = | ||
Latest revision as of 17:02, 31 August 2023
This page lists proposed ideas for projects to improve Inkscape. The original list is from Krzysztof Kosiński. Consider it a permanent work-in-progress "brainstorm" list and feel free to add your own comments and project proposals. None of these are "official" and have not been thoroughly reviewed/debated and so may or may not fit with actual development plans.
General Codebase
Object Printing
Replace the print functions in the SPxxx classes with a generic "Visitor" pattern and port the different export types (e.g. EMF, PDF, PS) to the new routines.
Janitorial Work
Clean up all unnecessary castings in C++ classes. Remove unnecessary use of "this". Etc.
Rename s/SP/Ink/
Various functions and variables have names from the early versions of Sodipodi, these names no longer makes sense (especially for new developers). Renaming s/SP/Ink/ would be ok if there aren't better ideas. This is most prevalent in the object tree, which may or may not be worth changing, but everything that is not part of the object tree should definitely be converted.
Retire Garbage Collector
We use the Boehm garbage collector, but for smart pointers we can use support in C++-11 now, so most likely any Inkscape-specific gc code can probably go. Analyze where this code is, what uses it, and how to port it to use standard code, then delete our gc bits
Object Tree
Robust ID handling refactoring
Currently ID clash resolution is implemented as a giant switch over object types, listing every possible dependency. Replace this with virtual methods on objects, which provide information on what each object refers to. Improve behavior when a dependency of an object is deleted, and when IDs are changed / deleted from the XML editor.
See id-class.cpp for specifics.
It should be possible to change ID and have Inkscape update all references. It should also not be automatically created for all objects. Tav
priority: Longer term
Typed XML tree
Improve XML tree so that it can store some attributes in parsed, binary form. The main target of this are the data URIs used to embed images, which could be stored as binary data only. This work should be done after completing task 3 (SAX parser), as this will make it easier.
priority: Longer term
XML Refactoring
Remove direct manipulation of XML from as many places as possible and replace it with SP tree methods.
Interface
On-canvas tool controls
More tool controls could be available on-canvas right by the object being edited. An example of this would be having some of the text tool controls available right by where text editing is happening akin to what GIMP provides.
priority: Longer term
Numeric input on the canvas
Right-clicking on nodes should bring up a numeric entry box which would allow you to specify its position numericaly. This could allow us to phase out some of the controls on the top bar. For dynamic offsets, the numeric entry would simply be the width of the offset
priority: Longer term
Unify document and desktop coordinates
Change the desktop coordinates to match document coordinates. Make it so that document coordinates are specified in the coordinate system of the toplevel SVG element, so that it is possible to emulate other coordinate systems using a suitable transform attribute or viewBox.
priority: Longer term
Shape manipulators
The idea here is to rewrite shape tools in the same paradigm as the node tool. Instead of storing all information about the shape in knots which differ only by their callbacks, allow to store information in a higher-level manipulator object. This would enable things like dragging the side of a rectangle and consistent outlining / update preferences for all shapes.
priority: Longer term
SVG Support
SVG-compliant flowed text (FPRJ-003)
Move the existing flowed text XML representation into an svg:switch and provide an alternative fallback representation with SVG 1.1 text objects only.
This should be done via SVG 2 CSS text wrapping which provides a simple SVG 1.1 fallback mechanism.
priority: Short term owner: Tav
Vector effects
Refactor live path effects so that their XML representation matches that of SVG 2.0 vector effects. Put them in switches, so that the output is not limited to a single path. Integrate them better with core Inkscape. For instance, instead of four actions: inset, outset, dynamic offset, linked offset, there should be only one: offset. Using it on a normal path would create a dynamic offset, while using it on a clone would create a linked offset. The same principle would apply to vector effects: creating them on a normal path would move the path to defs and replace it with the vector effect, while creating them on clones would delete the clone and create a reference to the original path.
Update: Vector effects will be dropped from SVG 2 but we can still refactor our own code to make it easier to use.
priority: Longer term
Better support for linked SVG images
Create the document and rendering tree for linked SVG images. Use Inkscape's renderer instead of relying on the librsvg loader to avoid inconsistencies. Allow importing the linked image as a group via the context menu.
There are two main conceptual ways of dealing with linked svg files, one is to treat svg files as 'bitmaps' using our own renderer to generate a bitmap and placing it inside much like we do with including outside png, jpeg files. This has implications involving exporting png with mismatched resolutions and pdf where text and vector elements are no longer vector in the output pdf.
The second method is to treat the svg as an advanced 'clone' which has it's own defs section. This would preserve the vector nature of the included svg file and allow rendering via pdf and png to happen without much exception. The implications of this have not been thought through completely.
priority: Medium term
SVG 2
Mesh gradients, hatches, etc. See SVG2 page. Tav
- 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.
Paths
Boolean operations and stroking
Add methods to PathVector objects:
a) Set operators (& | - ^), which perform the relevant boolean operation on the paths. Use the algorithm from CGAL or devise a new robust algorithm.
b) stroke(double line_width, LineJoin join, LineCap cap, double miter_limit), which performs the stroke-to-path operation.
c) stroke(double line_width, LineJoin join, LineCap cap, double miter_limit, std::vector<double> const &dasharray), which performs stroke-to-path with dashing.
priority: Longer term
Remove SPCurve (refactoring)
SPCurve is a thin wrapper around Geom::PathVector which exists for historical reasons. Its functionality should be added to PathVector, and SPCurve should be purged.
priority: Medium term term
Fonts
variable fonts usability/UX
filters UI usability/UX
Color Management
Analyze what users require for CMYK and other aspects of color management, including a review of what other software does, and what can currently be done with Inkscape. Examine off the shelf code that could be used (e.g. libcms). Define what needs implemented in Inkscape's dependencies (e.g. libcairo) vs. what can or must be done in Inkscape itself. Outline project(s) to implement the needed changes. See Color_management and Color Management Planning (which represents a head start into this task)
- 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
priority: short term
Animation
There are several distinct types of animation workflows and objectives, such as:
- CSS/SMIL animation - tweening/easing formulas for individual elements, aiming at e.g web display.
- Sequential animation - each layer is a static frame that can be played back with a time delay, and recorded to a video stream
- Keyframe animation - layers represent points on a timeline with objects whose states change through some interpolation mechanism
- Javascript?
While the intent, output, and UI for these may vary, the underlying machinery supporting them may have commonality, so the following projects may apply to one or more of the above types of animation.
Object interpolation display
Create routines to morph the properties and/or style of an object according to some proportion (such as elapsed time over a time period).
This will need modification of object structures to support the animation attributes, following the SMIL and CSS animation specifications.
contact: Tav priority: Medium term
Object animation property editor UI/UX design
Conceptualize how users would add and edit animation properties in Inkscape. What should be done in dialogs vs. in the main interface? Mockup ideas for how the UI could look. Describe the workflow the user would follow.
Time keyed layer display
Functionality to display/hide a list of layers in a fixed or variable sequence, or recorded to a sequential output format (e.g. a video output format or numbered raster images).
priority: Medium term
Frame transitions
Expand on the above projects by organizing objects in sequential layers, where the layers can mark either transition points for a given object, or an object that replaces one or more objects in an earlier frame.
priority: Longer term
CSS/SVG Web Animations
Export animation properties as corresponding CSS/SVG parameters to output files, following the model from the Web Animations specification so that both SMIL and CSS animations are supported. Inkscape Community/Tav
priority: Longer term
Technical Writing
Improve this Project List
Review all the projects in this list. Cleanup grammar or phrasing to make the descriptions clearer. Expand on points that are vague. Add links to relevant bug reports, feature requests, blueprints, etc. Add "[Please fill in]" to items that need more information; identify particular questions needing addressed where possible.
Inkscape Widgets Doxygen
Over the years Inkscape has collected a number of custom UI objects, which have been consolidated to src/widgets/. Many of these are un- or under-documented. For each widget, write doxygen comments in the header file explaining what the widget is and does, and document the widget's public API. In some cases there may be doxygen in the .cpp file for public API functions - this should move to the header.
Bring inkscape/doc up to date
The doc directory in the Inkscape codebase is used for high level technical documentation including architecture, codebase introduction, and new developer orientation, however it has not been very well maintained and much is obsolete or incorrect. It also needs to be reformatted into Markdown, and appropriate scripts created to generate it into HTML/PDF/SVG. There may be additional developer documentation in Wiki that would be worth inclusion here.
Code Doxygen Documentation
Ensure all functions declared in header files have doxygen-compatible documentation. See items in Janitorial tasks for the style we're going for. All doxygen of the core Inkscape code (i.e. excluding 3rd party libraries included in src/*/) should have consistently written and formatted doxygen, which should include descriptions of input, output, and return parameters, identification of potential errors, a one-line brief statement and a more detailed explanation of the routine's purpose.
User-facing documentation
Release Notes Improvement
Review the release notes for the next major Inkscape release. Update wording and phrasing to be more comprehensible for end users. Fill in missing items where possible. Create and add explanatory graphics (c.f as done in past release notes). Add Known Issues from the previous release that are still relevant.
Tutorials
- Review existing tutorials and update as appropriate
- Finish or remove unfinished tutorials
- Solicit community-contributed tutorial contributions
- Introduce new tutorials
Man page
- Update man page
- transcribe the examples to the new command line structure
- Add more helpful examples
Manual
Create a comprehensive, community-owned Inkscape manual: As a first step, devise a plan for how / where it will be created / hosted, and how versioning is going to work. Define its structure, and a set of editing guidelines. Recruit writers and proofreaders. Write the documentation. Keep the documentation up-to-date with the released Inkscape versions (ongoing task).
Packaging and Release Management
Library Package De-integration
Several 3rd party codebases are included in Inkscape's codebase (i.e., src/lib*/, src/2geom, possibly livarot?). This has convenience for local patching of our own improvements and simplifies the number of components platform packagers need to deal with, however this increases the weight of our codebase and makes our package larger on platforms such as Linux that have good dependency sharing. Arguably, it may also hinder collaboration with the upstreams or other users of the libraries. Certainly it makes it difficult to roll out fixes to one of those libraries to our users. So, we want these libraries to be packaged and released separately from Inkscape.
For each of these libraries, create a separate git repository in Inkscape's gitlab project for hosting our branch of that project's code. Make sure any of Inkscape's changes to it are clearly registered as distinct git commits. If there is an active upstream project maintaining that library, make sure each of our changes are registered in their patch or bug tracking systems.
In theory, Inkscape should only be using the libraries' public APIs; doublecheck that this is indeed the case, and identify any instances where Inkscape code is bypassing it and accessing library internals directly. These should be filed as high priority bugs in Inkscape's bug tracker.
Lastly, make sure that `make dist` passes successfully for each of our branched libraries, and generates a source tarball. Inform the Release Team of the need to start separately packaging and releasing these libraries in conjunction with Inkscape's release processes.
Bug Triage
With as many bugs as we've accumulated, working on them can seem daunting. Where to start!? Below are some encapsulated projects to try to achieve. Together, the more of these projects that are completed the less daunting the remaining work will be, and the better Inkscape will become!
The Bug management page in this wiki includes advice on how to judge bug status and importance levels.
Tip: Some of these tasks could be scripted and automated via the Launchpad email interface. See https://help.launchpad.net/BugTrackerEmailInterface
(100% Complete) Update Status for Critical Bugs from New
(DONE) Review each Critical bug with Status New, and change status to Incomplete if the last comment on the bug is a question, or Confirmed otherwise. -- Bryce
(100% Complete) Update Status for Critical Bugs from Fix Committed
Review each Critical bug with Status Fix Committed; most likely these are incorrect. If comments towards the end of the thread indicate a fix was committed to SVN, then it is okay to be in state Fix Committed. Otherwise, move it to a more accurate Status.
(100% Complete) Update Status for High Priority Bugs from Fix Committed
Review each High priority bug with Status Fix Committed; most likely these are incorrect. If comments towards the end of the thread indicate a fix was committed to SVN, then it is okay to be in state Fix Committed. Otherwise, move it to a more accurate Status.
Update Status for High Priority Bugs from New
Review each High priority bug with Status New, and change status to Incomplete if the last comment on the bug is a question, or Confirmed otherwise.
Tag OSX bugs
Using the Advanced search, identify bugs that are reported against OSX and update them to include the tag 'osx'.
Tag Windows bugs
Using the Advanced search, identify bugs that are reported against Windows and update them to include the tag 'windows'. Some bugs are already tagged with 'win32'
- Searched all entries with 'win' in it. Tagged all appropriate bug reports with 'win32'. Now only 'win32' tags exist, but no 'windows' tags. Renaming the tags via the database should be easier than doing it manually (if at all possible). Is this what you guys had in mind? --Cerno 15:40, 30 June 2008 (UTC)
Link Cairo bugs
Do a search for 'cairo'. Review the bugs (there's only about a dozen), and for each, identify if the issue is a Cairo bug. If so, look in the cairo bug tracker at freedesktop.org for a matching bug (or enter a new one if there isn't one already) and link it in via the 'Also affects: +Project'.
Set Importance on Confirmed / Fixed Bugs
Do a search on Importance=Undecided and Status=Fix Committed,Confirmed,In Progress. (There's 18 of these presently). Review each and assign it an Importance (probably Medium or High in most cases, but use best judgement).
Ping Old Low Priority Bugs
Search on bugs with Importance=Low, sorted by Oldest First. Go through the bugs that are more than a year old and review them. If they don't seem to have gotten much activity (e.g. few comments), and don't seem to be worth keeping, mark them Incomplete, with the following text:
"Thank you for taking the time to report this bug and helping to make Inkscape better. You reported this bug a long while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Can you try with latest Inkscape release? Thanks in advance."
or if it is a feature request: "Thank you for taking the time to report this feature request and helping to make Inkscape better. You requested this feature a long while ago and there hasn't been any activity in it recently. We were wondering; is this still on your wishlist? Can you try with latest Inkscape release and see if recent improvements have obsoleted your request? Thanks in advance."
Wait about a month, then follow up with a search against these bugs that have not received a response; they can then be closed as Invalid.
https://wiki.ubuntu.com/Bugs/Status
Confirm all appropriate bugs marked Incomplete with responses
Search on 'Incomplete with response', and review the feedback that's been given. If it appears the initial triager's information requests were met, and the bug seems legitimate, move it to Confirmed. If there seems to be further questions needing answered, ask them and leave it as incomplete.
As well, specify a priority for these bugs. Generally, issues that cause crashes or data loss are high priority unless they only occur in very narrow situations. Issues which are purely cosmetic or involve very obscure or limited conditions are low priority, and everything else is Medium. Only use Critical priority for extremely serious bugs that will be affecting most everyone using Inkscape.
Convert high priority wishlist bugs into blueprints
Browse the collection of bugs marked wishlist. Look for sets of related bugs that are all requesting essentially the same feature. Create a corresponding blueprint at https://blueprints.launchpad.net/inkscape, and use Specify a URL to attach it to a wiki page. Then consolidate the wishlist bug reports together onto the blueprint page. Specify if you're willing to act as the Drafter for the spec, and carry it through to acceptance, or if you prefer someone else take that role.
Once you've created the specification, use Link to bug to link each of the related bugs.
Close old incomplete bugs with no response
Do a query on bugs marked Incomplete with no response, and sort by age. All bugs older than 1 month with no reply can be closed as out of date.
Box blur (FPRJ-001)
Currently we always use a very accurate method to compute the Gaussian blur filter. Add an alternate method which approximates Gaussian blur using three stacked box blurs (simple averages). This is detailed in the SVG 1.1 SE specification.
Marker Knockout
Idea is to clean up markers where part of the line shows through. For example if a triangular arrowhead's tip is on the end point of a line with a relatively thick stroke, the rectangular end corners of the line shows up. Or if you're doing a mid-line marker that needs to have a transparent hole (e.g. a "subway station marker", it needs to show through.
To implement this, draw the line on another surface and mask it with the knockout shape. The filters code uses this approach, as an example. See also the SVG Markers specification.
contact: Tav priority: Nearer term
Restore Ancient Change History
Inkscape's earliest development history is missing, with the first commit being "bzr r1" when we migrated to bzr. Prior history was in CVS and is missing. While not a huge priority, it would be nice to have this pre-bzr history resurrected and prepended to our git history.
Rewrite / reintroduce 3D box
- 3-dimensional grid, perspective deformed, with snapping
Git Integration
Due to the nature of SVG (text files), versioning might offer a really good way to effectively manage local historical changes even when inkscape is closed. [Git] is a popular versioning software, and is well known among open source contributors. I imagine a versioning system could be "enabled" through the user interface, and allow a user to tag "releases", branch copies if need be, and maintain a historical log of changes. Git could also have been a great way to maintain a branch of different versions of the svg file when the Inkscape project made the change of default dpi for old files recently.
Other Misc. Ideas
- Improve support for changing the name of the XML element node in response to SP tree changes
- Inkscape for Android
- CAD drawing functionality
- OCR of bitmap traces
- Excentric radial gradients, see e.g. samples/orav.svg in the distribution. --bb
Finished Projects
[DONE] Remove all use of GList and GSList
These GLib data structures are poorly designed (they are simple lists without sentinels, leading to blunders such as O(N) performance when appending to a doubly-linked list) and not type-safe. Replace all uses with standard C++ containers or suitable Boost containers. </style>
[DONE] Common build system for all platforms
Migrate and port all necessary features to the CMake build system and remove Autotools.
[DONE] Use a different data structure for Inkscape::Selection
Inkscape::Selection currently uses GSList as its data structure. This is suboptimal, since a very common operation is checking whether some object is selected. Change Inkscape::Selection so that its underlying structure is a boost::multi_index container which implements the same semantics as Java's LinkedHashSet.
[DONE] Remove dom/ directory
This directory contains strange code which is barely used. The only class which is actually used is the URI class.