Inkscape for dinosaur track research, questions
Dear all,
I am palaeontologist at the University of Bonn, Germany, focusing on fossil dinosaur footprints and trackways. I regularly use Inkscape for my research (for measuring, data extration, and drawing of interpretive outlines), and have cited this software in several of my papers.
I am currently working on a methodological paper on how to analyze fossil footprints based on 3D models. The approach I will present in this paper includes Inkscape as an important component. The idea is to import raster images into Inkscape (different graphical 2D representations of the 3D model), align them into an image stack, and draw interpretive outlines on a separate layer. I use the Bezier curves tool to collect a number of landmark coordinates from the separate footprints, which I then export to automatically calculate a large number of measurements for statistical analysis. The paper is to be published in a peer-revied journal (currently, I have the Journal of Palaeontological Techniques in mind, https://www.jpaleontologicaltechniques.org/).
I already used this method in a recent paper (https://www.tandfonline.com/doi/abs/10.1080/02724634.2018.1512501) to rapidly collect measurements of a larger number of trackways. The aim of the new methodological paper is to improve this method and to make it available to our comunity of footprint researchers. However, there are two open issues/questions regarding Inkscape. I was wondering if you could give me some advice here.
Export of path node coordinates is, unfortunately, currently possible only via a plugin, which adds an additional hitch (but I understand that research is not the focus of Inkscape). Such a plugin was posted on the Inkscape Forum in 2011, with improvements added by different members (https://www.tandfonline.com/doi/abs/10.1080/02724634.2018.1512501). I simplified the code so that it returns node coordinates only (and not those of the handles), see code below.
Now to my questions:
1) I need to cite the modified coord export script in my paper, and make sure that it stays available. I assume that code published in the forum is not automatically released under a free licence, and that I cannot simply distribute the script together with the paper. A possibility might be to post the modified script to the forum and provide the link in the paper. This is only an option if the link remains available for a longer time (I cannot modify the paper once published). What would be the optimal way?
2) The coordinates given by the script need to be mirrored and translated to match the coordinates displayed within Inkscape itself. I would need to improve the script so that this is done automatically. I'm not into python scripting, but would try to figure this out. Any help/hints with this would be much appreciated.
Thank you very much in advance.
Kind regards, Jens Lallensack
----- xyexport.py -------
#!/usr/bin/env python
import inkex import sys import simpletransform import cubicsuperpath
class TemplateEffect(inkex.Effect): def __init__(self): inkex.Effect.__init__(self) def effect(self): for node in self.selected.iteritems(): output_all = output_nodes = "" for id, node in self.selected.iteritems(): if node.tag == inkex.addNS('path','svg'): output_all += "" output_nodes += "" simpletransform.fuseTransform(node) d = node.get('d') p = cubicsuperpath.parsePath(d) for subpath in p: for csp in subpath: output_nodes += str(csp[1][0]) + "\t" + str(csp[1][1]) + "\n" sys.stderr.write(output_nodes) effect = TemplateEffect() effect.affect()
Hallo Jens,
if you'd like to use a 'safe' extension that has been released under the GPL, try https://gitlab.com/su-v/inx-debug/tree/master/src (selected_nodes.py + .inx)
I've just tested it with Inkscape 1.0, and it still works (with a couple warnings, but they can be ignored).
For the one you already have... maybe ask in the forums? Who was the author? I suppose there's no license given in the python file?
In Inkscape 1.0, the coordinates displayed in the program will better match those printed out by the script (the Y axis will be inversed). Will that be enough for your purpose, or do you need the y axis in a specific direction?
Regards Maren
Am 01.11.19 um 15:37 schrieb Jens Lallensack:
Dear all,
I am palaeontologist at the University of Bonn, Germany, focusing on fossil dinosaur footprints and trackways. I regularly use Inkscape for my research (for measuring, data extration, and drawing of interpretive outlines), and have cited this software in several of my papers.
I am currently working on a methodological paper on how to analyze fossil footprints based on 3D models. The approach I will present in this paper includes Inkscape as an important component. The idea is to import raster images into Inkscape (different graphical 2D representations of the 3D model), align them into an image stack, and draw interpretive outlines on a separate layer. I use the Bezier curves tool to collect a number of landmark coordinates from the separate footprints, which I then export to automatically calculate a large number of measurements for statistical analysis. The paper is to be published in a peer-revied journal (currently, I have the Journal of Palaeontological Techniques in mind, https://www.jpaleontologicaltechniques.org/).
I already used this method in a recent paper (https://www.tandfonline.com/doi/abs/10.1080/02724634.2018.1512501) to rapidly collect measurements of a larger number of trackways. The aim of the new methodological paper is to improve this method and to make it available to our comunity of footprint researchers. However, there are two open issues/questions regarding Inkscape. I was wondering if you could give me some advice here.
Export of path node coordinates is, unfortunately, currently possible only via a plugin, which adds an additional hitch (but I understand that research is not the focus of Inkscape). Such a plugin was posted on the Inkscape Forum in 2011, with improvements added by different members (https://www.tandfonline.com/doi/abs/10.1080/02724634.2018.1512501). I simplified the code so that it returns node coordinates only (and not those of the handles), see code below.
Now to my questions:
- I need to cite the modified coord export script in my paper, and make
sure that it stays available. I assume that code published in the forum is not automatically released under a free licence, and that I cannot simply distribute the script together with the paper. A possibility might be to post the modified script to the forum and provide the link in the paper. This is only an option if the link remains available for a longer time (I cannot modify the paper once published). What would be the optimal way?
- The coordinates given by the script need to be mirrored and
translated to match the coordinates displayed within Inkscape itself. I would need to improve the script so that this is done automatically. I'm not into python scripting, but would try to figure this out. Any help/hints with this would be much appreciated.
Thank you very much in advance.
Kind regards, Jens Lallensack
----- xyexport.py -------
#!/usr/bin/env python
import inkex import sys import simpletransform import cubicsuperpath
class TemplateEffect(inkex.Effect): def __init__(self): inkex.Effect.__init__(self) def effect(self): for node in self.selected.iteritems(): output_all = output_nodes = "" for id, node in self.selected.iteritems(): if node.tag == inkex.addNS('path','svg'): output_all += "" output_nodes += "" simpletransform.fuseTransform(node) d = node.get('d') p = cubicsuperpath.parsePath(d) for subpath in p: for csp in subpath: output_nodes += str(csp[1][0]) + "\t" + str(csp[1][1]) + "\n" sys.stderr.write(output_nodes) effect = TemplateEffect() effect.affect() _______________________________________________ Inkscape Devel mailing list -- inkscape-devel@lists.inkscape.org To unsubscribe send an email to inkscape-devel-leave@lists.inkscape.org
Hello Maren,
thank you for the quick response. This already helps a lot!
if you'd like to use a 'safe' extension that has been released under the GPL, try https://gitlab.com/su-v/inx-debug/tree/master/src (selected_nodes.py + .inx)
Thanks for this hint. This works fine with Inkscape 0.92 for me (though not with 1.0, see below), and I think I will be able to simplify it according to my needs.
In Inkscape 1.0, the coordinates displayed in the program will better match those printed out by the script (the Y axis will be inversed). Will that be enough for your purpose, or do you need the y axis in a specific direction?
This is very good news. I need to have the correct values for the x axis only, the Y axis doesn't matter, so this would already solve the problem. I just compiled Inkscape 1.0 beta1 (under Linux), but both extensions (exportxy.py and selected_nodes.py) stopped working (they still appear in the "Extensions" menu, but are greyed out). Did I miss something?
Best wishes, Jens
Hallo Jens,
Am 02.11.19 um 09:25 schrieb Jens Lallensack:
In Inkscape 1.0, the coordinates displayed in the program will better match those printed out by the script (the Y axis will be inversed). Will that be enough for your purpose, or do you need the y axis in a specific direction?
This is very good news. I need to have the correct values for the x axis only, the Y axis doesn't matter, so this would already solve the problem.
- The x axis values will not change with the new version.
If your issue is that values are off by a certain factor, then you need to adjust the units (mm with default template) or the document scale setting (set it to 1). The latter will change the size of the content, so use with care.
I just compiled Inkscape 1.0 beta1 (under Linux), but both extensions (exportxy.py and selected_nodes.py) stopped working (they still appear in the "Extensions" menu, but are greyed out). Did I miss something?
- As for the greying out - it's not greyed out for me anymore (but it was).
I'm using the latest stock extensions from the extensions repository, and the latest master, not the official beta1 release (you can tell from the date in the Help > About dialog).
I'm not sure which one of these two things makes the difference for the greying out, I think it's the main repository code, not the extensions, but not 100% sure.
Maren
Whats the correct link for the forum post? you seem to have linked the paper twice.
Cheers
John
On Fri, Nov 1, 2019 at 2:38 PM Jens Lallensack jens.lallensack@gmail.com wrote:
Dear all,
I am palaeontologist at the University of Bonn, Germany, focusing on fossil dinosaur footprints and trackways. I regularly use Inkscape for my research (for measuring, data extration, and drawing of interpretive outlines), and have cited this software in several of my papers.
I am currently working on a methodological paper on how to analyze fossil footprints based on 3D models. The approach I will present in this paper includes Inkscape as an important component. The idea is to import raster images into Inkscape (different graphical 2D representations of the 3D model), align them into an image stack, and draw interpretive outlines on a separate layer. I use the Bezier curves tool to collect a number of landmark coordinates from the separate footprints, which I then export to automatically calculate a large number of measurements for statistical analysis. The paper is to be published in a peer-revied journal (currently, I have the Journal of Palaeontological Techniques in mind, https://www.jpaleontologicaltechniques.org/).
I already used this method in a recent paper (https://www.tandfonline.com/doi/abs/10.1080/02724634.2018.1512501) to rapidly collect measurements of a larger number of trackways. The aim of the new methodological paper is to improve this method and to make it available to our comunity of footprint researchers. However, there are two open issues/questions regarding Inkscape. I was wondering if you could give me some advice here.
Export of path node coordinates is, unfortunately, currently possible only via a plugin, which adds an additional hitch (but I understand that research is not the focus of Inkscape). Such a plugin was posted on the Inkscape Forum in 2011, with improvements added by different members (https://www.tandfonline.com/doi/abs/10.1080/02724634.2018.1512501). I simplified the code so that it returns node coordinates only (and not those of the handles), see code below.
Now to my questions:
- I need to cite the modified coord export script in my paper, and make
sure that it stays available. I assume that code published in the forum is not automatically released under a free licence, and that I cannot simply distribute the script together with the paper. A possibility might be to post the modified script to the forum and provide the link in the paper. This is only an option if the link remains available for a longer time (I cannot modify the paper once published). What would be the optimal way?
- The coordinates given by the script need to be mirrored and
translated to match the coordinates displayed within Inkscape itself. I would need to improve the script so that this is done automatically. I'm not into python scripting, but would try to figure this out. Any help/hints with this would be much appreciated.
Thank you very much in advance.
Kind regards, Jens Lallensack
----- xyexport.py -------
#!/usr/bin/env python
import inkex import sys import simpletransform import cubicsuperpath
class TemplateEffect(inkex.Effect): def __init__(self): inkex.Effect.__init__(self) def effect(self): for node in self.selected.iteritems(): output_all = output_nodes = "" for id, node in self.selected.iteritems(): if node.tag == inkex.addNS('path','svg'): output_all += "" output_nodes += "" simpletransform.fuseTransform(node) d = node.get('d') p = cubicsuperpath.parsePath(d) for subpath in p: for csp in subpath: output_nodes += str(csp[1][0]) + "\t" + str(csp[1][1]) + "\n" sys.stderr.write(output_nodes) effect = TemplateEffect() effect.affect() _______________________________________________ Inkscape Devel mailing list -- inkscape-devel@lists.inkscape.org To unsubscribe send an email to inkscape-devel-leave@lists.inkscape.org
Hi John,
thanks!
This is the forum post with the improved version of the script: http://www.inkscapeforum.com/viewtopic.php?t=8826#p32088
And here is the original version (same forum topic): http://www.inkscapeforum.com/viewtopic.php?t=8826#p31912
Best wishes, Jens
Am 02/11/2019 um 13:29 schrieb John Cliff:
Whats the correct link for the forum post? you seem to have linked the paper twice.
Cheers
John
On Fri, Nov 1, 2019 at 2:38 PM Jens Lallensack <jens.lallensack@gmail.com mailto:jens.lallensack@gmail.com> wrote:
Dear all, I am palaeontologist at the University of Bonn, Germany, focusing on fossil dinosaur footprints and trackways. I regularly use Inkscape for my research (for measuring, data extration, and drawing of interpretive outlines), and have cited this software in several of my papers. I am currently working on a methodological paper on how to analyze fossil footprints based on 3D models. The approach I will present in this paper includes Inkscape as an important component. The idea is to import raster images into Inkscape (different graphical 2D representations of the 3D model), align them into an image stack, and draw interpretive outlines on a separate layer. I use the Bezier curves tool to collect a number of landmark coordinates from the separate footprints, which I then export to automatically calculate a large number of measurements for statistical analysis. The paper is to be published in a peer-revied journal (currently, I have the Journal of Palaeontological Techniques in mind, https://www.jpaleontologicaltechniques.org/). I already used this method in a recent paper (https://www.tandfonline.com/doi/abs/10.1080/02724634.2018.1512501) to rapidly collect measurements of a larger number of trackways. The aim of the new methodological paper is to improve this method and to make it available to our comunity of footprint researchers. However, there are two open issues/questions regarding Inkscape. I was wondering if you could give me some advice here. Export of path node coordinates is, unfortunately, currently possible only via a plugin, which adds an additional hitch (but I understand that research is not the focus of Inkscape). Such a plugin was posted on the Inkscape Forum in 2011, with improvements added by different members (https://www.tandfonline.com/doi/abs/10.1080/02724634.2018.1512501). I simplified the code so that it returns node coordinates only (and not those of the handles), see code below. Now to my questions: 1) I need to cite the modified coord export script in my paper, and make sure that it stays available. I assume that code published in the forum is not automatically released under a free licence, and that I cannot simply distribute the script together with the paper. A possibility might be to post the modified script to the forum and provide the link in the paper. This is only an option if the link remains available for a longer time (I cannot modify the paper once published). What would be the optimal way? 2) The coordinates given by the script need to be mirrored and translated to match the coordinates displayed within Inkscape itself. I would need to improve the script so that this is done automatically. I'm not into python scripting, but would try to figure this out. Any help/hints with this would be much appreciated. Thank you very much in advance. Kind regards, Jens Lallensack ----- xyexport.py ------- #!/usr/bin/env python import inkex import sys import simpletransform import cubicsuperpath class TemplateEffect(inkex.Effect): def __init__(self): inkex.Effect.__init__(self) def effect(self): for node in self.selected.iteritems(): output_all = output_nodes = "" for id, node in self.selected.iteritems(): if node.tag == inkex.addNS('path','svg'): output_all += "" output_nodes += "" simpletransform.fuseTransform(node) d = node.get('d') p = cubicsuperpath.parsePath(d) for subpath in p: for csp in subpath: output_nodes += str(csp[1][0]) + "\t" + str(csp[1][1]) + "\n" sys.stderr.write(output_nodes) effect = TemplateEffect() effect.affect() _______________________________________________ Inkscape Devel mailing list -- inkscape-devel@lists.inkscape.org <mailto:inkscape-devel@lists.inkscape.org> To unsubscribe send an email to inkscape-devel-leave@lists.inkscape.org <mailto:inkscape-devel-leave@lists.inkscape.org>
Thought it looked familiar. I'm Simarilius in that thread, I supplied the dodgy original version that Neon22 improved. I'm happy for the code to be published, I based it off a blog post from a now dead blog (wayback link is here: http://web.archive.org/web/20141216062123/http://jumpnslide.tumblr.com/post/...) I have an email from that blog author Jean Moreno confirming he was happy for the code to be modified/ released under GPL which I can forward to you if you wish. Neon22 that modified it doesn't appear to have been active on the forum since 2013, but appears to have been active on Github and Inkscape.org recently. I've just tried emailing them via the openscad forum, will let you know if they reply.
Cheers
John
On Sat, Nov 2, 2019 at 12:52 PM Jens Lallensack jens.lallensack@gmail.com wrote:
Hi John,
thanks!
This is the forum post with the improved version of the script: http://www.inkscapeforum.com/viewtopic.php?t=8826#p32088
And here is the original version (same forum topic): http://www.inkscapeforum.com/viewtopic.php?t=8826#p31912
Best wishes, Jens
Am 02/11/2019 um 13:29 schrieb John Cliff:
Whats the correct link for the forum post? you seem to have linked the paper twice.
Cheers
John
On Fri, Nov 1, 2019 at 2:38 PM Jens Lallensack <jens.lallensack@gmail.com mailto:jens.lallensack@gmail.com> wrote:
Dear all, I am palaeontologist at the University of Bonn, Germany, focusing on fossil dinosaur footprints and trackways. I regularly use Inkscapefor
my research (for measuring, data extration, and drawing ofinterpretive
outlines), and have cited this software in several of my papers. I am currently working on a methodological paper on how to analyze fossil footprints based on 3D models. The approach I will present in this paper includes Inkscape as an important component. The idea isto
import raster images into Inkscape (different graphical 2D representations of the 3D model), align them into an image stack, and draw interpretive outlines on a separate layer. I use the Beziercurves
tool to collect a number of landmark coordinates from the separate footprints, which I then export to automatically calculate a large number of measurements for statistical analysis. The paper is to be published in a peer-revied journal (currently, I have the Journal of Palaeontological Techniques in mind, https://www.jpaleontologicaltechniques.org/). I already used this method in a recent paper (https://www.tandfonline.com/doi/abs/10.1080/02724634.2018.1512501)to
rapidly collect measurements of a larger number of trackways. The aim of the new methodological paper is to improve this method and to make it available to our comunity of footprint researchers. However, thereare
two open issues/questions regarding Inkscape. I was wondering if you could give me some advice here. Export of path node coordinates is, unfortunately, currently possible only via a plugin, which adds an additional hitch (but I understand that research is not the focus of Inkscape). Such a plugin was posted onthe
Inkscape Forum in 2011, with improvements added by different members (https://www.tandfonline.com/doi/abs/10.1080/02724634.2018.1512501).I
simplified the code so that it returns node coordinates only (and not those of the handles), see code below. Now to my questions: 1) I need to cite the modified coord export script in my paper, and make sure that it stays available. I assume that code published in theforum
is not automatically released under a free licence, and that I cannot simply distribute the script together with the paper. A possibility might be to post the modified script to the forum and provide thelink
in the paper. This is only an option if the link remains available for a longer time (I cannot modify the paper once published). What would be the optimal way? 2) The coordinates given by the script need to be mirrored and translated to match the coordinates displayed within Inkscapeitself. I
would need to improve the script so that this is done automatically. I'm not into python scripting, but would try to figure this out. Any help/hints with this would be much appreciated. Thank you very much in advance. Kind regards, Jens Lallensack ----- xyexport.py ------- #!/usr/bin/env python import inkex import sys import simpletransform import cubicsuperpath class TemplateEffect(inkex.Effect): def __init__(self): inkex.Effect.__init__(self) def effect(self): for node in self.selected.iteritems(): output_all = output_nodes = "" for id, node in self.selected.iteritems(): if node.tag == inkex.addNS('path','svg'): output_all += "" output_nodes += "" simpletransform.fuseTransform(node) d = node.get('d') p = cubicsuperpath.parsePath(d) for subpath in p: for csp in subpath: output_nodes += str(csp[1][0]) + "\t" + str(csp[1][1]) + "\n" sys.stderr.write(output_nodes) effect = TemplateEffect() effect.affect() _______________________________________________ Inkscape Devel mailing list -- inkscape-devel@lists.inkscape.org <mailto:inkscape-devel@lists.inkscape.org> To unsubscribe send an email to inkscape-devel-leave@lists.inkscape.org <mailto:inkscape-devel-leave@lists.inkscape.org>
Hi John,
wow, I certainly asked at the right place! Thank you so much for your efforts, it would be wonderful if it can be released under GPL.
Best, Jens
Am 02/11/2019 um 14:42 schrieb John Cliff:
Thought it looked familiar. I'm Simarilius in that thread, I supplied the dodgy original version that Neon22 improved. I'm happy for the code to be published, I based it off a blog post from a now dead blog (wayback link is here: http://web.archive.org/web/20141216062123/http://jumpnslide.tumblr.com/post/...) I have an email from that blog author Jean Moreno confirming he was happy for the code to be modified/ released under GPL which I can forward to you if you wish. Neon22 that modified it doesn't appear to have been active on the forum since 2013, but appears to have been active on Github and Inkscape.org recently. I've just tried emailing them via the openscad forum, will let you know if they reply.
Cheers
John
On Sat, Nov 2, 2019 at 12:52 PM Jens Lallensack <jens.lallensack@gmail.com mailto:jens.lallensack@gmail.com> wrote:
Hi John, thanks! This is the forum post with the improved version of the script: http://www.inkscapeforum.com/viewtopic.php?t=8826#p32088 And here is the original version (same forum topic): http://www.inkscapeforum.com/viewtopic.php?t=8826#p31912 Best wishes, Jens Am 02/11/2019 um 13:29 schrieb John Cliff: > Whats the correct link for the forum post? you seem to have linked the > paper twice. > > Cheers > > John > > On Fri, Nov 1, 2019 at 2:38 PM Jens Lallensack > <jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com> <mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com>>> wrote: > > > Dear all, > > I am palaeontologist at the University of Bonn, Germany, focusing on > fossil dinosaur footprints and trackways. I regularly use Inkscape for > my research (for measuring, data extration, and drawing of interpretive > outlines), and have cited this software in several of my papers. > > I am currently working on a methodological paper on how to analyze > fossil footprints based on 3D models. The approach I will present in > this paper includes Inkscape as an important component. The idea is to > import raster images into Inkscape (different graphical 2D > representations of the 3D model), align them into an image stack, and > draw interpretive outlines on a separate layer. I use the Bezier curves > tool to collect a number of landmark coordinates from the separate > footprints, which I then export to automatically calculate a large > number of measurements for statistical analysis. The paper is to be > published in a peer-revied journal (currently, I have the Journal of > Palaeontological Techniques in mind, > https://www.jpaleontologicaltechniques.org/). > > I already used this method in a recent paper > (https://www.tandfonline.com/doi/abs/10.1080/02724634.2018.1512501) to > rapidly collect measurements of a larger number of trackways. The > aim of > the new methodological paper is to improve this method and to make it > available to our comunity of footprint researchers. However, there are > two open issues/questions regarding Inkscape. I was wondering if you > could give me some advice here. > > Export of path node coordinates is, unfortunately, currently possible > only via a plugin, which adds an additional hitch (but I understand > that > research is not the focus of Inkscape). Such a plugin was posted on the > Inkscape Forum in 2011, with improvements added by different members > (https://www.tandfonline.com/doi/abs/10.1080/02724634.2018.1512501). I > simplified the code so that it returns node coordinates only (and not > those of the handles), see code below. > > Now to my questions: > > 1) I need to cite the modified coord export script in my paper, and > make > sure that it stays available. I assume that code published in the forum > is not automatically released under a free licence, and that I cannot > simply distribute the script together with the paper. A possibility > might be to post the modified script to the forum and provide the link > in the paper. This is only an option if the link remains available > for a > longer time (I cannot modify the paper once published). What would be > the optimal way? > > 2) The coordinates given by the script need to be mirrored and > translated to match the coordinates displayed within Inkscape itself. I > would need to improve the script so that this is done automatically. > I'm > not into python scripting, but would try to figure this out. Any > help/hints with this would be much appreciated. > > Thank you very much in advance. > > Kind regards, > Jens Lallensack > > > > ----- xyexport.py ------- > > #!/usr/bin/env python > > import inkex > import sys > import simpletransform > import cubicsuperpath > > class TemplateEffect(inkex.Effect): > def __init__(self): > inkex.Effect.__init__(self) > def effect(self): > for node in self.selected.iteritems(): > output_all = output_nodes = "" > for id, node in self.selected.iteritems(): > if node.tag == inkex.addNS('path','svg'): > output_all += "" > output_nodes += "" > simpletransform.fuseTransform(node) > d = node.get('d') > p = cubicsuperpath.parsePath(d) > for subpath in p: > for csp in subpath: > output_nodes += str(csp[1][0]) + "\t" + > str(csp[1][1]) + "\n" > sys.stderr.write(output_nodes) > effect = TemplateEffect() > effect.affect() > _______________________________________________ > Inkscape Devel mailing list -- inkscape-devel@lists.inkscape.org <mailto:inkscape-devel@lists.inkscape.org> > <mailto:inkscape-devel@lists.inkscape.org <mailto:inkscape-devel@lists.inkscape.org>> > To unsubscribe send an email to > inkscape-devel-leave@lists.inkscape.org <mailto:inkscape-devel-leave@lists.inkscape.org> > <mailto:inkscape-devel-leave@lists.inkscape.org <mailto:inkscape-devel-leave@lists.inkscape.org>> >
Hi Jens,
Heard back from Neon22, hes very happy for it to be released under GPL. If you can add this to the top of the code you put in the paper:
# # curve xy co-ordinate export # Authors: # Jean Moreno jean.moreno.fr@gmail.com # John Cliff john.cliff@gmail.com # Neon22 https://github.com/Neon22?tab=repositories # # Copyright (C) 2011 Jean Moreno # Copyright (C) 2011 John Cliff # Copyright (C) 2011 Neon22 # # Released under GNU GPL v3, see https://www.gnu.org/licenses/gpl-3.0.en.html for details. #
obviously add your name to those lists since you've modified it.
Thanks
John
On Sat, Nov 2, 2019 at 3:21 PM Jens Lallensack jens.lallensack@gmail.com wrote:
Hi John,
wow, I certainly asked at the right place! Thank you so much for your efforts, it would be wonderful if it can be released under GPL.
Best, Jens
Am 02/11/2019 um 14:42 schrieb John Cliff:
Thought it looked familiar. I'm Simarilius in that thread, I supplied the dodgy original version that Neon22 improved. I'm happy for the code to be published, I based it off a blog post from a now dead blog (wayback link is here:
http://web.archive.org/web/20141216062123/http://jumpnslide.tumblr.com/post/...)
I have an email from that blog author Jean Moreno confirming he was happy for the code to be modified/ released under GPL which I can forward to you if you wish. Neon22 that modified it doesn't appear to have been active on the forum since 2013, but appears to have been active on Github and Inkscape.org recently. I've just tried emailing them via the openscad forum, will let you know if they reply.
Cheers
John
On Sat, Nov 2, 2019 at 12:52 PM Jens Lallensack <jens.lallensack@gmail.com mailto:jens.lallensack@gmail.com> wrote:
Hi John, thanks! This is the forum post with the improved version of the script: http://www.inkscapeforum.com/viewtopic.php?t=8826#p32088 And here is the original version (same forum topic): http://www.inkscapeforum.com/viewtopic.php?t=8826#p31912 Best wishes, Jens Am 02/11/2019 um 13:29 schrieb John Cliff: > Whats the correct link for the forum post? you seem to have linked the > paper twice. > > Cheers > > John > > On Fri, Nov 1, 2019 at 2:38 PM Jens Lallensack > <jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com> <mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com>>> wrote: > > > Dear all, > > I am palaeontologist at the University of Bonn, Germany, focusing on > fossil dinosaur footprints and trackways. I regularly use Inkscape for > my research (for measuring, data extration, and drawing of interpretive > outlines), and have cited this software in several of mypapers.
> > I am currently working on a methodological paper on how to analyze > fossil footprints based on 3D models. The approach I will present in > this paper includes Inkscape as an important component. The idea is to > import raster images into Inkscape (different graphical 2D > representations of the 3D model), align them into an image stack, and > draw interpretive outlines on a separate layer. I use the Bezier curves > tool to collect a number of landmark coordinates from the separate > footprints, which I then export to automatically calculate a large > number of measurements for statistical analysis. The paper is to be > published in a peer-revied journal (currently, I have the Journal of > Palaeontological Techniques in mind, > https://www.jpaleontologicaltechniques.org/). > > I already used this method in a recent paper > (https://www.tandfonline.com/doi/abs/10.1080/02724634.2018.1512501)to
> rapidly collect measurements of a larger number of trackways.The
> aim of > the new methodological paper is to improve this method and to make it > available to our comunity of footprint researchers. However, there are > two open issues/questions regarding Inkscape. I was wondering if you > could give me some advice here. > > Export of path node coordinates is, unfortunately, currently possible > only via a plugin, which adds an additional hitch (but I understand > that > research is not the focus of Inkscape). Such a plugin was posted on the > Inkscape Forum in 2011, with improvements added by different members > (https://www.tandfonline.com/doi/abs/10.1080/02724634.2018.1512501).I
> simplified the code so that it returns node coordinates only (and not > those of the handles), see code below. > > Now to my questions: > > 1) I need to cite the modified coord export script in my paper, and > make > sure that it stays available. I assume that code published in the forum > is not automatically released under a free licence, and that I cannot > simply distribute the script together with the paper. A possibility > might be to post the modified script to the forum and provide the link > in the paper. This is only an option if the link remains available > for a > longer time (I cannot modify the paper once published). What would be > the optimal way? > > 2) The coordinates given by the script need to be mirrored and > translated to match the coordinates displayed within Inkscape itself. I > would need to improve the script so that this is done automatically. > I'm > not into python scripting, but would try to figure this out.Any
> help/hints with this would be much appreciated. > > Thank you very much in advance. > > Kind regards, > Jens Lallensack > > > > ----- xyexport.py ------- > > #!/usr/bin/env python > > import inkex > import sys > import simpletransform > import cubicsuperpath > > class TemplateEffect(inkex.Effect): > def __init__(self): > inkex.Effect.__init__(self) > def effect(self): > for node in self.selected.iteritems(): > output_all = output_nodes = "" > for id, node in self.selected.iteritems(): > if node.tag == inkex.addNS('path','svg'): > output_all += "" > output_nodes += "" > simpletransform.fuseTransform(node) > d = node.get('d') > p = cubicsuperpath.parsePath(d) > for subpath in p: > for csp in subpath: > output_nodes += str(csp[1][0]) + "\t" + > str(csp[1][1]) + "\n" > sys.stderr.write(output_nodes) > effect = TemplateEffect() > effect.affect() > _______________________________________________ > Inkscape Devel mailing list -- inkscape-devel@lists.inkscape.org <mailto:inkscape-devel@lists.inkscape.org> > <mailto:inkscape-devel@lists.inkscape.org <mailto:inkscape-devel@lists.inkscape.org>> > To unsubscribe send an email to > inkscape-devel-leave@lists.inkscape.org <mailto:inkscape-devel-leave@lists.inkscape.org> > <mailto:inkscape-devel-leave@lists.inkscape.org <mailto:inkscape-devel-leave@lists.inkscape.org>> >
Hi Maren, John,
many thanks again!
@Maren: I now tested using the latest development version, and the "selected_nodes" extension now works for me. However, I found that the coordinates are not returned in sequential order (the order that defines the path), which is crucial for my purpose, but in some random order. The order is even slightly different with Inkscape 0.91 compared to the development version. I would therefore, for now, stick with the ExportXY plugin, which, thanks to John, can now be published under the GPL.
Thank you very much for the hint with the document scale setting – that completely solved the issue that the x values were off.
@John: Thousand thanks, this is perfect!
The extension stopped working with Inkscape 1.0 though, which I was able to fix to some extent. I changed "self.selected.iteritems()" to "self.selected.items()" and now get the values again, together with a number of deprecation warnings. I was unable to resolve these warnings for now (any help welcome, of course), but I included an ugly hack that turns these warnings off, so that at least the output is clear.
A very pleasant surprise was that with Inkscape 1.0, both x and y values returned by the script fully match those displayed in Inkscape (without the y axis being inverted or similar).
I attached the modified code to this email.
Best wishes, and thanks again, Jens
Am 03/11/2019 um 10:32 schrieb John Cliff:
Hi Jens,
Heard back from Neon22, hes very happy for it to be released under GPL. If you can add this to the top of the code you put in the paper:
# # curve xy co-ordinate export # Authors: # Jean Moreno <jean.moreno.fr@gmail.com mailto:jean.moreno.fr@gmail.com> # John Cliff <john.cliff@gmail.com mailto:john.cliff@gmail.com> # Neon22 https://github.com/Neon22?tab=repositories # # Copyright (C) 2011 Jean Moreno # Copyright (C) 2011 John Cliff # Copyright (C) 2011 Neon22 # # Released under GNU GPL v3, see https://www.gnu.org/licenses/gpl-3.0.en.html for details. #
obviously add your name to those lists since you've modified it.
Thanks
John
On Sat, Nov 2, 2019 at 3:21 PM Jens Lallensack <jens.lallensack@gmail.com mailto:jens.lallensack@gmail.com> wrote:
Hi John, wow, I certainly asked at the right place! Thank you so much for your efforts, it would be wonderful if it can be released under GPL. Best, Jens Am 02/11/2019 um 14:42 schrieb John Cliff: > Thought it looked familiar. I'm Simarilius in that thread, I supplied > the dodgy original version that Neon22 improved. > I'm happy for the code to be published, I based it off a blog post from > a now dead blog (wayback link is here: > http://web.archive.org/web/20141216062123/http://jumpnslide.tumblr.com/post/2557920924/how-to-use-inkscape-as-a-game-development-tool) > I have an email from that blog author Jean Moreno confirming he was > happy for the code to be modified/ released under GPL which I can > forward to you if you wish. > Neon22 that modified it doesn't appear to have been active on the forum > since 2013, but appears to have been active on Github and Inkscape.org > recently. I've just tried emailing them via the openscad forum, will let > you know if they reply. > > Cheers > > John > > On Sat, Nov 2, 2019 at 12:52 PM Jens Lallensack > <jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com> <mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com>>> wrote: > > > Hi John, > > thanks! > > This is the forum post with the improved version of the script: > http://www.inkscapeforum.com/viewtopic.php?t=8826#p32088 > > And here is the original version (same forum topic): > http://www.inkscapeforum.com/viewtopic.php?t=8826#p31912 > > Best wishes, > Jens > > > > > Am 02/11/2019 um 13:29 schrieb John Cliff: > > Whats the correct link for the forum post? you seem to have > linked the > > paper twice. > > > > Cheers > > > > John > > > > On Fri, Nov 1, 2019 at 2:38 PM Jens Lallensack > > <jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com> <mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com>> > <mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com> > <mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com>>>> wrote: > > > > > > Dear all, > > > > I am palaeontologist at the University of Bonn, Germany, > focusing on > > fossil dinosaur footprints and trackways. I regularly use > Inkscape for > > my research (for measuring, data extration, and drawing of > interpretive > > outlines), and have cited this software in several of my papers. > > > > I am currently working on a methodological paper on how to > analyze > > fossil footprints based on 3D models. The approach I will > present in > > this paper includes Inkscape as an important component. The > idea is to > > import raster images into Inkscape (different graphical 2D > > representations of the 3D model), align them into an image > stack, and > > draw interpretive outlines on a separate layer. I use the > Bezier curves > > tool to collect a number of landmark coordinates from the > separate > > footprints, which I then export to automatically calculate a > large > > number of measurements for statistical analysis. The paper is > to be > > published in a peer-revied journal (currently, I have the > Journal of > > Palaeontological Techniques in mind, > > https://www.jpaleontologicaltechniques.org/). > > > > I already used this method in a recent paper > > > (https://www.tandfonline.com/doi/abs/10.1080/02724634.2018.1512501) to > > rapidly collect measurements of a larger number of trackways. The > > aim of > > the new methodological paper is to improve this method and to > make it > > available to our comunity of footprint researchers. However, > there are > > two open issues/questions regarding Inkscape. I was wondering > if you > > could give me some advice here. > > > > Export of path node coordinates is, unfortunately, currently > possible > > only via a plugin, which adds an additional hitch (but I > understand > > that > > research is not the focus of Inkscape). Such a plugin was > posted on the > > Inkscape Forum in 2011, with improvements added by different > members > > > (https://www.tandfonline.com/doi/abs/10.1080/02724634.2018.1512501). I > > simplified the code so that it returns node coordinates only > (and not > > those of the handles), see code below. > > > > Now to my questions: > > > > 1) I need to cite the modified coord export script in my > paper, and > > make > > sure that it stays available. I assume that code published in > the forum > > is not automatically released under a free licence, and that > I cannot > > simply distribute the script together with the paper. A > possibility > > might be to post the modified script to the forum and provide > the link > > in the paper. This is only an option if the link remains > available > > for a > > longer time (I cannot modify the paper once published). What > would be > > the optimal way? > > > > 2) The coordinates given by the script need to be mirrored and > > translated to match the coordinates displayed within Inkscape > itself. I > > would need to improve the script so that this is done > automatically. > > I'm > > not into python scripting, but would try to figure this out. Any > > help/hints with this would be much appreciated. > > > > Thank you very much in advance. > > > > Kind regards, > > Jens Lallensack > > > > > > > > ----- xyexport.py ------- > > > > #!/usr/bin/env python > > > > import inkex > > import sys > > import simpletransform > > import cubicsuperpath > > > > class TemplateEffect(inkex.Effect): > > def __init__(self): > > inkex.Effect.__init__(self) > > def effect(self): > > for node in self.selected.iteritems(): > > output_all = output_nodes = "" > > for id, node in self.selected.iteritems(): > > if node.tag == inkex.addNS('path','svg'): > > output_all += "" > > output_nodes += "" > > simpletransform.fuseTransform(node) > > d = node.get('d') > > p = cubicsuperpath.parsePath(d) > > for subpath in p: > > for csp in subpath: > > output_nodes += str(csp[1][0]) > + "\t" + > > str(csp[1][1]) + "\n" > > sys.stderr.write(output_nodes) > > effect = TemplateEffect() > > effect.affect() > > _______________________________________________ > > Inkscape Devel mailing list -- > inkscape-devel@lists.inkscape.org <mailto:inkscape-devel@lists.inkscape.org> > <mailto:inkscape-devel@lists.inkscape.org <mailto:inkscape-devel@lists.inkscape.org>> > > <mailto:inkscape-devel@lists.inkscape.org <mailto:inkscape-devel@lists.inkscape.org> > <mailto:inkscape-devel@lists.inkscape.org <mailto:inkscape-devel@lists.inkscape.org>>> > > To unsubscribe send an email to > > inkscape-devel-leave@lists.inkscape.org <mailto:inkscape-devel-leave@lists.inkscape.org> > <mailto:inkscape-devel-leave@lists.inkscape.org <mailto:inkscape-devel-leave@lists.inkscape.org>> > > <mailto:inkscape-devel-leave@lists.inkscape.org <mailto:inkscape-devel-leave@lists.inkscape.org> > <mailto:inkscape-devel-leave@lists.inkscape.org <mailto:inkscape-devel-leave@lists.inkscape.org>>> > > >
Am 03.11.19 um 18:57 schrieb Jens Lallensack:
Hi Maren, John,
many thanks again!
@Maren: I now tested using the latest development version, and the "selected_nodes" extension now works for me. However, I found that the coordinates are not returned in sequential order (the order that defines the path), which is crucial for my purpose, but in some random order. The order is even slightly different with Inkscape 0.91 compared to the development version. I would therefore, for now, stick with the ExportXY plugin, which, thanks to John, can now be published under the GPL.
- Mmh. Yes, it looks like the extension goes by selection order. Probably you're using Ctrl+A or click+drag to select the nodes, and that function of Inkscape seems to create some kind of random order in the node list that Inkscape hands on to the extension.
Good that the other extension does what you need! (I think it wasn't possible yet at the time to get the selected nodes list, so that extension doesn't know about the node list from Inkscape, and can't be confused by its ordering).
Maybe one of the persons involved could put the extension into a repository at gitlab or another code hosting site? That way, it's not going to get lost again :)
Maren
Thank you very much for the hint with the document scale setting – that completely solved the issue that the x values were off.
@John: Thousand thanks, this is perfect!
The extension stopped working with Inkscape 1.0 though, which I was able to fix to some extent. I changed "self.selected.iteritems()" to "self.selected.items()" and now get the values again, together with a number of deprecation warnings. I was unable to resolve these warnings for now (any help welcome, of course), but I included an ugly hack that turns these warnings off, so that at least the output is clear.
A very pleasant surprise was that with Inkscape 1.0, both x and y values returned by the script fully match those displayed in Inkscape (without the y axis being inverted or similar).
I attached the modified code to this email.
Best wishes, and thanks again, Jens
Am 03/11/2019 um 10:32 schrieb John Cliff:
Hi Jens,
Heard back from Neon22, hes very happy for it to be released under GPL. If you can add this to the top of the code you put in the paper:
# # curve xy co-ordinate export # Authors: # Jean Moreno <jean.moreno.fr@gmail.com mailto:jean.moreno.fr@gmail.com> # John Cliff <john.cliff@gmail.com mailto:john.cliff@gmail.com> # Neon22 https://github.com/Neon22?tab=repositories # # Copyright (C) 2011 Jean Moreno # Copyright (C) 2011 John Cliff # Copyright (C) 2011 Neon22 # # Released under GNU GPL v3, see https://www.gnu.org/licenses/gpl-3.0.en.html for details. #
obviously add your name to those lists since you've modified it.
Thanks
John
On Sat, Nov 2, 2019 at 3:21 PM Jens Lallensack <jens.lallensack@gmail.com mailto:jens.lallensack@gmail.com> wrote:
Hi John,
wow, I certainly asked at the right place! Thank you so much for your efforts, it would be wonderful if it can be released under GPL.
Best, Jens
Am 02/11/2019 um 14:42 schrieb John Cliff: > Thought it looked familiar. I'm Simarilius in that thread, I supplied > the dodgy original version that Neon22 improved. > I'm happy for the code to be published, I based it off a blog post from > a now dead blog (wayback link is here: > http://web.archive.org/web/20141216062123/http://jumpnslide.tumblr.com/post/...)
> I have an email from that blog author Jean Moreno confirming he was > happy for the code to be modified/ released under GPL which I can > forward to you if you wish. > Neon22 that modified it doesn't appear to have been active on the forum > since 2013, but appears to have been active on Github and Inkscape.org > recently. I've just tried emailing them via the openscad forum, will let > you know if they reply. > > Cheers > > John > > On Sat, Nov 2, 2019 at 12:52 PM Jens Lallensack > <jens.lallensack@gmail.com mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com mailto:jens.lallensack@gmail.com>> wrote: > > > Hi John, > > thanks! > > This is the forum post with the improved version of the script: > http://www.inkscapeforum.com/viewtopic.php?t=8826#p32088 > > And here is the original version (same forum topic): > http://www.inkscapeforum.com/viewtopic.php?t=8826#p31912 > > Best wishes, > Jens > > > > > Am 02/11/2019 um 13:29 schrieb John Cliff: > > Whats the correct link for the forum post? you seem to have > linked the > > paper twice. > > > > Cheers > > > > John > > > > On Fri, Nov 1, 2019 at 2:38 PM Jens Lallensack > > <jens.lallensack@gmail.com mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com mailto:jens.lallensack@gmail.com> > <mailto:jens.lallensack@gmail.com mailto:jens.lallensack@gmail.com > <mailto:jens.lallensack@gmail.com mailto:jens.lallensack@gmail.com>>> wrote: > > > > > > Dear all, > > > > I am palaeontologist at the University of Bonn, Germany, > focusing on > > fossil dinosaur footprints and trackways. I regularly use > Inkscape for > > my research (for measuring, data extration, and drawing of > interpretive > > outlines), and have cited this software in several of my papers. > > > > I am currently working on a methodological paper on how to > analyze > > fossil footprints based on 3D models. The approach I will > present in > > this paper includes Inkscape as an important component. The > idea is to > > import raster images into Inkscape (different graphical 2D > > representations of the 3D model), align them into an image > stack, and > > draw interpretive outlines on a separate layer. I use the > Bezier curves > > tool to collect a number of landmark coordinates from the > separate > > footprints, which I then export to automatically calculate a > large > > number of measurements for statistical analysis. The paper is > to be > > published in a peer-revied journal (currently, I have the > Journal of > > Palaeontological Techniques in mind, > > https://www.jpaleontologicaltechniques.org/). > > > > I already used this method in a recent paper > > > (https://www.tandfonline.com/doi/abs/10.1080/02724634.2018.1512501) to > > rapidly collect measurements of a larger number of trackways. The > > aim of > > the new methodological paper is to improve this method and to > make it > > available to our comunity of footprint researchers. However, > there are > > two open issues/questions regarding Inkscape. I was wondering > if you > > could give me some advice here. > > > > Export of path node coordinates is, unfortunately, currently > possible > > only via a plugin, which adds an additional hitch (but I > understand > > that > > research is not the focus of Inkscape). Such a plugin was > posted on the > > Inkscape Forum in 2011, with improvements added by different > members > > > (https://www.tandfonline.com/doi/abs/10.1080/02724634.2018.1512501). I > > simplified the code so that it returns node coordinates only > (and not > > those of the handles), see code below. > > > > Now to my questions: > > > > 1) I need to cite the modified coord export script in my > paper, and > > make > > sure that it stays available. I assume that code published in > the forum > > is not automatically released under a free licence, and that > I cannot > > simply distribute the script together with the paper. A > possibility > > might be to post the modified script to the forum and provide > the link > > in the paper. This is only an option if the link remains > available > > for a > > longer time (I cannot modify the paper once published). What > would be > > the optimal way? > > > > 2) The coordinates given by the script need to be mirrored and > > translated to match the coordinates displayed within Inkscape > itself. I > > would need to improve the script so that this is done > automatically. > > I'm > > not into python scripting, but would try to figure this out. Any > > help/hints with this would be much appreciated. > > > > Thank you very much in advance. > > > > Kind regards, > > Jens Lallensack > > > > > > > > ----- xyexport.py ------- > > > > #!/usr/bin/env python > > > > import inkex > > import sys > > import simpletransform > > import cubicsuperpath > > > > class TemplateEffect(inkex.Effect): > > def __init__(self): > > inkex.Effect.__init__(self) > > def effect(self): > > for node in self.selected.iteritems(): > > output_all = output_nodes = "" > > for id, node in self.selected.iteritems(): > > if node.tag == inkex.addNS('path','svg'): > > output_all += "" > > output_nodes += "" > > simpletransform.fuseTransform(node) > > d = node.get('d') > > p = cubicsuperpath.parsePath(d) > > for subpath in p: > > for csp in subpath: > > output_nodes += str(csp[1][0]) > + "\t" + > > str(csp[1][1]) + "\n" > > sys.stderr.write(output_nodes) > > effect = TemplateEffect() > > effect.affect() > > _______________________________________________ > > Inkscape Devel mailing list -- > inkscape-devel@lists.inkscape.org mailto:inkscape-devel@lists.inkscape.org > <mailto:inkscape-devel@lists.inkscape.org mailto:inkscape-devel@lists.inkscape.org> > > <mailto:inkscape-devel@lists.inkscape.org mailto:inkscape-devel@lists.inkscape.org > <mailto:inkscape-devel@lists.inkscape.org mailto:inkscape-devel@lists.inkscape.org>> > > To unsubscribe send an email to > > inkscape-devel-leave@lists.inkscape.org mailto:inkscape-devel-leave@lists.inkscape.org > <mailto:inkscape-devel-leave@lists.inkscape.org mailto:inkscape-devel-leave@lists.inkscape.org> > > <mailto:inkscape-devel-leave@lists.inkscape.org mailto:inkscape-devel-leave@lists.inkscape.org > <mailto:inkscape-devel-leave@lists.inkscape.org mailto:inkscape-devel-leave@lists.inkscape.org>> > > >
Inkscape Devel mailing list -- inkscape-devel@lists.inkscape.org To unsubscribe send an email to inkscape-devel-leave@lists.inkscape.org
uploaded it as a resource on inkscape.org, https://inkscape.org/~simarilius/%E2%98%85inkscape-exportxy-master (no idea why its put a star in the url) have also chucked it on github https://github.com/jwcliff/Inkscape_Exportxy
Cheers
John
On Sun, Nov 3, 2019 at 10:18 PM Maren Hachmann maren@goos-habermann.de wrote:
Am 03.11.19 um 18:57 schrieb Jens Lallensack:
Hi Maren, John,
many thanks again!
@Maren: I now tested using the latest development version, and the "selected_nodes" extension now works for me. However, I found that the coordinates are not returned in sequential order (the order that defines the path), which is crucial for my purpose, but in some random order. The order is even slightly different with Inkscape 0.91 compared to the development version. I would therefore, for now, stick with the ExportXY plugin, which, thanks to John, can now be published under the GPL.
- Mmh. Yes, it looks like the extension goes by selection order.
Probably you're using Ctrl+A or click+drag to select the nodes, and that function of Inkscape seems to create some kind of random order in the node list that Inkscape hands on to the extension.
Good that the other extension does what you need! (I think it wasn't possible yet at the time to get the selected nodes list, so that extension doesn't know about the node list from Inkscape, and can't be confused by its ordering).
Maybe one of the persons involved could put the extension into a repository at gitlab or another code hosting site? That way, it's not going to get lost again :)
Maren
Thank you very much for the hint with the document scale setting – that completely solved the issue that the x values were off.
@John: Thousand thanks, this is perfect!
The extension stopped working with Inkscape 1.0 though, which I was able to fix to some extent. I changed "self.selected.iteritems()" to "self.selected.items()" and now get the values again, together with a number of deprecation warnings. I was unable to resolve these warnings for now (any help welcome, of course), but I included an ugly hack that turns these warnings off, so that at least the output is clear.
A very pleasant surprise was that with Inkscape 1.0, both x and y values returned by the script fully match those displayed in Inkscape (without the y axis being inverted or similar).
I attached the modified code to this email.
Best wishes, and thanks again, Jens
Am 03/11/2019 um 10:32 schrieb John Cliff:
Hi Jens,
Heard back from Neon22, hes very happy for it to be released under GPL. If you can add this to the top of the code you put in the paper:
# # curve xy co-ordinate export # Authors: # Jean Moreno <jean.moreno.fr@gmail.com mailto:jean.moreno.fr@gmail.com> # John Cliff <john.cliff@gmail.com mailto:john.cliff@gmail.com> # Neon22 https://github.com/Neon22?tab=repositories # # Copyright (C) 2011 Jean Moreno # Copyright (C) 2011 John Cliff # Copyright (C) 2011 Neon22 # # Released under GNU GPL v3, see https://www.gnu.org/licenses/gpl-3.0.en.html for details. #
obviously add your name to those lists since you've modified it.
Thanks
John
On Sat, Nov 2, 2019 at 3:21 PM Jens Lallensack <jens.lallensack@gmail.com mailto:jens.lallensack@gmail.com> wrote:
Hi John, wow, I certainly asked at the right place! Thank you so much foryour
efforts, it would be wonderful if it can be released under GPL. Best, Jens Am 02/11/2019 um 14:42 schrieb John Cliff: > Thought it looked familiar. I'm Simarilius in that thread, I supplied > the dodgy original version that Neon22 improved. > I'm happy for the code to be published, I based it off a blog post from > a now dead blog (wayback link is here: >http://web.archive.org/web/20141216062123/http://jumpnslide.tumblr.com/post/... )
> I have an email from that blog author Jean Moreno confirming hewas > happy for the code to be modified/ released under GPL which I can > forward to you if you wish. > Neon22 that modified it doesn't appear to have been active on the forum > since 2013, but appears to have been active on Github and Inkscape.org > recently. I've just tried emailing them via the openscad forum, will let > you know if they reply. > > Cheers > > John > > On Sat, Nov 2, 2019 at 12:52 PM Jens Lallensack > <jens.lallensack@gmail.com mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com mailto:jens.lallensack@gmail.com>> wrote: > > > Hi John, > > thanks! > > This is the forum post with the improved version of the script: > http://www.inkscapeforum.com/viewtopic.php?t=8826#p32088 > > And here is the original version (same forum topic): > http://www.inkscapeforum.com/viewtopic.php?t=8826#p31912 > > Best wishes, > Jens > > > > > Am 02/11/2019 um 13:29 schrieb John Cliff: > > Whats the correct link for the forum post? you seem to
have
> linked the > > paper twice. > > > > Cheers > > > > John > > > > On Fri, Nov 1, 2019 at 2:38 PM Jens Lallensack > > <jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com> <mailto:jens.lallensack@gmail.com
<mailto:jens.lallensack@gmail.com>> > <mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com> > <mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com>>>> wrote: > > > > > > Dear all, > > > > I am palaeontologist at the University of Bonn,Germany, > focusing on > > fossil dinosaur footprints and trackways. I regularly use > Inkscape for > > my research (for measuring, data extration, and drawing of > interpretive > > outlines), and have cited this software in several of my papers. > > > > I am currently working on a methodological paper on how to > analyze > > fossil footprints based on 3D models. The approach I will > present in > > this paper includes Inkscape as an important component. The > idea is to > > import raster images into Inkscape (different graphical 2D > > representations of the 3D model), align them into an image > stack, and > > draw interpretive outlines on a separate layer. I use the > Bezier curves > > tool to collect a number of landmark coordinates from the > separate > > footprints, which I then export to automatically calculate a > large > > number of measurements for statistical analysis. The paper is > to be > > published in a peer-revied journal (currently, I have the > Journal of > > Palaeontological Techniques in mind, > > https://www.jpaleontologicaltechniques.org/). > > > > I already used this method in a recent paper > > > (https://www.tandfonline.com/doi/abs/10.1080/02724634.2018.1512501) to > > rapidly collect measurements of a larger number of trackways. The > > aim of > > the new methodological paper is to improve this method and to > make it > > available to our comunity of footprint researchers. However, > there are > > two open issues/questions regarding Inkscape. I was wondering > if you > > could give me some advice here. > > > > Export of path node coordinates is, unfortunately, currently > possible > > only via a plugin, which adds an additional hitch (but I > understand > > that > > research is not the focus of Inkscape). Such a plugin was > posted on the > > Inkscape Forum in 2011, with improvements added by different > members > > > (https://www.tandfonline.com/doi/abs/10.1080/02724634.2018.1512501). I > > simplified the code so that it returns node coordinates only > (and not > > those of the handles), see code below. > > > > Now to my questions: > > > > 1) I need to cite the modified coord export script in my > paper, and > > make > > sure that it stays available. I assume that code published in > the forum > > is not automatically released under a free licence, and that > I cannot > > simply distribute the script together with the paper.
A
> possibility > > might be to post the modified script to the forum and provide > the link > > in the paper. This is only an option if the linkremains > available > > for a > > longer time (I cannot modify the paper once published). What > would be > > the optimal way? > > > > 2) The coordinates given by the script need to be mirrored and > > translated to match the coordinates displayed within Inkscape > itself. I > > would need to improve the script so that this is done > automatically. > > I'm > > not into python scripting, but would try to figure this out. Any > > help/hints with this would be much appreciated. > > > > Thank you very much in advance. > > > > Kind regards, > > Jens Lallensack > > > > > > > > ----- xyexport.py ------- > > > > #!/usr/bin/env python > > > > import inkex > > import sys > > import simpletransform > > import cubicsuperpath > > > > class TemplateEffect(inkex.Effect): > > def __init__(self): > > inkex.Effect.__init__(self) > > def effect(self): > > for node in self.selected.iteritems(): > > output_all = output_nodes = "" > > for id, node in self.selected.iteritems(): > > if node.tag == inkex.addNS('path','svg'): > > output_all += "" > > output_nodes += "" > > simpletransform.fuseTransform(node) > > d = node.get('d') > > p = cubicsuperpath.parsePath(d) > > for subpath in p: > > for csp in subpath: > > output_nodes += str(csp[1][0]) > + "\t" + > > str(csp[1][1]) + "\n" > > sys.stderr.write(output_nodes) > > effect = TemplateEffect() > > effect.affect() > > _______________________________________________ > > Inkscape Devel mailing list -- > inkscape-devel@lists.inkscape.org mailto:inkscape-devel@lists.inkscape.org > <mailto:inkscape-devel@lists.inkscape.org mailto:inkscape-devel@lists.inkscape.org> > > <mailto:inkscape-devel@lists.inkscape.org mailto:inkscape-devel@lists.inkscape.org > <mailto:inkscape-devel@lists.inkscape.org mailto:inkscape-devel@lists.inkscape.org>> > > To unsubscribe send an email to > > inkscape-devel-leave@lists.inkscape.org mailto:inkscape-devel-leave@lists.inkscape.org > <mailto:inkscape-devel-leave@lists.inkscape.org mailto:inkscape-devel-leave@lists.inkscape.org> > > <mailto:inkscape-devel-leave@lists.inkscape.org mailto:inkscape-devel-leave@lists.inkscape.org > <mailto:inkscape-devel-leave@lists.inkscape.org mailto:inkscape-devel-leave@lists.inkscape.org>> > > >
Inkscape Devel mailing list -- inkscape-devel@lists.inkscape.org To unsubscribe send an email to inkscape-devel-leave@lists.inkscape.org
Inkscape Devel mailing list -- inkscape-devel@lists.inkscape.org To unsubscribe send an email to inkscape-devel-leave@lists.inkscape.org
Perfect! Thanks, John :D That's going to be useful.
Maren
Am 04.11.19 um 20:24 schrieb John Cliff:
uploaded it as a resource on inkscape.org http://inkscape.org, https://inkscape.org/~simarilius/%E2%98%85inkscape-exportxy-master%C2%A0(no idea why its put a star in the url) have also chucked it on github https://github.com/jwcliff/Inkscape_Exportxy
Cheers
John
On Sun, Nov 3, 2019 at 10:18 PM Maren Hachmann <maren@goos-habermann.de mailto:maren@goos-habermann.de> wrote:
Am 03.11.19 um 18:57 schrieb Jens Lallensack: > > Hi Maren, John, > > many thanks again! > > @Maren: > I now tested using the latest development version, and the > "selected_nodes" extension now works for me. However, I found that the > coordinates are not returned in sequential order (the order that defines > the path), which is crucial for my purpose, but in some random order. > The order is even slightly different with Inkscape 0.91 compared to the > development version. I would therefore, for now, stick with the ExportXY > plugin, which, thanks to John, can now be published under the GPL. - Mmh. Yes, it looks like the extension goes by selection order. Probably you're using Ctrl+A or click+drag to select the nodes, and that function of Inkscape seems to create some kind of random order in the node list that Inkscape hands on to the extension. Good that the other extension does what you need! (I think it wasn't possible yet at the time to get the selected nodes list, so that extension doesn't know about the node list from Inkscape, and can't be confused by its ordering). Maybe one of the persons involved could put the extension into a repository at gitlab or another code hosting site? That way, it's not going to get lost again :) Maren > Thank you very much for the hint with the document scale setting – that > completely solved the issue that the x values were off. > > @John: > Thousand thanks, this is perfect! > > The extension stopped working with Inkscape 1.0 though, which I was able > to fix to some extent. I changed "self.selected.iteritems()" to > "self.selected.items()" and now get the values again, together with a > number of deprecation warnings. I was unable to resolve these warnings > for now (any help welcome, of course), but I included an ugly hack that > turns these warnings off, so that at least the output is clear. > > A very pleasant surprise was that with Inkscape 1.0, both x and y values > returned by the script fully match those displayed in Inkscape (without > the y axis being inverted or similar). > > I attached the modified code to this email. > > Best wishes, and thanks again, > Jens > > > > > > Am 03/11/2019 um 10:32 schrieb John Cliff: >> Hi Jens, >> >> Heard back from Neon22, hes very happy for it to be released under GPL. >> If you can add this to the top of the code you put in the paper: >> >> # >> # curve xy co-ordinate export >> # Authors: >> # Jean Moreno <jean.moreno.fr@gmail.com <mailto:jean.moreno.fr@gmail.com> >> <mailto:jean.moreno.fr@gmail.com <mailto:jean.moreno.fr@gmail.com>>> >> # John Cliff <john.cliff@gmail.com <mailto:john.cliff@gmail.com> <mailto:john.cliff@gmail.com <mailto:john.cliff@gmail.com>>> >> # Neon22 <https://github.com/Neon22?tab=repositories> >> # >> # Copyright (C) 2011 Jean Moreno >> # Copyright (C) 2011 John Cliff >> # Copyright (C) 2011 Neon22 >> # >> # Released under GNU GPL v3, see >> https://www.gnu.org/licenses/gpl-3.0.en.html for details. >> # >> >> obviously add your name to those lists since you've modified it. >> >> Thanks >> >> John >> >> >> On Sat, Nov 2, 2019 at 3:21 PM Jens Lallensack >> <jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com> <mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com>>> wrote: >> >> >> Hi John, >> >> wow, I certainly asked at the right place! Thank you so much for your >> efforts, it would be wonderful if it can be released under GPL. >> >> Best, >> Jens >> >> >> >> Am 02/11/2019 um 14:42 schrieb John Cliff: >> > Thought it looked familiar. I'm Simarilius in that thread, I >> supplied >> > the dodgy original version that Neon22 improved. >> > I'm happy for the code to be published, I based it off a blog >> post from >> > a now dead blog (wayback link is here: >> > >> >> http://web.archive.org/web/20141216062123/http://jumpnslide.tumblr.com/post/2557920924/how-to-use-inkscape-as-a-game-development-tool) >> >> >> > I have an email from that blog author Jean Moreno confirming he >> was >> > happy for the code to be modified/ released under GPL which I can >> > forward to you if you wish. >> > Neon22 that modified it doesn't appear to have been active on the >> forum >> > since 2013, but appears to have been active on Github and >> Inkscape.org >> > recently. I've just tried emailing them via the openscad forum, >> will let >> > you know if they reply. >> > >> > Cheers >> > >> > John >> > >> > On Sat, Nov 2, 2019 at 12:52 PM Jens Lallensack >> > <jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com> <mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com>> >> <mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com> >> <mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com>>>> wrote: >> > >> > >> > Hi John, >> > >> > thanks! >> > >> > This is the forum post with the improved version of the >> script: >> > http://www.inkscapeforum.com/viewtopic.php?t=8826#p32088 >> > >> > And here is the original version (same forum topic): >> > http://www.inkscapeforum.com/viewtopic.php?t=8826#p31912 >> > >> > Best wishes, >> > Jens >> > >> > >> > >> > >> > Am 02/11/2019 um 13:29 schrieb John Cliff: >> > > Whats the correct link for the forum post? you seem to have >> > linked the >> > > paper twice. >> > > >> > > Cheers >> > > >> > > John >> > > >> > > On Fri, Nov 1, 2019 at 2:38 PM Jens Lallensack >> > > <jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com> >> <mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com>> <mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com> >> <mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com>>> >> > <mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com> >> <mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com>> >> > <mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com> >> <mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com>>>>> wrote: >> > > >> > > >> > > Dear all, >> > > >> > > I am palaeontologist at the University of Bonn, >> Germany, >> > focusing on >> > > fossil dinosaur footprints and trackways. I >> regularly use >> > Inkscape for >> > > my research (for measuring, data extration, and >> drawing of >> > interpretive >> > > outlines), and have cited this software in several of >> my papers. >> > > >> > > I am currently working on a methodological paper on >> how to >> > analyze >> > > fossil footprints based on 3D models. The approach I >> will >> > present in >> > > this paper includes Inkscape as an important >> component. The >> > idea is to >> > > import raster images into Inkscape (different >> graphical 2D >> > > representations of the 3D model), align them into an >> image >> > stack, and >> > > draw interpretive outlines on a separate layer. I >> use the >> > Bezier curves >> > > tool to collect a number of landmark coordinates >> from the >> > separate >> > > footprints, which I then export to automatically >> calculate a >> > large >> > > number of measurements for statistical analysis. The >> paper is >> > to be >> > > published in a peer-revied journal (currently, I >> have the >> > Journal of >> > > Palaeontological Techniques in mind, >> > > https://www.jpaleontologicaltechniques.org/). >> > > >> > > I already used this method in a recent paper >> > > >> > >> (https://www.tandfonline.com/doi/abs/10.1080/02724634.2018.1512501) to >> > > rapidly collect measurements of a larger number of >> trackways. The >> > > aim of >> > > the new methodological paper is to improve this method >> and to >> > make it >> > > available to our comunity of footprint researchers. >> However, >> > there are >> > > two open issues/questions regarding Inkscape. I was >> wondering >> > if you >> > > could give me some advice here. >> > > >> > > Export of path node coordinates is, unfortunately, >> currently >> > possible >> > > only via a plugin, which adds an additional hitch >> (but I >> > understand >> > > that >> > > research is not the focus of Inkscape). Such a >> plugin was >> > posted on the >> > > Inkscape Forum in 2011, with improvements added by >> different >> > members >> > > >> > >> (https://www.tandfonline.com/doi/abs/10.1080/02724634.2018.1512501). I >> > > simplified the code so that it returns node >> coordinates only >> > (and not >> > > those of the handles), see code below. >> > > >> > > Now to my questions: >> > > >> > > 1) I need to cite the modified coord export script >> in my >> > paper, and >> > > make >> > > sure that it stays available. I assume that code >> published in >> > the forum >> > > is not automatically released under a free licence, >> and that >> > I cannot >> > > simply distribute the script together with the paper. A >> > possibility >> > > might be to post the modified script to the forum and >> provide >> > the link >> > > in the paper. This is only an option if the link >> remains >> > available >> > > for a >> > > longer time (I cannot modify the paper once >> published). What >> > would be >> > > the optimal way? >> > > >> > > 2) The coordinates given by the script need to be >> mirrored and >> > > translated to match the coordinates displayed within >> Inkscape >> > itself. I >> > > would need to improve the script so that this is done >> > automatically. >> > > I'm >> > > not into python scripting, but would try to figure >> this out. Any >> > > help/hints with this would be much appreciated. >> > > >> > > Thank you very much in advance. >> > > >> > > Kind regards, >> > > Jens Lallensack >> > > >> > > >> > > >> > > ----- xyexport.py ------- >> > > >> > > #!/usr/bin/env python >> > > >> > > import inkex >> > > import sys >> > > import simpletransform >> > > import cubicsuperpath >> > > >> > > class TemplateEffect(inkex.Effect): >> > > def __init__(self): >> > > inkex.Effect.__init__(self) >> > > def effect(self): >> > > for node in self.selected.iteritems(): >> > > output_all = output_nodes = "" >> > > for id, node in >> self.selected.iteritems(): >> > > if node.tag == >> inkex.addNS('path','svg'): >> > > output_all += "" >> > > output_nodes += "" >> > > >> simpletransform.fuseTransform(node) >> > > d = node.get('d') >> > > p = cubicsuperpath.parsePath(d) >> > > for subpath in p: >> > > for csp in subpath: >> > > output_nodes += >> str(csp[1][0]) >> > + "\t" + >> > > str(csp[1][1]) + "\n" >> > > sys.stderr.write(output_nodes) >> > > effect = TemplateEffect() >> > > effect.affect() >> > > _______________________________________________ >> > > Inkscape Devel mailing list -- >> > inkscape-devel@lists.inkscape.org <mailto:inkscape-devel@lists.inkscape.org> >> <mailto:inkscape-devel@lists.inkscape.org <mailto:inkscape-devel@lists.inkscape.org>> >> > <mailto:inkscape-devel@lists.inkscape.org <mailto:inkscape-devel@lists.inkscape.org> >> <mailto:inkscape-devel@lists.inkscape.org <mailto:inkscape-devel@lists.inkscape.org>>> >> > > <mailto:inkscape-devel@lists.inkscape.org <mailto:inkscape-devel@lists.inkscape.org> >> <mailto:inkscape-devel@lists.inkscape.org <mailto:inkscape-devel@lists.inkscape.org>> >> > <mailto:inkscape-devel@lists.inkscape.org <mailto:inkscape-devel@lists.inkscape.org> >> <mailto:inkscape-devel@lists.inkscape.org <mailto:inkscape-devel@lists.inkscape.org>>>> >> > > To unsubscribe send an email to >> > > inkscape-devel-leave@lists.inkscape.org <mailto:inkscape-devel-leave@lists.inkscape.org> >> <mailto:inkscape-devel-leave@lists.inkscape.org <mailto:inkscape-devel-leave@lists.inkscape.org>> >> > <mailto:inkscape-devel-leave@lists.inkscape.org <mailto:inkscape-devel-leave@lists.inkscape.org> >> <mailto:inkscape-devel-leave@lists.inkscape.org <mailto:inkscape-devel-leave@lists.inkscape.org>>> >> > > <mailto:inkscape-devel-leave@lists.inkscape.org <mailto:inkscape-devel-leave@lists.inkscape.org> >> <mailto:inkscape-devel-leave@lists.inkscape.org <mailto:inkscape-devel-leave@lists.inkscape.org>> >> > <mailto:inkscape-devel-leave@lists.inkscape.org <mailto:inkscape-devel-leave@lists.inkscape.org> >> <mailto:inkscape-devel-leave@lists.inkscape.org <mailto:inkscape-devel-leave@lists.inkscape.org>>>> >> > > >> > >> > > _______________________________________________ > Inkscape Devel mailing list -- inkscape-devel@lists.inkscape.org <mailto:inkscape-devel@lists.inkscape.org> > To unsubscribe send an email to inkscape-devel-leave@lists.inkscape.org <mailto:inkscape-devel-leave@lists.inkscape.org> > _______________________________________________ Inkscape Devel mailing list -- inkscape-devel@lists.inkscape.org <mailto:inkscape-devel@lists.inkscape.org> To unsubscribe send an email to inkscape-devel-leave@lists.inkscape.org <mailto:inkscape-devel-leave@lists.inkscape.org>
Inkscape Devel mailing list -- inkscape-devel@lists.inkscape.org To unsubscribe send an email to inkscape-devel-leave@lists.inkscape.org
yes, many thanks for uploading it. Maybe this functionality is needed more than we think.
Best, Jens
Am 04/11/2019 um 21:25 schrieb Maren Hachmann:
Perfect! Thanks, John :D That's going to be useful.
Maren
Am 04.11.19 um 20:24 schrieb John Cliff:
uploaded it as a resource on inkscape.org http://inkscape.org, https://inkscape.org/~simarilius/%E2%98%85inkscape-exportxy-master%C2%A0(no idea why its put a star in the url) have also chucked it on github https://github.com/jwcliff/Inkscape_Exportxy
Cheers
John
On Sun, Nov 3, 2019 at 10:18 PM Maren Hachmann <maren@goos-habermann.de mailto:maren@goos-habermann.de> wrote:
Am 03.11.19 um 18:57 schrieb Jens Lallensack: > > Hi Maren, John, > > many thanks again! > > @Maren: > I now tested using the latest development version, and the > "selected_nodes" extension now works for me. However, I found that the > coordinates are not returned in sequential order (the order that defines > the path), which is crucial for my purpose, but in some random order. > The order is even slightly different with Inkscape 0.91 compared to the > development version. I would therefore, for now, stick with the ExportXY > plugin, which, thanks to John, can now be published under the GPL. - Mmh. Yes, it looks like the extension goes by selection order. Probably you're using Ctrl+A or click+drag to select the nodes, and that function of Inkscape seems to create some kind of random order in the node list that Inkscape hands on to the extension. Good that the other extension does what you need! (I think it wasn't possible yet at the time to get the selected nodes list, so that extension doesn't know about the node list from Inkscape, and can't be confused by its ordering). Maybe one of the persons involved could put the extension into a repository at gitlab or another code hosting site? That way, it's not going to get lost again :) Maren > Thank you very much for the hint with the document scale setting – that > completely solved the issue that the x values were off. > > @John: > Thousand thanks, this is perfect! > > The extension stopped working with Inkscape 1.0 though, which I was able > to fix to some extent. I changed "self.selected.iteritems()" to > "self.selected.items()" and now get the values again, together with a > number of deprecation warnings. I was unable to resolve these warnings > for now (any help welcome, of course), but I included an ugly hack that > turns these warnings off, so that at least the output is clear. > > A very pleasant surprise was that with Inkscape 1.0, both x and y values > returned by the script fully match those displayed in Inkscape (without > the y axis being inverted or similar). > > I attached the modified code to this email. > > Best wishes, and thanks again, > Jens > > > > > > Am 03/11/2019 um 10:32 schrieb John Cliff: >> Hi Jens, >> >> Heard back from Neon22, hes very happy for it to be released under GPL. >> If you can add this to the top of the code you put in the paper: >> >> # >> # curve xy co-ordinate export >> # Authors: >> # Jean Moreno <jean.moreno.fr@gmail.com <mailto:jean.moreno.fr@gmail.com> >> <mailto:jean.moreno.fr@gmail.com <mailto:jean.moreno.fr@gmail.com>>> >> # John Cliff <john.cliff@gmail.com <mailto:john.cliff@gmail.com> <mailto:john.cliff@gmail.com <mailto:john.cliff@gmail.com>>> >> # Neon22 <https://github.com/Neon22?tab=repositories> >> # >> # Copyright (C) 2011 Jean Moreno >> # Copyright (C) 2011 John Cliff >> # Copyright (C) 2011 Neon22 >> # >> # Released under GNU GPL v3, see >> https://www.gnu.org/licenses/gpl-3.0.en.html for details. >> # >> >> obviously add your name to those lists since you've modified it. >> >> Thanks >> >> John >> >> >> On Sat, Nov 2, 2019 at 3:21 PM Jens Lallensack >> <jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com> <mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com>>> wrote: >> >> >> Hi John, >> >> wow, I certainly asked at the right place! Thank you so much for your >> efforts, it would be wonderful if it can be released under GPL. >> >> Best, >> Jens >> >> >> >> Am 02/11/2019 um 14:42 schrieb John Cliff: >> > Thought it looked familiar. I'm Simarilius in that thread, I >> supplied >> > the dodgy original version that Neon22 improved. >> > I'm happy for the code to be published, I based it off a blog >> post from >> > a now dead blog (wayback link is here: >> > >> >> http://web.archive.org/web/20141216062123/http://jumpnslide.tumblr.com/post/2557920924/how-to-use-inkscape-as-a-game-development-tool) >> >> >> > I have an email from that blog author Jean Moreno confirming he >> was >> > happy for the code to be modified/ released under GPL which I can >> > forward to you if you wish. >> > Neon22 that modified it doesn't appear to have been active on the >> forum >> > since 2013, but appears to have been active on Github and >> Inkscape.org >> > recently. I've just tried emailing them via the openscad forum, >> will let >> > you know if they reply. >> > >> > Cheers >> > >> > John >> > >> > On Sat, Nov 2, 2019 at 12:52 PM Jens Lallensack >> > <jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com> <mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com>> >> <mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com> >> <mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com>>>> wrote: >> > >> > >> > Hi John, >> > >> > thanks! >> > >> > This is the forum post with the improved version of the >> script: >> > http://www.inkscapeforum.com/viewtopic.php?t=8826#p32088 >> > >> > And here is the original version (same forum topic): >> > http://www.inkscapeforum.com/viewtopic.php?t=8826#p31912 >> > >> > Best wishes, >> > Jens >> > >> > >> > >> > >> > Am 02/11/2019 um 13:29 schrieb John Cliff: >> > > Whats the correct link for the forum post? you seem to have >> > linked the >> > > paper twice. >> > > >> > > Cheers >> > > >> > > John >> > > >> > > On Fri, Nov 1, 2019 at 2:38 PM Jens Lallensack >> > > <jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com> >> <mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com>> <mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com> >> <mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com>>> >> > <mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com> >> <mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com>> >> > <mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com> >> <mailto:jens.lallensack@gmail.com <mailto:jens.lallensack@gmail.com>>>>> wrote: >> > > >> > > >> > > Dear all, >> > > >> > > I am palaeontologist at the University of Bonn, >> Germany, >> > focusing on >> > > fossil dinosaur footprints and trackways. I >> regularly use >> > Inkscape for >> > > my research (for measuring, data extration, and >> drawing of >> > interpretive >> > > outlines), and have cited this software in several of >> my papers. >> > > >> > > I am currently working on a methodological paper on >> how to >> > analyze >> > > fossil footprints based on 3D models. The approach I >> will >> > present in >> > > this paper includes Inkscape as an important >> component. The >> > idea is to >> > > import raster images into Inkscape (different >> graphical 2D >> > > representations of the 3D model), align them into an >> image >> > stack, and >> > > draw interpretive outlines on a separate layer. I >> use the >> > Bezier curves >> > > tool to collect a number of landmark coordinates >> from the >> > separate >> > > footprints, which I then export to automatically >> calculate a >> > large >> > > number of measurements for statistical analysis. The >> paper is >> > to be >> > > published in a peer-revied journal (currently, I >> have the >> > Journal of >> > > Palaeontological Techniques in mind, >> > > https://www.jpaleontologicaltechniques.org/). >> > > >> > > I already used this method in a recent paper >> > > >> > >> (https://www.tandfonline.com/doi/abs/10.1080/02724634.2018.1512501) to >> > > rapidly collect measurements of a larger number of >> trackways. The >> > > aim of >> > > the new methodological paper is to improve this method >> and to >> > make it >> > > available to our comunity of footprint researchers. >> However, >> > there are >> > > two open issues/questions regarding Inkscape. I was >> wondering >> > if you >> > > could give me some advice here. >> > > >> > > Export of path node coordinates is, unfortunately, >> currently >> > possible >> > > only via a plugin, which adds an additional hitch >> (but I >> > understand >> > > that >> > > research is not the focus of Inkscape). Such a >> plugin was >> > posted on the >> > > Inkscape Forum in 2011, with improvements added by >> different >> > members >> > > >> > >> (https://www.tandfonline.com/doi/abs/10.1080/02724634.2018.1512501). I >> > > simplified the code so that it returns node >> coordinates only >> > (and not >> > > those of the handles), see code below. >> > > >> > > Now to my questions: >> > > >> > > 1) I need to cite the modified coord export script >> in my >> > paper, and >> > > make >> > > sure that it stays available. I assume that code >> published in >> > the forum >> > > is not automatically released under a free licence, >> and that >> > I cannot >> > > simply distribute the script together with the paper. A >> > possibility >> > > might be to post the modified script to the forum and >> provide >> > the link >> > > in the paper. This is only an option if the link >> remains >> > available >> > > for a >> > > longer time (I cannot modify the paper once >> published). What >> > would be >> > > the optimal way? >> > > >> > > 2) The coordinates given by the script need to be >> mirrored and >> > > translated to match the coordinates displayed within >> Inkscape >> > itself. I >> > > would need to improve the script so that this is done >> > automatically. >> > > I'm >> > > not into python scripting, but would try to figure >> this out. Any >> > > help/hints with this would be much appreciated. >> > > >> > > Thank you very much in advance. >> > > >> > > Kind regards, >> > > Jens Lallensack >> > > >> > > >> > > >> > > ----- xyexport.py ------- >> > > >> > > #!/usr/bin/env python >> > > >> > > import inkex >> > > import sys >> > > import simpletransform >> > > import cubicsuperpath >> > > >> > > class TemplateEffect(inkex.Effect): >> > > def __init__(self): >> > > inkex.Effect.__init__(self) >> > > def effect(self): >> > > for node in self.selected.iteritems(): >> > > output_all = output_nodes = "" >> > > for id, node in >> self.selected.iteritems(): >> > > if node.tag == >> inkex.addNS('path','svg'): >> > > output_all += "" >> > > output_nodes += "" >> > > >> simpletransform.fuseTransform(node) >> > > d = node.get('d') >> > > p = cubicsuperpath.parsePath(d) >> > > for subpath in p: >> > > for csp in subpath: >> > > output_nodes += >> str(csp[1][0]) >> > + "\t" + >> > > str(csp[1][1]) + "\n" >> > > sys.stderr.write(output_nodes) >> > > effect = TemplateEffect() >> > > effect.affect() >> > > _______________________________________________ >> > > Inkscape Devel mailing list -- >> > inkscape-devel@lists.inkscape.org <mailto:inkscape-devel@lists.inkscape.org> >> <mailto:inkscape-devel@lists.inkscape.org <mailto:inkscape-devel@lists.inkscape.org>> >> > <mailto:inkscape-devel@lists.inkscape.org <mailto:inkscape-devel@lists.inkscape.org> >> <mailto:inkscape-devel@lists.inkscape.org <mailto:inkscape-devel@lists.inkscape.org>>> >> > > <mailto:inkscape-devel@lists.inkscape.org <mailto:inkscape-devel@lists.inkscape.org> >> <mailto:inkscape-devel@lists.inkscape.org <mailto:inkscape-devel@lists.inkscape.org>> >> > <mailto:inkscape-devel@lists.inkscape.org <mailto:inkscape-devel@lists.inkscape.org> >> <mailto:inkscape-devel@lists.inkscape.org <mailto:inkscape-devel@lists.inkscape.org>>>> >> > > To unsubscribe send an email to >> > > inkscape-devel-leave@lists.inkscape.org <mailto:inkscape-devel-leave@lists.inkscape.org> >> <mailto:inkscape-devel-leave@lists.inkscape.org <mailto:inkscape-devel-leave@lists.inkscape.org>> >> > <mailto:inkscape-devel-leave@lists.inkscape.org <mailto:inkscape-devel-leave@lists.inkscape.org> >> <mailto:inkscape-devel-leave@lists.inkscape.org <mailto:inkscape-devel-leave@lists.inkscape.org>>> >> > > <mailto:inkscape-devel-leave@lists.inkscape.org <mailto:inkscape-devel-leave@lists.inkscape.org> >> <mailto:inkscape-devel-leave@lists.inkscape.org <mailto:inkscape-devel-leave@lists.inkscape.org>> >> > <mailto:inkscape-devel-leave@lists.inkscape.org <mailto:inkscape-devel-leave@lists.inkscape.org> >> <mailto:inkscape-devel-leave@lists.inkscape.org <mailto:inkscape-devel-leave@lists.inkscape.org>>>> >> > > >> > >> > > _______________________________________________ > Inkscape Devel mailing list -- inkscape-devel@lists.inkscape.org <mailto:inkscape-devel@lists.inkscape.org> > To unsubscribe send an email to inkscape-devel-leave@lists.inkscape.org <mailto:inkscape-devel-leave@lists.inkscape.org> > _______________________________________________ Inkscape Devel mailing list -- inkscape-devel@lists.inkscape.org <mailto:inkscape-devel@lists.inkscape.org> To unsubscribe send an email to inkscape-devel-leave@lists.inkscape.org <mailto:inkscape-devel-leave@lists.inkscape.org>
Inkscape Devel mailing list -- inkscape-devel@lists.inkscape.org To unsubscribe send an email to inkscape-devel-leave@lists.inkscape.org
Inkscape Devel mailing list -- inkscape-devel@lists.inkscape.org To unsubscribe send an email to inkscape-devel-leave@lists.inkscape.org
participants (3)
-
Jens Lallensack -
John Cliff -
Maren Hachmann