I'm interested in setting up a git mirror of Inkscape SVN; who's the person in charge of our server currently? We'll need to have a fairly current version of git, libsvn, and the libsvn perl bindings installed to do this.
I've imported a 400x400 pixel TIFF image into an inkscape drawing, and
it comes out as 112.89 x 112.89 mm, which translates to a resolution of
roughly 90 dpi.
Where does this number come from? Shouldn't inkscape honour the dpi
information that is embedded in the TIFF image?
Alternatively, for images that don't have a "built-in" resolution,
inkscape should ask for a "native" size of the image or use a changeable
Also I noticed that some imported images have width and height xml
attributes while others don't. All this came to my attention when I
worked with a SVG file with 20 imported images of about 10MB each (TIFF
uncompressed) which bogged down my computer. I tried substitutung the
TIFFs with scaled-down (by .25) working copies, which worked fine for
those images that had width and height attributes (the others came out a
fourth of the size),
I'm just wondering how Inkscape arrives at the "native" size of an
image, and I wanted to know if others agreed with my notion that in a
vector drawing program the resolution of imported bitmaps was of high
It would also be nice if Inkscape could somehow reload image properties
if the original bitmap had changed (by scaling or cropping, for instance).
Some of the stuff I do with the calligraphy tool has gaps between sections I
would like to colour. Visually the gaps don't bother me, but I can't use
Flood Fill when the area isn't properly closed.
It would be nice there was a threshold where we could say that gaps of a
certain size should be considered closed. I imagine it would be like a
thickness to the paint where if it's very thick it can't flow through a
View this message in context: http://www.nabble.com/Flood-fill-suggestion---Bound-threshold-tf3822118.h...
Sent from the Inkscape - Dev mailing list archive at Nabble.com.
Better late than never, I would like to finally create my promised
tutorial on how to set up building and debugging with Eclipse under
Windows. A couple of questions first:
(1) I made an account for the wiki, but I'm not sure if I need some kind
of special permission to edit the main page
<http://wiki.inkscape.org/wiki/index.php/Inkscape> in order to add my
new page. Or maybe one of you guys has to just create the page for me
and I can start editing it? I would call it "UsingEclipse" probably, and
put it in the Dev Documentation under General. (Although I am only
doing Windows, somebody could add information related to Linux and Mac
later on.) Let me know how that all works...
(2) I'm hoping images can be uploaded directly to the wiki (for
screenshots). If not, then let me know what most people do to get
I wanted to change the Inkscape Application to some thing else. But I
am not able to find which files do i need to change.
The Application name : New Document 1 Inkscape
the inkscape should change to someother name!
it is like i want to change the brand name!!
is it possible?
if it is please let me know how!
I just wanted to know what the policy is for attaching images to emails
to this list. Are we allowed to attach images under a certain size, or
not at all? I have a suggestion for a GUI enhancement and I have
prepared a mock-up to explain it and hopefully get some useful feedback
I encounter some problems when using the geometric bounding box
option and trying to select perfectly vertical or horizontal paths.
The issue seems generic enough but I find it surprising that nobody
else experienced this problem since the geometric bounding box option
appeared quite some time ago now.
Some details are available in a bug report:
Am I the only one seeing this?
As a Playful Geometer, I have been developing some python libraries
for the manipulation of SVG, and I have developed some Inkscape
extensions that depend on the project, and reside in the code base of
The project resides on sourceforge here:
Some sample artwork developed using pLAySVG:
Currently the libraries self-install using python distutils, but the
Inkscape extensions do not. My difficulty in acomplishing the latter:
- for Linux, I must sudo to run the installer, so that when the
Inkscape extensions are copied to the extensions directory, they are
owned by root, and thus are not available to users running Inkscape
(this may be remedied by doing a chown in the setup.py script)
- for Windows and MacOSX, I do not know where to copy the extensions
Could someone offer me some suggestions on how to make this work?
Considering that Inkscape is leaning towards separate distribution of
extensions, it is important that these issues be fleshed out. I
started a wiki page as a HOWTO for package distribution of Inkscape
however, it does not deal with the owership issues I mentioned, so it
is inacurate in that sense.
Originally, my intentions with pLAySVG was just to allow me to create
images using code rather than point-and-click methods, but now I am
interested in making pLAySVG more than a pet project, something that
- an educational resource that will allow people (especially children)
to learn about geometry, computer graphics, SVG/XML documents in a
playful and creative way (similar to the way LOGO has been employed)
- a toolkit for those who wish to do graphics scripting
- most relevenatly, a toolkit for those who wish to develop Inkscape extensions
Considering this, I am interested in expanding the functionality of
pLAySVG to encorporate some the features already resident in Inkscape,
- path operations (i.e. union, combine)
- arc estimation as in the circle tool
- star tool
Could anyone offer any advice and/or assistance on this ?
As well, I'd like to figure out how I could tap into the functionality
of lib2geom and make it accessible for extensions developers and
stand-alone graphics scripting.
Lastly, I am interested in making my software used as an educational
resource, and I welcome any input you have on achieving this goal. I
have just submitted a proposal to OLPC to make this a part of XO
laptop learning and have contacted Jon concerning his post on working
with OPLC (although I'm probably not capable of porting).
Your feedback would be greatly appreciated,
-----BEGIN PGP SIGNED MESSAGE-----
There is a way of getting a very precise flood fill:
1. Join a copy of all the object to one big object.
2. Create rect which is so huge like the whole document
3. Use path/difference to get a flood fill for all positions.
4. Put the different shapes of the result in thier own objects.
5. Find out which of the result object has been clicked by the flood
fill operation and remove the other result objects.
I don't have the time to work myself into the inkscape code, but maybe a
inkscape developer like the idear and implement it.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
Somewhere from rev. 15034 to 15078 , the about screen broke. Running gdb and trying to open the about screen, Inkscape crashes; gdb and gives the backtrace below.
Thanks for fixing it!
Program received signal SIGSEGV, Segmentation fault.
---Type <return> to continue, or q <return> to quit---
0x00a88787 in std::_Rb_tree_decrement (__x=0x4b0ddd0)
94 ../../../../libstdc++-v3/src/tree.cc: No such file or directory.
Current language: auto; currently c++
#0 0x00a88787 in std::_Rb_tree_decrement (__x=0x4b0ddd0)
#1 0x00a6f294 in std::_Rb_tree<char*, std::pair<char* const, int>, std::_Select
1st<std::pair<char* const, int> >, ltstr, std::allocator<std::pair<char* const,
int> > >::insert_unique ()
#2 0x0047f770 in sp_filter_set_image_name ()
#3 0x0065f656 in sp_filter_primitive_set ()
#4 0x0048b47a in sp_gaussianBlur_set ()
#5 0x00421f53 in sp_object_set ()
#6 0x00422092 in sp_object_read_attr ()
#7 0x0065f4eb in sp_filter_primitive_build ()
#8 0x0048b2a9 in sp_gaussianBlur_build ()
#9 0x004224a0 in sp_object_invoke_build ()
#10 0x00423dfd in sp_object_build ()
#11 0x0047f34a in sp_filter_build ()
#12 0x004224a0 in sp_object_invoke_build ()
#13 0x00423dfd in sp_object_build ()
#14 0x004224a0 in sp_object_invoke_build ()
#15 0x00423dfd in sp_object_build ()
#16 0x0042fb0f in sp_root_build ()
#17 0x004224a0 in sp_object_invoke_build ()