Inkscape Wiki - User contributions [en]

Adding interface verbs

2007-02-12T00:48:40Z

DavidHOzAu: /* How to Add a Verb */ +piped link too

=Introduction to Verbs=

Commands in Inkscape are called 'Verbs'. They permit invoking internal functionality through menus and keyboard shortcuts. For example, they could allow you to assign a shortcut key to a set of actions you use a lot.

Verbs are not terribly difficult to add. You don't need to have much coding know-how in order to add a verb, and only a minimal knowledge of Inkscape internals. The aim of this page is to provide novice coders with a "paint by numbers" process that can be followed to add a new verb to Inkscape.

=How to Add a Verb=

First, add IDs for your new verbs to verbs.h:

[http://svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/src/verbs.h?r1=13280&r2=13309&sortby=date verbs.h]

The place of the ID in the list determines to which group it belongs
(EditVerbs, FileVerbs, etc) - however, this is pretty arbitrary, so
don't sweat if you can't find a perfect group for your verb, just use
whichever makes most sense.

Then is the meat of the matter. In verbs.cpp, fill in the verb structure with the name,
description, action ID, etc; also in the same file, write the actual
commands that the verb will do, in a switch case in one of ::perform
methods:

[http://svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/src/verbs.cpp?r1=13281&r2=13311&sortby=date verbs.cpp]

As you see, these verbs do different things depending on which tool
you are in. Before verbification, this was coded into tool context
files, and now we can remove that:

[http://svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/src/node-context.cpp?r1=13296&r2=13309&sortby=date node-context.cpp]
[http://svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/src/select-context.cpp?r1=13200&r2=13309&sortby=date select-context.cpp]
[http://svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/src/draw-context.cpp?r1=13148&r2=13310&sortby=date draw-context.cpp]
[http://svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/src/draw-context.cpp?r1=13148&r2=13310&sortby=date draw-context.cpp]

(the last one required writing two functions that will be called by the
verb).

Now assign the keys to the newly created verbs:

[http://svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/share/keys/inkscape.xml?r1=13302&r2=13307&sortby=date inkscape.xml]

and then copy inkscape.xml to default.xml.

Note: even if you are not assigning any key, you MUST list the new
verb in inkscape.xml, using a <bind> without a key. Not only this file
is a keymap, but it's also a reference for keymap writers, so it must
have all verbs, assigned or not.

If you added a shortcut which didn't exist before, update also doc/keys.xml.

If you want the new verb in the menu, edit menus-skeleton.h and
insert it there in an appropriate place.

Also review the other keymaps to see if you can assign the new verb to
some key that would make sense. So in adobe-illustrator.xml, I
assigned the new verbs to Alt+Ctrl+[], which seems to be the same
thing according to the comments:

[http://svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/share/keys/adobe-illustrator-cs2.xml?r1=13304&r2=13308&sortby=date adobe-illustrator-cs2.xml]

Finally update the [[Release Notes|release notes]] with your new work! :-)

=Candidates for New Verbs=

A couple words on what might be good candidates for verbification:

* anything that all tools do but which is still not a verb, such as Esc for deselection

* anything that is needed for more complete keymaps emulating other editors, for example as listed [http://sourceforge.net/tracker/index.php?func=detail&aid=1532158&group_id=93438&atid=604309 in this bug report].
** the bug report requests includes various suggestions including: additional Zoom percentages; increase text, size and decrease text size; bold, italic, underline, text.
**See also the alternate keyboard shortcut layouts found in inkscape/share/keys/ which contain comments about missing features or verbs.

* any global action (i.e. which is not limited to some tool's context) for which it just makes sense to have a quick shortcut, even if it is already available via a dialog, a tool control, or some other more complicated way (example: centering selected objects; increasing/decreasing blur/opacity/stroke width in selection, etc.).

=Requests for New Verbs=

If the above sounds like something you're interested in doing, here is a listing of actions that have been requested, that we'll need verbs for.

* Align-middle-and-center: Need a shortcut key for aligning selected objects to their centers (horizontally and vertically). [https://sourceforge.net/mailarchive/message.php?msg_id=37258028]

If you'd like to see a verb added for a new action, but can't implement it yourself, you can add it to the above list.

Adding interface verbs

2007-02-12T00:48:01Z

DavidHOzAu: /* How to Add a Verb */ double redirect

=Introduction to Verbs=

Commands in Inkscape are called 'Verbs'. They permit invoking internal functionality through menus and keyboard shortcuts. For example, they could allow you to assign a shortcut key to a set of actions you use a lot.

Verbs are not terribly difficult to add. You don't need to have much coding know-how in order to add a verb, and only a minimal knowledge of Inkscape internals. The aim of this page is to provide novice coders with a "paint by numbers" process that can be followed to add a new verb to Inkscape.

=How to Add a Verb=

First, add IDs for your new verbs to verbs.h:

[http://svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/src/verbs.h?r1=13280&r2=13309&sortby=date verbs.h]

The place of the ID in the list determines to which group it belongs
(EditVerbs, FileVerbs, etc) - however, this is pretty arbitrary, so
don't sweat if you can't find a perfect group for your verb, just use
whichever makes most sense.

Then is the meat of the matter. In verbs.cpp, fill in the verb structure with the name,
description, action ID, etc; also in the same file, write the actual
commands that the verb will do, in a switch case in one of ::perform
methods:

[http://svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/src/verbs.cpp?r1=13281&r2=13311&sortby=date verbs.cpp]

As you see, these verbs do different things depending on which tool
you are in. Before verbification, this was coded into tool context
files, and now we can remove that:

[http://svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/src/node-context.cpp?r1=13296&r2=13309&sortby=date node-context.cpp]
[http://svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/src/select-context.cpp?r1=13200&r2=13309&sortby=date select-context.cpp]
[http://svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/src/draw-context.cpp?r1=13148&r2=13310&sortby=date draw-context.cpp]
[http://svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/src/draw-context.cpp?r1=13148&r2=13310&sortby=date draw-context.cpp]

(the last one required writing two functions that will be called by the
verb).

Now assign the keys to the newly created verbs:

[http://svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/share/keys/inkscape.xml?r1=13302&r2=13307&sortby=date inkscape.xml]

and then copy inkscape.xml to default.xml.

Note: even if you are not assigning any key, you MUST list the new
verb in inkscape.xml, using a <bind> without a key. Not only this file
is a keymap, but it's also a reference for keymap writers, so it must
have all verbs, assigned or not.

If you added a shortcut which didn't exist before, update also doc/keys.xml.

If you want the new verb in the menu, edit menus-skeleton.h and
insert it there in an appropriate place.

Also review the other keymaps to see if you can assign the new verb to
some key that would make sense. So in adobe-illustrator.xml, I
assigned the new verbs to Alt+Ctrl+[], which seems to be the same
thing according to the comments:

[http://svn.sourceforge.net/viewvc/inkscape/inkscape/trunk/share/keys/adobe-illustrator-cs2.xml?r1=13304&r2=13308&sortby=date adobe-illustrator-cs2.xml]

Finally update the [[release notes]] with your new work! :-)

=Candidates for New Verbs=

A couple words on what might be good candidates for verbification:

* anything that all tools do but which is still not a verb, such as Esc for deselection

* anything that is needed for more complete keymaps emulating other editors, for example as listed [http://sourceforge.net/tracker/index.php?func=detail&aid=1532158&group_id=93438&atid=604309 in this bug report].
** the bug report requests includes various suggestions including: additional Zoom percentages; increase text, size and decrease text size; bold, italic, underline, text.
**See also the alternate keyboard shortcut layouts found in inkscape/share/keys/ which contain comments about missing features or verbs.

* any global action (i.e. which is not limited to some tool's context) for which it just makes sense to have a quick shortcut, even if it is already available via a dialog, a tool control, or some other more complicated way (example: centering selected objects; increasing/decreasing blur/opacity/stroke width in selection, etc.).

=Requests for New Verbs=

If the above sounds like something you're interested in doing, here is a listing of actions that have been requested, that we'll need verbs for.

* Align-middle-and-center: Need a shortcut key for aligning selected objects to their centers (horizontally and vertically). [https://sourceforge.net/mailarchive/message.php?msg_id=37258028]

If you'd like to see a verb added for a new action, but can't implement it yourself, you can add it to the above list.

SodiPodi

2007-02-12T00:46:09Z

DavidHOzAu: /* Inkscape Sodipodi Comparison */ double redirect

=== Inkscape Sodipodi Comparison ===

Inkscape started as a fork of Sodipodi and Inkscape would not be where it is today without having had the base of Sodipodi to build on. As the two programs evolve it becomes increasingly useful to compare the two so that the developers of each can consider what features to copy from each other, and so that users can which program is useful for which drawing task or suits them best.

* Overall, Inkscape progresses faster and has more developers working on it. Inkscape's developer and user lists are currently more active.

* Sodipodi's renderer is noticeably faster, but less correct (often has artifacts with complex self-intersecting paths).

* Sodipodi's freehand tool is different from Inkscape's. Inkscape and Sodipodi have improved different aspects of the freehand tool since the fork. Sodipodi uses for the freehand tool an algorithm similar to that of the calligraphic tool, with parameters like drag and mass (not adjustable, however, as of 0.34); this makes the tool seem to adapt how closely the curve should match the mouse's path, whereas in Inkscape one must choose a fixed tolerance in advance.

:Situation as of Inkscape 0.40: Some people prefer the behavior of Sodipodi's freehand, while others prefer Inkscape. See [[FreehandComparison]] page for example screenshots from both categories of users. After 0.40, Inkscape CVS will experiment with incorporating sodipodi's improvements.

* For documentation, Inkscape has a detailed manpage, several big SVG tutorials and a complete shortcuts reference in SVG and HTML. The Sodipodi documentation is limited to a brief text-only shortcuts list and various web pages. (Some of Inkscape's documentation could be helpful for Sodipodi use too.)

* Inkscape fixed scores of bugs that Sodipodi has not yet fixed. Most applicable fixes from Sodipodi since the fork have been ported to Inkscape. On the other hand, the tons of new features in Inkscape undoubtedly introduced their own bugs. Inkscape employs a very intensive bug tracking process, that seems to help stabilize new features, though. Overall, people seem to agree that Inkscape is more robust and crashes less.

* Inkscape's package for Microsoft Windows is self-contained and easy to install. A single package makes things simpler and more convenient for testers and ordinary users.
: Sodipodi requires a separate installation of GTK libraries which although more complicated can be helpful if you wish to use less diskspace/bandwidth by sharing the same version of GTK (and settings) with other applictions GTK applications such as the GIMP, GAIM and more.
Inkscape may in future try to also provide this kind of split package but given how rapidly Inkscape changes the most up to date version of GTK is almost always required anyway. To save bandwith the file inkscape.exe has been offered to testers allowing them to avoid a full upgrade every time but it would not be recommended for ordinary users.

* Opinion is mixed as to which interface is better. Overall, most people seem to prefer Inkscape's use of a Single Document Interface (SDI) to the use of a Controlled Single Document Interface (CSDI) in Sodipodi where to the Toolbox is the main window and the panels are all in other seperate windows.

** Inkscape has tools and tool controls attached to each editing window as toolbars. This seeks to minimize the need for floating windows and makes the most important controls more predictably positioned and faster to reach. Sodipodi has one big floating toolbox shared by all document windows.

::Sodipodi's interface has been described as more [http://www.gimp.org/ GIMP]-like. Inkscape's interface, on the other hand, resembles some of the commercial vector applications, most notably [[Xara X]].

:: Users with dual-screen setups and complex Window manager software tend to be those most likely to prefer the Sodipodi style interface as it allows/requires them to organise everything themselves.

:: One disadvantage to Inkscape's approach is that toolbars may either be partially cut off when the editing window is too small, or prevent the window from getting as small as possible. Inkscape toolbars are, in theory, detachable, so they can be removed from the editing window and float freely as separate windows. In practice, however, this is hardly usable because GTK does not make such detached toolbars stay on top, so they sink to the bottom very soon and are rather cumbersome to dig up again, especially if you have many windows. Let's hope GTK will fix this one day. (Windows need to set the correct hint to let the window manager know they are utility windows, the proceeding point may already be out of date and the following comments seem to confirm it).

::Also, any Inkscape toolbar can be permanently hidden; you can easily make a "bare" window without any buttons, if you are willing to use keyboard shortcuts instead of toolbar buttons.

** Inkscape's dialogs by default stay on top of the currently active document window. Sodipodi's dialogs (including the toolbox) sink.
:: Not anymore, recent version of Sodipodi has the same "problem" as Inkscape - dialogs stay on top. --[[HandgranatSandra]]
:: Do they stay on top of all editing windows (as in Inkscape), or only over the original one from which they were called? --bb

** Inkscape remembers the size and position of dialogs across sessions, Sodipodi does not.

* Inkscape has a lead in usability:

** Inkscape has many more keyboard and mouse shortcuts (but arguably this is greater flexibility not necessarily better usability, and accidentally hitting the wrong keybinding can waste time). Compare [http://inkscape.org/doc/keys.html Inkscape list] and [http://www.sodipodi.com/index.php3?section=documentation/usage/keybindings Sodipodi list]. Inkscape has a unique focus on keyboard accessibility of basic editing operations (move, transform, z-order, etc.)

** Inkscape remembers the zoom and view and window geometry of saved files.

** Selecting objects in Inkscape is much easier (select in groups, select under, forced rubberband, settable drag and grab tolerances, canvas autoscrolls when you drag objects or do a rubberband selection).

** Consistent treatment of stroke width, patterns, and gradients, which are either transformed in sync with their objects or stay unchanged in transformation, depending on a user setting.

** Inkscape has many more statusbar tips, tooltips, and other runtime verbiage. The size of an average .po file (containing all the interface strings) of Inkscape is more than twice that of Sodipodi.

** In Inkscape Exporting to bitmap (PNG) repeatedly is much more convenient since the filename and resolution are remembered, selected objects only export, more command line export options.

** Inkscape has made many usability enhancements, too many to list here. See [[Release Notes|release notes]] for the past versions for a complete list.

* Features of Sodipodi not currently in Inkscape (possibly incomplete; please add if you know of others):

** The "Apply to duplicate" checkbox in the Transformations dialog. However, in Inkscape 0.41 most if not all effects achievable by this checkbox can be replicated using the Tile Clones dialog that creates clones (which can then be unlinked to become regular duplicates).

** The "Repeat" command to repeat the last command.

* Features in Inkscape but not currently in Sodipodi:

** Layers.

** Manual and automatic kerning and letterspacing in text.

** Text on path, flowed text.

** Editing of SVG markers (e.g. arrowheads). Sodipodi has only a limited display support for markers.

** Much more convenient on-canvas gradient editing.

** Creation and editing of clones (SVG <use> element). Sodipodi only has limited display support for <use>.

** Clone tiling (arranging multiple clones with various symmetries, shifts, rotations, randomization, etc).

** Creation and editing of pattern fills. Sodipodi has only display support.

** Editing multi-stop gradients. Sodipodi has only display support.

** Intergration with Potrace, for tracing bitmap images to vectors. Sodipodi users can only use Potrace from the command line.

** Inkscape uses Pango for text and therefore better supports right-to-left and other non-Western scripts.

** Inkscape has more import and export formats, although many of them rely on external applications and are not available on all platforms.

** Inkscape has a usable (but still unfinished) plugins and extensions support. Python extensions that are shipped with Inkscape do a lot of fun things.

** Inkscape shapes and shape tools have more options and controls.

** More path operations (Simplify, Cut path, Division).

** Offset (inset or outset) paths, including dynamic and linked offsets.

=== History ===

Inkscape forked from SodiPodi in late 2003. See [[InkscapeHistory]] for more information.

=== Screenshots ===

[http://www.sodipodi.com/index.php3?section=screenshots Sodipodi screenshots]

=== Links ===

[http://www.sodipodi.com/ Sodipodi Official site]

=== License ===

GNU General Public License (GPL)

PastMilestones

2007-02-12T00:42:55Z

DavidHOzAu: /* Inkscape 0.37 - Milestone 3 */ double redirect

== Past Milestones ==

=== Milestone 0 ===

Inkscape Production:
* (DONE) Post hydra-october patchset to Sodipodi mailing list [bryce]
* (DONE) Import sodipodi into inkscape CVS as module 'inkscape' from hydra-october [mental]
* (DONE) Unsodipodify the tree, replacing instances of 'Sodipodi' with 'Inkscape' where appropriate (we will be keeping the sodipodi XML namespace for compatibility) [mental]
* (DONE) Install inkscape 0.00 for personal use [bryce]
* (DONE) Install inkscape 0.00 for personal use [mental]
* (DONE) Install inkscape 0.00 for personal use [ted]
* (DONE) Install inkscape 0.00 for personal use [njh]
* (DONE) Decide what release number N to use (0.00? 0.33? 0.35? 1.00?) - we'll use 0.35

Inkscape Experimental
* (DONE) Decide name for Mental's sketch 'inkscape-experimental'? 'experimental'? 'inkscape-next-gen'? -- It shall be called 'experimental' [mental]
* (DONE) Import code into CVS [mental]
* (DONE) Document use of the experimental module [bryce]

Inkscape Website
* (DONE) Set up a Wiki [bryce]
* (DONE) Post sketchy website with homepage, contact info, news, and pointer to wiki [bryce]
* (DONE) Set up website to auto-rebuild every few minutes [bryce]
Milestone 1

Inkscape Production
* (DONE) Get inkscape to build with a C++ compiler [team]
* (DONE) Fix CDATA issue [mental]
* (DONE) Get codebase to successfully complete `make distcheck` -- mental says 'worksforme' [team]
* (DONE) Fix 'snap to guides' crash bug [bryce]
* (DONE) Update the about dialog to include the new logo and version [bryce, tvon]
* (DONE) Cut a release of Inkscape 0.35 [ted]
* (DONE) Upload release tarball of Inkscape 0.35 to Inkscape SF file manager [ted]

Inkscape Experimental
* (DONE) Initiate work on grid-proto code & put in CVS [njh]
* (DONE) Conceptualize a new export dialog in python [tvon, njh]

Inkscape Website & Project
* (DONE) Create logo for Inkscape [team]
* (DONE) Create look and feel graphical design prototype for website [tvon]
* (DONE) Create 3+ screenshots of Inkscape Production [bryce]
* (DONE) Flesh out website more fully [bryce]
* (DONE) [[SourceForge]] RFE section needs setting up (categories and groups) [bryce]
* (DONE) Create inkscape_project module & add wiki.pl there [bryce]

=== Inkscape 0.36 - Milestone 2 ===

Objective: Implement new features & do prep work for major changes in future

Inkscape Production
* (DONE) Create Freshmeat project for Inkscape [tgould]
* (DONE) Remove the KDE / Qt code and dependencies [manny]
* (DONE) Check all listed Sodipodi bugs numbered from 775385 to less than 830500, and copy recreatible ones to Inkscape's CVS tracker [bryce]
* (DONE) Check all listed Sodipodi bugs numbered from 830500 and up, and copy recreatible ones to Inkscape's CVS tracker [kidproto]
* (DONE) Check all listed Sodipodi bugs numbered less than 775385 and copy recreatible ones to Inkscape's CVS tracker [kidproto]
* (DONE) Copy open patches from Sodipodi patch tracker to Inkscape [bryce]
* (DONE) Implement preliminary support for doxygen or doc++ in the codebase [tgould]
* (DONE) Implement preliminary support for arrowheads on path ends [bryce]
* (DONE) Make SPGroup?s behave like layers if inkscape:groupmode is set to "layer" [mental]
* (DONE) Decide on URI namespace [mental, bryce] - http://www.inkscape.org/namespaces/inkscape
* (DONE) Implement an Inkscape namespaces [mental]
* (DONE) Eliminate all warnings in g++ build process on Linux [joncruz]
* (DONE) Incorporate bulk of patches posted to patch tracker [Kees]
* (DONE) Fix bug: on quit, still says I have unsaved changes, even though I saved
* (DONE) Fix bug: save as/save should use "SVG with xmlns:sodipodi namespace" as default [tgould]
* (DONE) Fix bug: files are sometimes erroneously saved without the extension namespaces (typically the first time) [tgould, mental]
* (DONE) Rename &q
1000
uot;SVG with xmlns:sodipodi namespace" to "SVG with extension namespaces" [mental]
* (DONE) Rewrite inkscape manpage [bryce]
* (DONE) Replace the doc/keybindings.txt file with one from Wiki [tgould]
* (DONE) Create & post tarball of 0.36 release [tgould]
* (DONE) Create RPM for 0.36 [bryce]
* (DONE) Create Deb package for 0.36 [njh]
* (DONE) Create Windows exe package for 0.36 [mael]
* (DONE) Post release to Freshmeat [tgould or bryce]
* (DONE) Send mentions to [[GnomeDesktop]]?, LWN, and other sites [kidproto=rejon]

Interface & usability
* (DONE) Merge BORKEN UI reorganization [mental]
* (DONE) Make all dialogs unsinkable, closeable (ctrl-f4, ctrl-w), defocusable (esc, enter in textfields) [bb]
* (DONE) Make all dialogs remember size and position across sessions [bb]
* (DONE) Unify names of commands and dialogs [bb]
* (DONE) Implement Tab, Esc, ctrl-a in node editor [bb]
* (DONE) Fix scrollwheel problem [kees]

Inkscape Experimental R&D
* (DONE) Describe what needs to be done to fix ambiguous default namespace issue [mental]
:We need to disambiguate between qnames that have no namespace and qnames in the default namespace (normally SVG's). Since internally we use a standard set of prefixes with qnames rather than expanded names, this means using e.g. "svg:g" and "svg:svg" instead of "g" and "svg" everywhere to name SVG elements. Note that namespaces are normalized to our standard prefix mappings at load time, so that does not itself constitute a compliance issue. -- [[MenTaLguY]]?
* (DONE) Select a regression test system strategy (I wrote a very minimal testing framework) [mental]
* (DONE) Build a prototype [[GridOptions]]? dialog using gtkmm [njh]
* (DONE) Prototype stroking/path enhancements [njh]
* (DONE) Start assembling list of requirements for plugin system [bryce]
* (DONE) Change Inkscape from 'CSDI' to 'SDI'. See [HIG Document Interface Types] [mental]

Inkscape Website & Project
* (DONE) Convert wiki to new look and feel [tvon]
* (DONE) Convert website to new look and feel [tvon]
* (DONE) Post project status [bryce]
* (DONE) See if it's possible to make wiki send edit notification to a mailing list & set it up if so [bryce]
* (DONE) Figure out how to get http://inkscape.org to work correctly [mental, kees]
* (DONE) Set up a 'project' cvs module for putting config files, backups, etc. [bryce]
* (DONE) Plan out Milestone 3 [bryce]

=== Inkscape 0.37 - Milestone 3 ===

Objective: Convert codebase to C++ and cleanup codebase

Inkscape Production
* (DONE) Fill in [[HandlingPreferences]] with a how-to on storing and using preference values
* (DONE) Create patch to add doxygen documentation for sp-root [bryce]
* (DONE) Create a class hierarchy diagram & add to website [mental & bryce]
* (DONE) Create a block diagram of the subsystems* Define C++ namespaces (e.g., 'Inkscape::$subsystem')
* (DONE) Ensure doc/ dir is included in source tarballs [mental]
* (DONE) Commit to C++ build; rename .c files to .cpp [mental & njh]
* (DONE) Investigate getting spsvgview building in C++
* (DONE) Increase precision in SVG, apply and test the 256x zoom patch [bb]
* (DONE) Investigate why events don't always get passed from dialogs to canvas - see [[EventContextGrab]]
* (DONE) Fix node editor's display update properly when the path is modified outside of the editor - see [[SelectionModifiedSignal]]
* (DONE) Consider using the release number for the milestone number [bryce + kidproto]
* (DONE) Go through all Sodipodi feature requests and programming tasks and copy ones worth doing into Inkscape's tracker, or create Wiki pages for those that require discussion [kidproto=rejon]
* (DONE) Implement Fullscreen mode menuitem [jceuppens]
* (DONE) Review #if 0 code and delete any that doesn't look like it's needed or document why, if it is
** (DONE) Review #if 0 code in bonobo/ [bryce]
** (DONE) Review #if 0 code in *-context.cpp files [johan]
** (DONE) Review #if
1000
0 code in desktop*.cpp and svg-view.cpp files [ted]
** (DONE) Review #if 0 code in sp-gradient.cpp, sp-root.cpp [njh]
** (DONE) Review #if 0 code in file.h, interface.cpp, geom.cpp, inkscape.cpp, and style.cpp [ishmal]
** (DONE) Review #if 0 code in *-chemistry.cpp [njh]
** (POSTPONED) Review #if 0 code in seltrans.cpp [pjrm]
** (DONE) Review #if 0 code in knotholder.cpp, nodepath.cpp, rubberband.cpp, object-edit.cpp, and object-ui.cpp [bb]
** (DONE) Review #if 0 code in svg/ [bryce]
** (DONE) Review #if 0 code in dialogs/ [bryce]
** (DONE) Review #if 0 code in display/ [mental]
** (DONE) Review #if 0 code in helper/ [bryce]
** (DONE) Review #if 0 code in libnr/
** (DONE) Review #if 0 code in libnrtype/ [rejon]
** (DONE) Review #if 0 code in modules/
** (DONE) Review #if 0 code in widgets/ [bryce]
** (DONE) Review #if 0 code in xml/
** (DONE) dialogs folder [rejon]
* (DONE) Revise HACKING file(s) [bryce]
* (DONE) Create new screenshots for website & Freshmeat [kidproto=rejon]
* (DONE) Port good code from Sodipodi 0.33 (including xml:space work) [bb]
* (DONE) Update coding-style.txt when the [[Coding_Style]] page is finalized [bryce]
* (DONE) Do a final proof-read / edit of [[Coding_Style]] to formalize it [bryce]
* (DONE) Move the contents of the [[Coding_Style]] page to CVS [bryce]
* (DONE) Announce finalized coding-style.txt to inkscape-devel@ list [bryce]
* (DONE for src/*) Remove NRPoint based code. [njh, pjrm]
* (DONE) Update NEWS with copy of [[Release Notes|Release notes]] when all development is finalized [rejon]
* (DONE) Create & post tarball of 0.37 release [tgould]
* (DONE) GPG sign the tarballs - md5sum is not secure enough [tgould]
* (DONE)Look at the spec files from KDE-Redhat for how to use %defines for different flavors of distros (it works better for different versions of same distro.. its gets ugly when mixing distros)
* (DONE)Grab spec file from fedora.us in the sodipodi package to set up Fedora packaging
* (DONE) Create Mandrake SRPM & RPM for 0.37 [bryce]
* (DONE) Create Deb package for 0.37 [njh]
* (DONE) Create Windows exe package for 0.37 [ishmal]
* (DONE) Post release to Freshmeat [tgould]
* (DONE) Upload debs to debian unstable
* (DONE) Upload rpm(s) to Mandrake Cooker [bryce]
* (DONE) rename old glade directories and make sure name change is reflected throughout code [rejon]

Interface & usability
* (DONE) Enable keyboard navigation within dialogs (tab switching, next widget, etc) [bb]
* (DONE) Make text fields in dialogs directly editable
* (DONE) Make all dialogs remember size and position across sessions [bb]
* (DONE, except skew) Consistently enable restricted rotate (with Ctrl) everywhere [bb]
* (DONE) Implement the global dialogs on/off toggle [bb]
* (DONE) Store more global things in preferences (nudge distance, mouse scroll distance, etc) [bb]
* (DONE) Decide on mouse scrollwheel modifiers [everyone, see mailing list archives]
* (DONE) Full keyboard control in node edit [bb]
* (DONE) Flesh out the [[SecondaryToolbar]], at least for selector [bb]
* (DONE) Add keyboard shortcuts reference and tutorial to the Help menu [bb]
* (DONE) Allow the user to edit the control points in the gradient editor [njh]

Inkscape Experimental:
* (DONE) Identify the remaining XML compliance bugs needing to be fixed & add to plan for M4[[/M5]] [mental]
* (DONE) Investigate feasibility of removing libarikkei and plan doing it [bryce]
* (DONE) Investigate replacement of libnrtype with Pango and plan doing it [bryce]

Inkscape Website & Project
* (DONE) Set up a logging for jabber
* (DONE) Set up hourly cronjob to rebuild code docs onto website [tvon]
* (DONE) Set up Google Search for inkscape.org [kidproto=rejon]
* (DONE) Set up automatically updated display of man page(s) onto Inkscape website [kidproto=rejon]
* (DONE) Initiate clipart effort [bryce]

=== Milestone 4 - Bug Hunt & Testing - Inkscape 0.38 ===

* (DONE) Port Inkscape to work with ebuild, the gentoo packaging/compiling system
* (DONE) Knock bug list count down to 10 or fewer, or to a ratio of 1
1000
0% open/total [all]
* (DONE) Implement text kerning and spacing (hor & vert), at least by keys [bb]
* (DONE) outline help system, possible strategies and available documentation for inclusion - use SVG! [bb]

=== Milestone 5 - Pango Architectural Change - Inkscape 0.39 ===

* (DONE) Develop GTKMM mockup/ideas for the Layers dialog [brisgeek, mental]
* (DONE) Consider trimming [[ChangeLog]]? (currently ~370 KB) [bryce]
* (DONE) Wiki site refactoring/cleanup - move old or less useful links off the top wiki page [bryce]
* (DONE) Review and revise [[TricksAndTips]] - can some of these move to the User Manual?
* (DONE) Reduce/eliminate debug messages that occur when doing e.g. node editing, etc.
* (DONE) Remove last bits of dependency on libart by copying what we need out of it, into libnr
* (DONE) Cleanup/reorganize Wiki homepage (too many links!) - perhaps move some into a PDF manual?
* (DONE) Finish moving tool options to 2ndary palette
** (DONE) move arc tool options to 2ndary palette (code in src/toolbox.cpp)
** (DONE) Remove tool options dialogue and code from project [bulia]
** (DONE) Fix Alt+X
* (DONE) Make window layout settable in View menu
* (DONE) Fix markers preview
* (DONE, unless I missed something) Fix all object-replacing commands to preserve ID
* (DONE) Fix svg:use support, create the Clone command [bb]
* (DONE) Add -V, --version commandline option to display application version & copyright info
* (DONE) Replace calls to arikkei string/tokenizing routines in libnrtype/ with standard glib functions & remove libarikkei
* (DONE) Expand the Preferences dialog (see [[HandlingPreferences]]) [bb]
* (DONE) Create [[SetStyleSignal]]? and make Dropper useful [bb]
* (DONE) Reorganize/trim down User Interface Discussion section of main wiki page [bryce]
* (DONE) Incorporate ECMA Javascript [ishmal]

Adopt Pango for handling fonts (http://inkscape.org/cgi-bin/wiki.pl?Pangoification)
* (DONE) Add Pango as an optional dependency for Inkscape & test on our various target platforms
* (DONE) Make Pango a required dependency for Inkscape & remove compile-time option scaffolding
* (DONE) Create a pango_test in the experimental CVS module [fred]
* (DONE) Test outlines using Pango [fred] - c.f. test_font->[[RasterFont]]?(one_mat,the_stroke_width)
* (DONE) Test vertical text using Pango with multi-glyph characters like an A with an umlaut [fred]
* (DONE) Document functions in libnrtype
* (DONE) Test out if letterspacing / kerning works with Pango [fred]
* (DONE) Reimplement the libnrtype routines in Pango terms [fred]
* (DONE) Go through the code looking for nrtype calls and replace them with direct calls to Pango
* (DONE) Eliminate need for the libnrtype API via direct calls whereever possible.

Holdovers from last release
* (DONE) Write an extensions/plugin enhancement proposal(s) and post to mailing list and [this wiki page] for review [bryce]
* (DONE, but needs fixing libnr display while dragging) Implement "scale stroke" switch

Publicity & Networking
* (DONE) Write an article about the project to various websites [bryce]
* (DONE) Try to get a mention on LWN

Website Revision
* (DONE) Find & move pages out of the wiki that should really be in the main website

* (DONE) Archive obsolete pages in the Inkscape wiki
* (DONE) Consider refactoring for the main Inkscape website

* (DONE) Trim down the number of links on the main wiki page to be much fewer

=== Milestone 6 - Features and Fixes - Inkscape 0.40 ===

New[[/Changed]]? Dependencies
* (DONE) Add a dependency on libgc (the Boehm conservative collector), which will be required for the AST code [mental]
* (DONE) Switch to sigc++ 2 + gtkmm 2 early in 0.40, before we start doing gtkmm-intensive stuff like the layers dialog etc. [mental]
* (DONE) Add Gtk-Wimp (for windows theming)
* (DONE) Use new file dialog when GTK 2.4 is released (but need to smooth out)

Internal
* (DONE) Create new gtkmm classes Inkscape::Dialog, Inkscape::Application, and some widgets [bryce]
* (DONE) Auto-include AUTHO
c93
RS list into manpage on build [pjrm]
* (DONE) Set up automatic insertion of current application version into Inkscape man page [pjrm]
* (DONE) Change the SEGV and SIGABRT handlers to reliably autosave and put up a crash dialog
* (DONE) add support for inkscape:label attribute for author-readable object names [mental]
** (DONE) add SPObject::defaultLabel() to return a default label string if inkscape:label is unset [bryce]
* (DONE) Implement SPItem::{locked,setLocked,visible,setVisible} [bryce]
* (DONE) Implement SPDesktop::item[[IsHidden]]?(SPItem *) for getting per-desktop visibility [mental]

Drawing
* (DONE) Implement Text on Path
* (DONE) Smoother freehand pencil tool [pjrm]
* (DONE) Make gradient management & chaining work similar to patterns [bb]
** (DONE) Fix fill-opacity ignored with gradients [bb]
* (DONE except bug #1061934) add support for visibility CSS property [mental]

Interface & Usability
* (DONE) Make all knots display explanations in statusbar on mouseover
* (DONE) Implement "Select Under" [bb]
* (DONE) Add shortcuts to button tooltips (at least for verbs)
* (DONE) Basic metadata[[/RDF]] support for clipart, etc.
* (DONE) Rudimentary layers UI
** (DONE) Finish new gtkmm layer selector [mental]
*** (DONE) Update list upon addition/removal/reordering of layers [mental]
*** (DONE) Finish show/hide lock/unlock buttons [mental]
*** (DONE) Add UI for setting inkscape:label attribute [bryce]
*** (DONE) Fix funky widget resizing [bryce]
*** (DONE) unselect objects when manually switching layers [mental]
** (DONE) Tie off loose ends with layer-related commands [mental]
*** (DONE) Add "selection to sublayer" command and its inverse [mental, bb]
*** (DONE) Make "move to next/prev layer" move selected objects to next/prev layer [mental, bb]
* (DONE) UI support for visibility
** (DONE) Implement and enable "visible" checkbox in object properties (using SPObject::{visible,setVisible} [bryce]
** (DONE) Make "intelligent" raise/lower aware of visibility status (using per-desktop SPDesktop::item[[IsHidden]]?) [bb]
** (DONE) Make selection tool and tests for item-at-point aware of per-desktop visibility [bb]
* (DONE) object label support
** (DONE) add ability to set inkscape:label from "Item Properties" [bryce]

** (DONE) remove id setting from "Item Properties"? [bryce]
** (DONE) switch to using SPObject::label()[[/SPObject]]?::defaultLabel() in UI where object ID is currently used [bryce]
* (DONE) add (preliminary) support for "title" and "desc" elements to "Item Properties"

Documentation & Packaging

* (DONE) Split tutorials into even smaller pieces, document new stuff since 0.38
** (DONE) shrink and subdivide Elements and Principles of Design (made smaller) [rejon]
** (DONE) Create a new tutorial (Shapes) [bulia]
* (DONE) Push for new dependencies to be updated upstream [all]

=== Milestone 7 - Bugfix Release - Inkscape 0.41 ===

* (DONE) Experiment with use of Glade for inkscape_gtkmm
* (DONE) Fix 150 "points" worth of bugs
* (DONE) PR and Release announcement sent out [rejon + bryce]

=== Milestone 8 - [[GtkMM]] Architectural Change - Inkscape 0.42 ===

General Gtkmm Interface
* (DONE) Merge the inkscape_gtkmm codebase into mainline with cmdline option to activate it [bryce]
* (DONE) Implement text in shape UI
* (DONE) Selection and node tools: double-click on group sets group as current layer (without altering inkscape:groupmode) [bb]

Icons and Cursors
* (DONE) Implement basic icon theming capability
* (DONE) Convert all xmp icons to svg's
* (DONE) Create one alternate icon/cursor set

Dialogs Redevelopment and improved HIG-Compliance
* (DONE) Fill Stroke dialog
** (DONE) Overhaul Gradient UI to improve management and creation
* (DONE) Align and Distribute Dialog - Convert to Gtkmm
* (DONE) Trace Dialog - Convert to Gtkmm
* (DONE) Transformation Dialog - Convert to Gtkmm
* (DONE) Object Properties dialog
** (DONE) Redesign Object Properties dialog
* (DONE) Create a swatches dialog

Layer Enhancements
* (DONE) search checks inkscape:label, and ignores layers [bb]
* (DONE) Move to Layer Above Shift + Page Up
* (DONE) Move to Layer Below Shift + Page Down

Extensions Prep Work
* (DONE) Example extension package

Other
* (DONE) Clean up tool ("event context") code

=== Milestone 9 - RFE's - Inkscape 0.43 ===

New/changed Dependencies
* (DONE) Add libcroco
* (DONE) Add dependencies for Whiteboard and other Google [[SoC]] projects

Internal
* (DONE) Reduce open/total RFE ratio to 55%
* (DONE) Bidirectional text in Pango needs attention
* (DONE) [[MakeVertical]] in Pango needs attention
* (DONE) Integrate use of libcroco for handling Cascading Style Sheets.

RFE's
* (DONE) tools: add/remove points on path, bezier drag
* (DONE) Markers
* (DONE) Load-from-URL [bryce]

Dialogs
* (DONE) Redevelop About screen [kees]
** (DONE) break out the credited developers, translators, and testers [kees]
** (DONE) investigate use of Gtk About [kees]

Testing
* (DONE) Implement tests of Inkscape against the [[W3C]] test suite [rick beton, bryce]
* (DONE) Host a Bug Party [nicu, bryce]

=== Milestone 10 ===

fill in from [[Roadmap]] page

Help wanted

2007-02-12T00:41:51Z

DavidHOzAu: /* Inkscape Promotion */ double redirect

== Help Wanted ==

This page lists easy, entry-level type tasks where help is needed.
These tasks focus on non-coding, or light-coding activities that are
desperately needed right now.

If you complete one of these tasks, please mark it (DONE) with your
name (so we know who to give thanks to!) If you discover other tasks
that you think others could do, please list them here.

=== Inkscape Planning ===

One of Inkscape's secrets to success is that we plan our work out, track tasks carefully, and work to keep all the todo lists trim and under control. Obviously, no coding experience is needed here. You'll need to have an eye for order, and it helps to know a bit about what's going on with Inkscape development but that isn't required.

* Update the Inkscape [[Roadmap]] - Compare what's listed there with what's been recently added to the [[Release Notes|release notes]], and to recently closed Feature Requests and Bugs in the Inkscape Tracker. Mark things done in the roadmap as appropriate (and indicate who did them).
* Find more tasks to add to [[HelpWanted]]
* [[UpdatingTrackerItems|Update Tracker Items]] - See that page for details. Inkscape prides itself in keeping good track of bugs, features, and patches. No coding ability is required. This is an excellent way to help keep Inkscape chugging along. In particular:
** The low priority bugs (level 3) should be reviewed. Some may be fixed by now, others may be out of date or irrelevant.
** Try recreating the new bugs (those at level 5). Add a comment whether you can or cannot recreate them.
** Search for duplicate or redundant feature requests, and mark the dupes.
* Go through [[NewFeatureProposals]] and pull in ideas from the Feature Request task tracker. Add more details (be creative!) to expand and unify the ideas. Sketch out some mockups if you so desire. Add a comment to the Feature Request with a pointer to the wiki page that discusses it.

=== Wiki Updating ===

The inkscape wiki is always in need of editing and maintenance. Inkscape depends on its community (that's you!) to keep the wiki organized and useful.

Items in need of updating:
* Ensure the formatting of different wiki pages is consistent. Make sure each page has a title, uses wiki syntax, etc.
* Search for spam. Easy, take a look at [[Special:Recentchanges|Recent Changes]], review what people have posted, delete any spam.
* Remove useless pages. There's a bit too many links on the main wiki page, so trimming will help reduce the clutter. Move pages to [[WikiAttic]] or move their contents into more useful sections.
** [[InkscapePopularity]] - appears abandoned and unfinished - maybe combine with another page?
** [[Free Desktop Graphic Suite]] - seems abandoned and unfinished
** [[AccessibleGraphics]]
** [[ModalInterfaces]] - maybe fold the basic ideas into [[DeveloperManual]]?
** [[TextUsability]] - maybe should be moved into the [[Roadmap]]?
** [[KeyboardShortcuts]] / [[KeyboardShortcutsToDo]] / [[KeyboardProfiles]] - maybe combine all of these? Docco seems to have been moved elsewhere
* Create a nicely laid out Inkscape Developer Wiki area
** Move the items that are extremely specific to Inkscape development into it. Don't move everything in the Developer Documentation section, though, as some of that is useful to users that are simply trying to troubleshoot problems. Items to move:
*** [[DeveloperManual]]
*** [[WorkingWithCVS]]
*** [[HandlingPreferences]]
*** [[AddSPObject]]
*** [[ReprListeners]]
*** [[InkscapeJanitors]]
*** Coding Style Discussion
*** [[FileTypes]]
*** Icons
*** [[InkscapeColor]]
*** [[PrintingSubsystem]]
*** SVG Tiny Compliance
*** CSS Support
*** [[TranslationInformation]]
*** [[ObjectManager]]
*** [[DialogsReorganization]]
*** Statusbar API
*** [[SubsystemRearchitecture]]
*** [[GtkMMification]]
*** [[PathRepresentaiton]]
*** Cairoification
*** [[ScribusInteroperability]]
*** Animation-(Timeline)
*** [[NewFeatureProposals]]
*** [[ExtensionArchitectureProposals]]
** Distinguish between development ideas/proposals, plans/specs, and documentation/techniques
** Add other useful links for reference documentation on topics of relevance to Inkscape development
*** [[OpenVG]]
*** [[OpenDocument]]
* Flesh out the [[DeveloperManual]] - we want to expand this into something that will provide a useful reference for new (and old!) developers.
** Pull in [[ErrorsAndWarnings]], [[DebuggingTips]], [[HandlingPreferences]], [[AddSPObject]], [[ReprListeners]]
** Look through other wiki pages for docs that really should be included in the [[DeveloperManual]] and move them there.
** Browse through the Inkscape-devel mailing list for development tips/tricks/suggestions to add
** Draw some diagrams or relevant pictures to include in the manual, to help break things up
** Create a Table of Contents
** Review and update the docs to more accurately match the state of the codebase
** Skim through the inkscape codebase for comments worth adding to the [[DeveloperManual]]

Completed items: (historical record)
* Merge [[ApplicationIcons]] and [[Icons]]. Also looks like these need editing and update in general. Merge Done --[[User:GigaClon|GigaClon]] 09:35, 21 June 2006 (PDT)
* Remove useless pages. There's a bit too many links on the main wiki page, so trimming will help reduce the clutter. Move pages to [[WikiAttic]] or move their contents into more useful sections.
** [[CPlusPlus]] / [[Pangoification]] - these are both done, the pages aren't really useful anymore. Done --[[User:GigaClon|GigaClon]] 07:45, 18 June 2006 (PDT)

=== Inkscape Promotion ===

Believe it or not, there are still people in the world who don't know about Inkscape. Your job is to fix this! Here are some ideas for helping to spread the word about Inkscape:

* Update [[InkscapeFeatures]] - Review recent changes to [[Release Notes|Release notes]] and make sure [[InkscapeFeatures]] capture all the major features we've got.
* Contact magazine publishers and ask that they include Inkscape coverage and/or copies of Inkscape in their magazine CD's

=== Inkscape Documentation ===

Inkscape users love having new tutorials, guides, and references.

* Help author, edit, translate, and review tutorials
* Join the Inkscape Manual team. This aims to compile a complete reference, so if writing Wikipedia articles appeals to you, you'll love this!
* Write more content for the website or wiki
* Get articles published about Inkscape on FootNotes, DeviantArt, FreshMeat, or other community sites

=== Making Screenshots ===

For a user, screenshots are perhaps the most important resource at inkscape.org. It's what most people look at first: they want pretty pictures.

Please see the [[MakingScreenshots]] page for fuller explanation of this topic and instructions on how to make screenshots and submit them to the [http://inkscape.org/screenshots/index.php gallery].

=== Inkscape Janitors ===

If you can code (even if you're new to coding), check out [[InkscapeJanitors]] for specific coding requests. Code it up, create a patch, and upload it to the patch tracker. Easy!

Help wanted

2007-02-12T00:40:59Z

DavidHOzAu: double redirect

== Help Wanted ==

This page lists easy, entry-level type tasks where help is needed.
These tasks focus on non-coding, or light-coding activities that are
desperately needed right now.

If you complete one of these tasks, please mark it (DONE) with your
name (so we know who to give thanks to!) If you discover other tasks
that you think others could do, please list them here.

=== Inkscape Planning ===

One of Inkscape's secrets to success is that we plan our work out, track tasks carefully, and work to keep all the todo lists trim and under control. Obviously, no coding experience is needed here. You'll need to have an eye for order, and it helps to know a bit about what's going on with Inkscape development but that isn't required.

* Update the Inkscape [[Roadmap]] - Compare what's listed there with what's been recently added to the [[Release Notes|release notes]], and to recently closed Feature Requests and Bugs in the Inkscape Tracker. Mark things done in the roadmap as appropriate (and indicate who did them).
* Find more tasks to add to [[HelpWanted]]
* [[UpdatingTrackerItems|Update Tracker Items]] - See that page for details. Inkscape prides itself in keeping good track of bugs, features, and patches. No coding ability is required. This is an excellent way to help keep Inkscape chugging along. In particular:
** The low priority bugs (level 3) should be reviewed. Some may be fixed by now, others may be out of date or irrelevant.
** Try recreating the new bugs (those at level 5). Add a comment whether you can or cannot recreate them.
** Search for duplicate or redundant feature requests, and mark the dupes.
* Go through [[NewFeatureProposals]] and pull in ideas from the Feature Request task tracker. Add more details (be creative!) to expand and unify the ideas. Sketch out some mockups if you so desire. Add a comment to the Feature Request with a pointer to the wiki page that discusses it.

=== Wiki Updating ===

The inkscape wiki is always in need of editing and maintenance. Inkscape depends on its community (that's you!) to keep the wiki organized and useful.

Items in need of updating:
* Ensure the formatting of different wiki pages is consistent. Make sure each page has a title, uses wiki syntax, etc.
* Search for spam. Easy, take a look at [[Special:Recentchanges|Recent Changes]], review what people have posted, delete any spam.
* Remove useless pages. There's a bit too many links on the main wiki page, so trimming will help reduce the clutter. Move pages to [[WikiAttic]] or move their contents into more useful sections.
** [[InkscapePopularity]] - appears abandoned and unfinished - maybe combine with another page?
** [[Free Desktop Graphic Suite]] - seems abandoned and unfinished
** [[AccessibleGraphics]]
** [[ModalInterfaces]] - maybe fold the basic ideas into [[DeveloperManual]]?
** [[TextUsability]] - maybe should be moved into the [[Roadmap]]?
** [[KeyboardShortcuts]] / [[KeyboardShortcutsToDo]] / [[KeyboardProfiles]] - maybe combine all of these? Docco seems to have been moved elsewhere
* Create a nicely laid out Inkscape Developer Wiki area
** Move the items that are extremely specific to Inkscape development into it. Don't move everything in the Developer Documentation section, though, as some of that is useful to users that are simply trying to troubleshoot problems. Items to move:
*** [[DeveloperManual]]
*** [[WorkingWithCVS]]
*** [[HandlingPreferences]]
*** [[AddSPObject]]
*** [[ReprListeners]]
*** [[InkscapeJanitors]]
*** Coding Style Discussion
*** [[FileTypes]]
*** Icons
*** [[InkscapeColor]]
*** [[PrintingSubsystem]]
*** SVG Tiny Compliance
*** CSS Support
*** [[TranslationInformation]]
*** [[ObjectManager]]
*** [[DialogsReorganization]]
*** Statusbar API
*** [[SubsystemRearchitecture]]
*** [[GtkMMification]]
*** [[PathRepresentaiton]]
*** Cairoification
*** [[ScribusInteroperability]]
*** Animation-(Timeline)
*** [[NewFeatureProposals]]
*** [[ExtensionArchitectureProposals]]
** Distinguish between development ideas/proposals, plans/specs, and documentation/techniques
** Add other useful links for reference documentation on topics of relevance to Inkscape development
*** [[OpenVG]]
*** [[OpenDocument]]
* Flesh out the [[DeveloperManual]] - we want to expand this into something that will provide a useful reference for new (and old!) developers.
** Pull in [[ErrorsAndWarnings]], [[DebuggingTips]], [[HandlingPreferences]], [[AddSPObject]], [[ReprListeners]]
** Look through other wiki pages for docs that really should be included in the [[DeveloperManual]] and move them there.
** Browse through the Inkscape-devel mailing list for development tips/tricks/suggestions to add
** Draw some diagrams or relevant pictures to include in the manual, to help break things up
** Create a Table of Contents
** Review and update the docs to more accurately match the state of the codebase
** Skim through the inkscape codebase for comments worth adding to the [[DeveloperManual]]

Completed items: (historical record)
* Merge [[ApplicationIcons]] and [[Icons]]. Also looks like these need editing and update in general. Merge Done --[[User:GigaClon|GigaClon]] 09:35, 21 June 2006 (PDT)
* Remove useless pages. There's a bit too many links on the main wiki page, so trimming will help reduce the clutter. Move pages to [[WikiAttic]] or move their contents into more useful sections.
** [[CPlusPlus]] / [[Pangoification]] - these are both done, the pages aren't really useful anymore. Done --[[User:GigaClon|GigaClon]] 07:45, 18 June 2006 (PDT)

=== Inkscape Promotion ===

Believe it or not, there are still people in the world who don't know about Inkscape. Your job is to fix this! Here are some ideas for helping to spread the word about Inkscape:

* Update [[InkscapeFeatures]] - Review recent changes to [[ReleaseNotes]] and make sure [[InkscapeFeatures]] capture all the major features we've got.
* Contact magazine publishers and ask that they include Inkscape coverage and/or copies of Inkscape in their magazine CD's

=== Inkscape Documentation ===

Inkscape users love having new tutorials, guides, and references.

* Help author, edit, translate, and review tutorials
* Join the Inkscape Manual team. This aims to compile a complete reference, so if writing Wikipedia articles appeals to you, you'll love this!
* Write more content for the website or wiki
* Get articles published about Inkscape on FootNotes, DeviantArt, FreshMeat, or other community sites

=== Making Screenshots ===

For a user, screenshots are perhaps the most important resource at inkscape.org. It's what most people look at first: they want pretty pictures.

Please see the [[MakingScreenshots]] page for fuller explanation of this topic and instructions on how to make screenshots and submit them to the [http://inkscape.org/screenshots/index.php gallery].

=== Inkscape Janitors ===

If you can code (even if you're new to coding), check out [[InkscapeJanitors]] for specific coding requests. Code it up, create a patch, and upload it to the patch tracker. Easy!

HelpMenu

2007-02-12T00:39:19Z

DavidHOzAu: double redirect

== Help Menu Content + Reorganization ==

The "Help Menu" in the [[GlobalMenuBar]] in Inkscape needs to be organized and filled with good content. As of inkscape-20031202, Inkscape has only two items displayed in the Help Menu:

* About Inkscape
* About Modules
** SVG Input
** SVGZ Output
** Dia Input
** Roundhole
** Dropshadow
** AI Input
** SVG Output Inkscape
** SVG Output
** SVGZ Input

Obviously, the above is not acceptable for a good Help Menu. We should all start putting our thoughts here about the Help Menu's organization and content. We need to add some items like (please add to or refine this list):

* [[KeyboardShortcuts]]
* tutorials
* manual
* man page
* [[Release Notes|Release notes]]
* contents (like evolution)
* Inkscape FAQ (like evolution)
* Submit Bug Report (like evolution)
* [[TricksAndTips]]

Not only do the "About Modules" need to pop-up a dialog saying what they are about when selected (as they currently don't), but they should also probably be rearranged like so:

* About Modules
** Input
*** SVG Input
*** SVGZ Input
*** Dia Input
*** AI Input
** Output
*** SVG Output
*** SVGZ Output
*** SVG Output Inkscape
** Filters
*** Roundhole
*** Dropshadow

----

See

* [http://www.g2meyer.com/usablehelp/lastreso.html Help is the Last Resort].
* [http://www.raycomm.com/techwhirl/magazine/technical/embeddedhelp.html Embedded Help: Background and Applications for Technical Communicators]
* [http://www.kavasoft.com/iConquer/help/iConquer%20Help.htm iConquer Help] for an example of help menu. Note that you cannot compel people to use (play) a game. If it is unfriendly and/or unusable people will simply [http://www.needcoffee.com/html/lit/lecturehall/lecture3.htm stay away in droves].
* [http://www.stepwise.com/SpecialCoverage/WWDC2001/501.html Help is a basic building block] Online help is a companion to the computer and is used as the "last resort" by most users. It is where they turn when they reach an impasse and should be a springboard back into accomplishing real work. Good online help, therefore, will focus on describing real world tasks and how to accomplish them. It will emphasize troubleshooting and acknowledge prior experience.
* [http://www.asktog.com/columns/017ManualWriting.html How to Publish a Great User Manual]
* [http://developer.gnome.org/documents/style-guide/usability-non-objectives.html Things You Are Not Trying to Do]
* [http://www.creativepro.com/story/review/17454.html Surprisingly Agile Photoshop Elements] Another example

Some of these are not very relevant to this page's 'mission' I wanted to include the first, and added the rest to provide some balance for it. I will prune this list in due course.

ArticleIntroducingInkscape0.40

2007-02-12T00:38:12Z

DavidHOzAu: double redirect

This is intended to be a PR piece to support the 0.40 release and outline
a few of the key features in a conversational style, to supplement the
[[Release Notes|release notes]], and to drum up interest in participating in Inkscape
development.

= Introducing Inkscape 0.40 =

The November 2004 release of the Inkscape drawing application brings to
users a number of oft-requested features. In this article we'll review
these features and briefly demonstrate their usage and potential. It's
also important to emphasize Inkscape as a participatory project, so
we'll close with some things you can do to help nudge the ball forward.

== Inkscape Tutorage ==

If you've ever used a vector drawing tool before, you'll probably find
the buttons and controls pretty obvious. If not, or if you want to
learn the tool in detail, Inkscape includes several handy tutorials
under the Help menu item. While these don't cover every aspect of
Inkscape, the Inkscape team has made great strides at fleshing them
out. In this release, the team has added new tutorials about the Shape
and Calligraphy tools, the "Potrace" tracing feature, and updated other
tutorials with new sections and more detailed information.

It's worth noting that the Tutorials themselves are created in - you
guessed it - Inkscape itself! In fact, as you become skilled with
Inkscape and develop new tricks and techniques, you're strongly
encouraged to write them up and contribute them to be included in future
tutorials. (If you speak another language than English, the project also maintains
translations of the tutorials, so do consider contributing a translation
or two!)

== Layers Feature ==
<nowiki>
<img src="/wiki_uploads/layers01.png" alt="Layers" align="right">
</nowiki>
The principal feature for this release is the addition of layer
management to Inkscape. This oft-requested feature has required a good
deal of internal rework to support, but leverages SVG's "Group"
mechanism to allow seperation of shapes, text and paths onto different layers.

The promise of this feature is to allow sets of shapes to be hidden or
visible, or to be "locked" from editing so the artist can focus on one
set of items at a time. This capability should hopefully enable artists
to create much more sophisticated artwork than has been possible in previous
releases of Inkscape.

<nowiki>
<img src="/wiki_uploads/layers02.png" alt="Layers 2" align="left">
</nowiki>

TODO - Demonstrate usage

== Text On Path ==

<nowiki>
<img src="/wiki_uploads/textpath01.png" alt="Text on Path Screenshot" align="right">
</nowiki>
Another long-requested feature is the ability to place text on arbitrary
paths. Inkscape 0.40 brings this feature to use in a big way.

TODO - Demonstrate usage

== Bitmap Tracing ==

An exciting (and unplanned) feature new to this release is the ability
to vectorize bitmap, or 'raster', images. Tools had been available
since well before Inkscape to do this, but until now it had to be done
manually and separately from Inkscape. With a smack to the head, one of
the developers realized it'd be easy to add this feature directly within
Inkscape, and so it was. We recommend checking out the tracing tutorial
under Tutorial section of the Help menu.

TODO - Demonstrate the feature

Already, we've seen some rather stunning artistic applications of this
tool, and we're looking forward to seeing what use people can make out
of this new capability.

== POV Raytracing ==

Another intriguing addition in this release is the ability to export
SVG as inputs to POV Ray, to be able to generate 3D renderings of your
2D drawings. This is sort of a proof-of-concept-ish feature; we're
curious what folks think of it; if you find an interesting use of it,
please show it off and give some ideas for how to make it even more
useful.

TODO: Example please

== Randomized Stars ==

The ability to 'randomize' the shapes of stars was another feature added
due not to user requests but mostly just because it could be done.
We don't know how useful the feature is, but it's terribly fun to play
with. Again, please show off if you create something cool with it.

TODO: Provide an example image

== Calligraphy ==

In past releases of Inkscape, the Calligraphy Tool was not really
considered a very useful tool, but with a few tweaks, it's been turned
into something quite powerful.

After clicking on the Calligraphy Tool, look at the controls in the Tool
Control Bar. Here's what the different controls do:

Width: This is the width of the stroke to draw. Think of it as the
width of your pen's nib.

Thinning: This controls how much the stroke narrows when you draw
the pen quickly. This emulates brush-like behavior where slow strokes
produce fatter lines than thin ones. For a perfect calligraphy style,
set it to a value of 0.00.

Angle: This is the angle (in degrees) of the nib compared with
horizontal. Change this to emulate different ways of holding the pen.

Fixation: This controls whether the nib angle varies with the stroke
direction. Essentially, with a value of 1 it makes the nib behave like
a carefully held calligraphy pen, and with a value of 0 it works more
like a felt pen.

Mass: This controls the pen's "inertia". Essentially, it lets you
control how smooth the stroke will be, at the expense of
responsiveness. With a value of 0 your stroke will be jagged and
irregular, capturing your every twitch. With a value of 1 the pen feels
like you're dragging a boat through water, but the stroke is quite
smooth and regular. If you find the pen doesn't "feel right", try
fiddling with this parameter - each artist will find a different value
to be most comfortable.

Drag: This is the resistance to movement of the pen. A value of 0.50
will feel most natural; lower values mean that slight motions will
produce large, sweeping curves; higher values make it feel like you're
writing in clay, and it takes very strong movements to produce much of a
line. This may be useful for altering the artistic style of your
lettering.

While the Calligraphy Tool has always been available in Inkscape, the
variety of controls made available in this release should hopefully give
you a lot more to experiment with, and make this tool much more
powerful for your work.

== And Much More! ==

<nowiki>
<a href="/wiki_uploads/screenshot.png"><img src="/wiki_uploads/screenshot_thn.png" alt="Screenshot" align="center"></a>
</nowiki>

The above should cover most of the major changes you'll notice in
Inkscape, but is far from exhaustive. Many small usability tweaks,
performance enhancements, bug fixes, and code cleanup have also gone
into this release. Most of these are identified in the Release Notes,
but of course the most fun is to discover them while using the tool!
;-)

You'll notice some changes in layout of a few dialogs, for instance.
Copy and paste, grid, use of current style, the statusbar, XML editor,
and so on have all received some attention and show off new ideas that
users and developers have had lately.

In addition to the controls mentioned earlier, many shapes have new
controls and ways of manipulating them. See the Shapes tutorial for a
full overview of the capabilities.

<nowiki>
<img src="/wiki_uploads/preferences.png" alt="Preferences" align="right">
</nowiki>
A most convenient feature was added to the tool buttons - double clicking
on them brings up the preferences for that tool. Quite handy!

In the past, Windows users have lagged behind Linux users for Inkscape
functionality due to Windows-specific issues that the developers hadn't
been able to address. In this release, focus has gone into helping get
those issues figured out, so hopefully Windows users will find Inkscape
as stable as the Linux users.

== Participation ==

Inkscape is different from commercial software that you may be used to,
in that it is a grassroots-driven, open effort to create the tool.
Everyone that works on it does so as a volunteer. There's no budget to
worry about, no salaries being paid, no quarterly sales forcasts.
Everyone participates for the simple reason that they wish to have a
great SVG-based drawing tool freely available on Linux, Windows and
other platforms.

The implication of all this is that unlike commercial software, where
your role starts and ends at the cash register, with open source
projects you have an important role to play within the process. You've
heard the phrase, "Time is money," which you can interpret to mean that
your time is as valuable as your money. In an open source project like
Inkscape, your time can actually be much more valuable than money - your
efforts can directly assist in improving the software for everyone,
whereas money usually has to be translated into something that benefits
the project, so it's more of an indirect process.

Of course, not everyone can afford to dedicate as much time as the core
developers have to Inkscape, so you probably wonder how you could
contribute a small amount - perhaps no more than a couple hours on just
one evening - helping improve Inkscape without getting committed to
something huge. Fortunately, there are many ways to help.

First and foremost is to simply spread the word. Inkscape doesn't have
a marketing budget, nor does it put out any advertising. Instead it
depends on users to share their experiences with others, help people
install it, and show them how to use it. Figure that for every ten
people you help use it, you'll gain a convert that will contribute to
Inkscape in some way some day.

Second, and probably even more important is to strengthen the feedback
loop. Since its release, Inkscape has benefitted immensely from the bug
reports, testing, and feature suggestions from hundreds of users. These
efforts by users help us identify breakage and issues in new code
swiftly, and has helped Inkscape increase in quality faster than
expected. Because of this powerful, tight feedback loop with the user
community, Inkscape has achieved a level of stability that commercial
software only achieves through expensive manual regression and usability
testing efforts. Inkscape instead benefits from the "Many eyes make
bugs shallow" effect that comes from good open source practices. So
bang on the tires, peek in all the nooks and corners, and if you see
something that's obviously wrong, send in a report! Or review the
existing reported bugs and see if you can replicate them; if so, add
some notes about your own observations, to help give the programmer some
additional evidence to help narrow in on the problem.

Third, as a skilled user of Inkscape your Inkscape talents can be used
directly to help the software in a variety of ways. As mentioned above,
tutorial writing is an easy way to share your skill with other users.
Inkscape also has a sister project, the Open Clip Art Library
(www.openclipart.org) where you can share templates, clipart, patterns,
and other such works with users. This is especially valuable for the
less artistic amongst us, and opens usefulness of Inkscape (and other
SVG tools) to a much wider audience - even programmers!

Fourth, Inkscape maintains a wiki for discussing feature development and
documenting various aspects of the project. If you're into wikis,
please consider joining in on the wiki discussions. Help with scoping
out new architectures, fleshing out feature suggestions into plan of
actions, and turning the rough notes into finished forms.

Finally, if you can program there are a variety of ways of helping out
in even small ways. In addition to working on the codebase itself,
Inkscape supports "extensions", which are simple scripts or commandline
tools to provide functionalities to Inkscape. You can find these tools
in the Inkscape 'share' directory
(e.g. /usr/share/inkscape/extensions). To add a new tool, you create an
XML file with a .inx extension to register it with Inkscape. These
tools should accept SVG on standard in and produce a different file
format to standard out (or vice versa). Browse some of the examples and
think about other file formats worth supporting in Inkscape, and write
up your own script.

== "Draw Freely." ==

To sum up: Lots of cool new features, hope y'all like it, and do think
about donating a few spare cycles to making the tool better.

We've got a lot to look forward to in the future. In the near to mid
term, we expect to reimplement the UI in C++, investigate some
performance optimization ideas, and of course continue adding many more
features and fixes. Longer term, we want to make Inkscape better suited
for both advanced artistic use as well as basic technical drawing use
(already we have an eye on a Visio VDX-to-SVG converter, mmm...)

[[Category:Marketing]]

Talk:InkscapePopularity

2007-02-12T00:30:06Z

DavidHOzAu: Talk:InkscapePopularity moved to Talk:Inkscape popularity: CamelCase is depreciated

#REDIRECT [[Talk:Inkscape popularity]]

Talk:Inkscape popularity

2007-02-12T00:30:06Z

DavidHOzAu: Talk:InkscapePopularity moved to Talk:Inkscape popularity: CamelCase is depreciated

I was really excited when I found Inkscape and tried it until I realized Inkscape can't import pdf or postscript files. It's hard to imagine the graphics art community embracing a program which doesn't interoperate with two such major standards. I don't know how to code so I can't contribute, but here's hoping someone will add this capability.

Kevin

InkscapePopularity

2007-02-12T00:30:05Z

DavidHOzAu: InkscapePopularity moved to Inkscape popularity: CamelCase is depreciated

#REDIRECT [[Inkscape popularity]]

Inkscape popularity

2007-02-12T00:30:05Z

DavidHOzAu: InkscapePopularity moved to Inkscape popularity: CamelCase is depreciated

The idea of this is mostly about helping Inkscape and other open-source apps being more popular in the professional and academic graphic design world.

The needed is getting help from arts/design and engineering universities, associations (like http://www.icograda.org), design-related studios, offset printing companies, etc., the most worldwidely as possible.

Getting contact from both arts/design and engineering worlds would provide us to get the best features and intensive testing (specially on the speed and accuracy we need from this kind of application)

What also would help on Inkcape popularity is making it more visible from graphic design related magazines, like Eye (http://www.eyemagazine.com/), Communication Arts (http://www.commarts.com/), U&LC (http://www.uandlc.com/), Emigre (http://www.emigre.com/), [[DotDotDot]], etc.

Comments and helps on this task is hugely welcome!

How to attract graphic design professionals: Prioritise the UI

* Clarity and usability. If Freehand and Illustrator do things a certain way in terms of layout or terminology then so should Inkscape - unless it is seriously sub-optimal.

::I agree, except that Illustrator ways are indeed often suboptimal, especially in the context of Inkscape. Anyway, please make specific proposals. --bb

* The default keyboard shortcuts should be the same as the industry leaders. Reduce clutter and look at the UI trends Adobe are pushing. They have a lot of historical baggage to accomodate which Inkscape doesn't so we can get there quicker and cleaner. Another point.

::See my comment in your RFE on this. --bb

* Apps with hundreds of floating pallettes look unprofessional (Gimp?). Make those pallettes dockable and lockable. Keep tech terminlogy off of the interface (tranform matrices??).

::Agree, making dialogs dockable and reducing their number is always on our TODO. As for transform matrix, it's used in a single place - where you can _edit_ that matrix. It's a feature for those who need it and knows what to do about it. --bb

(I'll eventually edit this rant and move it to a more appropriate place.)

[[Category:Developer Discussion]]

Inkscape popularity

2007-02-12T00:29:21Z

DavidHOzAu: rm redundant restatement of article title

ProjectInfo

2007-02-12T00:27:30Z

DavidHOzAu: ProjectInfo moved to Project information: CamelCase is depreciated

#REDIRECT [[Project information]]

Talk:SupportedOperatingSystems

2007-02-12T00:19:37Z

DavidHOzAu: Talk:SupportedOperatingSystems moved to Talk:Supported operating systems: CamelCase is depreciated

#REDIRECT [[Talk:Supported operating systems]]

Talk:Supported operating systems

2007-02-12T00:19:37Z

DavidHOzAu: Talk:SupportedOperatingSystems moved to Talk:Supported operating systems: CamelCase is depreciated

== Fedora Core 3 and Inkscape ==

O/S: Fedora Core 3
The repository (yum) version of Inkscape is 0.43 (corrected) 
The latest Inkscape does not seem to be forthcoming as a binary for Fedora. 
I have tried the '''autopackage''' and I get this error when I run inkscape:
 
inkscape: /usr/bin/../lib/libpng12.so.0: no version information available (required by inkscape) inkscape: /usr/bin/../lib/libstdc++.so.6: version `GLIBCXX_3.4.4' not found (required by inkscape)

I have sought these things in yum, but have not had much luck. 
I tried to compile from source. Ouch. The dependencies are overwhelming and I will have to compile them from source too! It's too confusing for me.

Now, I am not an expert, just a designer who wants to use his favourite tool! On Windows I can install the 0.44 version no problem, seems ironic that it cannot be so on Linux.

Any suggestions? Perhaps a wiki page to help twits like me through these situations?

(Fixed an error, don't suppose anyone will actually read this anyway :()

:Possibly, because the bug tracker is the proper interface for such problems. --[[User:Colin Marquardt|Colin Marquardt]] 04:15, 21 July 2006 (PDT)

SupportedOperatingSystems

2007-02-12T00:19:37Z

DavidHOzAu: SupportedOperatingSystems moved to Supported operating systems: CamelCase is depreciated

#REDIRECT [[Supported operating systems]]

Supported operating systems

2007-02-12T00:19:37Z

DavidHOzAu: SupportedOperatingSystems moved to Supported operating systems: CamelCase is depreciated

Inkscape binaries are provided for the following platforms:

=== [http://inkscape.org/download.php Official binary distributions] ===
* Linux
* Windows Me, NT, 2000, XP (Windows 95, 98, 98se just until version 0.41)
* [[MacOSX|Mac OS X]] 10.3 (Panther) and later; Starting with the [http://wiki.inkscape.org/wiki/index.php/ReleaseNotes042 0.42 release]

If your favorite OS (we are thinking of [[CompilingSunSolaris|Solaris]], Plan9, FreeBSD) isn't listed above, you can help by [[CreatingDists|building your own packages]] or [[CompilingInkscape|compiling from source]].

Note: Support for Windows is dependent on Gtk, and it is not clear that [http://users.iafrica.com/c/cq/cquirke/win95ver.htm Windows 9x] will be supported indefinitely.

Note: Should we regard certain distributions, perhaps Debian, Gentoo and SuSE Community Edition as 'Tier One' and always provide qualified install packages for these, leaving the rest to be covered by Autopackage

See also the [http://www.inkscape.org/download.php Download Page] which has a slightly longer version of this info, and the actual files.

[[Category:About Inkscape]]