Dear Inkscape Developers, I added a few features to Inkscape for use in embroidery, because the commercial tools available don't offer the artistic flexibility I want. I would like to have your opinion on if you think it makes sense to integrate such functionality into the Inkscape mainline, or if it would be too much of a stretch. It boils down to some LPEs and an export format. The commercial tool I have from Bernina (a Swiss sewing machine manufacturer) is based on Corel Draw. Below is a list of the additions I did / I am working on. Please let me know what you think about this. With these additions, Inkscape offers substantially more flexibility than affordable commercial SW (and affordable here means 500..1000$). Best regards, Michael 1.) Ways to fill an area with clusters of contours Inkscape already offers 2 path interpolation LPEs which allow this. I plan to add a 3rd one which creates a set of equidistant inset/outset paths. 2.) A way to connect sub path of a path into one continuous path I added an LPE to do this with various options of end interpolation. Maybe if I use bool-ops I need to extend it with some sort of sorting, cutting and auto reversing mechanism to keep the connections short. 3.) A way to cut a path into stitches (straight line segments) in a controlled way. I added an LPE to do this, but it is quite primitive as yet. 4.) Bool ops on paths because in embroidery you cannot simply hide an object below another one. I just added a bool-op LPE for this - needs some additional work to cut contours against a closed path. 5.) A tool to convert graphics output to some format an embroidery / sewing machines can read. I wrote an external tool to convert HPGL to a common embroidery format (stitch/DST), but could also integrate this into Inkscape. 6.) Maybe a tool to hide connections between path segments below filled areas. For a sewing machine it is quite complicated to do a "pen up" - it has to cut the threads, so one typically hides connection paths below some embroidery to avoid thread cutting. Currently I do this semi-manually. Doing this automatically might be quite complicated. ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Dear Inkscape Developers, I added a few features to Inkscape for use in embroidery, because the commercial tools available don't offer the artistic flexibility I want. I would like to have your opinion on if you think it makes sense to integrate such functionality into the Inkscape mainline, or if it would be too much of a stretch. It boils down to some LPEs and an export format. The commercial tool I have from Bernina (a Swiss sewing machine manufacturer) is based on Corel Draw. Below is a list of the additions I did / I am working on. Please let me know what you think about this. With these additions, Inkscape offers substantially more flexibility than affordable commercial SW (and affordable here means 500..1000$). Best regards, Michael 1.) Ways to fill an area with clusters of contours Inkscape already offers 2 path interpolation LPEs which allow this. I plan to add a 3rd one which creates a set of equidistant inset/outset paths. 2.) A way to connect sub path of a path into one continuous path I added an LPE to do this with various options of end interpolation. Maybe if I use bool-ops I need to extend it with some sort of sorting, cutting and auto reversing mechanism to keep the connections short. 3.) A way to cut a path into stitches (straight line segments) in a controlled way. I added an LPE to do this, but it is quite primitive as yet. 4.) Bool ops on paths because in embroidery you cannot simply hide an object below another one. I just added a bool-op LPE for this - needs some additional work to cut contours against a closed path. 5.) A tool to convert graphics output to some format an embroidery / sewing machines can read. I wrote an external tool to convert HPGL to a common embroidery format (stitch/DST), but could also integrate this into Inkscape. 6.) Maybe a tool to hide connections between path segments below filled areas. For a sewing machine it is quite complicated to do a "pen up" - it has to cut the threads, so one typically hides connection paths below some embroidery to avoid thread cutting. Currently I do this semi-manually. Doing this automatically might be quite complicated. ------------------------------------------------------------------------------ Site24x7 APM Insight: Get Deep Visibility into Application Performance APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month Monitor end-to-end web transactions and take corrective actions now Troubleshoot faster and improve end-user experience. Signup Now! http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Dear Josh, > Yes, I personally think this would make sense to add directly into > Inkscape. very well. I think quite a few people would love to see this in Inkscape. > Do you have your code hosted anywhere online for other to take a > look at and/or test? not yet. The main purpose of my email was to discuss the best method to do this. I guess if you plan to integrate it, I should create an embroidery branch on launchpad, which means I would need permission to do so. I should say that I have close to 0 experience with bzr, but quite a bit with git and before with SVN, Clearcase & Co. If you first want to check if I do reasonable quality code, I can of cause upload a patch e.g. on my website. In case you want me to start on launchpad right away: my launchpad account name is MSoegtrop. Best regards, Michael On 29.02.2016 04:41, Josh Andler wrote: > Hey Michael, > > Yes, I personally think this would make sense to add directly into > Inkscape. We already have Gcodetools extensions in trunk (which is "special > case" like embroidery), so to me it seems like it would be a great fit to > extend the functionality of Inkscape to include this. > > Do you have your code hosted anywhere online for other to take a look at > and/or test? > > Cheers, > Josh > > On Sat, Feb 27, 2016 at 6:39 AM, Michael Soegtrop <MSoegtrop@...889...> > wrote: > >> Dear Inkscape Developers, >> >> I added a few features to Inkscape for use in embroidery, because the >> commercial tools available don't offer the artistic flexibility I want. >> I would like to have your opinion on if you think it makes sense to >> integrate such functionality into the Inkscape mainline, or if it would >> be too much of a stretch. It boils down to some LPEs and an export >> format. The commercial tool I have from Bernina (a Swiss sewing machine >> manufacturer) is based on Corel Draw. >> >> Below is a list of the additions I did / I am working on. >> >> Please let me know what you think about this. With these additions, >> Inkscape offers substantially more flexibility than affordable >> commercial SW (and affordable here means 500..1000$). >> >> Best regards, >> >> Michael >> >> >> 1.) Ways to fill an area with clusters of contours >> >> Inkscape already offers 2 path interpolation LPEs which allow this. I >> plan to add a 3rd one which creates a set of equidistant inset/outset >> paths. >> >> >> 2.) A way to connect sub path of a path into one continuous path >> >> I added an LPE to do this with various options of end interpolation. >> Maybe if I use bool-ops I need to extend it with some sort of sorting, >> cutting and auto reversing mechanism to keep the connections short. >> >> >> 3.) A way to cut a path into stitches (straight line segments) in a >> controlled way. >> >> I added an LPE to do this, but it is quite primitive as yet. >> >> >> 4.) Bool ops on paths because in embroidery you cannot simply hide an >> object below another one. >> >> I just added a bool-op LPE for this - needs some additional work to cut >> contours against a closed path. >> >> >> 5.) A tool to convert graphics output to some format an embroidery / >> sewing machines can read. >> >> I wrote an external tool to convert HPGL to a common embroidery format >> (stitch/DST), but could also integrate this into Inkscape. >> >> >> 6.) Maybe a tool to hide connections between path segments below filled >> areas. For a sewing machine it is quite complicated to do a "pen up" - >> it has to cut the threads, so one typically hides connection paths below >> some embroidery to avoid thread cutting. >> >> Currently I do this semi-manually. Doing this automatically might be >> quite complicated. >> >> >> >> >> >> >> ------------------------------------------------------------------------------ >> Site24x7 APM Insight: Get Deep Visibility into Application Performance >> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month >> Monitor end-to-end web transactions and take corrective actions now >> Troubleshoot faster and improve end-user experience. Signup Now! >> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140 >> _______________________________________________ >> Inkscape-devel mailing list >> Inkscape-devel(a)lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/inkscape-devel >> >

