Inkscape Wiki - User contributions [en]

ComplianceTesting

2006-07-25T15:35:33Z

GigaClon: Categorization

Testing the compliance of Inkscape to the SVG specifications

* Inkscape's current [[SVG Test Suite Compliance]]

* SVG Renderer Comparision Page: http://www.linuxrising.org/svg_test/test.html

* SVG Specifications: http://www.w3.org/TR/SVG/

* SVG Mobile Specification: http://www.w3.org/TR/SVGMobile/

* Adobe XMP Specification: http://www.adobe.com/products/xmp/

[[Category:Developer Discussion]]

CommunicationChannels

2006-07-25T15:34:56Z

GigaClon: Categorization

Communication is key for the success of any team effort, and in
open source projects, written communication is critical for success.
Briefly I'd like to explain the different communication channels we
have, in case some are unfamiliar with them.

=== Jabber ===

Chat is a convenient, immediate, and free-form way of exchanging
information, and we make heavy use of it. For fun we decided to try out
Jabber and liked it enough that we've continued to use it. Details
about getting started with it are on the website.

We'd like to know if people would prefer IRC, though. If enough people
cannot or do not wish to use Jabber, then we should switch to IRC.
Please speak up if you have an opinion on this.

If you have a good discussion in chat that you think others might be
interested in, consider sending a copy of the log to the mailing list.

=== IRC (Internet Relay Chat) ===

Use your favorite irc capable chat client to connect to:
irc.freenode.net
And
/join #inkscape
This is an unofficial discussion location, until sanctioned.

=== Email Lists ===

Email is preferred for information that needs wider visibility, such as
things that will require discussion in preparation for making
decisions. The mailing lists are also archived, so new developers can
review past discussions to get up to speed.

If you see or write a good email on a topic that people will wish to
refer to longer in the future, consider pasting a copy of it into Wiki,
so that it'll be easier for people to find and maintain later.

