- Inkscape Devel - Inkscape Mailman

Inkscape for dinosaur track research, questions
by Jens Lallensack 04 Nov '19

04 Nov '19

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()

3 13

Board meeting Oct 4th
by Bryce Harrington 29 Oct '19

29 Oct '19

Our monthly board meeting is scheduled for Friday, Oct 4th, at 10am Pacific in #inkscape-devel. All members are welcome. http://wiki.inkscape.org/wiki/index.php/Board_Meetings I unfortunately have an all-day event for work downtown on Friday, can someone else please run the Inkscape board meeting? I should be able to attend in lurk mode. Agenda: ------- * Hackfest planning * Infrastructure - mailing list migration off SourceForge - Wiki migration off OSUOSL - Weblate service deployment * Software Release status - Inkscape 1.0beta - Inkscape 1.0 * GSoC * Bug migration off Launchpad * Other Business Action Items from last meeting: ------------------------------- Transcripts of previous meetings: --------------------------------- http://alpha.inkscape.org/board/meetings/transcripts/ Bryce

2 2

About Screen Contest: 2 weeks 6 days left to submit your entries!
by Maren Hachmann 28 Oct '19

28 Oct '19

Hi Inkscape users, there's still time to participate in the About Screen Contest for Inkscape 1.0 ! We'd love to see many more and varied entries from you! Rules and more info: https://inkscape.org/community/about-screen-contests/ Contest entries: https://inkscape.org/gallery/=about-screen-contest/contest-for-10/ So, reserve some time this week for contributing to the magical Inkscape 1.0 in this cool way :D Don't wait until the last minute! Tim Jones helps you by checking your entries for rule compliance, make sure to watch for any comments on your About Screen proposal! Looking forward to what y'all will come up with! Maren

1 0

Question about wiki account
by Tomáš Marný 10 Oct '19

10 Oct '19

Hello! Can I apply for a wiki account here? I updated the Czech translation, which was not in good condition. And I also want to update Czech terminology. Thank you for your response. Sincerely, Tomáš M.

2 1

String and Feature freeze
by Marc Jeanmougin 09 Oct '19

09 Oct '19

Hi devs and translators ! Just to make it official, we are now in feature and string freeze : - New features that have any possibility of having a bug or to need testing will be postponed to post-branching time - Any modification to strings will need to be approved and will need an email to translators ML - Dev focus should ideally be given to bugfixing ;) @Translators : the pot file should now be stable, as Maren indicated a few hours ago (only two strings changed since then), sorry for the changes Thanks all for your involvement in this release! -- Mc

1 0

Join the 1.0 About Screen Art Contest!
by Maren Hachmann 07 Oct '19

07 Oct '19

Hello Inkscape Community, it's that time again! Starting October 7th (today) through November 17th we are accepting submissions for the About Screen Contest for Inkscape 1.0! This is your opportunity to contribute to this major milestone for your favorite vector graphics editor! The contest winner's artwork will be showcased in the 'Help > About' menu entry in Inkscape. You can use the current Beta version to play with the new features and to make your artwork be a good representation of what Inkscape 1.0 can do! Learn more about the contest here: https://inkscape.org/community/about-screen-contests/ Good luck to all - and, of course: Draw Freely :)

1 0

Is this a known issue? (and the dumbest bug ever)
by Josh Andler 15 Aug '19

15 Aug '19

I searched the bug tracker (perhaps using language that was too specific) but I couldn't find a report... Is a path using dashes with rounded caps supposed to ignore the rounded caps when you convert Stroke to Path? It visually does it right with butt or square caps, but rounded caps get converted as butts from how it appears. I'm seeing this in both stable and trunk and it seems... like an odd oversight. Anyone else have thoughts? Cheers, Josh

1 0

Mailman3 outage
by Bryce Harrington 14 Aug '19

14 Aug '19

The mailman3 list server was offline the past week, due to troubles it had delivering email to administrative user accounts. This generated excessive error logging to disk. I'm not 100% sure this is root caused but after clearing the queue it seems to be running happily again. I'll try and keep a closer eye on it. Bryce P.S. there's still a problem with some people unable to subscribe to the mailing lists; I doubt this change will fix chat, so this problem is still on the todo list.

1 0

Re: Beta-blockers ?
by Patrick Storz 14 Aug '19

14 Aug '19