I made a lib2geom toy which creates stitches especially for hair-like effects where an area should be filled with lines similar to a given curve: http://i.imgur.com/bx829Uk.png Code is in the src/toys/hair* files: https://github.com/abrock/lib2geom It works the following way: 1. Create offset curves until there is no intersection between curve and offset curve. 2. Create equidistant stitches on the middle curve 3. Create stitches similar to the ones on the middle curve on all other curves 4. Calculate intersections between curves and area outline. Throw away stitches outside the area. 5. Find the best ordering of lines so the amount of stitches along the area outline for connecting different parts is minimized. I do the connecting stitches along the outline since I sometimes want to use a very low density of lines and then I can't hide the connecting stitches under "future lines".

Great work Alexander!

Maybe you can use the half_outline form join_type LPE intead the livarot one.

Is cool you improve it! Im working in a offset LPE currently and hope can use this new code soon.

On 11/21/2016 05:53 PM, Jabier Arraiza wrote: > > Is cool you improve it! Im working in a offset LPE currently and > hope > can use this new code soon. I improved it further the new code is in the *_stable-functions here: https://github.com/abrock/lib2geom/blob/master/src/toys/geom-pathstro ke.cpp The old method for offset_cubic: 1. move the control points 2. checked if the error at t=.5 was below some threshold 2. a) if yes return 2. b) otherwise subdivide path and repeat (up to some recursion depth limit). The new method: 1. move the control points 2. Find the point on the curve where the distance differs the most from the desired distance 3. Adjust control point (only lengthes, preserve direction and smoothness) to minimize this maximum error 4. checked if the error at t=.5 was below some threshold 4. a) if yes return 4. b) otherwise subdivide path and repeat (up to some recursion depth limit). This method seems to prevent degradation where the number of nodes increases exponentially due to numerical instability. Attached are examples of the old and new method used to repeatedly offset an initial red curve. The old code produces 4625 segments in the last step, the new code 3. Should I prepare a merge request? I'd like to run some tests, any suggestions which kind? I think the most important thing is to test for a wide variety of paths if the created offset path has constant distance from the original path. Best Regards, Alexander ------------------------------------------------------------------- ----------- _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

I could help you if you want. By the way, can you tell me abot similar overlaping on Powerstroke, Bend, and Pattern Along Path. If they can be improved in similar way there is a important advance step.

I start using your code in my offset branch now to start trying.