* [http://lists.sourceforge.net/mailman/listinfo/inkscape-announce inkscape-announce] - Announcements about Inkscape, its plugins, events, etc. (low volume)
* [http://lists.sourceforge.net/mailman/listinfo/inkscape-devel inkscape-devel] - This is the main development discussion list
* [http://lists.sourceforge.net/mailman/listinfo/inkscape-tracker inkscape-tracker] - All bug / feature / patch posts to the SF tracker get sent here
* [http://lists.sourceforge.net/mailman/listinfo/inkscape-cvs inkscape-cvs] - All cvs commit messages get sent here (high volume)

=== Wiki ===

Wiki is the new discussion medium we're introducing. A Wiki is a
website that can be edited and added to by anyone. It's like a virtual
whiteboard, and that's how we want to use it. It's good for gaining
wide visibility and it's more persistent than email (no having to browse
through archives).

Wiki's are great for capturing info quickly and semi-permanently, and
for writing collaboratively. This makes them perfect for brainstorming
and hashing out plans, designs, floating proposals, etc.

Wiki's can get a bit chaotic over time, and for people with only a quick
interest in the project they can be too much effort to search through
for "official" information. So, if a page in Wiki becomes 'official'
enough that it needs higher visibility and/or more formality, consider
turning it into a proper web page.

=== Website ===

The website is simple flat HTML files, using SSI to put the header and
footer on. It's stored in the CVS module inkscape_web. Anyone with CVS
commit permissions can and is encouraged to make changes to the
website.

Changes to the website are posted to the inkscape-cvs@ mailing list.

Each communication medium has its strengths and weaknesses. If we are
all good about using them appropriately, and promoting information
from one to the next where beneficial, it will give Inkscape a great
communication infrastructure. Miscommunication is a leading cause of
trouble in projects, so it is well worth our effort to work to prevent
them from occurring.

[[Category:About Inkscape]]

Common Dialogs

2006-07-25T15:34:12Z

GigaClon: Categorization

Where it is possible, dialogs should look and behave the same in the applications.

[[Stroke dialog]]

[[Close dialog]]

[[New document dialog]]

[[Text dialog]]

[[Layer dialog]]

[[View menu]]

[[Overwrite document]]

[[Category:Needs Work]]

ColourPicker

2006-07-25T15:33:19Z

GigaClon: Categorization

Inkscape and [[The_Gimp]] should share a colour picker. The Gtk one is simple but not powerful enough for serious work.

Of course, some of what pickers and features we need will depend on what exactly we mean by [[InkscapeColor]]

Here are some example pickers that are worth copying:

* http://www.joncruz.org/NewColorSel.png
* http://java.sun.com/docs/books/tutorial/figures/uiswing/components/ColorChooserDemo2.gif
* http://www.oldjewelsoftware.com/ppicker/index.html
* http://www.color-wheel-pro.com/
* http://www.tigercolor.com/
* http://www.synergymedia.net/products/ColorPerfect/
* http://macosx.narcissisme.dk/colordesigner_v7_screenshot.jpg
* http://www.code-line.com/software/colorconsultantpro.html
* http://citeseer.nj.nec.com/macintyre91constraintbased.html

And a few recent additions
* http://www.colorschemer.com/
* http://www.wellstyled.com/tools/colorscheme2/index-en.html

== Patents ==

There is a Adobe Patent on Tabbed Palettes.

More Infos:
http://swpat.ffii.org/patents/samples/ep689133/index.en.html

== Thoughts: ==

It would be best to avoid copying any of these exactly.

I like the idea of allowing the user to adjust groups of colours in a picture simultaneously.

The colour picker should be implemented using a widget that displays SVG.

[[Category:Developer Discussion]]

Close Dialog

2006-07-25T15:29:04Z

GigaClon: Categorization

<table style="width: 100%;">
<tr>
<td style="text-align: center; font-weight: bold;">GIMP</td>
<td style="text-align: center; font-weight: bold;">Inkscape</td>
<td style="text-align: center; font-weight: bold;">Scribus</td>
</tr>
<tr>
<td>upload:closeimage_gimp.png</td>
<td>upload:closeimage_inkscape.png</td>
<td>upload:closeimage_scribus.png</td>
</tr>
</table>

<p>
The Close dialog used in Inkscape is closest to what is specified in the Gnome Human Interface Guidelines.
There has been some discussion on the Gnome list about trying to create a standard Close Dialog to try and get rid of this inconsistency that effects the whole of Gnome.
</p>

Might be of interest: [http://live.gnome.org/UsabilityTeam_2fSaveConfirmationDialogs HIG compliance] (that page is really quite hard to read)

[[Category:Developer Discussion]]
[[Category:Needs Work]]

ClipBoard

2006-07-25T15:26:36Z

GigaClon: Merging ClipboardBehavior

I think the best way to handle the clipboard is to make it an SPDocument in its own right. When object(s) are copied to the clipboard, we should:

1. compile a list of objects and their dependencies (eliminating duplicates -- see [[DependencyTracking]])
2. clear the clipboard SPDocument
3. use some (currently unwritten) facility for bulk-copying SPObjects (see [[BulkObjectCopy]]) between documents with references intact to copy the object list to the clipboard document

When pasting, we just use the same bulk object copy facility to copy from the clipboard SPDocument to the destination document (which may or may not be the origin document).

Question: should we handle SPUse specially?

Eventually, we should look at things like taking advantage of e.g. [[StockLibraryInterface]] to avoid creating unneeded duplicates of things like referenced gradients when pasting into the same document. But that's icing.

-----

===ClipboardBehavior===
This is an area to collect information about how the clipboard is currently behaving, and how it's not meeting expectations in different instances. It's time to get the clipboard cleaned up nice, so we'll need to know all the instances that users might need us to address.

[[Category:Developer Discussion]]

Clipart Topics

2006-07-25T15:23:28Z

GigaClon: Categorization

This page is to collect suggestions for what people would like to see covered in the clipart collection.

suggested so far:

* Computer symbols / computer networks
* Musical instruments
* Transport (airplane, bus, car, ship)
* Christmas
* Easter
* Party -- something that will aid in creation of invitation cards, posters and so on.
* Celtic stuff (knots, etc.)
* Storage media symbols (CD, DVD, VCR tape, cassette tape, reel-to-reel tape, LP record)
* Animals (cat, dog, lion, cow, mice, bee hive, etc.)
* Wirey "stick" figures like in MS powerpoint doing different kinds of actions
* Professionals (construction worker, teacher, lawyer, PHB, etc.)
* Symbols for industries (music industry, beef industry, computer industry, etc.)
* U.S. road symbols and signs
* Chemistry symbols
* Flowchart symbols
* Electronic symbols
* Warnings: Biohazard, inflamable, electric shock, etc
* Smilies

This page, which is orphaned would seem to have been made obsolete by the work at [http://www.openclipart.org/wiki/?ClipartRequests Clipart Requests]

[[Category:Wiki Attic]]

ClipTemplates

2006-07-25T15:22:07Z

GigaClon: /* Logistics of the Template System File and Folder Hierarchy */

''How to organise a template directory and how to design svg templates.''

=== Two Concepts for Templates ===

''Let me define: user level (~/.inkscape/templates) and system level (share/templates) templates.''

These are the two features that should be implemented so that Inkscape supports a healthy concept of templates:

''' 1. Default Template that is opened on startup of Inkscape '''

* This document should be called default.svg and a default.svg located at the user level has priority over the system level default.svg.
* We should include the default.svg in the system level folder standard, but have a backup plan if that is not found.

''' 2. New File Menu Item: New from Template... that shows a dialog allowing users to choose from a list of preset sizes or specify their own Custom size.'''

* If a new document is open with nothing on it, then replace that document with the selected template.
* The hierarchy for the system level should be transparent to the user, and shown as a simple list in the dialog or as a treeview if it is believed that extra complexity is needed. (similar to the [[The_Gimp]] 2.0 or Adobe Illustrator etc)

=== Rationale for Support of this ===

If this is implemented then people could build and add their own canvas sizes to the app, and we could support multiple sizes. We could also support our SVG format with having graphics pre-built onto the canvas. This could be useful for slide presentations, calendars, blueprints, letterhead (with logo and text on it), etc.

=== Logistics of the Template System File and Folder Hierarchy ===

The proposed structure of the system-level templates folders would be:

*COVERS
**CDformat
**DVDformat
**TAPE
**VHS

*LABELS
*BACKGROUNDS
*BANNERS
*ICONS
*PAPER SIZES
*WEB
**BUTTONS
**BANNERS
*TEMPLATE THEMES
*OTHER

(Add more please)

The user level hierarchy, if folders within it exist, would be added to the Open Templates list in order. Thus if a user had a folder called PAPER SIZES, then anything in that would be added along with the system level into the Open Templates sub-menu.

=== Name of the Template File ===

The name of the template should be autodescriptive as:

ARBITRARYNAME+MEDIA+SIZE.svg

autumn_cd_cover.svg
autumn_background_a4.svg

Templates may have some help for placing or modifying items through the "no print" and "Sensible" features.
You can make no "printable" and no "Sensible" items by pressing left mouse button over an item and choosing the "Item Properties" entry.
Help could be something like "Title", "Left Side" or "Cut Here".

[[Category:Developer Discussion]]

ClipTemplates

2006-07-25T15:20:07Z

GigaClon:

''How to organise a template directory and how to design svg templates.''

=== Two Concepts for Templates ===

''Let me define: user level (~/.inkscape/templates) and system level (share/templates) templates.''

These are the two features that should be implemented so that Inkscape supports a healthy concept of templates:

''' 1. Default Template that is opened on startup of Inkscape '''

* This document should be called default.svg and a default.svg located at the user level has priority over the system level default.svg.
* We should include the default.svg in the system level folder standard, but have a backup plan if that is not found.

''' 2. New File Menu Item: New from Template... that shows a dialog allowing users to choose from a list of preset sizes or specify their own Custom size.'''

* If a new document is open with nothing on it, then replace that document with the selected template.
* The hierarchy for the system level should be transparent to the user, and shown as a simple list in the dialog or as a treeview if it is believed that extra complexity is needed. (similar to the [[The_Gimp]] 2.0 or Adobe Illustrator etc)

=== Rationale for Support of this ===

If this is implemented then people could build and add their own canvas sizes to the app, and we could support multiple sizes. We could also support our SVG format with having graphics pre-built onto the canvas. This could be useful for slide presentations, calendars, blueprints, letterhead (with logo and text on it), etc.

=== Logistics of the Template System File and Folder Hierarchy ===

The proposed structure of the system-level templates folders would be:

COVERS
CDformat
DVDformat
TAPE
VHS

LABELS
BACKGROUNDS
BANNERS
ICONS
PAPER SIZES
WEB
BUTTONS
BANNERS
TEMPLATE THEMES
OTHER

(Add more please)

The user level hierarchy, if folders within it exist, would be added to the Open Templates list in order. Thus if a user had a folder called PAPER SIZES, then anything in that would be added along with the system level into the Open Templates sub-menu.

=== Name of the Template File ===

The name of the template should be autodescriptive as:

ARBITRARYNAME+MEDIA+SIZE.svg

autumn_cd_cover.svg
autumn_background_a4.svg

Templates may have some help for placing or modifying items through the "no print" and "Sensible" features.
You can make no "printable" and no "Sensible" items by pressing left mouse button over an item and choosing the "Item Properties" entry.
Help could be something like "Title", "Left Side" or "Cut Here".

[[Category:Developer Discussion]]

ClipTemplates

2006-07-25T15:19:45Z

GigaClon: Categorization

''How to organise a template directory and how to design svg templates.''

=== Two Concepts for Templates ===

''Let me define: user level (~/.inkscape/templates) and system level (share/templates) templates.''

These are the two features that should be implemented so that Inkscape supports a healthy concept of templates:

''' 1. Default Template that is opened on startup of Inkscape '''

* This document should be called default.svg and a default.svg located at the user level has priority over the system level default.svg.
* We should include the default.svg in the system level folder standard, but have a backup plan if that is not found.

''' 2. New File Menu Item: New from Template... that shows a dialog allowing users to choose from a list of preset sizes or specify their own Custom size.'''

* If a new document is open with nothing on it, then replace that document with the selected template.
* The hierarchy for the system level should be transparent to the user, and shown as a simple list in the dialog or as a treeview if it is believed that extra complexity is needed. (similar to the [[The_Gimp]] 2.0 or Adobe Illustrator etc)

=== Rationale for Support of this ===

If this is implemented then people could build and add their own canvas sizes to the app, and we could support multiple sizes. We could also support our SVG format with having graphics pre-built onto the canvas. This could be useful for slide presentations, calendars, blueprints, letterhead (with logo and text on it), etc.

=== Logistics of the Template System File and Folder Hierarchy ===

The proposed structure of the system-level templates folders would be:

COVERS
CDformat
DVDformat
TAPE
VHS

LABELS
BACKGROUNDS
BANNERS
ICONS
PAPER SIZES
WEB
BUTTONS
BANNERS
TEMPLATE THEMES
OTHER

(Add more please)

The user level hierarchy, if folders within it exist, would be added to the Open Templates list in order. Thus if a user had a folder called PAPER SIZES, then anything in that would be added along with the system level into the Open Templates sub-menu.

=== Name of the Template File ===

The name of the template should be autodescriptive as:

ARBITRARYNAME+MEDIA+SIZE.svg

autumn_cd_cover.svg
autumn_background_a4.svg

Templates may have some help for placing or modifying items through the "no print" and "Sensible" features.
You can make no "printable" and no "Sensible" items by pressing left mouse button over an item and choosing the "Item Properties" entry.
Help could be something like "Title", "Left Side" or "Cut Here".

[[Category:Developer Discussion]]

Dia

2006-07-06T21:07:09Z

GigaClon: Categorization

Please post links to screenshots and/or insights of this vector app. We must learn from others.

=== Description ===

[[Dia]] is a structured diagrams program similar in purpose to [[MicrosoftVisio]]. It is not currently available in a native windows (GDI) version, only as ported GTK application.

The real strength of [[Dia]] is that it has a good collection of templates and preset shapes which make it easier to create Diagrams quickly.
With tools that make it easy to manage large collections of clipart and the clones functionality already in Inkscape it should be possible to provide many of the same advantages to Inkscape users.

[[Dia]] uses a Controlled Single Document Interface (CSDI) similar to [http://gimp.org the GNU Image Manipulation Program] and [[Sodipodi]].

[[Dia]] is written in C and has support for plugins written in Python.

[[Dia]] makes use of XSLT which hopefully [[Inkscape]] could share.
[[Dia]] also has support for importing various file formats and it would be excellent if there were some way to share these libraries or have a shared infrastructure for vector graphics the similar to how there is the generic gdkpixbuf for raster graphics.

=== Screenshots ===

[http://www.gnome.org/projects/dia/scrshot.html Screenshots Page]

=== Links ===

[http://www.gnome.org/projects/dia/ Official Project Page for Dia]

[http://freshmeat.net/projects/dia/ Freshmeat Project Page for Dia]

[http://www.advogato.org/proj/Dia/ Advogato Project Page for Dia]

[http://netsoc.tcd.ie/~horkana/dia/ Alan Horkan's Dia gallery] (includes screenshots)

=== License ===

GNU General Public License (GPL)

[[Category:Developer Dicussion]]

Developer manual

2006-07-06T21:00:55Z

GigaClon: unbroken

= Inkscape Developer's Manual =

== Introduction ==

For those of you just joining us, or who have been with us but are just
now getting the itch to work on Inkscape, I thought I'd give some tips
for how to get started working in the codebase based on our own
experiences.

One of the first things most people wonder is "what should I work on".
As you may have already noticed, we generally don't "assign" projects.
We figure there's plenty more work to do than people to do it, so you
may as well work on something that you're either interested in or that
adds something of benefit to you; that's extra motivation to get your
own itches scratched.

If you're really stumped though, we keep a detailed [[Roadmap]] in wiki that
you're welcome to browse through to look for ideas of things to work
on. Tasks that do not have names beside them are open for anyone to
take; if you want to take ownership of a task, just put your name beside
it. Feel free to add or reword tasks as needed, although try not to
load up the current milestone with tasks that aren't critical for the
release. Feel free to work on stuff that is several milestones down the
road; there's rarely any problem with getting stuff done sooner than
planned. ;-)

We have a process for gaining CVS commit access. The reason is that
while it is important that we keep access to the codebase open, we don't
want to be crazy and leave it wide open to any random passer-by. The
process is that we require that the person make two contributions
(patches, documentation, web collateral, etc.) and then make a request
to get account access.

In general you won't need CVS commit access in order to start doing
development, because you can work from an anonymous checkout and create
patches. If you've not done this before, you'll need to learn this
skill first (basically see docs for `cvs diff`).

When you first start hacking on Inkscape code, I wouldn't recommend
taking an objective of implementing a specific feature, because you will
need some time to familiarize yourself with the codebase, and because
you won't really know what features are going to be straightforward to
implement and which will be highly challenging. Of course, if you have
the time and love adventures, this might be a fun way to go.

There are four approaches that I've seen people effectively use in
getting into the codebase:

<ul>
<li>Write code documentation. Some people who don't mind adding
comments to code or writing docs find it useful to just go through
code they're interested in working on and writing up what it does.
The codebase is in dire need of better docs, so this approach pays
dividends well into the future.
</li>

<li>Fix bugs. Tracing down the cause of reported bugs is an effective
way to gain understanding of the codebase in small chunks. Many
common bugs can be traced down and fixed in a matter of hours, and
often will identify some bit of code in need of refactoring or
extension. Note that some of our older bugs are in the system
because they're hard to fix, so you'll want to work on the more
recent ones.
</li>

<li>Chip in on a group effort. Occasionally we identify a major
refactoring effort (such as when we converted from C to C++), that
we encourage lots of people to help on, in the philosophy that many
hands makes short work. This work tends to be pretty rote so is
not hard for new folks to get involved with; it just takes time. We
generally have one of these kinds of efforts per release. It
usually isn't glamorous work, but in aggregate moves the codebase
forward in a major way.
</li>

<li>Subsystem/module work. Some people want to get their hands in the
details quick, so take the approach of developing new code separate
from the codebase, to be integrated in later. This generally tends
to take a larger time commitment than the other approaches, but can be
an effective approach in some circumstances. We have a CVS module
called 'experimental' that you're welcome to house your work until
it's ready for prime time.
</li>
</ul>

Beyond that, you're going to find the documentation for the Inkscape
code is pretty scarce. We've worked on bits and pieces but
unfortunately the vast majority of the code is undocumented. On the
plus side, often you can implement the stuff you care about after
learning only a limited portion of the codebase.

I think you'd find Inkscape an enjoyable Open Source project to work on.
There's a huge range of interesting and useful skills that can be
learned from it, plus the developers are great guys to participate with.
The project itself runs smoothly and puts a premium on keeping things
friendly and low-stress, so heated arguments are rare. The users have
been great to work with and very appreciative of even small new features
and fixes. Plus, since Inkscape is so visual in nature, it's very cool
to see how your little changes make noticeable improvements to the app
overall.

== C++ Reference ==
* FAQ (with answers) sheet. We strongly recommend that everyone read this site comprehensively. You should not need to bookmark it, it should be the first of the sites on your autocomplete list for <code>par</code>!

http://www.parashift.com/c++-faq-lite/

It is actually more in-depth than the name FAQ suggests. Many experienced C++ programmers would benefit from it.

* List of [http://www.cs.helsinki.fi/u/vkarvone/2004s/cplusplus/errors.html schoolboy errors]. None of these should appear in [http://en.wikipedia.org/wiki/Free/Libre/Open-Source_Software FLOSS] code.

== Strings ==
Please make sure any user-visible strings are localizable. This requires wrapping them with "_(" and ")", like so:

"Select object"
becomes
_("Select object")

In case the interpretation of the string may be ambiguous or may differ according to context, you can add a context prefix (that won't be displayed) in order to eliminate the ambiguity.
"Ambiguous string"
can then become
Q_("Context|Ambiguous string")

For more complex things, please check the gettext/localization documentation.
See also http://developer.gnome.org/doc/API/2.0/glib/glib-I18N.html

== Standards Compliance - Extension Namespaces ==

* Only elements and attributes from our extension namespaces that ''do not affect rendering'' may be saved in SVG documents.
* Generally, this means that extension elements and attributes should only be used to provide UI hints.
* Extension elements and attributes should ''only'' be used where an existing facility provided by XML or SVG is not sufficient.

== Global Verbs ==

Here's a readers' digest summary of how Inkscape accelerators work:

A global mapping between key combinations and integer verb IDs
(sp_verb_t) is maintained in shortcuts.cpp; these are registered using
sp_shortcut_set().

Given an sp_verb_t and an SPView, you can get an SPAction which
represents that action in that view. These mappings are currently
hard-coded in verbs.cpp.

SPActions derive from NRActiveObject, which putatively provides a
"lightweight" method of doing callbacks, versus GObject signals. I
don't completely understand how it works.

SPActions also contain the label, image, etc, used for buttons and
menuitems.

sp_shortcut_invoke() looks up the SPAction for a keypress and SPView and
invokes it automatically. SPEventContexts call it for keypresses that
they do not handle themselves.

== Garbage collection ==

As you know, many automatic garbage collectors (like libgc) only
free and recycle memory periodically. This means you may have some
extra slush that could be freed, but hasn't yet.

There are other forces at work, though...

Pretty much all allocators, whether automatic or not, whether the
system malloc() or some custom allocator like libgc's, work the
same way: they request large blocks of memory from the operating
system, then divvy those blocks into smaller ones internally to
satisfy application allocation requests.

When an application frees memory, that memory is usually recycled
internally rather than returned to the OS immediately. The reason
for this is that the large memory blocks acquired from the OS must
be completely unused before they can actually be freed.

Let's say for example that an allocator acquires 16 8MB blocks from
the OS in response to 32768 4k application allocations...

In a worst-case scenario, it's possible that the application could
free 32752 of those 4k blocks but the remaining 16 4k just happen
to be distributed across the 16 8MB blocks requested from the OS.

If that happens, from the application's point of view it may only
have 64k allocated, but as far as the OS is concerned, it's still
using 128MB!

Note that this applies to nearly all allocators in common use.

While it's unusual for things to get quite that bad, memory
fragmentation is common enough that many popular allocators (for
example Perl's) simply don't bother trying to return memory to the
OS at all (the memory will still get forcibly reclaimed by the OS
when the process exits).

[ FWIW, libgc's allocator is one of the ones that _does_ make an
effort to release memory to the OS, but it is limited by
fragmentation like any other ]

Also note that for various reasons, the statistics you get from the
OS aren't going to directly reflect the amount of heap-allocated
memory. Be careful drawing conclusions from only looking at e.g.
the output of top(1)...

(the worst thing is that due to the modern practice of
overcommitting memory, the OS may literally lie to an application
about the amount of memory it is being given, hoping the
application won't really try to use it all)

The best approach to evaluating memory usage is if you can ask the
allocator for information on memory usage directly, as that matches
the world from the point of view of the application.

leftover gradients/markers/patterns
will get automatically cleaned up when the objects that use them are
deleted.

Caveats:

* this only applies to such objects created with a build of Inkscape which post-dates this commit (June 7)

* not all automatically-created objects will necessarily be collected; the code that creates them needs to be updated to set the correct collection policy

* paint objects won't get collected until another editing operation takes place, since NRArenaShape currently holds onto an SPStyle for too long

Technical details:

Assuming its collection policy permits it, an object will be collected
if neither it nor its descendants have any outstanding inter-document
URI references (nonzero SPObject::hrefcount).

There are two "policies" for collecting orphans:

* "with-parent" - the object will only be collected if one of its ancestors is collected

* "always" - the object is always collected if unused

(a third policy might be "never", which would necessarily also prevent
that object's ancestors from ever being collected; I do not plan on
implementing it)

The policy in effect is determined by the inkscape:collect attribute.

Be careful with the "always" policy; it really only makes sense for
"private" objects that are indirectly created behind the scenes (e.g. by
selecting a fill or marker option in the GUI).

SPDocument manages a queue of objects to collect; SPObject handles the machinery for actually queueing them when their hrefcount falls (based on policy), and performing the actual collection (delete).
SPDocument::collectObjects() performs a collection pass; it's currently only called from sp_document_maybe_done().

== Inkscape Experimental CVS ==

The 'experimental' module in Inkscape CVS is provided as a kind of "scratchpad" for
working up new ideas that aren't quite ready for folding into the main codebase.
This includes architectural sketches, examples, experimental patchsets, tools & utilities, or
whatever else strikes the developer's fancy.

Please create a subdirectory within experimental/ for your work. You're welcome to either post
the stuff at the top level or create a subdirectory for yourself. Things linked in at the top level
should be considered fair game for other developers to collaborate on; items posted under
a developer's username should be considered ask-first. Same sort of idea as wiki.

One of the principles behind this module is the idea of a shared working space. Other developers
working in experimental can fairly easily see what others are working on in the tree, and perhaps
borrow or contribute ideas back and forth. Since it is by definition not 'production' code, the
work may be incomplete or in a non-compileable state, and thats O-K.

When an experiment has matured to the point of being actually useful, please move it out of
the experimental module to someplace more appropriate. Or alternatively if the experimental
work has become obsolete or irrelevant, please remove it so we can avoid having the
experimental tree get too bulky.

== Directory Organization ==

=== Distribution / Packaging Files ===

Files related to generation of distribution packages should go under inkscape/packaging, as follows:

inkscape/packaging/
common/
debian/
fedora/
fink/
mandrake/
suse/

=== "Share" Collateral ===

A variety of items are installed in addition to the program itself, and placed into a 'share' directory structured as follows:

AUTHORS
NEWS
clipart/
examples/
extensions/
fonts/
gradients/
icons/
keyboards/
markers/
palettes/
patterns/
screens/
about.svg
templates/
tutorials/

In the CVS codebase, all of these are placed in inkscape/share/ (except AUTHORS and NEWS which will be copied to share during installation. The idea is that in theory, this entire tree structure can be copied into place on the user's machine.

However, we need to provide the user some level of control over the installation. They may wish to exclude some items, or may wish to augment the default install with some items external to the Inkscape package. For example, they may wish to incorporate external clipart collections. One approach would be to install symlinks in the given component directory to the external collection. For example, if the flags package were to install into /usr/share/flags-svg/, we'd just symlink there.

=== Code modules ===
Several parts of the code were written in a modular way, and they have been
accordingly placed in subdirectories of src/, while the main src directory
still contains the biggest part. To get a first overview of the modules, you
might want to have a look at these dependency graphs before you read deeper
into the source code (outside at the moment):

[http://www.ark.in-berlin.de/gri-debug.svgz]
[http://www.ark.in-berlin.de/gri-dialogs.svgz]
[http://www.ark.in-berlin.de/gri-display.svgz]
[http://www.ark.in-berlin.de/gri-io.svgz]
[http://www.ark.in-berlin.de/gri-libcroco.svgz]
[http://www.ark.in-berlin.de/gri-libnr.svgz]
[http://www.ark.in-berlin.de/gri-libnrtype.svgz]
[http://www.ark.in-berlin.de/gri-livarot.svgz]
[http://www.ark.in-berlin.de/gri-widgets.svgz]
[http://www.ark.in-berlin.de/gri-xml.svgz]

These are not all modules! For questions about how to generate these graphs
with graph-includes, please [mailto:rwst@users.sf.net].

Question on .svgz files: Is the server sending the right 'Content-Encoding:' header?
This matters to Mozilla browsers in standards compliance mode! http://jwatt.org/svg/authoring/#server-configuration

= See Also =
* [[DirectoryReorgProposal]]
* [[InkscapeJanitors]]
* [[CompilingInkscape]]

= Links =
[http://advogato.org/article/51.html Software Quality]

[[Category:Developer Documentation]]

InkscapePopularitaet

2006-07-05T03:18:58Z

GigaClon: Categorization

Inkscape-Popularität

Es geht in erster Linie darum, Inkscape und anderen Open-Source-Anwendungen zu helfen, in der professionellen und akademischen Grafikdesign-Welt populärer zu werden.

Daher ist es nötig, Hilfe von weltweiten Kunst/Design- und technischen Universitäten, Vereinigungen (wie http://www.icograda.org), Designstudios, Satzdruckfirmen usw. zu bekommen.

Rückmeldungen sowohl aus der Kunst/Design- als auch aus der Technik-Welt würden uns in die Lage versetzen, den besten Leistungsumfang zu bestimmen und intensives Testen zu erhalten (besonders bezüglich der Geschwindigkeit und Genauigkeit, die wir bei dieser Art Anwendung benötigen).

Was der Popularität von Inkscape ebenfalls zugute kommen würde, wäre das häufigere Erscheinen von Artikeln in Grafik-Magazinen wie Eye (http://www.eyemagazine.com/), Communication Arts (http://www.commarts.com/), U&LC (http://www.uandlc.com/), Emigre (http://www.emigre.com/), [[DotDotDot]] usw.

Kommentare und Hilfe bei dieser Aufgabe sind höchst willkommen!

Um die Aufmerksamkeit der Design-Profis zu wecken: Priorität auf die Benutzeroberfläche richten

* Übersichtlichkeit und Benutzerfreundlichkeit: Wenn Freehand und Illustrator Dinge in Bezug auf des Layout und die Fachsprache auf eine bestimmte Art und Weise handhaben, sollte das Inkscape ebenfalls tun - außer es ist gänzlich suboptimal.

::Dem kann ich beipflichten, außer daß Illustrator Dinge oft suboptimal löst, besonders im Zusammenhang mit Inkscape. Machen Sie aber trotzdem konkrete Vorschläge. --bb

* Ein weiterer Punkt: Die Standard-Tastaturkürzel sollten dieselben sein wie bei den führenden Programmen. Reduziert das Wirrwarr und schaut auf die Oberflächentrends, die Adobe setzt. Dort können sie eine Menge Erfahrung aus der Vergangenheit mit einbringen, was Inkscape nicht kann, sodaß wir unser Ziel schneller und sauberer erreichen können.

::Sehen Sie sich dazu meinen Kommentar in Ihrem RFE an. --bb

* Anwendungen mit Hunderten schwebender Paletten sehen unprofessionell aus (GIMP?). Diese Paletten sollten sich andocken und verankern lassen. Haltet die technische Fachsprache aus der Oberfläche heraus (Matrizen transformieren??).

::Da stimme ich zu, die Dialoge andockbar zu machen und ihre Anzahl zu verringern, steht immer auf unserer To-do-Liste. Was Matrizen transformieren angeht, es wird nur einmal benutzt - dort, wo Sie die Matrize bearbeiten können. Das ist ein Feature für diejenigen, die es brauchen und wissen, was sie damit anfangen können. --bb

(Ich werde diesen Text irgendwann bearbeiten und an eine angemessenere Stelle verschieben)

[[Category:German]]

FeatureNotePadArchive

2006-07-05T03:17:31Z

GigaClon: linkage

----------
''wwwwolf writeth:''

WIREFRAME MODE

"Outline" mode. "Draft" mode. "X-Ray" mode. You know what I'm talking about. The mode where only the edges of the paths are drawn, stroked at constant width. Turn it off, and you have everything visible normally again.

I've seen this in Adobe Illustrator (Ctrl+Y), Sketch, Corel Draw!, even the good ole 1991 vintage Arts & Letters.

I think this is pretty important because I love to work with lots of overlapping, same-or-nearly-same-color objects that don't have strike at all. Would make drawing easier...

----------

'''kwixson writes:'''

Some little ideas that I haven't had time to fully spec yet, but I don't want to forget...

* Text tool can optionally draw (with click and drag, as opposed to just click) a text box of defined dimensions, into which text is flowed automatically.
* Cursor icons for Pen, Pencil and Calligraphy tools
* Visual cues for Pen tool cursor in append mode, and other modes (i.e., +, -, ^, etc.)
* Terminiate continuous draw mode when a path is closed in append mode

all DONE

-----

'''Björn writes:'''
1.) _Pressure sensitivity_
- Everybody else got it (Xara, Illustrator, even Gimp) and it is almost necessary for professional drawing.

------

Export .eps. Enough said.

------

Plan for fill&stroke:

First:

* remove "get from dropper" (always on, via [[SetColorSignal]]) (DONE, no signal necessary, just picks new color from selection)

* remove "mode", make global preference "Store colors as rgb/cmyk" (DONE, it's not about storing color actually, so just removed)

* remove redundant color picker selector (DONE)

* transientize, remember size&position, remove Close in the color selector window from Doc props; find if there are others like it (DONE)

* Make evenodd switch a pair of toggle buttons inside colorselector (DONE)

Then:

* remove "apply to"; make all shapes use current color, but on prefs page for each tool, make a switch between "use current" (default on for shapes) or "use its own style" (default on for pens & text), plus a button "take style from the selection". (DONE)

* enable partial color settings (bug http://sourceforge.net/tracker/index.php?func=detail&aid=937393&group_id=93438&atid=604306; actually that will be a separate "adjust colors" dialog)

* add master opacity from object props (DONE)

----------

Provide a UI mechanism where one can cycle through just those object intersected by a pick point. That is, in a large, heavily overlapping graphic, you could point at the thing you want (even though it's behind three or four other things) and quickly choose that object, either from a menu, or by some form of constrained "tab-key" operation.

DONE with Alt+click

----------

How about a better way to parse the xml code? The files are way bigger than they need to be, and it would be nice if there was an option to tidy up the code upon saving.

-- use svgz or plain svg, or both
---------

In selector top panel, make a frame titled "Transform" and covering 4 toggle buttons: stroke (works), rounded rect corner (works), gradient, pattern (need to fix for paths stored-optimized, then add optional compensation in item_write_transform; first to fix the wrong patternTransform application)
-------

Textboxes (multiple shapes, and text-box linking to make the text-flow)
DONE
------

auto "add" new gradient when switching an object to gradient in fill&stroke, instead of reusing the last one used

DONE
------

3. Is item visibility supported? I see the checkbox in Item Properties
but it appears to always be disabled. However, even if it did work,
having to open up and mouse over to extra dialogs is very time consuming.
When working with complex images in Illustrator I am all the time flipping
visibility and sensitivity on/off and it's a quick process because you can
toggle it directly from the layer view. It would be nice if the XML
viewer had a check-box or something right next to each item for quick
visibility and sensitivity changes (see how Layers work in The Gimp,
Illustrator, and Photoshop).

DONE
-------------------------
There are still many artists who use very old versions of Illustrator and Corel Draw so as to get the very most out of cheap hardware and hopefully that is a market that Inkscape can soon grab.
Jasc Web Draw is adequate but if Inkscape can provide a consumer friendly user interface it will serve as a big kick in the Pants for Jasc and hopefully force them to improve their low budget Vector Graphics toy.

-------------------------
when creating a new object, it should have the same attributes as the last
I mean: drawind shapes, if I set one to stroke and fill of a certin kind, each after that should start with the same
until I change it. a palette would be nice, but this is a little different.
if I draw a rect, then set it to blue, 1px black stroke, then draw another, it should be blue, 1px black stroke
these are not settings that are save from session to session, just while working.
small detail, but it'd make things much easier.
in minimum it should behave differently for shapes/text
You definitely do not want text to appear colored/filled by default

-- aduhan

DONE
-------------------------
swingincelt writes:

Apply transform function is something I'd really like to see.

-- doable by switching to "store transforms: optimized"
----------
axiom writes:

Not sure where this goes, but when I have some text, why does all the text in the frame have to have the same attributes? What if I want to have some letters a different color? There is apparantly no way to highlight text

DONE
----------

(DONE) A "New"/"Change" label in all drawing tool toolbars changing depending on whether you have an object of the corresponding type selected

------

Store/guess export filenames for objects; an attribute of spitem, inkscape:export-as=, settable when exports selection and selection contains only one item; fill it in in the dialog; when not set, guess it from prev/next siblings by in/decrementing their filenames' numeric parts (DONE except for guessing, which is likely to be confusing).

------

(DONE) Implement "select under" by ctrl-alt-clicking in selector: Stay in one place and ctrl-alt-click repeatedly watching the statusbar that shows what is selected, it will cycle through the entire stack of objects _at this point_ (not all objects in the document).

------

better gradient editor: ideally arbitrary stops, one color widget that switches to the selected stop (DONE)

------

When opening a file from an empty unchanged document, replace it with the opened one instead of opening a new window (DONE)

------

Write a function to compare two reprs' positions regardless of their parents, by scanning the entire tree (unless they have the same parent, in which case the sp_repr_compare_position() is used) and declaring the one that is run across first to be the lower in z-order. Use it whenever z-order matters (splivarot now has such a function in boolean_op, rather ugly but works).

------

Then make a function next-overlapping and prev-overlapping which finds only overlapping objects; use them in raise/lower commands so that the selection cycles through only the objects that overlap it, not all the objects of the document as now (this presently makes lower/raise almost unusable in large documents). (DONE)

------

Would it be feasible to have the # key toggle both the grid visibility
and grid snapping at the same time? (DONE)

------

Make 1) rubberband 2) eventually all drags scroll window when moved beyond edge. Common function to do that? (DONE)

------

paste in cursor location instead of the original; a separate command for paste-where-it's-from (DONE)

------

remove "clear all", provide "deselect" in edit menu instead (DONE)

------

8. Besides the grouping, visibility, and sensitivity stuff I'd like to
have a "path simplify" command. In Illustrator that takes a path and
removes redundant nodes within certain curve and angle tolerance.

::Done, although needs more work

10. Faster zoom features. I wish I could hit "zoom-out" 3 or 4 times and
not have it redraw each time. Or maybe have a saved zoom factor or
something that I can toggle. I like to zoom in and out a lot to look at
things so I want it to be really fast.

::Now zoom increment is settable in prefs, and there's a history of zooms; it does not redraw when zooms come in quick succession

12. The pencil tool (freehand draw) seems to create a lot more nodes than
Illustrator does. Illustrator must use a curve fitting algorithm or
something because it doesn't use as many nodes to create the path but it
still fits what you draw. Maybe it just uses a difference tolerance, I
don't know.

::Now the fitting tolerance is settable in prefs, and is higher by default

------

maybe_done must catch selection_change and zero its key, so that subsequent same-dir arrow-key movements of different objects are not lumped into one undo step

------

display font name in the statusbar description of text object

------

When more than one group (and possibly some non-groups) are selected, "ungroup" must ungroup all groups in the selection

-------------------------
The below is in regards to Sodipodi 0.32:

1. Is there any way to select individual items from a group? I know you
can open the XML viewer and select items but when you have 100's or 1000's
of items in a group this is extremely annoying and time consuming compared
to just clicking on the item in the artboard (otherwise I usually can't
even find the item buried in the XML list).

:ctrl-click

5. When selecting multiple items (holding down shift on the keyboard)
sometimes it loses the whole selection. I have no idea what causes this,
it may have to do with trying to click an item and "missing". Or it might
have something to do with accidentally dragging a bit while selecting.
Anyway, it is extremely annoying to carefully select 20 or 100 items and
then it happens and boom, you've lost the entire selection and have to
start over again.

:drag tolerance took care of it --bb

6. The "dragging" effect on nodes makes it nearly impossible to use a
tablet with Sodipodi and hard to use a mouse when working quickly.
Usually when creating a path I will quickly rough out the shape and I just
want normal straight, non-curved lines. So I want to click, click, click,
click and make the path. The problem is that if you even drag 1 pixel it
creates a curve or other strange things that I'll then have to go back and
correct. Instead of moving quickly I have to stop at each new point,

click carefully, then move the mouse to the next point. When using a
tablet it's pretty much impossible to click without moving the pointer at
all so this causes all kinds of problems (and not when just creating new
paths).

:drag tolerance took care of it --bb

-------------------------
I commend the inkscape team for picking the excelent language of C++ for development.

I sencerly hope that they use the language to its full potential by using the STL, inheritance and the other fine features that makes C++ a fine language to use. Otherwise it is a waste of time.

Remember, OOP is frustrating and takes a huge amount of time to do right, but when it is done the product is clean, extensible and almost devoid of bugs. Not that its impossible or even overy difficult to make an object oriented program in C, but using C++ with its built in support for virtual functions, protected functions and the like is a step in the right direction.

Well done! Make Bjarne proud!

-----
a knot must pass keyboard events it doesn't process to parent, so esc-deselecting works when mouse is over a resize handle

-------------------------
This is in regards to Sodipodi 0.32:

How can one add nodes to a path? There's a button (the one with '+') but
it adds a node in the middle of a segment. However, most of the time I
want to add a new node AFTER the last node!

Current behaviour: O - - - - - - - - - - - O ===> O - - - - - O - - - - - O

What I want to have: O - - - - - - - - - - - O ===> O - - - - - - - - - - - O - - - - - - O

: While in pen or pencil tool, press CTRL+A to toggle append/add
: modes.
: In Append mode currently selected path has miniature 'anchors',
: that turn red if mouse is over them. Starting new line, while
: anchor is highlighted appends new line to the old (i.e. you can
: add as many points as you like using pen tool).

:In node edit you can press ctrl-d on a node to duplicate it.

Also, in the same spirit, how do you easily join two paths? I mean, say
you have 2 separate segments, and you want to change them into one
triangle. How do you do that? Currently, I have to "compound" them,
select a end node of each path, and click the "-" button; but then, they
merge into a middle point. This would'nt be so much of a problem if it
was easier to add a point to a path!

: I think latest CVS version has 'join with line' option in
: node toolbox.
: Also combining segments (combine tool), and using either pen or
: pencil in 'append' mode allows you to connect existing
: segments from anchors.

-- Nicolas MONNET

-------------------------
First - good name. Does name matter? Yes, if it is to be widely accepted it must sound professional and Inkscape sounds professional.

Second - good move to clean up code and standardize and C++ is a good, widely accepted language (ie every programmer knows it)

Third - please clean up the menus - I tried to use Sodipodi and the menus were very hard to use.

Fourth - the export to rasters like png are a very needed item.

Thanks for your efforts.

---------------

7. Sodipodi seems to crash a good bit. I get afraid to use certain
operations. For most normal work (when just working with nodes and paths)
it seems very stable but when I start combining paths, importing files,
and dragging stuff around in the XML viewer it doesn't take long before
the crash happens. It's usually not a crash that brings up the crash
dialog. It's the kind where you blink and Sodipodi is just gone. I have
also had it crash when I accidentally randomly and quickly click 3 or 4
times on the artboard while drawing. Actually, just doing anything
randomly or quickly seems to make it crash (zooming in/out, clicking lots
of buttons and hotheys). Sorry I can't be more specific, I'll try to
follow more closely what's going on when it crashes.

-------------

I also found the menus particularly hard to use.

I find the whole concept of a "dialogs" menu to be extremely abberent and a rather useless nonsense grouping about as much use as dumping them under "miscellanous". There is also a whole lot of functionality in the Toolbox and various dialogs that I expected to find as a menu item but did not which rather threw me for a curve ball.

I'd like the menus to be at least similar to Adobe Illustrator so that I any learning I do can be reapplied and put on my CV as a skill that managment types will recognise rather than give me funny looks for (the GIMP is still not a funny name, it is just embarassing).

I cant wait to see Sodipodi and Inkscape compete and improve each other.

-------------------------
Sodipodi is very nice, although I have a huge dislike for the interface - while original, it feels very "cludgy" to use. I would love to see a gimp-1.3 inspired interface (1.2 wasn't very nice with it's window juggling but 1.3 has a much nicer drag and drop way of organising & grouping the windows you use more often). With a ui overhaul Sodipodi/Inkscape could be very, very nice.

----------------

BTW, is there already some good user-documentation for Sodipodi/Inkscape? Because as a user, I don't mind how bad the code is and how much dead code there is, all I need is a manual to learn that other 90% of the app. With a manual I can really *use* the program, find bugs, and file bugreports....

[[Category:Wiki Attic]]

User testimonials

2006-07-05T03:12:47Z

GigaClon: /* From: Phil Shapiro */

=== From: User Bats ===
Date: March 2006
Subject: Notes from a recent job using Inkscape.

Hey,
Please go to [[User:Bats|my user page]] where I have a write-up about Inkscape 0.43 and my recent thoughts and comments written just after I had finished the job.

Inkscapes makes Linux really cool (from my perspective), keep it up!

=== From: Gab Studio ===
Date: Sun, 25 Apr 2004
Subject: Great software !!!

Hi;

I'm just trying *INSKCAPE* and would like to *congratulate you all*.

I join my first work... if you want to add it in the galery :)

BRAVO again from France for this great software
have fun

regards

Gab

=== From: Jared Thompson ===
Date: Tue, 16 Mar 2004
Subject: awesome program

I know this may not be according to the purposes of this list,

but I just wanted to say that I recently discovered inkscape and I think
it is quite an impressive program so far.
I have been playing with it non stop for the past few days and love it,
the website is also nice and clean.
there are plenty of tips and in the program a help file that gives a
good overview to get beginners started

I will be looking forward to contribute what I can as time goes forward.

again,
just wanted to say thanks for an awesome program

-jared

=== From: Artemio ===
Date: Sun, 28 Mar 2004
Subject: thank you

Dear Inkscape developers,

at first, please take my sincere congratulations - Inkscape is on the 3rd
place in my top 5 list of most used applications! :-)

You have made possible what I have dreamt for over two years since I started
using Linux (I use ONLY Linux since that time). You have done a really great
work. Inkscape has absolutely everything I need from a vector editor and even
more. It's very light, fast and the interface is very straightforward and
intuitive. Thank you, thank you very much!

Frankly, you have blown all my expectations away - I didn't think someone
would do font->path thing possible, this is amazing! Now I can bring my SVGs
_anywhere_ and they will be read just as I made them (already tested this).

Please excuse me for talking too much, it's just that I really respect your
work and wish you all the best! I do have some little suggestions to you, but
I will write them in my next message :-)

Good luck to you all and thanks so much again!

Artemio.

=== From: Charles Goodwin ===
Date: Sun, 09 May 2004
Subject: Re: wow, this is amazing!

Everything about Inkscape has been impressive thus far, not least of
which the speed with which action is taken to address any issue.

- Charlie

=== From: Trent Buck ===
Date: Tue, Jun 8, 2004
Subject: Re: new illustrator screenshots

Quoth Alan Horkan on or about 2004-06-08:
<blockquote>

On Sat, 5 Jun 2004, Trent Buck wrote:<br>
<i>FWIW, I think inkscape's UI is already better than AI's.</i>

You said Inkscape is better so I make it a challenge to you to list more
ways, and maybe we can start a comparision chart in the Wiki which would
be useful for promoting Inkscape.
</blockquote>

OK, I'll confess, I haven't used AI for than about half-an-hour, because
I couldn't get the hang of the interface. Let me itemize my reasons for
using Inkscape.

Bear in mind that these are my *opinions*, not necessarily *right* in a
technical sense. I'll put a '+' in front of things that are actually UI.

Inkscape beats AI

+ As a newbie, I found the Inkscape (well, sodipodi) interface to be
pretty self-explanatory. Using AI I get the feeling I should take a
3-day course just to learn how to use it.
(Maybe this is just because of all the extra features, I don't know.)

It's free. When something happens I can check the source. It is
also far easier to add or request features.

It works on linux. Enough said.

The GTK toolkit is relatively clean, customizable and robust.

Inkscape beats Sodipodi

The larger community results in faster growth in all areas.

Boolean operations. Miscellaneous tweaks make Inkscape more
comfortable.

Inkscape beats both of them

+ Buttons are around the edge. It has been shown by HCI folks that
this is a far better design than the toolkit approach. Fitts' Law
states that you can click screen corners and edges far faster than,
say, 10px in from the edge.
http://encyclopedia.thefreedictionary.com/Fitts'%20law

+ Likewise, this means everthing is in one window, which works much
better with my windowmanager (http://ratpoison.sf.net).

+ Keybindings for everything. I don't normally even have a rodent
plugged into my system, so being able to stay keyboard-centered is a
major advantage.

I should also point out that I'm not really an artistic person, my
strengths are more oriented in mathematics, english and science. I am a
CS student by profession. I mostly use Inkscape when I need an image
and there isn't a specialized tool to draw it.

It could well be that I don't see Inkscape's deficiencies because my
drawings aren't complicated enough to need them.

-trent

=== From: Richard MacIntyre ===

Unless they've already mentioned it hereon, Julian MacDonald has kindly written a script, and Francois Guillet has just begun work on an SVG plugin, respectively, for SVG import into Art of Illusion- a 3D program- from Inkscape. see: http://sourceforge.net/forum/forum.php?thread_id=1117167&forum_id=47782

I have so far successfully done some stuff to test Julian's script, which I might post- <i>er, that is if I can recusitate my hard disk :/ .</i>

Nice work on Inkscape, btw: A very informative/transparent/diligent process; crisp tool icons with high-contrast; a well-done tutorial/manual, and an aesthetically-pleasing ink-droplet for the About screen. (I got a couple of kids at a cafe playing with Ink''s weird & wonderful calligraphy tool on my laptop :)

I look forward to R.1 or sooner, when I can leave Illustrator behind!

As a footnote:
<blockquote>A few years ago, when I had a contract that required the use of my legitimately-purchased copy of Illustrator, I called Adobe to get a replacement registration/re-installation number for the one I had lost. Even though I jumped through every one of their hoops- both at the time of purchase, as well as at the time of the request- they ultimately refused to issue a new one, and I lost the contract.</blockquote>

Richard

=== From: Henry House ===
Date: Wed, 7 Jul 2004
Subject: New user happy with inkscape!

I used to use A. Illustrator years ago before I used Linux. Ever since then
I have been dissatisfied with the various Free vector drawing applications
available for Linux. I just started using Inkscape yeterday and I am very
impressed! There are keyboard shortcuts for most operations! The boolean
operations (union, divide, etc) work! (The lack of such has been a major
impediment to my use of other vector drawing applications.) My only major
problem so far has been that the selected object is difficult to see because
the selection indicators do not contrast strongly with their object or
follow their object's path outline.

Henry House

=== From: Jose Hevia ===
Date: Mon, 19 Jul 2004
Subject: About DATA and METADATA

Oh, I'm very excited about the little big improvements of inkscape
0.39: In ex.You could go to Object-> Object Properties and ...Change
an object identifier!!! This was in previous versions but didn't seem
to work for me.

So now we could have info not only of the sorting of objects but for
the objects itselfs(multiple in a file) ,so I could make a map of
Africa an name Angola,Rwanda...,summit to open clipart,search in
google :

Rwanda+africa+svg and, there it is!.The bad news is that if I'm not an
english speaker I don't know that "Marruecos" name from my Atlas is
Morocco in english word.(Yes there are a lot of people that have not
thought about that ever).

=== From: Phil Shapiro ===
Date: Sun, 25 Jul 2004
Subject: heartfelt thanks for creating inkscape

thanks a megabyte for your visionary work in creating inkscape. i
discovered this amazing software last week and have been talking it up
on various national email lists i'm on. (see below a message i sent
this evening to the list of Community Technology Centers' Network -
CTCNet), one of the largest nonprofit organizations working to bridge
the digital divide.)

CTCNet's annual conference is going to be in cleveland in june, 2005, in
case you (or any of the othe inkscape developers) might be in the area
at that time. it's likely more than 1000 technology access activists
will be attending this conference. stephen quinn is the wonderful
person organizing this conference. squinn@ctcnet.org

thanks again. you've inspired many by creating inkscape and your
creation will unleash a river of artistic creativity by many who cannot
afford a commercial vector drawing program.

- phil shapiro
arlington, virginia

Just want to add my appreciation of the work done on Inkscape. Very impressive!

shic (309152) on Monday December 20, 2004

Thank you! I'm by no means a graphic artist, but every few months I find I need to draw a diagram for a document, or a simple logo, or a form of some sort or other. Back in the late 80s/early 90s I used RISCOS and "!Draw" which I found to be awesome. I move to SUNOS, then SOLARIS, then Linux before finally requiring Windows (don't ask) as my primary platform - and until today I have been extremely unimpressed with the options for vector graphics. Until you mentioned Inkscape I'd done everything from battling with XFig and Latex to being confused by Adobe Illustrator - which was serious overkill for a simple letterhead design. Inkscape already seems to meet my needs - the first program, commercial or otherwise, I've found in the last 15 years since !Draw which deserves this acolade. I think Sourceforge should promote this project more actively - it deserves to be project of the month or something in order to raise awareness.

http://slashdot.org/comments.pl?sid=133308&cid=11135973

I am not a visual person.

I am not a designer, not a drawer, not a painter, not a photographer.

I'm a man of words, really, if I need to be creative, it's words.

Having said that, can I sue you for the time I've lost playing with
Inkscape? No? Goddamnit.

It's wonderful. Intuitive. The 'everything should be keyboard
accessible' philosophy rocks. It has everything.

Yesterday I tried, to amuse myself, making a mockup panelling for a
comic that I'm working on with a visual artist (you guessed it - I
mostly do the words :P).. it's incredible how painful proper layout with
CSS can be. As these things go, 'to amuse myself' turned into a holy
crusade and I would not rest until I could churn out professional layout
mockups by the dozen. So I got Inkscape.

The next 2 hours were spent rotating and resizing stars and occasionally
saying 'wow'. I shake my angry fist at you all.

Daniel

Date: Sun, 6 Feb 2005 16:14:27 +0100
Subject: [Inkscape-user] Presentations with Inkscape

Hello,

I'm currently preparing a talk and thus looking for a presentation
software. The following criterias have to be met:

* open source software
* should either run on my Apple iBook, a NetBSD system, or both

I've been toying with Inkscape lately, and I enjoyed drawing some
figure for the talk. It's real fun to use all the nice features like
rounded boxes, transparency, etc. Inkscape provides.

So while I was at it, I just went ahead and created the correspondent
presentation slide. It took some time until I actually discovered
"inkview" -- you should definitely place a note somewhere, so people
will find it! But this is just the thing I was looking for. No fancy
transitions and other useless stuff, but clean font rendering and nice
figures. Fonts actually render much cleaner than in Apple Works'
presentations. It's a lot faster than batik-slideshow, plus it scales
the slide down, so you don't have to worry about that when you draw it.

So, I just wanted to thank you for this great piece of software, and
keep it up!

Just as a side note: I installed Inkscape 0.40 and all its dependencies
from The NetBSD Packages Collection [1] both on NetBSD and Mac OS X
10.3, and it works like a charm. (Except that I cant get fullscreen
output from inkview, but that may be related to Apple's X11
implementation.)

[1] <http://www.pkgsrc.org/>

Regards,
Christoph

----------

Inscape is a free, cross-platform SVG (Scalable Vector Graphics) format program that lets you create logos, illustrations and other drawings like commercial packages such as Macromedia Freehand or Adobe Illustrator.

http://ltc.smm.org/visualize/toolkit - Science Museum of Minnesota (3D Visulation toolkit)

[[Category:About Inkscape]]

Inkscape popularity

2006-07-05T03:10:16Z

GigaClon: Categorization

Inkcape popularity

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]]

FeatureNotePadArchive

2006-07-05T03:08:37Z

GigaClon: Categorization

----------
<i>wwwwolf writeth:</i>

WIREFRAME MODE

"Outline" mode. "Draft" mode. "X-Ray" mode. You know what I'm talking about. The mode where only the edges of the paths are drawn, stroked at constant width. Turn it off, and you have everything visible normally again.

I've seen this in Adobe Illustrator (Ctrl+Y), Sketch, Corel Draw!, even the good ole 1991 vintage Arts & Letters.

I think this is pretty important because I love to work with lots of overlapping, same-or-nearly-same-color objects that don't have strike at all. Would make drawing easier...

----------

<B>kwixson writes:</B>

Some little ideas that I haven't had time to fully spec yet, but I don't want to forget...

* Text tool can optionally draw (with click and drag, as opposed to just click) a text box of defined dimensions, into which text is flowed automatically.
* Cursor icons for Pen, Pencil and Calligraphy tools
* Visual cues for Pen tool cursor in append mode, and other modes (i.e., +, -, ^, etc.)
* Terminiate continuous draw mode when a path is closed in append mode

all DONE

<HR>

<B>Björn writes:</B>
1.) _Pressure sensitivity_
- Everybody else got it (Xara, Illustrator, even Gimp) and it is almost necessary for professional drawing.

------

Export .eps. Enough said.

------

Plan for fill&stroke:

First:

* remove "get from dropper" (always on, via [[SetColorSignal]]) (DONE, no signal necessary, just picks new color from selection)

* remove "mode", make global preference "Store colors as rgb/cmyk" (DONE, it's not about storing color actually, so just removed)

* remove redundant color picker selector (DONE)

* transientize, remember size&position, remove Close in the color selector window from Doc props; find if there are others like it (DONE)

* Make evenodd switch a pair of toggle buttons inside colorselector (DONE)

Then:

* remove "apply to"; make all shapes use current color, but on prefs page for each tool, make a switch between "use current" (default on for shapes) or "use its own style" (default on for pens & text), plus a button "take style from the selection". (DONE)

* enable partial color settings (bug http://sourceforge.net/tracker/index.php?func=detail&aid=937393&group_id=93438&atid=604306; actually that will be a separate "adjust colors" dialog)

* add master opacity from object props (DONE)

----------

Provide a UI mechanism where one can cycle through just those object intersected by a pick point. That is, in a large, heavily overlapping graphic, you could point at the thing you want (even though it's behind three or four other things) and quickly choose that object, either from a menu, or by some form of constrained "tab-key" operation.

DONE with Alt+click

----------

How about a better way to parse the xml code? The files are way bigger than they need to be, and it would be nice if there was an option to tidy up the code upon saving.

-- use svgz or plain svg, or both
---------

In selector top panel, make a frame titled "Transform" and covering 4 toggle buttons: stroke (works), rounded rect corner (works), gradient, pattern (need to fix for paths stored-optimized, then add optional compensation in item_write_transform; first to fix the wrong patternTransform application)
-------

Textboxes (multiple shapes, and text-box linking to make the text-flow)
DONE
------

auto "add" new gradient when switching an object to gradient in fill&stroke, instead of reusing the last one used

DONE
------

3. Is item visibility supported? I see the checkbox in Item Properties
but it appears to always be disabled. However, even if it did work,
having to open up and mouse over to extra dialogs is very time consuming.
When working with complex images in Illustrator I am all the time flipping
visibility and sensitivity on/off and it's a quick process because you can
toggle it directly from the layer view. It would be nice if the XML
viewer had a check-box or something right next to each item for quick
visibility and sensitivity changes (see how Layers work in The Gimp,
Illustrator, and Photoshop).

DONE
-------------------------
There are still many artists who use very old versions of Illustrator and Corel Draw so as to get the very most out of cheap hardware and hopefully that is a market that [[InkScape]] can soon grab.
Jasc Web Draw is adequate but if [[InkScape]] can provide a consumer friendly user interface it will serve as a big kick in the Pants for Jasc and hopefully force them to improve their low budget Vector Graphics toy.

-------------------------
when creating a new object, it should have the same attributes as the last
I mean: drawind shapes, if I set one to stroke and fill of a certin kind, each after that should start with the same
until I change it. a palette would be nice, but this is a little different.
if I draw a rect, then set it to blue, 1px black stroke, then draw another, it should be blue, 1px black stroke
these are not settings that are save from session to session, just while working.
small detail, but it'd make things much easier.
in minimum it should behave differently for shapes/text
You definitely do not want text to appear colored/filled by default

-- aduhan

DONE
-------------------------
swingincelt writes:

Apply transform function is something I'd really like to see.

-- doable by switching to "store transforms: optimized"
----------
axiom writes:

Not sure where this goes, but when I have some text, why does all the text in the frame have to have the same attributes? What if I want to have some letters a different color? There is apparantly no way to highlight text

DONE
----------

(DONE) A "New"/"Change" label in all drawing tool toolbars changing depending on whether you have an object of the corresponding type selected

------

Store/guess export filenames for objects; an attribute of spitem, inkscape:export-as=, settable when exports selection and selection contains only one item; fill it in in the dialog; when not set, guess it from prev/next siblings by in/decrementing their filenames' numeric parts (DONE except for guessing, which is likely to be confusing).

------

(DONE) Implement "select under" by ctrl-alt-clicking in selector: Stay in one place and ctrl-alt-click repeatedly watching the statusbar that shows what is selected, it will cycle through the entire stack of objects _at this point_ (not all objects in the document).

------

better gradient editor: ideally arbitrary stops, one color widget that switches to the selected stop (DONE)

------

When opening a file from an empty unchanged document, replace it with the opened one instead of opening a new window (DONE)

------

Write a function to compare two reprs' positions regardless of their parents, by scanning the entire tree (unless they have the same parent, in which case the sp_repr_compare_position() is used) and declaring the one that is run across first to be the lower in z-order. Use it whenever z-order matters (splivarot now has such a function in boolean_op, rather ugly but works).

------

Then make a function next-overlapping and prev-overlapping which finds only overlapping objects; use them in raise/lower commands so that the selection cycles through only the objects that overlap it, not all the objects of the document as now (this presently makes lower/raise almost unusable in large documents). (DONE)

------

Would it be feasible to have the # key toggle both the grid visibility
and grid snapping at the same time? (DONE)

------

Make 1) rubberband 2) eventually all drags scroll window when moved beyond edge. Common function to do that? (DONE)

------

paste in cursor location instead of the original; a separate command for paste-where-it's-from (DONE)

------

remove "clear all", provide "deselect" in edit menu instead (DONE)

------

8. Besides the grouping, visibility, and sensitivity stuff I'd like to
have a "path simplify" command. In Illustrator that takes a path and
removes redundant nodes within certain curve and angle tolerance.

::Done, although needs more work

10. Faster zoom features. I wish I could hit "zoom-out" 3 or 4 times and
not have it redraw each time. Or maybe have a saved zoom factor or
something that I can toggle. I like to zoom in and out a lot to look at
things so I want it to be really fast.

::Now zoom increment is settable in prefs, and there's a history of zooms; it does not redraw when zooms come in quick succession

12. The pencil tool (freehand draw) seems to create a lot more nodes than
Illustrator does. Illustrator must use a curve fitting algorithm or
something because it doesn't use as many nodes to create the path but it
still fits what you draw. Maybe it just uses a difference tolerance, I
don't know.

::Now the fitting tolerance is settable in prefs, and is higher by default

------

maybe_done must catch selection_change and zero its key, so that subsequent same-dir arrow-key movements of different objects are not lumped into one undo step

------

display font name in the statusbar description of text object

------

When more than one group (and possibly some non-groups) are selected, "ungroup" must ungroup all groups in the selection

-------------------------
The below is in regards to Sodipodi 0.32:

1. Is there any way to select individual items from a group? I know you
can open the XML viewer and select items but when you have 100's or 1000's
of items in a group this is extremely annoying and time consuming compared
to just clicking on the item in the artboard (otherwise I usually can't
even find the item buried in the XML list).

:ctrl-click

5. When selecting multiple items (holding down shift on the keyboard)
sometimes it loses the whole selection. I have no idea what causes this,
it may have to do with trying to click an item and "missing". Or it might
have something to do with accidentally dragging a bit while selecting.
Anyway, it is extremely annoying to carefully select 20 or 100 items and
then it happens and boom, you've lost the entire selection and have to
start over again.

:drag tolerance took care of it --bb

6. The "dragging" effect on nodes makes it nearly impossible to use a
tablet with Sodipodi and hard to use a mouse when working quickly.
Usually when creating a path I will quickly rough out the shape and I just
want normal straight, non-curved lines. So I want to click, click, click,
click and make the path. The problem is that if you even drag 1 pixel it
creates a curve or other strange things that I'll then have to go back and
correct. Instead of moving quickly I have to stop at each new point,

click carefully, then move the mouse to the next point. When using a
tablet it's pretty much impossible to click without moving the pointer at
all so this causes all kinds of problems (and not when just creating new
paths).

:drag tolerance took care of it --bb

-------------------------
I commend the inkscape team for picking the excelent language of C++ for development.

I sencerly hope that they use the language to its full potential by using the STL, inheritance and the other fine features that makes C++ a fine language to use. Otherwise it is a waste of time.

Remember, OOP is frustrating and takes a huge amount of time to do right, but when it is done the product is clean, extensible and almost devoid of bugs. Not that its impossible or even overy difficult to make an object oriented program in C, but using C++ with its built in support for virtual functions, protected functions and the like is a step in the right direction.

Well done! Make Bjarne proud!

-----
a knot must pass keyboard events it doesn't process to parent, so esc-deselecting works when mouse is over a resize handle

-------------------------
This is in regards to Sodipodi 0.32:

How can one add nodes to a path? There's a button (the one with '+') but
it adds a node in the middle of a segment. However, most of the time I
want to add a new node AFTER the last node!

Current behaviour: O - - - - - - - - - - - O ===> O - - - - - O - - - - - O

What I want to have: O - - - - - - - - - - - O ===> O - - - - - - - - - - - O - - - - - - O

: While in pen or pencil tool, press CTRL+A to toggle append/add
: modes.
: In Append mode currently selected path has miniature 'anchors',
: that turn red if mouse is over them. Starting new line, while
: anchor is highlighted appends new line to the old (i.e. you can
: add as many points as you like using pen tool).

:In node edit you can press ctrl-d on a node to duplicate it.

Also, in the same spirit, how do you easily join two paths? I mean, say
you have 2 separate segments, and you want to change them into one
triangle. How do you do that? Currently, I have to "compound" them,
select a end node of each path, and click the "-" button; but then, they
merge into a middle point. This would'nt be so much of a problem if it
was easier to add a point to a path!

: I think latest CVS version has 'join with line' option in
: node toolbox.
: Also combining segments (combine tool), and using either pen or
: pencil in 'append' mode allows you to connect existing
: segments from anchors.

-- Nicolas MONNET

-------------------------
First - good name. Does name matter? Yes, if it is to be widely accepted it must sound professional and Inkscape sounds professional.

Second - good move to clean up code and standardize and C++ is a good, widely accepted language (ie every programmer knows it)

Third - please clean up the menus - I tried to use Sodipodi and the menus were very hard to use.

Fourth - the export to rasters like png are a very needed item.

Thanks for your efforts.

---------------

7. Sodipodi seems to crash a good bit. I get afraid to use certain
operations. For most normal work (when just working with nodes and paths)
it seems very stable but when I start combining paths, importing files,
and dragging stuff around in the XML viewer it doesn't take long before
the crash happens. It's usually not a crash that brings up the crash
dialog. It's the kind where you blink and Sodipodi is just gone. I have
also had it crash when I accidentally randomly and quickly click 3 or 4
times on the artboard while drawing. Actually, just doing anything
randomly or quickly seems to make it crash (zooming in/out, clicking lots
of buttons and hotheys). Sorry I can't be more specific, I'll try to
follow more closely what's going on when it crashes.

-------------

I also found the menus particularly hard to use.

I find the whole concept of a "dialogs" menu to be extremely abberent and a rather useless nonsense grouping about as much use as dumping them under "miscellanous". There is also a whole lot of functionality in the Toolbox and various dialogs that I expected to find as a menu item but did not which rather threw me for a curve ball.

I'd like the menus to be at least similar to Adobe Illustrator so that I any learning I do can be reapplied and put on my CV as a skill that managment types will recognise rather than give me funny looks for (the GIMP is still not a funny name, it is just embarassing).

I cant wait to see Sodipodi and Inkscape compete and improve each other.

-------------------------
Sodipodi is very nice, although I have a huge dislike for the interface - while original, it feels very "cludgy" to use. I would love to see a gimp-1.3 inspired interface (1.2 wasn't very nice with it's window juggling but 1.3 has a much nicer drag and drop way of organising & grouping the windows you use more often). With a ui overhaul Sodipodi/Inkscape could be very, very nice.

----------------

BTW, is there already some good user-documentation for Sodipodi/Inkscape? Because as a user, I don't mind how bad the code is and how much dead code there is, all I need is a manual to learn that other 90% of the app. With a manual I can really *use* the program, find bugs, and file bugreports....

[[Category:Wiki Attic]]

ColorPalette

2006-07-05T03:07:09Z

GigaClon: Categorization

=== Custom Palette ===

For fill colors and gradients there needs to be be a 'custom
palette', so that the user can "bookmark" particular colors or gradients
for future use. Twelve small buttons should be added in the Color paint
area of the Object Style Dialog, and should show up to twelve custom
colors/gradients. When a button is clicked, the color or gradient
settings in other widgets should be changed to match. There should also
be a straightforward way for users to add/remove/change items in the
color palette.

=== Palette Files ===

Each document has its own custom palette, which is initially blank.
The user can load or save palettes to palette files, in standard formats
consistent with other graphics software.

A global palette.svg file should be installed with Sodipodi, that provides the default palette settings for a blank document. This can include colors as well as any gradients listed in the global gradients.svg file (see the Object Style Gradients task). We must build a reasonably complete palette (e.g. all named HTML colors), along with the most common gradients (e.g. black-to-white, black-to-transparent, white-to-transparent, both vertical and horizontal).

Optionally, the user can have a palette.svg file in their home
~/.sodipodi directory. If present, this will be loaded instead of the
global default file, overriding it. This file may refer to gradients in
both the global gradients.svg file, as well as a gradients.svg file in
the user's ~/.sodipodi directory.

(suggestion: possibility to import .acf (Ascii Colour File?) and .bcf (Binary Colour File?) from Macromedia Freehand - .acf, since is a .txt based file (each colour channel is 16bit, meaning 48bit for RGB and 64bit for CMYK), seems to be an open format since it's a .txt )
(importing .acf and .bcf can be really useful when colour norm companies patented their colour standards (which makes difficult Inkscape distributing these ones), and lots of vectorial apps users are still hugely dependant of these colour norms)

example of Macromedia Freehand .acf palette file (converted from Unix rgb.txt):
http://wiki.inkscape.org/cgi-bin/wiki.pl?UnixRgbAcf

(question: how far Inkscape (as open-source app) can use known pallete norms, like Pantone, Focoltone, Toyo, Munsell, etc., since some of these are patented, as well copyrighted? - this question has meaning when lots of vectorial-editor users uses intensively these palette norms)
(note: contacting personally each colour norm companies is more than welcome, even expecting negative feedback as i got from Trumatch, which said it's patented and copyrighted, and they licenceed to software systems - my proposal: with artists and engineers help, how about us making an open-source project for a colour norm, regreting print and display, and trying to make it the most popular (even on offset printers, and inkjet/laser printer manufacturers!) colour norm than ever?)

=== Color Dropper ===

Status: Halfway implemented, needs more work.

If the current palette has one or more undefined entries, then when
one selects colors with the dropper, then they are automatically added
to the palette, unless the user is holding the 'ctrl' key.

See also [[CurrentColorWidget]]

=== Color Defaults Indicator ===

In [[The_Gimp]], there is an indicator showing the current foreground and
background colors. If the user clicks on them, color selectors pop up
to allow making different selections.

Sodipodi needs an analogous mechanism, but it should include current
fill and stroke color settings.

=== Other suggestions ===

* Having custom palletes, like from Gnome
* Accuraced palettes from colour norms, like Pantone, Trumatch, Focoltone, Toyo, etc. (since lots of people uses it, specially professionally)
** problem: some are patented/copyrighted, which seems each norm company like this must be contacted for authorization (?) - as well, is also an open-source colour norm standard welcome? (which works on both video/printing outputs, like Pantone seems to be?)

=== References ===

[http://sourceforge.net/tracker/index.php?func=detail&aid=468485&group_id=4054&atid=354054 "468485 - custom palette"]

[http://sourceforge.net/tracker/index.php?func=detail&aid=469121&group_id=4054&atid=354054 469121 - "Curve editing and right click menu"]

-----

It would be really nice if we could use the same color palette format as [[The_Gimp]]. I know that it ruins the nice XML/SVG consitency thing - but it means we get lots of palettes for free and potentially a website could have one palette that they use across all tools. --Ted

[[Category:Developer Discussion]]

ColorPalette

2006-07-05T03:06:31Z

GigaClon: Categorization

CompilingYellowDog

2006-07-05T03:03:59Z

GigaClon: linkage

== YELLOWDOG Linux 3.0 ==

It's pretty straight forward as with most of the current distributions.

First of all, unpack the latest inkscape.tar.gz:

$ tar zxvf inkscape-0.35-pre0.tar.gz

Try to ./configure and find out that you need libpng.
Next try to understand that although `yum install libpng' says that you have the latest working version for your system, you still cannot get Inkscape to compile (the reason is that you need libpng-devel for this.)
Since there is no Yellowdog RPMs for libpng-devel, go to http://www.libpng.org/ and download the latest tarball (1.2.5 works fine), ./configure, make, and make install.
Go back to your Inkscape source directory and re./configure.<br>
Inkscape will happily compile now!<br>

-- Daniel Dïaz
[[Category:Developer Documentation]]

Inkscape invariants

2006-07-05T03:02:27Z

GigaClon: /* Invariants of InkScape */

=== Invariants of [[Inkscape]] ===

These are the founding goals for Inkscape that we'll be adhering to in this project.

* Full SVG (plus XML, CSS2) compliance
* Core written in C/C++
* Gtk-based user interface following the standards set out in the GNOME HIG
* Emphasis on a small core and extensibility. Extensions should be first-class citizens, so we can say "no" to features in the core without guilt.
* Open, community-oriented development processes
* Baseline is the [[SodipodiHydra]] codebase
* Where a better solution cannot be found, default to the way Illustrator does it.

[[OtherGoals]] - discussion of general project objectives and motivations

[[Category:About Inkscape]]

Branding

2006-07-05T03:01:54Z

GigaClon: Categorization

=== Name ===

Inkscape: Open Source Scalable Vector Graphics Editor

* Inkscape should be capitalized (not BiCapitalized), and is only one word. Inkscape is not named Inkspace.

Incorrect: inkscape, Ink Scape, Inkspace, InkScape

=== Tagline ===

Draw Freely.

(watch capitalization, and don't forget the full stop)

=== Logo Treatment ===

Colors:

* 1-color: Prefered colors (in order of preference) are black (on lighter backgrounds), or white (on sufficiently dark backgrounds). The snowcap and rim line knocked out (transparent).

* 2-color: The mountain and ink should be black, and white (for the snowcap and rim line)

=== Sample branding image ===

upload:draw-freely.png

The font (available here: http://www.paratype.com/pstore/fonts/pushkin.htm) was made by Paratype from the handwriting of Pushkin, the greatest Russian poet of 19th century - who was also an artist, loved to do sketches on the margins of his manuscripts (using ink of course :) Pushkin's characteristic "flying" handwriting style and sketches (mostly profile portraits) are very familiar to anyone speaking Russian.

----
^^---
short remark:
the tagline "Draw freely" with a font that it is _not_ free is a contradiction for me ([[User:FZap]])

----

[[Category:About Inkscape]]
[[Category:Needs Work]]

Ikivo

2006-07-05T02:58:42Z

GigaClon: Categorization

== Ikivo Animator ==

[http://www.ikivo.com/animator Ikivo Animator] is an application that animates SVGt content for mobile devices. It has a treeview where svg elements are selected for animations. All animations appear in the timeline where they can be manipulated.

=== Major Features ===
* Animating Colors
* Animating Gradients
* Animating Opacity (including Gradient Stops, and entire Gradients)
* Animating Scale and Rotation
* Animating the display properties
* Animating Motion with editable splines and control points
* Basic Text Creation (Much better to use an external program to create text.)
* Animating the Pacing of Animations
* Save as UTF-8 or UTF-16
* Preview an svg as it '''should''' appear on a phone. (Sadly not all SVGt viewers have the same support)
** This is significant since most mobile phones that support SVGt use the [http://www.ikivo.com/02player.html Ikivo SVGt player]. (65 million Ikivo, 30 million others?? Reported at 3GSM 2006)
* Supports both OS X and Windows.
* Browsing/viewing for SVG Content and restricting all svg content to tiny.

=== Screen Shots ===
http://www.ikivo.com/img/ikivo_animator_anim1.gif http://www.ikivo.com/img/ikivo_animator_anim2.gif
----
[http://www.ikivo.com/animator Ikivo Animator] has more features that help with Animation but they don't seem to have any good tutorials on using these features. The Animator website '''really''' needs some more work.
* Recommended Retail Price $295 (2005, Ikivo Animator 1.1)

[[Category:Developer Discussion]]

Haypo

2006-07-05T02:57:14Z

GigaClon: Categorization

[[Galleries|Back to Galleries]]

Today (2003/02/21), just one picture :

http://www.haypocalc.com/perso/image/vache_qui_rit.ico.png

[http://www.haypocalc.com/perso/image/vache_qui_rit.png See full size], [http://www.haypocalc.com/perso/image/vache_qui_rit.tar.gz Source (.svg)]

Author : Victor STINNER (haypo), http://www.haypocalc.com/contact/

[[Category:Wiki Attic]]

EricWilhelm

2006-07-05T02:56:55Z

GigaClon: EricWilhelm moved to User:EricWilhelm

#redirect [[User:EricWilhelm]]

User:EricWilhelm

2006-07-05T02:56:55Z

GigaClon: EricWilhelm moved to User:EricWilhelm

Inkscape user, Perl/Python/Ruby hacker, and open-source CAD/graphics/engineering software developer. I have been producing, tracking, and contributing to multiple open-source projects for several years. Primarily focussed on CAD and engineering, I started [http://scratchcomputing.com/ Scratch Computing] and the [[VectorSection]] project as a way to build solid foundations for other developers so that open-source software can be more easily built on standards while also staying connected to the commonly used data formats of the proprietary software world.

Corey Burger

2006-07-05T02:56:07Z

GigaClon: Corey Burger moved to User:Corey Burger: Consistancy

#redirect [[User:Corey Burger]]

User:Corey Burger

2006-07-05T02:56:07Z

GigaClon: Corey Burger moved to User:Corey Burger

Corey Burger dabbles in the kiddie end of pool when it comes to Inkscape. You can see more about me on the [https://wiki.ubuntu.com/CoreyBurger Ubuntu wiki].

AnunciAlliberament044

2006-07-05T02:51:29Z

GigaClon: Categorization

Traducció de http://wiki.inkscape.org/wiki/index.php/ReleaseAnnounce044

== Inkscape anuncia la versió 0.44 :: http://www.inkscape.org :: Dibueixeu en llibertat ==

La comunitat de l'Inkscape ha alliberat oficialment avui la darrera versió del seu programari de dibuix d'imatges vectorials. L'Inkscape 0.44 satisfà una gran quantitat de peticions d'usuaris, suporta un gran nombre de característiques d'SVG, està traduït en més idiomes i afegeix molta velocitat i simplicitat.

Dels molts canvis notables en la interfície d'usuari s'inclouen un diàleg de capes, selector de color adjuntat, un diàleg de preferències redissenyat, una barra d'eines de text i noves icones. D'altres canvis més profunds inclouen centres de rotació persistents, indicació d'estil interactiva en la barra d'eines, dreceres de teclat configurables, millores en el retolador cal·ligràfic i la nova característiques per "escolpir nodes". I la exportació en PDF suporta transparències.

En alliberaments anteriors, es proporcionava un sistema experimental de connectors d'"Efectes", però sempre ha estat inhabilitat per defecte. Amb aquesta versió, l'equip pensa que ja està prou avançat, així que s'ha habilitat per defecte.

Per a dibuixos molt complexos, l'Inkscape ara proporciona un mode contorn, que millora el rendiment. El nostre suport a SVG s'ha incrementat més encara amb la implementació de l'etiqueta <switch>. S'ha implementat els perfils de color ICC per a les imatges. I centenars d'altres característiques i correccions d'errors.

També volem agrair Google per l'esponsorització de cinc estudiants per treballar en diferents àrees de desenvolupament de l'Inkscape: filtres SVG, especificació del protocol de pisarra compartida Inkboard, exportació a PDF amb Cairo i optimitzacions de la memòria.

Descarregueu els paquets per a Linux, Windows i Mac OS X:

http://sourceforge.net/project/showfiles.php?group_id=93438

Per a més detalls, veieu les completes notes de la versió 0.44:

http://wiki.inkscape.org/wiki/index.php/Release_Notes

I captures de pantalla enviades per la comunitat:

http://www.inkscape.org/screenshots/

===Quant a l'Inkscape===

L'Inkscape és una eina de dibuix de codi obert que fa servir el format de gràfics de vectors escalable SVG del World Wide Web Consortium ([[W3C]]). Algunes de les característiques suportades inclouen formes bàsiques, camins, textos, marcadors, clons, transparències, transformacions, degradats i agrupació. A més, l'Inkscape suporta metadades de Creative Commons, edició de nodes, capes, operacions de camins complexes, text a camí, text a formes i edició XML de l'SVG. També importa múltiples formats com EPS, <nowiki>PostScript</nowiki>, JPEG, PNG, BMP i TIFF i exporta PNG així com múltiples formats basats en vectors.

La principal motivació per a l'Inkscape és proporcionar a la comunitat del codi obert una eina de dibuix que suporti completament XML, SVG i CSS2 del [[W3C]]. D'altres feines addicionals inclouen convertir el codi base de <nowiki>C/GTK+</nowiki> a <nowiki>C++/GTKmm</nowiki>, posant èmfasi en un nucli lleuger amb potents característiques afegides mitjançant un mecanisme d'extensions, i la creació d'un procés de desenvolupament obert, amicable i orientat a la comunitat.

[[Category:Italian]]

BenutzerGalerien

2006-07-05T02:50:44Z

GigaClon: Categorization

== Urprungsfassung ==

Englische Ursprungsfassung [[Galleries|hier]]

== Gallerien ==

Füg hier einen Link zu deiner eigenen Inkscape-Galerie an

=== Clipart ===
* [http://openclipart.org Open Clip Art Library] (en)
* [http://edeca.net/site/graphics [[NauticalFlags]]] freie SVG-Flaggen (nautisches Alphabet; en)

=== Comics & Cartoons ===
* [http://www.poulejapon.com [[PouleJapon]]] täglicher Comic, gemacht mit Inkscape (en, fr, jap)
* [http://www.inkpipe.com Inkpipe.com] SVG-Cartoons und -Gekritzel (en)
* [http://www.xp-swiss.org/wiki/index.php?title=Comics_%28english%29 X-Coders] die XP-Swiss eXtreme Programming Cartoons (en)
* [http://lunar8.rydia.net/ Mental's Lunar 8 Comics] (en)
* [http://www.bakedbabies.com Baked Babies] (ein paar mit Inkscape erstellte Comics; WARNUNG: nicht für Kinder!; en)
* [http://thmayos.free.fr/inkscape/manga_inspiration.svgz Manga Inspiration] schnelle Zeichnung mit Inkscape 0.42 (SVG)

=== Artwork & Wallpapers ===
* [http://programmer-art.org/artwork Daniel G. Taylor's Art Page] (funktioniert wieder!; en)
* [http://www.le-radar.com/?art/galerie Cedric Gemy] (fr)
* [http://urke.deviantart.com/gallery/ Urke MMI] (en)
* [http://hooboo.free.fr/index.php franz. [[OpenOffice]].org Maskottchen] von Ben Bois, gemacht mit Inkscape (fr)
* [http://kde-look.org/content/show.php?content=16627 [[AmaroK]] Icon] KDE Artwork von Zekant (en)
* [http://kde-look.org/content/show.php?content=18204 Mupen64 Icon] KDE Artwork von Zekant (en)
* [http://www.volvoguy.net/ubuntu/ Ubuntu SVG Artwork] (en)
* [http://www.smartart.it/albums/wallpapers/abducted_1600x1200.sized.png Gentoo SVG Artwork] Wenn es sich bewegt, kompilier es!
* [http://www.kde-look.org/usermanager/search.php?username=salahuddin66 Großartige Wallpapers!] (en)
* [http://zvonsully.home.ro/ zvonSully Wallpapers] powered by Inkscape & SVG (en)
* [http://www.senses0.org.mv/popzees/artwork_white.html Artwork von Senses0 mit Inkscape] (en)

=== Künstler/innen, die Inkscape verwenden ===
* [http://www.dushkin.org/ Dushkin] ist ein Digital-Künstler des modernen Zeitalters. Die meisten seiner Werke sind mit Inkscape gemacht.

=== Inkscapebezogenes ===
* [http://popolon.org/inkscape/ Popolon Inkscape Tutorials and Illustrationen] das meiste auf Französisch, manches auf Englisch oder Chinesisch

=== Mit Inkscape erstellte Projekte ===
* http://www.hinterlandcasa.it SVG Panele & Buttons, gemacht mit Inkscape (it)
* [http://www.joncampbell.ca/inkscape/gallery.php Jon Campbell] Auswahl von mit Inkscape gemachten Projekten (en)
* [http://david.bellot.free.fr/svg-cards SVG-Spielkarten] (en)
* [http://nicubunu.ro/pictures/rpg/inkscape_rpg_map.png RPG-Landkarte] (Screenshot) von [http://nicubunu.ro/ Nicu Buculei]

=== Andere ===
* [http://inkscape.deviantart.com/ inkscape.deviantart.com] die Inkscape-Gruppe auf deviantART 1 (en)
* [http://inkscapers.deviantart.com/ inkscapers.deviantart.com] die Inkscape-Gruppe auf deviantART 2 (en)
* [http://zubauza.deviantart.com/gallery zubauza's Galerie @ deviantART] (en)
* [[Haypo]] (en)
* [[simarilius]] (en)
* [[Jofo]] (en)
* [[ChromeCat]] (en)
* [[Simondebelem]] (en)
* [[Gwyn]] (en)
* [http://ciberirmandade.org/gatonegro/index.php?option=com_mambospgm&Itemid=27 Gatonegro deseño - gatonegro.co.nr] (esp)
* [http://www.insert.waw.net.pl/vector/firecat_large.jpg Piotr Kosmala]
* [http://erture.webpark.pl/vinci.html Radek Turek] (en)
* [http://haef.szm.sk/ Henrich Fichna] (en)
* [http://blog.die-scheiss-kiste.de/wordpress/ Andy's Blog] Blog; Inkscape ist eines der Themen, mit Beispielen und freien SVG-Downloads (de)
* [http://www.dirk-hoeschen.de/content/index.php?opi=view&id=8 Bevel Tutorial] Tutorial für Anfänger/innen über das Erzeugen von Schrägen-[[/Kanten]]-Effekten mittels Farbverläufen (de)
* [http://imaginaciongnu.tk Imaginación GNU] (esp)

[[Category:German]]

ArticlesEtPresentations

2006-07-05T02:49:06Z

GigaClon: Categorization

== Wiki d'Inkscape ==
C'est une aire libre pour le developement et la discussion d'Inkscape.

La version FR est en cours de traduction, vous pouvez consulter la version plus complète en anglais : [[ArticlesAndPresentations]]
ou aider à la traduction.

Si vous désirez en savoir plus a propos de la [[WikiSyntax]]?

<table cellspacing="11" width="100%"><tr valign="top">
<td style="width:33%;background-color: #EFFBFF; padding:.5em; border: 1px solid #BFEEFF">
=== A propos d'Inkscape ===
* [http://www.inkscape.org/?lang=fr Page principale d'Inkscape]
* [[AProposdInkscape]]
* [[FonctionaliteesDInkscape]]
* [[FAQ]] - Foire Aux Questions
* [[InformationsSurLeProjet]]
* [http://inkscape.org/cgi-bin/wiki.pl?SupportedOperatingSystems Systèmes d'Exploitations Supportés]
* [[Tools]] - Outils et applications supportées
* [[Galleries]]
* [[ArticlesEtPresentations]]
* Témoignages
* PopularitéesDInkscape
* [[ContactInfo]] nos heros

</td><td style="width:33%;;background-color: #[[FFF1EF]]; padding:.5em; border: 1px solid #[[FFC7BF]];margin:.5em">
=== Documentation Utilisateur ===
* [[InkscapeTerminologie]]
* [[ManualUtilisateur]]
* [http://inkscape.org/doc/index.php?lang=fr Didacticiels]
* [[InkscapeSVG]] par rapport au plain SVG
* [[ActiverLesExtensions]]
* [[ActiverLesEffets]]
* [[QueFontLesEffets]]
* [[UtiliserLOutilConnecteur]]
* [[Installer les fontes en tant qu'utilisateur]]

* Notes de version pour la 0.43 et les précedentes
* [[AnnoncesdePresse]] pour la 0.43 et les précedentes
* [http://inkscape.org/cgi-bin/wiki.pl?ArticleIntroducingInkscape0_40 Introduction à Inkscape 0.40 (en anglais)]

* [[AutresProjets]] (liens externes)
</td><td style="width:33%;background-color: #FFFAEF; padding:.5em; border: 1px solid #[[FFE9BF]]; margin:.5em">
=== Aider Inkscape Sans developpement ===

* [[RechercheAide]]
* CréerDistro: Comment faire des Paquets
* [[EditerLeSiteWeb]]
* [[EcrireDesNouvelles]]
* [[MettreAJourLesElementsDuSuivi]] Items
* Idées[[DeDidacticiels]]

* [[TesterInkscape]]

</td></tr></table><table cellspacing="0" width="100%" style="background-color: #FFFAEF; border-width:0em .5em; border-style:solid; border-color:white"><tr valign="top" style="padding:11px 0em 0em 11px">
<th colspan="2" align="left" style="padding:.5em 0em 0em .5em">
=== Documentation Developeur ===
</th></tr><tr valign="top" align="left"><td style="width:50%;padding:.5em">
==== General ====
* [[ManuelDevelopeur]]
* [[CompilerInkscape]]
* [[TravaillerAvecLeCVS]]
* [[GererLesPreferences]]: Créer et utiliser les réglages des préférences.
* [[AddSPObject]]: Comment ajouter un nouveau type SPObject
* [[ReprListeners]]: Répondre aux changement du document XML
* [[ErrorsAndWarnings]]: how to deal with reporting errors, warnings, and other messages
* [[DebuggingTips]]: divers astuces pour aider au problèmes de debuggage.

* [[DeveloperTitles]]: Termes four differents rôles dans Inkscape
* [[InkscapeJanitors]]: Petites tâches qui ont besoin d'être éffectuée
* [http://livarot.sourceforge.net/ Livarot]: Pour les opérations booléennes

</td><td style="width:50%;padding:.5em">
==== Discussion de developpement ====
* [[Roadmap]]: la principale TODO liste
* [[NewFeatureProposals]]
* [[ExtensionArchitectureProposals]] - Propositions de l'architecture d'extentions
* [[Coding Style|Discussions sur le style de développement]]
* [[FileTypes]] - Formats de fichiers
* [[Icons]] (Application + Interface)
* [[ApplicationIcons]] ( plus d'application + interface )
* [[InkscapeColor]] Les couleurs dans Inkscape
* [[PrintingSubsystem]]
* [[SVG Competitors Plan]] - MS WVG vis a vis de SVG, etc
* [[SVG Tiny Compliance]] - Compatibilitée SVG Tiny
* [[SVG Test Suite Compliance]] - Suite de test complète [[W3C]]
* [[CSS Support]] - Support CSS
* [[OpenVG]] Standard (brouillon)
* [[OpenDocument proposal]] - Proposition pour [[OpenDocument]].
* [[Googles Summer of Code]] - L'été du développement de Google

</td></tr><tr valign="top" align="left"><td style="width:50%;padding:.5em">
==== Discussion sur L'Interface Utilisateur ====
* [[TranslationInformation]] - Informations de traduction
* [[AccessibleGraphics]] - Graphiques accessibles
* [[ObjectManager]] - Gestionnaire d'objets
* [[DialogsReorganization]] - Réorganisation des dialogues
* [[DialogReplacement]] - Remplacement des dialogues
* [[ModalInterfaces]] - Interfaces modulaires
* [[TextUsability]] - Outils de texte/dialogue dialogue
* [[KeyboardShortcutsToDo]] - Raccourcies claviers à faire
** [[KeyboardProfiles]] - Comment aider à la gestion des différents types de clavier
* [[StatusbarAPI]] - API de la barre d'état
* [[Animation]]
** [[Animation-(Timeline)]] - Ligne de temps pour l'animation
* [[Free Desktop Graphic Suite]] - Suite graphique en logiciel libre

</td><td style="width:50%;padding:.5em">
==== Discussion de réachitecture ====
* [[SubsystemRearchitecture]] Réachitecture des sous-système
* [[CPlusPlus]] - Convertion vers C++
* [[Pangoification]] - Replacer le sous-système de rendu des fontes
* [[GtkMMification]] - Remplacer le code C en objets gtkmm
* [[PathRepresentation]] - Representation des chemins
* [[Cairoification]] - Utilisation de la librairie Cairo
* [[ScribusInteroperability]] - Interopérabilitée avec Scribus

</td></tr></table>
----
* [[WikiAttic]]: pages qui ne sont d'actualitée, mais ɡardées pour des raisons historiques

[[Category:French]]
[[Category:Needs Work]]

Acerca de Inkscape

2006-07-05T02:39:00Z

GigaClon: Categorization

Inkscape es una herramienta de dibujo multiplataforma de código abierto para gráficos vectoriales, que utiliza el formato abierto SVG (Scalable Vector Graphics) recomendado por el [http://www.w3.org/ World Wide Web Consortium] (W3C).

[[Category:Spanish]]

Features of Inkscape/fr

2006-07-05T02:21:16Z

GigaClon: Categorization

Il est difficile d'acceder à un logiciel sans connaitre ce qu'il peut et ne peut pas faire. Voici donc une vue globale des fonctionalitées d'Inkscape, ainsi que certaines planifiées pour le futur.

== Fonctionalitées déjà présentes ==

=== Création d'objets ===

* Dessiner : lignes à mains levées (avec des chemins simples), courbes de Bézier et des segments de droites, calligraphie à la plume (dessin à main levée utilisant des chemins remplis representant les touches calligraphiques, plume ou pinceau).
* Outils de formes : rectangles (peuvent avoir des angles arrondis), ellipses (incluant cercles, arcs et segments), étoiles/polygones (peuvent êtres arrondis et/ou modifié au hazard), spirales.
* Outil texte : texte multiligne, édité directement sur l'image, pouvant suivre un chemin ou fermé dans une forme. quelconque)
* Bitmaps (inserer des bitmaps ou conversion d'objets selectionnés en bitmap)
* Clones (copies d'objets liées dynamiquement), incluant un outil pour crée des motifs et différents arrangements de clones comme des mosaïques.

=== Manipulation d'objets ===

* Transformations affines (déplacement, changement d'échelle, rotation, torsion), chacunes interactives sur le dessin et/ou en spécifiant les valeurs exactes.
* Opérations de tri-Z (profondeur)
* Groupement d'objets, avec la possibilitée de « selectionner un groupe » sans défaire un groupe, ou d'entrer dans un groupe comme si il s'agissait d'un calque temporaire.
* Calques, avec la possibilitée de verouiller et/ou cacher chaque calque individuelement, de les réorganiser. Les calques peuvent être gerés en arborescence.
* Copier et coller des objets.
* Commandes d'alignement et distribution, distribution en grille.

=== Remplissage et contour ===

* Selecteur de couleurs (RVB, TSV, CMJN, roue de couleur)
* Pipette de couleurs
* Copie/colle du style des objets.
* Éditeur de gradiant permettant des gradiants à multiples intermédiaires.
* Remplissage par motifs (bitmap, ou vectoriel).
* contours hashurés, pointillés etc..., avec differents hashages prédefinis.
* Marqueurs de chemin (e.g. extrémités de flèches, découpage, etc...)

=== Opérations sur les chemins ===

* Édition de nœuds : Déplcaer les nœuds et les poignées de contrôle de nœuds de Bézier, la distribution et l'alignement des nœuds, etc.
* Conversion de chemin : Depuis les objets texte, formes, ou conversion de contour de chemin en nouveau chemin.
* Opérations booléennes sur les chemins.
* Simplification de chemins avec seuil de simplification variable
* Rétrecissement (ou érosion) et Dilatation des chemins, avec notament des offset liés ou dynamiques des objects.
* Vectorisation de bitmap (En couleur ou noir et blanc)

=== support du texte ===

* Texte multilignes.
* Utilise n'importe quelle fonte installée dans le système, uncluant les écritures gauche-droite et droite-gauche.
* Kerning, modification dynamique des espaces entres les lettres et entre les lignes.
* Texte sur chemin (Les textes et chemins restent éditables et son modifiés dynamiquement, directement sur l'image).
* Texte dans un chemin (remplit une forme en fonction des contours).

=== Rendering ===

* Affichage totalement antialiasé (décrénelé)
* Support de la transparence alpha pour l'affichage et l'export PNG
* Rendering dynamique et interactif complet des objets WYSIWYG.

=== Divers ===

* Visualisation et édition complète de l'arborescence du document avec l'éditeur XML
* Export PNG et [[PostScript]]
* Options de commande en ligne pour l'export et les conversions (pratique pour les scripts).
* Edition et géneration d'un fromat de fichier totalement compatible SVG
* Visualisation du meme document dans plusieurs fenêtres (avec differents zoom).

=== Effets ===
Ne sont pas considérées comme stables, s'activent via les préférences.

* Interpolations de formes et de couleurs entre 2 objets.
* Déformation fractal (algorithme de Koch, arborescence)
* ondulation des chemins.
* Ombre portée.
* Dessin des nœuds.
* Fret de guitare.
* ...

== Fonctionalitées dans la version de développement ==

* Modification des courbes chemin en tirant directement la courbe.
* Support des tablettes graphiques (surtout interressant pour l'outil calligraphique et tracé à main levée), gère la pression et l'inclinaison.
* Tableau blanc réseau, via le protocol jabber.
* Connecteurs dynamique entre différents objets avec évitement d'objet désirés.

== Fonctionalitées planifiées ==

* ... plus fonctionalitées

== Suivi [[SourceForge]] ==

[http://sourceforge.net/tracker/?atid=604309&group_id=93438&func=browse Demandes de fonctionalitées sur le suivi de [[SourceForge]].net]

[[Category:French]]

Documentation translation

2006-06-27T21:14:42Z

GigaClon: Categorization

== Tutorial Translation ==

Inkscape tutorial sources are in Docbook XML format, with illustrations in SVG. If you want to translate one or more tutorials, first download the Docbook source here:

http://svn.sourceforge.net/viewcvs.cgi/inkscape/doc-docbook/trunk/

Each tutorial is in its own subdirectory. You need the *.xml file, for example basic/tutorial-basic.xml. You could get it and simply replace all English text in it with the text in your language, preserving all XML markup. See README at that location for some notes on markup. Other (better) ways are described below.

* If there's already such a file in SVN, you can edit it instead :) If there's no xml file at the above location but there's a translation of this tutorial in SVG format (in share/tutorials in Inkscape distribution), you'll need to convert it to Docbook (and probably update). Conversion can be done simply by: select the text blocks of an SVG tutorial in Inkscape, Ctrl+C, and Ctrl+V in your text editor, then add the markup.

* Save your file as <original name>.<language suffix>.xml, for example basic/tutorial-basic.es.xml for Spanish.

* Do not use symbolic entities like &aacute; (they're not defined in XML without a DTD). Instead use either numeric entities such as &#225; or simply write your text in UTF-8.

* Most illustrations don't need translations, so you leave the references to them from English XML intact. If however an illustration has some text that you want to translate, open the illustration file in Inkscape (e.g. basic/basic-f12.svg), edit it as needed, and save under a different name (e.g. basic/basic-f12-es.svg). Then change the filename reference in the XML source appropriately.

* When finished, run [http://xmlsoft.org/xmllint.html xmllint] on your file to make sure it's well-formed: <code>xmllint --noout --noent --valid <filename></code>

* Send the file to Joshua Andler <scislac at users dot sf dot net>, and he'll convert it to SVG and HTML and upload it to SVN and the web site.

* If after that you want to make any changes, download the file from the above location again, because it may have changed compared to the one you have.

===Tools===
* OmegaT - http://www.omegat.org/omegat/omegat_en/omegat.html
* Transolution - http://transolution.python-hosting.com/
* xml2po, see below

====Transforming XML into PO files====
One can also use xml2po to get PO files out of the XML sources, and also transform the PO files back to XML. After you have a PO file, follow the instructions for editing those files below.

xml2po is available in gnome-doc-utils (http://ftp.gnome.org/pub/gnome/sources/gnome-doc-utils/).

Here are some command lines that were used to translate a German tutorial (the de-locale), please adapt accordingly until we nicely integrate this into our Makefiles.

<pre>
## use this at the very beginning, when there is no translation at all:
xml2po --output=basic/tutorial-basic.pot basic/tutorial-basic.xml

## use this when there is a *.de.xml, but you want a de.po:
xml2po --output=basic/de.po --reuse=basic/tutorial-basic.de.xml basic/tutorial-basic.xml

## xml2po is not happy when this directory doesn't exist:
mkdir .tmp.basic

## use this when the tutorial-basic.xml has been updated and you
## want the new stuff in your de.po:
xml2po --update-translation=basic/de.po basic/tutorial-basic.xml

## use this to create a tutorial-basic.de.xml from your de.po (ScislaC
## will use this file to create the final tutorial SVG file)
## WARNING: Unfortunately, this doesn't put localized screenshot
## file names into the xml file!
xml2po --po-file=basic/de.po basic/tutorial-basic.xml > basic/tutorial-basic.de.xml
</pre>

== Keyboard and mouse translation ==

* TBD

== User Manual ==
* See also [[Embedded Help]]
* First download the user manual xml document from [http://svn.sourceforge.net/viewcvs.cgi/inkscape/user_manual/trunk/xml/ SVN]
* edit the trunk/xml/inkscapeUTF.xml file. All languages are inside.
* Just read the file, choose the language reference you want to use (en, fr...) and translate by duplicating the node and changing lang attribute to yours.
* when finishing editing, if necessary edit the Makefile and add your language to the Makefile. In every case test your file with some tools (xmllint...) or just type again "make your_language" : syntax errors will be displayed : please correct them.
* submit your work as a patch in the patch tracker and warn Cédric Gemy (cedric at le-radar.com) by email.

== Man pages ==

* first download inkscape.pod from [http://svn.sourceforge.net/viewcvs.cgi/inkscape/inkscape/trunk/inkscape.pod?view=log SVN]
* rename it to inkscape.xx.pod, where xx is the code for your language
* open inkscape.xx.pod in your favourite text editor (pay attention to encoding which must be UTF8), and directly translate in the file.
* you can take a look at a first example of translation with inkscape.fr.pod
* finally, submit your work in the patch tracker and drop a mail to the inkscape devel mailing list.

[[Category: Developer Discussion]]

ClipBoard

2006-06-27T00:57:55Z

GigaClon: Categorization

I think the best way to handle the clipboard is to make it an SPDocument in its own right. When object(s) are copied to the clipboard, we should:

1. compile a list of objects and their dependencies (eliminating duplicates -- see [[DependencyTracking]])
2. clear the clipboard SPDocument
3. use some (currently unwritten) facility for bulk-copying SPObjects (see [[BulkObjectCopy]]) between documents with references intact to copy the object list to the clipboard document

When pasting, we just use the same bulk object copy facility to copy from the clipboard SPDocument to the destination document (which may or may not be the origin document).

Question: should we handle SPUse specially?

Eventually, we should look at things like taking advantage of e.g. [[StockLibraryInterface]] to avoid creating unneeded duplicates of things like referenced gradients when pasting into the same document. But that's icing.

-----

There's a user-visible behavior page now under [[ClipboardBehavior]]

[[Category:Developer Discussion]]

CinePaint

2006-06-27T00:56:54Z

GigaClon: Categorization

Cinepaint

Animation/Film app based on GIMP, allowing us to edit a film from a picture sequence (very useful and unique feature)

http://cinepaint.sourceforge.net/

[[Category:Needs Work]]

Cenon

2006-06-27T00:52:38Z

GigaClon: Categorization

Please post links to screenshots and/or insights of this vector app. We must learn from others.

=== Screenshots ===

[http://www.cenon.info/gallery/gallery_gb.html Screenshots]

=== Links ===

[http://www.cenon.info/ official site]

=== Notes ===

The reason I'm posting this app, is because the CENON codebase recently was made free. This software has many import/export formats, and we might be able to use their code for import/export formats.

=== License ===

vhfPL - GPL like license

[[Category:Developer Discussion]]

CarlHetherington

2006-06-27T00:47:34Z

GigaClon: consistant formatting

Carl Hetherington, an Inkscape developer.

[[Category:Developer]]

Caliga

2006-06-27T00:47:08Z

GigaClon: Categorization

=== english ===

Hi!

I joined the Inkscape community in September 2005.

I translated the website and some tutorials to german. :)
If you want to give a comment or suggestion:
Email: [inkscape at stiefelweb semicolon de]
Jabber: [caliga ät gristle (.) org]
ICQ: [143406052]
I may also hang out on IRC: #inkscape.de, #inkscape

Visit my website: [http://www.caligamedia.de caligamedia]

=== deutsch ===

Hi!

Ich arbeite seit September 2005 in der Inkscape-Community.

Ich habe die Website und ein paar Tutorials übersetzt :)
Kommentare oder Vorschläge könnt ihr hier loswerden:
Email: [inkscape at stiefelweb semicolon de]
Jabber: [caliga ät gristle (.) org]
ICQ: [143406052]
Vielleich häng ich auch im IRC ab: #inkscape.de, #inkscape

Besucht meine Seite [http://www.caligamedia.de caligamedia]!

[[Category: Developer]]

CadInteroperability

2006-06-27T00:46:13Z

GigaClon: Categorization

== CAD Interoperability ==

Computer-aided design (CAD) is another particular application for 2D vector graphics. A difference
between CAD and other types of drawing is that precision is extremely important. Another difference
is the need for dimensioning of items in the drawing. Workflow can also be very different between CAD
and other vector drawing uses. Because of these reasons, Inkscape is unlikely to ever be useful as
a CAD tool directly.

However, being able to import CAD drawings for final cleanup/rendering, or to mock up some ideas
before putting into CAD, may be of use. The de factor standard exchange format for CAD programs
is DXF. Having support for this format suddenly opens up interoperability with a huge range of other
applications, including not only 2D CAD such as qcad, but also 3D rendering programs such as
Blender, etc.

[[Category:Developer Discussion]]

BugParty

2006-06-27T00:43:01Z

GigaClon: Categorization

= Bug Party =

== Announcement: ==

Bug Party Invitation

In an effort to beat the bug tracker and the feature tracker into submission, the Inkscape project is hosting a "Bug Party" on Saturday, September 24, 2005. This is an excellent opportunity for new contributors and non-developers to participate in the project.

All day long (in the US time) the IRC channel #inkscape on server irc.freenode.org will be open, along with the correspondent Jabber room (see http://inkscape.org/discussion.php for more details). We expect to reach peak hours at 16-20 UTC on September 24 (8-12 PST) and 0-4 UTC on September 25 (16-20 PST on September 24) and guarantee presence of core Inkscape developers on those time intervals.

For additional information, rules, procedures and tools, a Wiki page is available: http://wiki.inkscape.org/cgi-bin/wiki.pl?BugParty

If you are an Inkscape user looking for a way to contribute or an existing contributor wanting to contribute more, we await you!

To be distributed at:
* Inkscape users list;
* Inkscape test list;
* Openclipart list;
* Scribus list?;
* news item on front page (aggregated to various Planet sites).

== Fun Stuff: ==
* Color logo: http://nicubunu.ro/pictures/inkscape/debug.png
* Black and white: http://nicubunu.ro/pictures/inkscape/debug_bw.png
* With additional feedback: http://nicubunu.ro/pictures/inkscape/debug_finale.png

== Objectives: ==
* trim down the number of open bugs/enhancement request. we should find old bugs which do not exist anymore, features already implemented and not closed in the tracker, duplicates and, why not, quick fixes.

== Rules: ==
* if a bug report is one release old/one month old, we can't reproduce it and don't have any follow-up from the poster, then it can be closed;
* code to fix bugs is to be posted as patches to the patch tracker for review and integration

== Procedures: ==
* is possible to post to the tracker without login to sourceforge.net, but a login is recommended, because this improve your ability to follow-up later;
* not everyone is allowed to close a bug, so people without this right should comment in the bug reasoning why the bug should be closed (is a duplicate, not happen anymore, can't be reproduced). We should define a way to work after that, alternatives are:
** put in a message a special string, like TOCLOSE, which can be queried later, for closure;
** announce the bug number on the chat channel, so it can be closed interactively;
** put the URL of the bug in the wiki page.
* if a feature request would never be implemented, it can be closed, but with good reasoning of why it will not be implemented (like not within the scope of a vector drawing application, not compatible with the existing codebase)

== Tools: ==
* a new version of Inkscape will be needed [to determine later what version: 0.42.2, CVS build, etc.)
** Easy ways get builds.
*** Daily Win32 builds http://www.inkscape.org/win32-snap/
*** Linux AutoPackages http://inkscape.modevia.com/ap/
** Build Your Own
*** Working with CVS http://wiki.inkscape.org/cgi-bin/wiki.pl?WorkingWithCVS and Compiling Inkscape http://wiki.inkscape.org/cgi-bin/wiki.pl?CompilingInkscape
* the Inkscape bug tracker at sf.net: http://sourceforge.net/tracker/?group_id=93438&atid=604306
* the Inkscape feature tracker at sf.net: http://sourceforge.net/tracker/?group_id=93438&atid=604309
* the Wiki page: http://wiki.inkscape.org/cgi-bin/wiki.pl?BugParty
* the Inkscape developer mailing list: inkscape-devel AT lists.sourceforge.net
* How to report a bug: http://inkscape.org/report_bugs.php

[[Category:Wiki Attic]]

BryceHarrington

2006-06-27T00:42:03Z

GigaClon: Categorization

Bryce Harrington, an Inkscape developer. Lives in Tigard, Oregon and works at
[http://www.osdl.org/ OSDL].

[[Category:Developer]]

BreadthFirstUndo

2006-06-27T00:39:22Z

GigaClon: Categorization

ok, breadth first undo:
* Take a document with an oval and a square
* Resize the oval.
* Move the square.
* Set the oval's stroke width

Normal undo would undo the square, then the oval.

Breadth first undo would allow the user to undo either the square or the oval. The edits in the document can be considered a sequence of parallel edits, the order of undo on any particular element is only defined by edits on it, or on something that affects it. The undo history becomes:

New document
New oval
Resize oval
Set stroke
New square
Move square

Another way to change undo is to provide a branch in the history whenever an undo followed by an edit occurs. For example,
* Take a document with an oval and a square
* Resize the oval.
* Move the square.
* Set the oval's stroke width
* undo, undo
* add spiral

The history of this document could be displayed like this:

Resize oval
Move square
Set oval stroke width
Add spiral

The two concepts can be merged to give an edit tree for each object in the document, the traditional undo being threaded through the tree.

[[Category:Developer Discussion]]

BrandonCsSanders

2006-06-27T00:38:48Z

GigaClon: Categorization

I'm an Inkscape enthusiast (and evangelist) who has been a user since well before the fork. I live in the same city as Bryce and have been chatting with him about ways to get involved in the development. You can find more info about me on [http://brandon-cs-sanders.com/ my portal page].

[[Category: Developer]]

BigPicture

2006-06-27T00:33:15Z

GigaClon: redirect

#REDIRECT [[OpenPublishingToolsOrganization]]

Beez

2006-06-27T00:31:32Z

GigaClon: Categorization

''Beez::'' is a vector-drawing editor/animator to create SVG animations

it's really limited software for now.
* only for win32
* only plain fill SVG path
* allow onion skin

[http://beez.sourceforge.net http://beez.sourceforge.net] Beez:: web site

This project has been discontinued.

[[Category:Wiki Attic]]

Beatware Mobile Designer

2006-06-27T00:27:52Z

GigaClon: Categorization

=== Description ===
Beatware Mobile Designer is a new app positioned to capture the new Tiny SVG market by making a mobile development app. Specifically check out their profile editor for designing for different SVG targe formats. Also, their animation tools are very good. This apps supports effects, object library, among many other features.

=== Screenshots ===

* [http://rejon.org/projects/inkscape/reference/beatwave/ A bunch of screenshots rejon took]
* [http://www.beatware.com/images/screenshot_md_2.gif Profile Editor]

http://www.beatware.com/images/screenshot_md_1.gif

=== Links ===

[http://www.beatware.com/products/md.html official site]

[[Category:Developer Discussion]]

CompilingStatic

2006-06-23T17:30:25Z

GigaClon: Categorization

Static compilation of Inkscape is one way to sidestep dependency issues. Instead of requiring the user to install the particular versions of particular libraries, we just include them in the Inkscape binary.

Warning Will Robinson, this has a cost: The inkscape binary gets BIG. But that's the tradeoff we pay for gaining this convenience. From a packager's point of view it's also a bit more work, but this page will list out the steps to take achieve it. Of course, we'll still provide "regular" libs for people who are willing to get the dependencies in order, or who won't like downloading a huge package.

== Libraries ==

By static, we mean "all the nasty C++ and other new-fangled stuff". This is not a TRUE static binary. We are going to include only the items that we expect people may not have on their systems, and leave the more standard libraries dynamically linked.

Since you probably don't want to overwrite your existing versions of these libraries, put them somewhere other than /usr or /usr/local or /opt. For these examples, I'll use /extra/static. Since they depend on eachother, order is important. To have the builds see the new static libraries, you'll need to export these variables first:
PATH=/extra/static/bin:$PATH
PKG_CONFIG_PATH=/extra/static/lib/pkgconfig:/usr/local/lib/pkgconfig:/usr/lib/pkgconfig
CPPFLAGS=-I/extra/static/include/opt/gnome/lib/pkgconfig/
LDFLAGS=-L/extra/static/lib
export PATH PKG_CONFIG_PATH CPPFLAGS LDFLAGS

(SuSE Linux users, add ":/opt/gnome/lib/pkgconfig/" to PKG_CONFIG_PATH above)

Unless noted, each of the libraries is built with:
./configure --disable-shared --enable-static --prefix=/extra/static
make
make install

List of support libraries to build statically first (they are used by the various libraries in the "Remaining" section below):
* libpng 1.2.8+ (this requires "cp scripts/makefile.linux Makefile" and to edit Makefile's "prefix" to /extra/static. Then a "make install-static" is all you need)
* libjpeg 6b+ (this requires a final "make install-lib")
* libxml 2.0+
* libgc 6.4+ (since some distros don't have this yet. In 6.3, I had to edit os_dep.c, and replace the __libc_stack_end pragma/extern with "ptr_t __libc_stack_end = 0;" to get it to link. This may be fixed in new versions.)

Libraries not needed, since they don't end up making anything useful. They're still listed here to retain their order, and to keep their weird configs for anyone else to play with in the future if pango can be convinced to work:
* libexpat 1.95+
* glib 2.0+
* atk 1.0+
* freetype 2.0+
* xft 2.1+
* fontconfig 2.2+ (remove "doc" and "test" from Makefile's SUBDIRS)
* pango 1.0+ (ends up not working at all when built statically)
* gtk+ 2.4+ (configure with "./configure --enable-static --disable-shared --without-libtiff --disable-modules --with-included-loaders=xpm,png,bmp,jpeg --prefix=/extra/static", and you'll also have to edit Makefile to drop "demos" and "tests", and modules/Makefile to remove "input" from SUBDIRS. Also seems to need -lz added after -lm everywhere in the gdk-pixbuf directory's Makefile for dealing with the static libpng.)

Remaining libraries to build statically:
* libsigc++ 2.0+ (because C++ bindings ABI has changed several times, breaking Inkscape for several distros. edit Makefile to remove "docs" from SUBDIRS). (The mention of ABI breakage is a serious accusation, but the libsigc++ developers have never had any reports of it. murrayc.)
* glibmm 2.4+ (because of C++ bindings)
* gtkmm 2.4+ (because of C++ bindings. edit Makefile to remove "examples", "demos", and "tests" from SUBDIRS. You can also use --disable-examples and --disable demos, which are meant to speed things up. murrayc)

== Inkscape ==

If you're just building inkscape yourself, you can finally configure and build inkscape:
./configure ....
make

If you're building an RPM, you can build it with the existing inkscape.spec file. Two things need to happen:
# Build against the static tree you've made. Do this by adding "--define 'ink_static_root /extra/static'" to the rpmbuild command line.
# Disable automatic dep finding (since it doesn't work correctly for static binaries). Do this by creating ~/.rpmmacros with a line that reads "%__find_requires /path/to/script" and make that script look like this:
#!/bin/bash
cat >/dev/null

The resulting command line will be something along the lines of (can add "--target i686" for an i686-optimized version, too):
rpmbuild -ta --nodeps inkscape-0.41.tar.gz --define 'ink_static_root /extra/static'

[[Category:Developer Documentation]]

CompilingYoper

2006-06-23T17:29:21Z

GigaClon: Categorization

== [http://Yoper.com Yoper] ==

This has been tested for Inkscape0.39 on Yoper i686-2.1.0-4:

# review the [http://www.yoper.com/forum2/index.php?showtopic=800 Guide to Compiling Software from Source] & [http://www.yoper.com/forum2/index.php?showtopic=2577&view=findpost&p=13450 tips on compiling]
# compile [http://prdownloads.sourceforge.net/libsigc/libsigc%2B%2B-1.2.5.tar.gz?download libsigc++-1.2.5.tar.gz]
# Run <code>ldconfig</code> as root so the library can be found by the OS
# copy /usr/include/freetype2/freetype to /usr/include/freetype
# compile inkscape!

[[Category:Developer Documentation]]

CompilingMacOsX

2006-06-23T17:23:31Z

GigaClon: Categorization

== Compiling on Mac OS X ==

=== Requirements ===
To compile Inkscape from source you will need:
*Mac OS X 10.3 (Power PC) or higher
*A full [http://fink.sourceforge.net/faq/usage-fink.php?phpLang=en#unstable unstable fink] installation
*Inkscape's source code. You can get the [http://www.inkscape.org/download.php official release source code], a [http://www.inkscape.org/cvs-snap/ SVN snapshot] or a copy of the [http://www.inkscape.org/svn.php?lang=en SVN repository].
*A [http://darwinports.opendarwin.org/ DarwinPorts] install if you want to use inkboard.
*XCode 2.3 on OS X 10.4 (gcc 4.0.1)

You need to install software on which Inkscape depends, using Fink and/or DarwinPorts.

=== Dependencies ===

They are necessary for Inkscape to compile. In a Terminal type:
<pre>
fink install \
intltool \
glib2 glib2-dev glib2-shlibs \
gtk+2 gtk+2-shlibs gtk+2-dev \
libpng3 libpng3-shlibs \
libsigc++2 libsigc++2-shlibs \
gtkmm2.4 gtkmm2.4-dev gtkmm2.4-shlibs \
libtool14 libtool14-shlibs \
libxml2 libxml2-shlibs \
popt popt-shlibs \
gc gc-shlibs \
automake1.8
</pre>

You need version 1.8 of automake 1.8 (and not 1.9, the latest in Fink). Fink installs many packages from source so this is usually long.

You may also need to build popt from source (tested on 10.4):
[ftp://ftp.rpm.org/pub/rpm/dist/rpm-4.1.x/popt-1.7.tar.gz]

(Since May 2006, the version of sigc++ required when using gcc 4 is 2.0.12 or greater. For a short time, only 2.0.11 was available in Fink. The latest version of libsigc++2, version 2.0.17, has now been added to fink unstable so everything should compile normally again.)

=== Optional Features ===

To enable some additional functionality in Inkscape you might want to install:
* <code>lcms</code> : color management via LittleCMS
* <code>loudmouth >= 1.0</code> : collaborative whiteboard (only available in DarwinPorts)
* <code>boost >= 1.32</code> : auto-organisation of connectors
* <code>gnome-vfs</code>
* <code>gnome-print</code>
* <code>xft2</code>
for each of these you need the developement packages as well (the name ends by <code>-dev</code>)

=== Easy Compile ===

You can try to download this [http://jo.irisson.free.fr/dropbox/inkscape/makeosx.sh bash script] which automates the processes of updating Inkscape from the svn repository, setting the build environment, building and producing a simple package of Inkscape. Modify it with your favorite text editor in order to set a correct install prefix and to change configuration options.

Check Inkscape source code [http://www.inkscape.org/svn.php?lang=en from svn] and copy the script to the base of your local svn repository. Make it executable:
<pre>chmod +x makeosx.sh</pre>
and then simply run it
<pre>./makeosx.sh</pre>

If something doesn't run smoothly, refer to the indications underneath.

=== Setting the build environment ===

Fink's hierarchy is not searched for libraries by default. Therefore, before the configuration starts, some environment variables need to be set. The environment variables are presented in bash syntax here. You can create a file named <code>set_env_variables.sh</code> and copy/paste this inside:
<pre>
FINK="/sw"
export CFLAGS="-O3 -Wall"
export CXXFLAGS="$CFLAGS"
export CPPFLAGS="-I$FINK/include"
export LDFLAGS="-L$FINK/lib"
export CPATH="$FINK/include"
export PATH="/usr/X11R6/bin:$PATH"
export LIBRARY_PATH="/usr/X11R6/lib:$FINK/lib"
export PKG_CONFIG_PATH="$FINK/lib/pkgconfig"
</pre>

In addition, you must make sure that Inkscape is compiled with the compiler version that Fink uses, otherwise Inkscape will not link properly. To determine which compiler to use type:
<pre>
head -n 5 $FINK/etc/fink.conf | grep "Distribution"
</pre>

If your fink distribution is 10.4 add:
<pre>
export CC="gcc-4.0"
export CXX="g++-4.0"
</pre>
to <code>set_env_variables.sh</code>, else (10.3, 10.4-transitional) add:
<pre>
export CC="gcc-3.3"
export CXX="g++-3.3"
</pre>

You can also use <code>ccache</code> (<code>fink install ccache</code>) to speed up the compilation a bit. To do so, modify the compiler lines accordingly:
<pre>
export CC="ccache gcc-??"
export CXX="ccache g++-??"
</pre>

Eventually, open a Terminal and, in the directory where you created the file <code>set_env_variables.sh</code>, type:
<pre>
bash; source set_env_variables.sh
</pre>

=== Configuring ===

You might need to build the configure script first (if you compile Inkscape for the first time). Cd to Inkscape's source directory and run:
<pre>
./autogen.sh
</pre>

Then run the configure script:
<pre>
./configure --prefix=/path/to/build/products/ --enable-osxapp
</pre>

The <code>--prefix</code> option sets the directory where the build products are placed. It must be somewhere you have write access to. The option <code>--enable-osxapp</code> allows you to package Inkscape into an <code>.app</code> bundle in order to access it like a regular OS X application. Remove this option if you only want to build Inskscape, not to package it afterwards. Of course you can add here classic configuration options such as <code>--enable-lcms</code> for color management or <code>--enable-inkboard</code> for whitboard functionality.

=== Starting the Build ===

Piece of cake:
<pre>
make
make install
</pre>

== Packaging Inkscape into an .app bundle ==

=== Creating the .app and a simple .dmg ===

Assuming that you have used the <code>--enable-osxapp</code> option during <code>configure</code>, the process is fully automatized. You just have to open a Terminal, cd to Inkscape's sources directory and type:
<pre>
cd packaging
./osx-app.sh -s /path/to/build/products/bin/inkscape ../Info.plist macosx
</pre>
The <code>-s</code> options produces an app bundle stripped of debugging information (which is therefore smaller). Omit this option if you want to keep debugging info.

Either way, this creates two files in current directory: Inkscape.app that you can copy to your Applications directory and Inkscape.dmg for distribution.

=== Creating a more complete .dmg ===

Many Mac OS applications are distributed in a dmg with a background picture and some basic installation instructions. In order to distribute Inkscape this way you first need to create an .app bundle of Inkscape as described above. Then you need to create a read-write disc image big enough to contain the app bundle:
<pre>
hdiutil create -size 50m -fs HFS+ -volname "Inkscape" RWinkscape.dmg
</pre>
This step has only to be done once. For next builds you will just have to re-attach the image and copy the new Inkscape .app inside it. To attach the disc image, double click the .dmg or use:
<pre>
hdiutil attach RWinkscape.dmg
</pre>

The second step is to copy everything you need inside the attached disc image (which is available as a white disc icon named "Inskcape" on your Desktop). You need:
*the .app bundle
*an alias to the Applications folder (CTRL+click "Applications" and select "Make Alias")
*the [http://jo.irisson.free.fr/dropbox/inkscape/background.png background picture]

Finally you need to improve the appearance of the disc image.

First you need to set the background image:
#navigate to the attached disc image with the Finder
#switch the Finder to Icon's view (View > as Icons)
#open the View Options window (View > Show View Options)
#check the radio button to select options for "This window only"
#in the "Background" section, select "Picture" and choose the background picture you just copied in the disc image.
You may want to make the background image file invisible to have a cleaner aspect:
<pre>
/Developer/Tools/SetFile -a V /Volumes/Inkscape/background.png
</pre>
The icon of the file should become kind of transparent and you should not see it anymore if you relaunch the Finder.

Then, arrange the Finder window as you want people to see it. You may want to hide the Finder brushed metal skin to have a smaller window (click the elongated transparent button in the top right corner of the Finder window), fit the window to the background image, move Inkscape's icon to be next to the arrow (you may need to deselect some presentation options in View > Show View Options) and center the window in your screen.
You should end up with a window looking like [http://jo.irisson.free.fr/dropbox/inkscape/inkscape_distrib.png this].

The last step consists in creating a compressed read-only disc image from this read-write disc image:
<pre>
hdiutil detach /Volumes/Inkscape
DATE=`date "+%Y%m%d"`
hdiutil convert -format UDCO -o Inkscape_$DATE.dmg RWinkscape.dmg
</pre>
This creates a smaller disc image with a name like Inkscape_20060424.dmg.

Everything is summarized in a [http://jo.irisson.free.fr/dropbox/inkscape/bundleosx.sh bash script].

== Enabling python effects ==

Many "effects" in the Effect menu of Inkscape use python as a scripting language. Mac OS X ships with python but not with pyXML which is needed by Inkscape effects.
You can install a binary version downloadable with the developement builds of Inkscape:

:http://inkscape.modevia.com/macosx-snap/?M=D

Or you can install it from source:
# download the source code from [http://sourceforge.net/project/showfiles.php?group_id=6473 sourceforge]
# unpack the <code>.tar.gz</code> file
# cd into the newly created directory
# set the variable <code>MACOSX_DEPLOYMENT_TARGET</code> to the number of your operating system (10.3 for Panther, 10.4 for Tiger. It probably won't work on previous systems). In bash syntax this means typing:<pre>export MACOSX_DEPLOYMENT_TARGET=10.?</pre>
# move the python files and build C extensions<pre>python setup.py build</pre>
# install (the install is system wide so you need administrator rights)<pre>sudo python setup.py install</pre>and type your password.

== Links ==

=== Apple Documentation ===
* [http://developer.apple.com/documentation/MacOSX/Conceptual/BPRuntimeConfig/BPRuntimeConfig.html Introduction to Runtime Configuration] Covers the Info.plist files, Preferences, Environment variables and has a list of the most important Properties that the Property List should contain.

=== Packaging ===

* [http://www.sveinbjorn.org/platypus Sveinbjorn Thordarson's Website] The author of Platypus, the Script Exec wrapper that launches the Inkscape binary.
* [http://freespace.ausgamers.com/2005/02/creating-os-x-application-bundles-step.html Creating OS X application bundles step by step] Covers the bundle concepts, copying libraries into the bundle, editing libraries with the install_name_tool, the Info.plist file and adding an icon.
* [http://java.sun.com/developer/technicalArticles/JavaLP/JavaToMac3/ Bringing your Java Application to Mac OS X] I would regard this a little dated, and the detail is (unsurprisingly) Java-related, but it is a gentle introduction to the role of the .app bundle and give a most clear account of how to create one.
* The [http://gimp-app.sourceforge.net/gimp.app.howto.txt Gimp .app Howto] This is a very bare document, and would be of little help to you if you were new to making packages. Note that it seems to refer to a more mature Clipboard technique and Online help than we currently have; and we ought to move to parity in these areas.

[[Category:Developer Documentation]]