- Inkscape Devel - Inkscape Mailman

Inkscape 0.92 and Converting Inkscape to CMake
by Bryce Harrington 19 Jan '16

19 Jan '16

CMake is a key goal for the Inkscape 0.92 release. We're close, but some important work still remains. Are you familiar with CMake? It's important not only that we convert the codebase, but that we also install our developers (i.e. YOU!!) with adequate cmake know-how to be able to update stuff as needs arise. Is CMake something you've not yet learned? I've written up a little Inkscape-specific tutorial / class to give you the basics. Please put it on your near-term todo list: http://wiki.inkscape.org/wiki/index.php/Working_with_CMake Once you're ready to tackle some cmake work, please take a look at my write-up of cmake tasks that I think we need to get done: http://wiki.inkscape.org/wiki/index.php/CMake_Tasks I've organized that page by tasks that I feel we need to get done for 0.92, versus ones that have to be done post-0.92 (since they'd break the autoconf stuff), and minor tasks that can be safely done whenever. Thanks for lending a hand to helping with the CMake work. My dream is that by achieving this conversion, we'll be able to unify a lot of our platform-specific packaging. Effort that currently is divided between linux, osx, and win32, will be able to be merged so we can better collaborate with packaging generally. Bryce

2 2

Re: [Inkscape-devel] Quality of gradients.
by mathog 14 Jan '16

14 Jan '16