On 11/22/2016 10:41 AM, Jabier Arraiza wrote: > I could help you if you want. By the way, can you tell me abot > similar > overlaping on Powerstroke, Bend, and Pattern Along Path. If they > can be > improved in similar way there is a important advance step. I'll have a look at the code later. Is this behaviour for Pattern Along Path considered a bug or a feature? http://imgur.com/a/29UAe So if my changes would lead to this behaviour, would that be good or bad? http://imgur.com/a/TTLZd > I start using your code in my offset branch now to start trying. I'm glad to hear that :-) Best Regards, Alexander ------------------------------------------------------------------- ----------- _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Hi Alexander, I could help you if you want. By the way, can you tell me abot similar overlaping on Powerstroke, Bend, and Pattern Along Path. If they can be improved in similar way there is a important advance step. I start using your code in my offset branch now to start trying. Cheers, Jabier. On Tue, 2016-11-22 at 04:06 -0500, Martin Owens wrote: > Hi Alexander, > > We've not moved to github yet, so if you need to do a merge > request, > you'll either have to make a bzr branch or get the help of another > developer (hopefully on the mailing list) to do the merge for you. > > Best Regards, Martin Owens > > On Tue, 2016-11-22 at 01:30 +0100, Alexander Brock wrote: > > On 11/21/2016 05:53 PM, Jabier Arraiza wrote: > > > > > > Is cool you improve it! Im working in a offset LPE currently > > > and > > > hope > > > can use this new code soon. > > > > I improved it further the new code is in the *_stable-functions > > here: > > https://github.com/abrock/lib2geom/blob/master/src/toys/geom-path > > st > > ro > > ke.cpp > > > > The old method for offset_cubic: > > 1. move the control points > > 2. checked if the error at t=.5 was below some threshold > > 2. a) if yes return > > 2. b) otherwise subdivide path and repeat (up to some recursion > > depth > > limit). > > > > The new method: > > 1. move the control points > > 2. Find the point on the curve where the distance differs the > > most > > from > > the desired distance > > 3. Adjust control point (only lengthes, preserve direction and > > smoothness) to minimize this maximum error > > 4. checked if the error at t=.5 was below some threshold > > 4. a) if yes return > > 4. b) otherwise subdivide path and repeat (up to some recursion > > depth > > limit). > > > > This method seems to prevent degradation where the number of > > nodes > > increases exponentially due to numerical instability. Attached > > are > > examples of the old and new method used to repeatedly offset an > > initial > > red curve. The old code produces 4625 segments in the last step, > > the > > new > > code 3. > > > > Should I prepare a merge request? > > I'd like to run some tests, any suggestions which kind? I think > > the > > most > > important thing is to test for a wide variety of paths if the > > created > > offset path has constant distance from the original path. > > > > Best Regards, > > Alexander > > --------------------------------------------------------------- > > ---- > > ----------- > > _______________________________________________ > > Inkscape-devel mailing list > > Inkscape-devel(a)lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > > ------------------------------------------------------------------- > ----------- > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Hi, Considering what this file contains, it might have its place in lib2geom (which is already on github ;) )

On Tue, 2016-11-22 at 10:51 +0100, Marc Jeanmougin wrote: > Hi, > > Considering what this file contains, it might have its place in > lib2geom (which is already on github ;) ) True, and if re-factored into that it makes sense to keep it there. Do we plan to keep lib2geom there if Inkscape moves to GitLab instead of GitHub? No need to keep them in the same place of course. Martin,

On 11/22/2016 11:21 AM, Martin Owens wrote: > > Considering what this file contains, it might have its place in > > lib2geom (which is already on github ;) ) > > True, and if re-factored into that it makes sense to keep it there. I could: 1. Move the file to lib2geom and create a pull request there 2. Make Inkscape trunk compatible to the new version of lib2geom Thoughts? Best Regards, Alexander ------------------------------------------------------------------- ----------- _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

On 11/23/2016 01:22 AM, Jabier Arraiza wrote: > Hi Alexander. Your code works very well in my offset branch, > Thanks. > > One thing more to do is add the more extrapolated joins located > into > helper/geom-pathstroke.cpp/h on Inkscape trunk. I copied my code into inkscape trunk (on my machine) and tested it using the "Join type" LPE. I noticed two problems: 1. It is rather slow 2. Some degenerated cases are not handled well (glitches). I'm working on it and I'm going to make a merge request to inkscape which replaces the function offset_cubic. Best Regards, Alexander ------------------------------------------------------------------- ----------- _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

Hi, I made the offset_cubic function more stable and fast and merged it into the latest version from Inkscape trunk so you can test extrapolated joins etc., you can find it here so you can test it if you want: https://github.com/abrock/lib2geom/blob/master/src/toys/geom-pathstroke.cpp I played a little with the Join Type LPE and collect path data samples so I can automatically compare different offset methods: https://github.com/abrock/lib2geom/tree/master/src/tests/half-outline-paths Feel free to send me any path data / svg file with paths that behave odd. I added a svg file with comparisons between the new and old behaviour and proposal for "correct" behaviour which I might be able to implement. Best Regards, Alexander