We are proud to announce our first contribution to inkscape : Live Path
Effects for groups.
You can already test it from svn trunk.
In a word, you can now add a LPE to a group of paths.
For most LPE, the effect is applied recursively (try sketch, curve stitching
or gears) but for Bend Path the result is more powerful : the distortion
applies on the whole group.
You can edit original path of the group by double-clicking on the group (as
A path with a LPE can be part of a group with a LPE, this is a sort of of
You can make groups of groups, it will work (There is one known bug when
using bend path, we will fix it very soon).
You can apply definitively the effect with "Convert Object to path"
We will soon make that when ungrouping, the effect is copied to each item in
I will update the ReleaseNotes as soon as possible.
We are currently working on LPE stacking (a simple UI is done, the engine is
in a good way) and on an envelope deformation effect (it uses LPE
PointParams for control points).
Steren for the "PI:Inkscape" team of Ecole Centrale de Lyon.
I just created a Wiki page with my proposal for the GSoC . I have
attempted to incorporate most of the comments I received so far, with
emphasis on getting the unit tests in shape. I would appreciate any
For one thing, I named the page ...-blueprint, but I haven't created an
actual blueprint yet, mostly because the page is worded more like a
proposal than a blueprint (and I'm not yet that familiar with the
blueprint feature). Would it still be desirable to have a blueprint for
BTW, I omitted all non-technical information (like my previous
experience) from this Wiki page, it obviously will be part of the
proposal I will submit.
For Windows users, the Win32 0.46pre4 has been updated to pre4-2 due to a
missing file error. My apologies.
You'll find pre4-2 on the Sourceforge server here;
This version is already quite stable, but please it for any further bugs and
report to https://bugs.launchpad.net/inkscape/
If there are no other major problems, we will move to a stable release early
Note, there are some known issues that won't be fixed for 0.46.0, as per the
* (LP: #180890) Blend modes do not work correctly over transparent
backgrounds. A workaround is to place an opaque rectangle underneath
the bottom-most layer.
* (LP # 202704) Blur and other filters are very slow when applied to an
object with transform= attribute with rotation or skew. To avoid this
slowdown, either do not rotate/skew objects you use with filters, or
apply filters only to paths (but not shapes to text) because paths,
default, get no transform= attribute when you rotate or skew them.
* Windows printing has two known issues. In both cases the workaround
to print to bitmap (Print -> Rendering -> Bitmap).
- (LP # 205732) Blurred objects are misaligned when printing.
- (LP # 208217) Masked objects disappear when printing.
View this message in context: http://www.nabble.com/Win32-pre4-2-%28minor-error-fixed%29-tp16370629p163...
Sent from the Inkscape - Dev mailing list archive at Nabble.com.
Voting is open for Inkscape committee member until Friday, April 4th.
Voting is Cool! Vote now! (Voting is open to everyone listed in AUTHORS.)
The nominees are:
(sorry, forgot to put subject line in post)
> I see that a Leopard dmg package for Inkscape 0.46 is posted, but not a Tiger
> (OSX 10.4.11) version, and the Leopard package doesn't run on Tiger.
> I won't be upgrading my Macbook to Leopard for a while, if at all, and would
> like to upgrade to
> the latest Inskcape.
> Is anyone planning to make a Tiger dmg?.
> If not, and the build system is fairly-well automated, I could try to build a
> Tiger universal package on my macbook, I have xcode etc installed.
> Any advice on this?
Like suggested in another post, I have added functionality to the LPE PathParam. Now, it can also link to another shape/text on canvas. Especially the text is nice. For example:
1. Type text (not flowtext)
2. draw curved path
3. apply lpe-Pattern along path to curved path
4. select text and copy it
5. select curved path and press link to path button in the LPE dialog for the pattern source parameter
6. see what happens. edit the text and see what happens :)
Please report bugs to me directly (not in launchpad, because I won't see it). I know deleting of the path to which is linked is bugged; it has not been implemented yet.
I'm interested in improving Inkscape's test framework for the GSoC. I've
read the GSoC related documentation. I've also read all the information
on testing on the Wiki that I could find and had a look at some of the
current unit tests in SVN.
Unfortunately I don't have a Linux system set up at the moment, so I
can't actually execute 'make check'. So far I've come up with the
following draft plan:
1. Make sure the existing tests work on Win32 (and MacOS X).
2. Set up system to rerun tests periodically/when needed.
3. *Possibly* also try generating some historical data (where possible).
4. Implement new tests for (at least):
- nr-compose (I already did this locally, at least partially)
- livarot (parts of)
- sp_svg_... (transform_read/write, read/write_path, etc.)
5. Integrate (existing) SVG conformance tests so that they are also
rerun. I will attempt to partially automate this (as far as I
understand the current tests are evaluated manually) by storing
result images and only asking for human judgement when an image
changes. I'm also thinking of a few more advanced ways of automating
some of these tests.
6. Add performance information by timing tests (as well as rendering of
images, for the SVG conformance tests for example).
In short my intention is to create a system which (continuously) keeps
track of the status of unit tests as well as SVG conformance and
performance of Inkscape. Test results will be accessable online.
I also plan to use gcov to keep track of test coverage and if
interesting (read: if the tests take long) reduce the number of tests
that have to be rerun each time. I'm currently checking whether I can
get gcov to work to my satisfaction with Inkscape.
If deemed interesting I might also add information from gprof to give a
better idea of what parts of the code are interesting to optimize (and
keep track of performance over time on a fine-grained level). I already
regularly use gprof with Inkscape myself.
Is this more or less what was originally intended? In any case, I would
appreciate any suggestions and/or information you might have.
I have been looking at the existing unit tests in the Inkscape codebase,
and interestingly enough I've found a few references to test files in
the exclude list of build.xml that don't actually exist. In part this is
because they refer to automatically generated files from CxxTest unit
tests, and some others are probably explained by tests that were
converted from Utest to CxxTest. But I have also found a few which I
If anyone knows what happened to these files, and especially if anyone
has these files (or of course other test files) still lying around, I'd
love to hear about it (and if you do have one, how usable is it).
BTW, there are also two nr-compose related test files which are not in
the codebase, but I'm afraid that's due to me :) (I still have them
lying around and will probably convert them to CxxTest and make sure
they end up in the repository.)