- Inkscape Devel - Inkscape Mailman

Roughen video
by Jabiertxo Arraiza Cenoz 28 Apr '14

28 Apr '14

Hi to all. Here is a video from my last work. Roughen LPE https://www.youtube.com/watch?v=130Dbt0juvY Soon Simplify LPE and Perspective-Envelope LPE videos. Hi, Jabier.

1 0

Plugin: onionskin plugin for animation
by Lucas H 28 Apr '14

28 Apr '14

Hi there, I recently wrote a plugin to allow an 'onionskin' view of inkscape layers to aid animation. I'm developing some other animation-related plugins, too. Someone told me I should let the Inkscape dev team know about it, so here I am. All the info is here: http://github.com/lingo/inkscape_onionskin Reddit post (for flames,trolls,or upvotes): http://www.reddit.com/r/Inkscape/comments/242ys3/onionskin_plugin_to_make_a… Kind regards, - Lucas

1 0

Units
by Tavmjong Bah 28 Apr '14

28 Apr '14

Hi, I had a discussion with several people at the SVG Working group meeting in Leipzig this past week about user units vs. "real" units. I proposed that it be possible to set a ratio for the initial user unit to inch (or cm). This was not well received. My basic conclusion from these discussions is that the use of any real unit (inch, pt, etc.) inside an SVG file (other than on the root 'width' and 'height') is pointless. The correct way to proceed is to set the 'width' and 'height' of the SVG to the size of the drawing and then the 'viewBox' to the same values without units, e.g.: <svg width="20in" height="15in" viewBox( 0 0 20 15 ) ... > Once you have done this, one user unit is one inch. If you actually set a length to an inch inside the file (i.e. width="1in"), it will be interpreted as 90 inches since we use 90 user units per inch. OK, so be it. The gods have spoken. However, we should at some point change 90 user units per inch to the CSS 2.1 value of 96 which has now been fixed in stone. (Illustrator has the same problem, having used a value of 84.) Tav

9 21

New LPE roughen
by Jabiertxo Arraiza Cenoz 26 Apr '14

26 Apr '14

Thanks to Josh for the idea to port two extensions to a one LPE. The extensions are Add Nodes and Jitter nodes. And the effect born as "roughen". I need some help to redefine the strings to make more easy to undertand. Also can work on widgets to visual make a separator from Add Nodes widgets and Jitter ones. Here are the code: https://code.launchpad.net/~jabiertxof/inkscape/roughen Regards, Jabier.

1 0

Straight Geom::Curve pointAt problem
by Jabiertxo Arraiza Cenoz 26 Apr '14

26 Apr '14

Hi to all. I have a linear Geom::Curve for example whith a "d" like: M 0,0 100,0 I pass to this curve the function "pointAt(0.333333)" The previsible result is "33.333"... but this, give me "25.9259". Any body know whats happend? Thanks very much in advance.

2 2

Merge in certain Ponyscape features
by liamw 25 Apr '14

25 Apr '14

