- Inkscape Devel - Inkscape Mailman

gitlab.com gold group features
by Marc Jeanmougin 14 Jul '20

14 Jul '20

Hi all, this is a short "what do you think about this?" message about gitlab. Current state of things : we currently use gitlab on their "gold" plan which does include proprietary extensions to the free software gitlab core (those features are scoped labels, multiple assignees, related issues (/duplicates), multiple issues boards, exceptions to protected branches, push rules, merge approvals). By "just asking", we could also have access to group-level gold features, such as Epics which are like meta-issues to track releases or big feature plans ( https://docs.gitlab.com/ee/user/group/epics/ ) and Group milestones (instead of having per-project milestones) The question is simple : should we ? (Pro : we get access to it; Cons : it's asking to use proprietary features, which is not something we usually do) -- Marc

2 1

Quick update on scribus pdf. current screenshots.
by NASA Jeff 11 Jul '20

11 Jul '20

here's the current screenshot: https://i.imgur.com/T5awaBn.jpg and of the work to be done: https://i.imgur.com/ccU08hN.png i have to do a grid / form layout and some elements, which is trickier than it sounds. more tricky than freee-flow text. i may decide are best left free standing and not in any particular editable layout.

2 1

Hackfest Today! 4PM UTC Leadership/Board day
by Martin Owens 11 Jul '20

11 Jul '20

Dear Develoeprs, Users and everyone, Today is the first experimental online hackfest day. Go here to join: https://digimedia1.r2.enst.fr/b/vec-tz3-fi9 Today we'll join joining teams and talking about what responsibilities different parts of the project do or should have as well as hosting a "Meet the board" meeting at 5PM UTC. Hope to see you all there! Next week: UX and design day! Best Regards, Martin Owens

1 0

PDF and patents, feel free to ignore this if it's touchy.
by NASA Jeff 11 Jul '20

11 Jul '20

Hi, I'm currently writing an import filter to import free flow pdf text into Scribus for editing but i'm aware that there's no free pdf editor worth it's salt because pdf is patent encumbered. as a result all pdf editors that let you edit free flow pdf text are quite expensive and the free versions often limited by watermarks. anyhow, i hope i've avoided any patent issues as layout and fonts used bare no resemblance to anything pdf uses as I aggregate all the text and use Scribus's quite advanced layout engine to do the bulk of the heavy lifting with some vaguely intelligent aggregation code to aggregate the text in the filter. anyhow, can anyone give me a heads up on pdf and patents?

2 1

Inkscape Vectors July Meeting Invitation
by Maren Hachmann 03 Jul '20

03 Jul '20

Hello everyone, the Inkscape Vectors (Marketing and Outreach team) are holding their monthly meeting tomorrow at 15:00 UTC. (time zone converted: https://www.timeanddate.com/worldclock/fixedtime.html?msg=Inkscape+Vectors+… ) Find the proposed Agenda at https://gitlab.com/inkscape/vectors/general/-/issues/162 . Please add your agenda item suggestions to the issue, and join us in the dedicated rocket.chat channel at https://chat.inkscape.org/channel/team_vectors See you tomorrow! Maren

1 0

bit of an update on svg animation
by NASA Jeff 28 Jun '20

28 Jun '20

- hi everyone - I've been looking at animation support and evaluating the competition. also I found a javascript implementation of the web animations api which may be the animation engine to support as it's getting native support in browsers. that doesn't limit us by not allowing support for snap or GSAP on top of this. web animations API works with css and svg and provides interfaces to animation, keyframes and timelines. - - https://github.com/web-animations/web-animations-js <https://github.com/web-animations/web-animations-js> github.com *web-animations/web-animations-js* <https://github.com/web-animations/web-animations-js> JavaScript implementation of the Web Animations API - web-animations/web-animations-js - SVGator, a commercial svg animator supports javascript (using it's custom engine) or css - I still wouldn't suggest supporting any old javascript, but a cut down version of javascript where complex functions get replaced with stubs that return some default value and the code can be evaluated to get the animation (limited by what javascript functionality is implemented) and property settings for the animation can be traced. I would do this roughly by using the built in parser in the javascript engine to calculate animation settings to be presented in the UI. the commercial svg animation tool SVGator supports javascript and css. it doesn't allow the javascript to be modified in the application, I haven't tried importing and svg file with modified javascript. it may also be a good idea to support snap or GSAP ontop of this, on the other hand, they may become obsolete as web animation s API gets full support and people start writing functions for it such as the morph one found here https://coherent-labs.com/Documentation/cpp-gameface/d1/dea/shape_morphing.… - - for instance, simple loops may be supported, but more complex(that use the result of a function call to determine the loop[ conditions) ones may be too complex to support rationally - Doing this loses nothing as the animation will still run in a browser, but Inkscape may only support animations with complex functionality partitioning - Accurate animation playback can still be supported by executing the javascipt but I would limit imports to trusted javascript and not any old javascript for reasons of side effects and security. there are already shims that implement SMIL in javascript, and assuming they allow you to position the timeline and query keyframes and object attributes they should allow for a relatively straight forward SMIL implementation so long as javascript is supported. this proposal sees inkscape supporting SMIL, CSS and javascript. the Web Animations API implementation should allow for the support of CSS without any javascript but can still be used for the actual process of animating and setting the timeline position. at the moment I'm still working on importing text from pdf files in scribus. I have most of the functionality already implemented for this out just requires a bit of polish. to do that I'm going to refactor the code to use a simple framework that should make the code a lot cleaner, be faster and support all the features for the Polish needed to have a decent implementation.

2 5

Suggestions documentation regarding "Getting Started with Inkscape Development"
by wiesi＠posteo.net 24 Jun '20

24 Jun '20

Hello, I recently filed a pull request and was pointed out to * increase the timeout in "Settings => CI/CD => General Pipelines => Timeout" to 3h * Check the "Allow commits from members who can merge to the target branch" in the pull request settings. I suggest to add a section in "Getting Started with Inkscape Development" on the homepage describing the correct settings and maybe also how to create a fork on gitlab (or just link the gitlab documentation). Cheers, Thomas

2 2

Inkscape Hackfest 2020
by Martin Owens 23 Jun '20

23 Jun '20

Dear Inkscape developers and users, I've been thinking about how best we can host a hackfest for 2020 given all the restrictions. After talking with multiple people, I've decided that the best format for an online hackfest is to have one spread out over the summer. So may I present to everyone the Summer of Hackfest: https://gitlab.com/inkscape/vectors/general/-/issues/161 This gitlab issue is just for organising people's preferences, and thoughts. Once I have times confirmed, I'm going to write everything in the regular hackfest wiki page for everyone. So. The idea here is to take advantage of the online nature of this year's hackfest activity and allow people more breathing room between sessions. Each week I'll be hosting a video chat which you will be free to join and just hang out in and where hopefully some of the important topics will happen once per week. No grueling commitment, no big block of time, just a predictable schedule of lovely inkscape topics which will be publisised to get more people involved than ever before. Please join me on GitLab to proposed topics and set your preferred times. I'm looking for one topic per week, so that's six topics. And thanks for your participation. Best Regards, Martin Owens

1 0

chrome's support for modifying web animations api in it's developers console.
by NASA Jeff 21 Jun '20

21 Jun '20

Chrome seems to do a reasonable job of capturing and modifying web animations API in JavaScript. Its not so hot, however, when it comes to elements that have animations that are programmatically generated, it doesn't even group them all together and identify the source of programmatic generation, which in many cases is just a simple trace of the code. I dare say it could do better than just passively listening out for animation events and actually infer many of the from the source documents.

1 0

[GSoC Paths] Status update
by Moazin Khatri 18 Jun '20

18 Jun '20

Hi everyone, I would like to provide a status update on the Path Library Improvement project. Since this is my first report to the list (the last one wasn't public), I'd like to discuss everything done so far. This report is huge and quite technical, so if you want a short version, it is this: "I have successfully written a relatively short piece of code that creates simplification results totally identical to the livarot version. The algorithm is the same as livarot and is nearly as fast. I'm about to start cleaning it, documenting it and integrating it with simplify, lpe-simplify and pencil tool. This will be done within the next two days." Now the detailed version: According to the original schedule, I was supposed to work on the Path Simplification feature and that is what I have been doing. I started with writing some boilerplate code that will allow me to trigger my own Path Simplification code in Inkscape. This is so that I can compare its results with livarot based simplification quickly. I started exploring the simplification algorithm of lightvarot and wrote some path flattening (the process of approximating a path by line segments) myself. I integrated these in Inkscape and the algorithm produced pretty satisfying results but it was too slow. In a "Release" build, the performance might be okay for a "Path > Simplify" but would do pretty bad in live path effects. For what it's worth, I also created an animation explaining this algorithm. You can find it here: https://moazin.github.io/simplification-algos.html Disappointed by its performance, I replaced the main part of the algorithm with its equivalent from livarot (that's explained in the link attached under the title "Livarot / Simplifying the curve". The performance improved but there were significant differences between the results. I had a choice here, I could either just rewrite a cleaner version of livarot's code or understand what's causing the differences and fix those. I chose to do the latter. I started following the procedure "draw paths -> trigger both algorithms -> debug both simultaneously -> understand and fix the differences -> repeat". Going down this route, I understood almost all the parts of livarot and was even able to discover/fix bugs in both livarot and lightvarot. Here are the reasons behind the differences: 1. The codes for flattening the paths were different so obviously there were differences in the results. I simply implemented livarot's algorithm for splitting cubic beziers to solve this problem. 2. There is an iteration of Newton-Raphson method. (I'll probably add what this iteration is and what it does in the link attached above soon, it's mostly math stuff). I suspect that the code for this iteration in lightvarot is mathematically incorrect, so I fixed it. I will do the derivation again to be sure if it's really a bug though. Anyways, I fixed it by replacing the constants from my derivation (which are identical to the livarot version). 3. There is a special portion in livarot code which fixes what livarot calls the "splotch" problem. When the number of points you're fitting are few, you can sometimes get a fit which fits the points correctly but overall doesn't fit the polyline properly. There is some special code that calculates error differently to take into account this situation and thereby avoid bad fits. My code was missing this code, so I wrote it. 4. There is a slight optimization in livarot that reuses some calculations and I suspect it compromises on the accuracy of the fits. I need to investigate more to be sure. I fixed it in livarot by simply using the non-optimized version. (There are two `AttemptSimplify`) 5. There were some silly bugs in livarot's non-optimized `AttemptSimplify`. A minus was replaced by a plus and a weight factor was commented. Fixed both of those on the livarot side. After doing all of these changes, both versions are producing totally identical results. The computation time is also mostly identical. There is a very minor difference in the flattening part which I'm working on. The code can be found at: https://gitlab.com/moazin/inkscape/-/tree/integrating-livarot-low-redesign My code lives in `src/path/PathSimplifier(.h/.cpp)` and `src/path/PathFlattener(.h/.cpp)`. The temporary verb "Path > MyOperation" triggers code in `src/path/path-myoperation(.h/.cpp)`. The commit history is pretty much garbage since I have been experimenting a lot. Over the weekend I'll be cleaning this code, documenting it properly and integrating it in lpe-simplify and the pencil tool. I'll add the final resulting code "cleanly" on a fresh branch. An interesting part of this project is the "design" of whatever code I write. But I think it's too early for me to start thinking about it because as I move towards Boolean Operations, a lot of new things will be discovered and whatever "design" I decide on would change. So, IMHO, this can be discussed later once I am done with Boolean Operations. Please feel free to ask any questions that you may have or provide feedback. Thank you, Moazin

2 1