- Inkscape Devel - Inkscape Mailman

Fwd: $ systemd-analyze plot | inkview
by anatoly techtonik 21 Nov '18

21 Nov '18

Hi. Is it true that `inkview` is kind of unmaintained? Still maybe it is possible to modify it to accept input from stdin? https://bugs.launchpad.net/inkscape/+bug/1804432 I could do it myself if `inkview` was written in Python. -- anatoly t.

2 1

Inkscape.org in Chinese in Google Chrome (fine in Firefox)
by C R 19 Nov '18

19 Nov '18

Inkscape website navigation comes up in Chinese in Google Chrome. (screenshot attached) Anyone else seeing this? I tried re-choosing English in the language options on the site, but still get Chinese symbols. Odd. -C

3 2

Announcing lib2geom Release 1.0
by Bryce Harrington 11 Nov '18

11 Nov '18

lib2geom v1.0.0 =============== 2geom is a C++ library of mathematics for paths, curves, and other geometric calculations, designed to be well suited for vector graphics: Bézier curves, conics, paths, intersections, transformations, and basic geometries. Originally developed to restructure and improve path data structures in Inkscape, this library's codebase has been maintained and shipped as part of the professional vector graphics software for over a decade. The major contributors to the 2geom library are Nathan Hurst, Michael G. Sloan, Krzysztof Kosiński, Johan B. C. Engelen, MenTaLguY, Aaron Spike, Marco Cechetti and JF Barraud. Work on this release has focused on updating the 2geom source control, build, test and packaging systems for both Linux and Windows. The py2geom python extension package has been restored and improvements have been made to overall code stabilization and quality. The primary motivation for 2geom's 1.0 release is to support a future Inkscape 1.0 launch. With this evolution to a distinct package, the 2geom team is seeking new opportunities to collaborate with individuals and projects interested in using this proven tool. Downloads ========= Source Release: http://alpha.inkscape.org/releases/lib2geom-1.0.0.tar.bz2 [http://alpha.inkscape.org/releases/lib2geom-1.0.0.tar.bz2.sig] (Other packages for this release may be available in the future; keep an eye on https://www.inkscape.org.) More Information ================ Website: http://lib2geom.sourceforge.net/ Code: https://gitlab.com/inkscape/lib2geom Chat: https://chat.inkscape.org/home Bryce

2 1

GTK3 Lower Bounds
by Jabier Arraiza 08 Nov '18

08 Nov '18

Hi all. I ask on chat about lower bounds of GTK3 version. Tav point me to http://wiki.inkscape.org/wiki/index.php/Tracking_Dependencies He also suggest it can be moved from 3.18 to 3.22 in Linux but he is not sure about other OS. What about @win_team and @mac_team? Regards, Jabier.

4 4

Issues on Gitlab?
by Tobias Bernard 06 Nov '18

06 Nov '18

Hi all, I'm a UX designer and long-time Inkscape user. I work at Purism, and I'm on the GNOME design team. I've been meaning to get involved with Inkscape for years, but the tools used for development (Launchpad, mailing lists, IRC) don't make it very easy unfortunately. I was very happy when I saw the code migrated to Gitlab, because it's a much more modern tool that works great for design issues thanks to inline media (we've been using it in GNOME for the past year and it's been a total game changer). Unfortunately, though the code is on Gitlab now, it's still not possible to open issues there. I was told this would change "soon" earlier this year, but so far this hasn't happened. Is there a timeline for opening issues on Gitlab? What are the current blockers? I'd really like to avoid using Launchpad if at all possible :) Cheers, Tobias

4 6

Website update: current status
by Maren Hachmann 06 Nov '18

06 Nov '18

Hi there, Martin, Bryce and Travis from our friendly hosters at OSUOSL have worked on switching the inkscape.org website to the newer version this evening. In some parts of the world, due to DNS propagation, you might not yet see the new page, but you will soon (it looks pretty much the same, though, just the backend is newer). It now features a new shiny django (yay!). Unfortunately, it currently has problems with page edits, news edits and resource uploads. Please hold off editing anything on it, to not lose any work. Martin is working on fixing things, and will let you know when it's good for editing again. Downloads and viewing the pages work as usual (except for viewing pasted texts), so most people won't be affected by the issues. Kind Regards, Maren

2 5