(revised version of message sent originally only to Gez.) On 09-Jan-2016 12:33, Gez wrote: > For my professional work, the way inkscape renders gradients is a show- > stopper. The quality of my work suffers if I don't apply one of those > tedious workarounds discussed in this thread. The EMF export function supports simple gradients as descriptions (high & low color values, scale and direction of linear gradient) and so are not quality limited in this manner. Perhaps in some instances you could export to EMF and then render from that in another application which doesn't have the 8bit limit? Unfortunately there is no exact support for radial gradients in the EMF or EMF+ standards. Currently Inkscape emulates such gradients in EMF files with many small single colored elliptical slices. The best one could do with EMF would be to use the peculiar "triangle" gradient mode (Google "GRADIENT_FILL_TRIANGLE") to emulate a radial gradient. Then instead of rings it would be a lot of small wedges, each with its own part of the gradient. At the moment there is no code in Inkscape to do this. (EMF+, which is not yet supported at all in inkscape but is coded into libUEMF, has something called a "Path Gradient Brush" which is essentially a bunch of these triangle gradients merged, so that instead of specifying a lot of triangles, one specifies a center point and a path.) Going this route would be a one way trip, since the code for working back from multiple triangle gradients to a radial one would need to be pretty clever to look for and detect this sort of clustering and arrangement of gradients, especially since those EMF records need not be consecutive in the file. (Going from EMF+'s Path Gradient Brush to an SVG radial gradient would be easier because it would not have the multiple record problem.) Also an awful lot of these triangles might be needed to get a smooth looking radial gradient, that is, one that doesn't look like a set of nested polygons resulting from "contour lines" of constant colors. Perhaps slightly varying the angle in each slice would hide that effect a bit? Anyway, for future reference: EMF Triangle gradient (look about 1/3 down from the top) http://www.flounder.com/gradientfiller.htm EMF+ Path Gradient Brush http://www.codeproject.com/Articles/20018/Gradients-made-easy Regards, David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech

1 0

Licensing issues with Scour (aka 'Optimized SVG' output)
by Eduard Braun 12 Jan '16

12 Jan '16

Hi all, I'm posting here today hoping that we can finally resolve some licensing issues which recently emerged regarding the Scour extension for Inkscape (also know as 'Optimized SVG' output). I'll try to summarize the issue as good as possible so everybody is up to speed: * Right now we bundle an old version of Scour that is dual-licensed with Apache 2.0 license and GPLv2+. This dual licensing was only introduced in a very recent commit [1] when the original author Jeff Schiller agreed to re-license his code under the terms of GPLv2+ after license issues in Inkscape were brought up in a previous discussion [2]. However at this point there were multiple contributions to the Scour codebase by other authors who did not accept to re-license their contributions. This is why the re-licensing is likely to be void and the the current maintainer of Scour (Tobias Oberstein) decided not to apply the dual-licensing when switching over to GitHub with the project [3]. * I recently updated the Scour extension for Inkscape and want to merge these changes [4]. Obviously I followed Tobias Obersteins decision not to apply the dual-licensing, so the new version only has the Apache 2.0 License. * The open question now is: Can we bundle the Scour code with Inkscape and how to we do it? In my opinion this should not be a problem since Scour is an external module that is *indepentent* from Inkscape, e.g. license incompatibilities do not play a role here which is also the opinion of Tobias Oberstein (see [5] for details and references). Also most project members seem to agree (see comments in the merge request [4]) However If we don't want to follow this reasoning we have to decide on alternatives (especially since the code currently in trunk might well have an invalid license). I hope we can once and for all resolve this issue! Best Regards, Eduard [1] http://bazaar.launchpad.net/~scouring/scour/trunk/revision/222 [2] https://sourceforge.net/p/inkscape/mailman/message/32342425/ [3] https://github.com/codedread/scour [4] https://code.launchpad.net/~eduard-braun2/inkscape/scour/+merge/278387 [5] https://github.com/codedread/scour/issues/7

5 13

Inkscape is legally backed by the Software Freedom Conservancy, but SFC needs your help
by Dave Crossland 12 Jan '16

12 Jan '16

Hi Software Freedom Conservancy is the legal backer of Inkscape, but it is at risk of shutting down :( You can help make it sustainable by joining as a member for $120/year - just 14 people are needed! :) SFC is a not-for-profit charity that helps promote, improve, develop, and defend Free, Libre, and Open Source Software (FLOSS) projects. Conservancy provides a non-profit home and infrastructure for FLOSS projects. This allows FLOSS developers to focus on what they do best — writing and improving FLOSS for the general public — while Conservancy takes care of the projects' needs that do not relate directly to software development and documentation. http://sfconservancy.org/members/current/ lists the projects that they support, and the following are relevant to libre graphics: - Inkscape - Git - BOOST - a programming framework used in Inkscape - SWIG - another programming framework used in Inkscape, that enables Python scripting - K-3D - 3d modeling app - Outreachy - helps people from groups underrepresented in free and open source software get involved Just 14 more people needed to meet their membership goal this month, since those who sign up by January 31 count twice, thanks to Private Internet Access. Please consider joining as a member :) -- Cheers Dave

1 0

Board Meeting @ Friday Jan 8, 2016
by Bryce Harrington 11 Jan '16

11 Jan '16

Reminder that the meeting is tomorrow at Noon Pacific time. For agenda and past meeting logs please see: http://wiki.inkscape.org/wiki/index.php/Board_Meetings Bryce

1 1

30 second video for the Inkscape project: New features & work from the past year
by C R 08 Jan '16

08 Jan '16

Okay, so there was not enough interest in doing the interview montage, so I'm back-burnering that one. :) So instead, let's show them what's new in Inkscape! I am doing a brief video commercial for the Inkscape project with updates from the last year. So what are you favourite Inkscape features/progress. This will replace the "two slides" at LGM, with something much more swish and polished to show off the hard work that's been done in Inkscape over the last year (starting from or around April last year). What I need: A list of your favourite new features in Inkscape (developed in the last year, or that will be finished and/or working by the date of LGM in April). I will combine them with mine and submit a video (after showing to everyone on this mailing list and #gimp to make sure we have all the facts right. Cheers. -C

5 13

Should i push to lp:inkscape/0.91.x?
by Aurélio A. Heckert 07 Jan '16

07 Jan '16

Hi folks, I was getting troubles with extensions on Illustrator generated SVGs, so i solve it and send to the repo: http://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/revision/14564 That means trunk = the future 0.92.x As i'm away for a while i must ask: Should i push this patch to lp:inkscape/0.91.x? I believe yes, but i don't know the rules to push on a stable branch. Thanks! -- *Aurélio A. Heckert (aka Aurium)* http://softwarelivre.org/aurium *COLIVRE — Coop. de Tecnologias Livres* http://colivre.coop.br *Inkscape* — Desenhe Livremente http://inkscapeBrasil.org

2 3

ERRO NO INK SCAPE
by Ione Logullo 06 Jan '16

06 Jan '16

Estou tentando colocar um título no caminho mas não estou conseguindo. Já segui todos os procedimentos mas o INKSCAPE não reage, já desinstalei e instalei o programa duas vezes. Eu já fiz isso anteriormente e não tive nenhuma dificuldade mas agora não consigo mais, vocês podem me ajudar? Ione Logullo +55 21 984036492 --- Este email foi escaneado pelo Avast antivírus. https://www.avast.com/antivirus

5 5

Problem compiling
by Jabier Arraiza 05 Jan '16

05 Jan '16

Hi to all. I have a problem compiling inkscape on a SSD. Sometimes when compiling it crash with this error: https://inkscape.org/es/gallery/item/7231/ I also have HD problems not sure are related. Thanks in advance for any help.

1 0

Path Count Restriction in Division, Cut and Difference
by Martin Owens 05 Jan '16

05 Jan '16

I've committed a change to splivarot.cpp to remove the restriction which stopped our difference/cut/division functions from working on multiple paths. I was reading the forum post at http://www.inkscapeforum.com/viewtopic.php?f=5&t=20762 and it didn't seem to make much sense, so I did a few tests which I've posted here: https://inkscape.org/en/gallery/item/7216/ You can see we do the most sensible things already and the new functionality enabled by the commit doesn't seem to make a /lot/ of sense as far as I can see, but then I'd like to not artificially restrict the function because someone might find it interesting. The other hand is that there might be a more common sense way of doing the functions. Maybe by making a union first, or some other thing. But we'd first have to see examples on what users think they'll get when they run these operations on their multiple paths. Best Regards, Martin Owens

5 10