Hi Marc, thanks for planning this thoroughly! Answers below. Am 12.08.2019 um 21:13 schrieb Marc Jeanmougin: > == Extensions (Martin, Patrick, others) == > > What is the state of extensions (#156) ? In particular, their > translatability (#333) ? Is the current submodule commit in a "good > state" ? What to do with the old uniconvertor extensions, do we update > them to uniconvertor 2.0rc5 ? While Martin and others did (and are still doing) a great job on the bundled Python extensions I'm currently working on the extension implementation in Inkscape itself. I just finished one big part (.inx format updates and the internal logic in Inkscape to parse preferences/parameters form it while also creating nice GUIs) which is ready for review at https://gitlab.com/inkscape/inkscape/merge_requests/808 As Martin already mentioned translations are basically handled as before (still use inkscapes .pot/.po files), only the way we mark strings for translation in the.inx changed. Once the MR is merged it will be a trivial job to update the .inx files with some search&replace, although the code should be fully backwards-compatible to earlier .inx files. Regarding splitting the translations of extensions into the extension repo (and also allowing third-party extensions to ship their own translations): The current MR implements the syntax, but the actual functionality is not included yet. However I realized while working on it, that I already have done most of the required refactoring, minimizing the effort that remains for finishing the feature. If we feel like this is a welcome feature for 1.0 already, we can probably implement it in time instead of delaying it until 1.1 as I initially planned. I'm starting to think that this would actually be nice, as we can offer a finished feature in 1.0 instead of just syntax for a feature that is not implemented yet. > == Gtk General interface stuff (all) == > > Do we still have interface problems like toolbars not showing up or > menus needing two clicks, or anything of the sort, on any platform ? Is > #195 still reproducible ? I'm not aware of anything specific right now that prevents usage. In general there's still a fundamental "glitchiness" to gtk3 on Windows, but I'm afraid that's just how gtk3 works on Windows these days. We'll certainly get some questions about it, but I wouldn't know what to do to significantly improve this until the release. > == Packaging (RdH, Patrick, others) == > > Approximately how much work is still needed for macOS stable dmg > production or windows packaging ? > > What happens with the ubuntu bionic "dependency wait" ? ( > https://launchpadlibrarian.net/437056488/buildlog.txt.gz ) Updating our existing Windows packaging for 1.0 should be easy (once I can motivate myself to do it). I always planned to look into cpack and investigate if it can produce proper installers, so we might eventually get rid of our own packaging and reduce the overhead of maintaining it, but that might need some more work. > == Performance (all) == > > Do we still have these massive performance problems as soon as the > Objects dialog (or XML ?) has been opened ? I'm not aware anybody pushed a fix? Didn't retest, though. Apart from that performance stil lseems worse than 0.92.x (at least on Windows), but also here I wouldn't really know what to do. It's usable, but it's not good. One particular performance issue (I know there were multiple reports, but not sure we have an actual issue for it and GitLab throws 500 errors at me): Selecting a new font takes a very long time (a few seconds at least, some take 10-20 seconds). Not sure if this is exclusive to Windows? It does not happen in 0.92.x, though (with the same version of fontconfig/harfbuzz/pango/...), so it's either something we're doing, or something gtk3 is doing differently from gtk2. I think performance wasn't always bad in master, though. I think it started either with the variable fonts support or after the SPStyle refactor. > > == Text (Tav, Jabier, others) == > > How usable is the text tool ? Do we implement the "hamburger" toolbar ? > Do we still have issues with variable font sliders ? How understandable > are our text tools, and are users able to "just write text" without > surprises ? (with line heights for instance ?) Tbh, I can't use the text toolbar myself anymore... Either I'm to stupid or we really *should* do something about usability. It never behaves as expected and always sets properties in ways that were not intended. One line-height related issue that also needs attention is https://gitlab.com/inkscape/inkscape/issues/244 > == SVG2 (Tav, all) == > > I'm not sure we have discussed enough the transition between SVG1.1 and > SVG2. If we start producing svg2 documents that are not svg1.1-valid, > should we use version="2" in <svg> ? how will it be understood by other > renderers ? When and how do we intend to switch the 1.2 flawed text into > the newly flawed text, how will we handle old documents, and how do we > ensure they will render exactly the same ? Do we provide a way to save > in "valid SVG1.1 document without SVG2 stuff" ? I'd say we should always produce SVG1.1 fallbacks, even if we use SVG2 features? Maybe we can then add an option to disable the compatiblity shims and produce a "pure" SVG2 document. I know some switches are available, but Tav can probably comment better on what is implemented and what isn't. > == Documentation (Maren) == > > I saw https://gitlab.com/inkscape/inkscape-docs/documentation/issues/2 , > do we have more stuff to update ? By the way, how do we sync the > inkscape/inkscape repo with the inkscape/inkscape-docs ? As Maren mentioned already there's a lot to update content-wise. I've handled most of the technical side and meant to make a call for help at some point, but didn't get the chance to do it yet. Once content is updated I typically copy the CI-generated files manually and push the update to the inkscape repo. Basically this can wait till shortly before 1.0, but we can certainly schedule a preliminary update for the beta(s). Cheers, Patrick

1 0

Beta-blockers ?
by Marc Jeanmougin 14 Aug '19

14 Aug '19

Hi all, The toolbar bug seems fixed for most systems and only seems to appear on wayland (at least I can't trigger it on xorg), and is now reported upstream at https://gitlab.gnome.org/GNOME/gtk/issues/2000 The translation system seems better (#311), so … do anyone see any issue that would need to be fixed before releasing a beta ? -- Mc

4 5