Many of the developers are probably aware of a popular fork of Inkscape called Ponyscape. If you don't know of it, here are the extra features it offers: • Inverse clipping (clearly I'm not going to merge this in) • Objects dialog (http://sta.sh/0zb66ec8hyk ) • Tags dialog (selection sets http://sta.sh/01n137vphezw ) • Power stroke point control dialog (activated by shift+clicking width points http://sta.sh/01s1vyyazw8k ) • CubicBezierSmooth Power Strokes (http://sta.sh/0232eheuvzn0 ) • UI enhancements (for example https://bugs.launchpad.net/inkscape/+bug/1310688 ) • 5 new path effects ◦ Attach Path (there is a great tutorial on this by R4inbowR4ge here http://youtu.be/5o5P0897vb8 ) ◦ Bounding Box (...clearly you know what this one does, right?) ◦ Ellipse by 5 Points ◦ Fill Between Strokes (obsoleted) ◦ Fill Between Many (http://sta.sh/0mze2vk449o ) Path effects gallery: http://sta.sh/2257tq53v5kb My plan is to get (most) of these features merged into trunk to keep them from bit-rotting away. I have created a branch here at Launchpad: https://launchpad.net/~inkscapebrony/inkscape/inkscape which addresses the majority of these features. I've also fixed this: https://bugs.launchpad.net/inkscape/+bug/1290573 and this: https://bugs.launchpad.net/inkscape/+bug/1290573 (AFAIU neither have been fixed in trunk) I'm asking for a little review—and possibly some feedback?—on the new features in the branch. Also, I am not familiar enough with the Inkscape codebase to know what to do with the very old looking SPTag stuff, which is why it isn't in my branch yet. If anyone wants to take a look and advise me on how to refactor this to make it work, the tag stuff is here: http://sta.sh/01etufm3jqvt (seriously, what the heck is an SPObjectClass? is that some sort of impls thing?) -- View this message in context: http://inkscape.13.x6.nabble.com/Merge-in-certain-Ponyscape-features-tp4970… Sent from the Inkscape - Dev mailing list archive at Nabble.com.

6 7

Clang address sanitizer abort
by Tavmjong Bah 25 Apr '14

25 Apr '14

Hi, Fedora 20 recently updated from clang 3.3 to clang 3.4. When I compiled Inkscape trunk with the new version and ran it, I immediately got an abort. I was playing around with clang a few months ago and appear to have set the CXXFLAGS to: -fsanitize=address-full,undefined,integer Can anybody help me interpret the error message? Thanks, Tav ================================================================= ==22156==ERROR: AddressSanitizer: stack-use-after-scope on address 0x7fff03896920 at pc 0x4617518 bp 0x7fff03896370 sp 0x7fff03896368 WRITE of size 8 at 0x7fff03896920 thread T0 #0 0x4617517 in std::_Deque_base<Geom::Affine, std::allocator<Geom::Affine> >::_Deque_impl::_Deque_impl() (/home/tavmjong/Sandbox_clang/bin/inkscape+0x4617517) #1 0x46170d7 in std::_Deque_base<Geom::Affine, std::allocator<Geom::Affine> >::_Deque_base() (/home/tavmjong/Sandbox_clang/bin/inkscape+0x46170d7) #2 0x45fc91e in std::deque<Geom::Affine, std::allocator<Geom::Affine> >::deque() (/home/tavmjong/Sandbox_clang/bin/inkscape+0x45fc91e) #3 0x4c0d983 in Inkscape::Extension::Internal::PrintMetafile::PrintMetafile() (/home/tavmjong/Sandbox_clang/bin/inkscape+0x4c0d983) #4 0x4b84106 in Inkscape::Extension::Internal::PrintEmf::PrintEmf() (/home/tavmjong/Sandbox_clang/bin/inkscape+0x4b84106) #5 0x4c0d434 in Inkscape::Extension::Internal::PrintEmf::init() (/home/tavmjong/Sandbox_clang/bin/inkscape+0x4c0d434) #6 0x4183e6a in Inkscape::Extension::init() (/home/tavmjong/Sandbox_clang/bin/inkscape+0x4183e6a) #7 0x1f799e4 in inkscape_application_init(char const*, int) (/home/tavmjong/Sandbox_clang/bin/inkscape+0x1f799e4) #8 0x1306174 in sp_main_gui(int, char const**) (/home/tavmjong/Sandbox_clang/bin/inkscape+0x1306174) #9 0x1303496 in main (/home/tavmjong/Sandbox_clang/bin/inkscape +0x1303496) #10 0x394f021d64 in __libc_start_main (/lib64/libc.so.6 +0x394f021d64) #11 0x12ff5cc in _start (/home/tavmjong/Sandbox_clang/bin/inkscape +0x12ff5cc) Address 0x7fff03896920 is located in stack of thread T0 at offset 96 in frame #0 0x4c0d65f in Inkscape::Extension::Internal::PrintMetafile::PrintMetafile() (/home/tavmjong/Sandbox_clang/bin/inkscape+0x4c0d65f) This frame has 4 object(s): [32, 40) '' [96, 176) '' <== Memory access at offset 96 is inside this variable [224, 232) '' [288, 292) '' HINT: this may be a false positive if your program uses some custom stack unwind mechanism or swapcontext (longjmp and C++ exceptions *are* supported) SUMMARY: AddressSanitizer: stack-use-after-scope ??:0 std::_Deque_base<Geom::Affine, std::allocator<Geom::Affine> >::_Deque_impl::_Deque_impl() Shadow bytes around the buggy address: 0x10006070acd0: f3 f3 f3 f3 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 f8 0x10006070ace0: f8 f8 f8 f8 f1 f1 f1 f1 00 f4 f4 f4 f3 f3 f3 f3 0x10006070acf0: f8 f8 f8 f8 00 00 00 00 00 00 00 00 00 00 00 00 0x10006070ad00: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0x10006070ad10: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00 f4 f4 f4 =>0x10006070ad20: f2 f2 f2 f2[f8]f8 f8 f8 f8 f8 f8 f8 00 00 f4 f4 0x10006070ad30: f2 f2 f2 f2 00 f4 f4 f4 f2 f2 f2 f2 04 f4 f4 f4 0x10006070ad40: f3 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00 0x10006070ad50: 00 00 00 00 00 00 00 00 f1 f1 f1 f1 00 f4 f4 f4 0x10006070ad60: f3 f3 f3 f3 00 00 00 00 00 00 00 00 00 00 00 00 0x10006070ad70: 00 00 00 00 00 00 00 00 00 00 00 00 f1 f1 f1 f1 Shadow byte legend (one shadow byte represents 8 application bytes): Addressable: 00 Partially addressable: 01 02 03 04 05 06 07 Heap left redzone: fa Heap right redzone: fb Freed heap region: fd Stack left redzone: f1 Stack mid redzone: f2 Stack right redzone: f3 Stack partial redzone: f4 Stack after return: f5 Stack use after scope: f8 Global redzone: f9 Global init order: f6 Poisoned by user: f7 ASan internal: fe ==22156==ABORTING

4 5

Google Summer of Code 2014
by Josh Andler 23 Apr '14

23 Apr '14

Hi All, We're happy to announce that we have two students who will be working on projects with our organization this year during Summer of Code. Krzysztof Kosiński will work on implementing robust boolean and stroking operations for 2Geom. Tomasz Boczkowski will work on improving Inkscape's support for SVG paints. We look forward to working with them and wish them the best of luck this summer. Cheers, Josh

1 0

Should select area for text objects include leading and trailing spaces?
by mathog 22 Apr '14

22 Apr '14

In this bug: https://bugs.launchpad.net/inkscape/+bug/1243401 there is a discussion about whether or not the selectable area for a text object should include leading and trailing spaces. That is, for text objects 1 = " " and 2 = " a b " the old behavior was that the "arrow" or "+A" selection pointers would not detect object 1 at all and would move across the leading and trailing spaces of object 2 without registering a hit. The patch in that bug makes these pointers treat spaces like any other character. People were coming down on both sides of the change and ScislaC suggested moving that discussion here. See posts 20-27 for the discussion so far. Regards, David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech

6 25

OSX/Win32 packaging issues
by Bryce Harrington 21 Apr '14

21 Apr '14

Okay, let's try this again. 2. Chill. √ Development focuses on wrapping up √ Disable features that aren't finished √ Identify 'make distcheck' issues -----> Identify any critical OSX/Win32 packaging issues Identify remaining writing needed for Release Notes. √ Regressions Bug Hunt: 500 points Update tutorials and other docs ------------------------------------------------------------------------ OSX Packaging Issues ------------------------------------------------------------------------ For 0.91, the OSX packaging is under renovation to bring it up to standards that OSX users expect. su_v has taken a deep look into what we've had, and is working on a new package that uses the native Gtk-Quartz functionality. As this is a pretty massive packaging change, we'll need to track this closely and lend hands as needed to ensure it's a success. Good news is there's still ample time, and strong interest in seeing this succeed. su_v, do you have a todo list of what remains to be done? ------------------------------------------------------------------------ Windows Packaging Issues ------------------------------------------------------------------------ The Windows side is also going under major renovations to introduce WIX packaging, which provides an MSI windows package. However, it sounds like the older NSI package format works well enough, that the consensus as reported by Adib is to stick with this package for 0.91, and allow the WIX package more time. Adib - do I understand the plan correctly? Are there any roadblocks or critical issues remaining? One concern I have is that we are not providing a 64-bit package, and are directing users off-site to a third party for this. I'd like to understand more about this 64-bit package, and what it would take to provide this package ourselves for 0.91. Would someone mind educating me on this? Bryce

2 1