lib2geom 0.9.0 (pre-release for 1.0)
by Bryce Harrington 05 Nov '18

05 Nov '18

A pre-release of lib2geom is packaged and can be downloaded here: Download: http://alpha.inkscape.org/prereleases/lib2geom-0.9.0.tar.bz2 Signature: http://alpha.inkscape.org/prereleases/lib2geom-0.9.0.tar.bz2.sig I've doublechecked that it builds and its tests pass, but I would really appreciate if someone else could check too. I haven't tried building Inkscape against it, and while I don't expect any issues at all, it would be wonderful if someone could check. Assuming all is well, I'll put out the final 1.0 release in a few days. The release notes are inlined below. Michele has kindly offered to help craft a news announcement to go with the release. Bryce lib2geom v1.0.0 =============== 2geom is a C++ library of mathematics for paths, curves, and other geometric calculations, designed to be well suited for vector graphics: Bézier curves, conics, paths, intersections, transformations, and basic geometries. This library was originally developed to restructure and improve the various path data structures in Inkscape, but the design intent is for it to be of general utility to others. The codebase has shipped as and been maintained as part of the Inkscape software for over a decade. It has been a very long time since 2geom saw a packaged release, and so much has changed it is hard to reduce to a summary. Recent work has focused on updating its source control, build, test, and packaging systems to more modern technologies for both Linux and Windows, and on restoring the py2geom python extension package to usability. Attention in recent years has also focused on stabilization and code quality improvement. The primary motivation for this 1.0 release is in support of overall efforts towards the (future) Inkscape 1.0 release, but we also hope that having this as a distinct package from Inkscape itself will facilitate wider collaboration. We would love to hear people find good uses for this beyond the Inkscape codebase!

2 4

Duplicating objects in a Python extension
by Pieter Barendrecht 05 Nov '18

05 Nov '18

Hi all, Given a selected object (e.g. firstObject = self.selected[self.options.ids[0]]) in a Python extension, how can I duplicate it? I've checked a couple of code snippets (e.g. pathscatter.py as well as some online content) and stumbled upon copy.deepcopy(...) and append() for layers, but I don't have it working properly yet. Usually, I add a new object (e.g. a path) using newObject = inkex.etree.SubElement(self.current_layer, inkex.addNS('path','svg'), pathAttribs), where pathAttribs has been defined before. Can I add the duplicated object in a similar way? When I substitute 'pathAttribs' with 'firstObject' or a deepcopy() of it, I get the following FutureWarning — FutureWarning: The behavior of this method will change in future versions. Use specific 'len(elem)' or 'elem is not None' test instead. newObject = inkex.etree.SubElement(self.current_layer, inkex.addNS('path','svg'), firstObject) As an exercise I'm trying to write an extension that generates a circular array of a selected (path) object. The approach could be to first duplicate the object and subsequently transform it (i.e. rotate and possibly translate) using simpletransform.composeTransform () and simpletransform.applyTransformToPath(). As a follow-up question, is it possible to clone an object from within a Python extension? With 'clone' I mean the operation that's available in Inkscape through Edit → Clone → Create Clone. Thanks! Best, Pieter

2 4

Python coder needed for simple Launchpad/Gitlab metrics tools
by Bryce Harrington 03 Nov '18

03 Nov '18

Hi all, I've got a little scripting project for someone interested in exercising their python skills for Inkscape over the next couple weeks. It involves collecting data about bug reports via the Launchpad API, and a similar tool using the Gitlab API. One tool will use Launchpad's API to get data about bugs (age, # comments, length of description, etc.) and calculate a score. We essentially want to measure the "triaging difficulty" of each bug. The other tool will use Gitlab's API to detect bugs that have been moved from Launchpad, what the LP bug # was, and the person that did the triaging work. It also does some simple quality checks on the ported bug - presence of tags, length of bug description, is the bug description in valid markdown format, etc. If this sounds interesting, let me or Chris Rogers know and we can fill you in a few more details and help you get going. Bryce

1 0

Vectors Meeting - Tomorrow
by Ryan Gorley 03 Nov '18

03 Nov '18

Hello all, Just a friendly reminder that the Vectors are meeting tomorrow. The agenda is being refined but the time and place can be found here: https://gitlab.com/inkscape/vectors/general/issues/74 All are welcome! Ryan

1 0