- Inkscape Devel - Inkscape Mailman

Code of Conduct review
by Krzysztof Kosiński 29 Oct '15

29 Oct '15

Hello I think the CoC can be considerably improved. I think it's too wordy in a few places. Here is my proposed revised text. Inkscape online communities are intended to be a friendly, inclusive spaces for users to collaborate on the further development of Inkscape, share and discuss their creations, inspire each other and interact in constructive ways. To that end, we have established a set of guidelines that we believe will help foster such an environment. Anyone willing to follow these guidelines is welcome. In your interactions with others, please do your best to: - Be respectful. There's always a human very much like you at the other end. Always treat them respectfully and be kind to them, even if you disagree with them. - Be responsible. Everyone makes mistakes from time to time; own up to them and be willing to work on fixing them. If someone has been harmed or offended, listen carefully and work to right the wrong. - Don't take criticism personally. Remember that criticizing an idea (e.g. a technical proposal or an user interface blueprint) is different from criticizing the person that proposed it. Do not become overly attached to your contributions and do not demand preferential treatment for them because of your standing in the community. Ideas should stand on the merit of their supporting arguments, not on the merit of their originators. - Use neutral language. Avoid words that others are likely to find offensive or excluding. - Forgive. If someone wronged you and apologized, do not keep demanding special punishment. Don't hold a grudge or seek to settle scores. Be willing to let things slide if it benefits the community. - Give credit where it is due. Never try to pass off others' work as your own. - Disclose and address conflicts of interest. You should be aware when you are conflicted due to employment or other projects you are involved in, and abstain or delegate decisions that may be seen to be self-interested. When in doubt, ask for a second opinion. - Step down considerately. When you leave a responsible position in the Inkscape project, do so in a way that minimizes disruption to the community. Tell people you are leaving and take the proper steps to ensure that others can pick up where you left off. The following actions and behaviours are deemed unacceptable: - Harassment of other users, including but not limited to threats of any kind, insults, discriminatory language and jokes, unwelcome sexual attention, posting personally identifying information ("doxing"). - Deliberate disruption: trolling, spamming, flaming, baiting, attention seeking, distribution of malware, any kind of attacks against Inkscape computing infrastructure or that of its parent organizations. - Distribution of illegal or pornographic material in Inkscape communities. - Advocating or encouraging any of the above. If you believe a member of an Inkscape community is in breach of the above code, report it to the appropriate moderators (contact info here), even if you are not among the directly affected parties. Violations of the code can be met with disciplinary action, ranging from a private warning to complete, permanent expulsion. If you feel you have been unfairly accused or penalised, you may contact Inkscape's board (link to governance section here). Decisions of the board are final. Summary of changes: I removed some text that I felt was repetitive and split the code into 2 sections with desirable and undesirable behaviors. I also added 2 points: "Forgive" and "Give credit where it is due", which I think are pretty important, and a paragraph at the end about disciplinary action. Best regards, Krzysztof

5 11

Spray Tool Improvements III
by Jabier Arraiza 28 Oct '15

28 Oct '15

Hi again, my last video about new features to the spray tool: https://www.youtube.com/watch?v=aTdKu7mAZE8 Thanks to Gabriel Grosso for the idea and to Mc for his help on review. Cheers, Jabier.

3 3

Spray Tool II
by Jabier Arraiza 27 Oct '15

27 Oct '15

Thanks to Gabriel Grosso idea I just add a new feature to the no overlap branch. Here are a short video working. https://www.youtube.com/watch?v=1eTG2U3qlb4 All the best, Jabier.

2 1

/usr/share/inkscape/extensions/interp.py
by Philip Rhoades 26 Oct '15

26 Oct '15

People, I didn't get a response from anyone on the user list about the question hereunder so the next Q is: Is it possible to modify interp.py so that it can write the interpolated paths to a text file so that I can create the separate, individual SVGs with my own script? I don't know Python and it would take me forever to understand interp.py - I would be happy to pay someone for the modification . . Thanks, Phil. On 2015-10-25 14:20, Philip Rhoades wrote: > People, > > OK, I see I can use Inkscape's "Interpolation" to do a bit of what I > want and OpenShot lets me use SVG "frames", so is it possible to script > the interpolation process so that the individual, intermediate objects > get written to separate SVG files somehow? I can do this manually by > massaging the current interpolated SVG file but just being able to do: > > Interpolate -> Write to separate files > > would save a LOT of time . . > > Any possibilities? > > Thanks, > > Phil. -- Philip Rhoades PO Box 896 Cowra NSW 2794 Australia E-mail: phil@...1587...

2 1

New branch SprayTool Improvements
by Jabiertxo Arraiza Cenoz 26 Oct '15

26 Oct '15

Hi to all. I Just finish my new branch focus on Spray Tool. The feature I added is optionaly no overlap with offsets for spray tool. There is a video here: https://www.youtube.com/watch?v=uehj4ATOWos Also in the video show at the end a option in roughen LPE to work with spray tool to give always diferent shapes on each spray item. The code for the Spray tool is here: https://code.launchpad.net/~inkscape.dev/inkscape/spraytool-no-overlap The code to the roughen LPE is now on trunk. Cheers, Jabier.

2 1

New branch SprayTool Improvements
by Jabiertxo Arraiza Cenoz 25 Oct '15

25 Oct '15

Hi to all. I Just finish my new branch focus on Spray Tool. The feature I added is optionaly no overlap with offsets for spray tool. There is a video here: https://www.youtube.com/watch?v=uehj4ATOWos Also in the video show at the end a option in roughen LPE to work with spray tool to give always diferent shapes on each spray item. The code for the Spray tool is here: https://code.launchpad.net/~inksca pe.dev/inkscape/spraytool-no-overlap The code to the roughen LPE is now on trunk. Cheers, Jabier.

3 4

Measure improvements
by Jabier Arraiza 21 Oct '15

21 Oct '15

Hi to all. I just propose for merge a branch to improve measure tool. I made a video to show it working. Think is not a bad idea to get reviewers :) https://www.youtube.com/watch?v=OE0cVDGCzbM By the way, all the best. Jabiertxo.

6 11

roughen-improvements LPE
by Jabiertxo Arraiza Cenoz 19 Oct '15

19 Oct '15

Hi to all. First of all sorry for the noise whith the roughen related commits, the work is near end but finaly i decide made a new branch to reduce noise and also work in other place. I take the code working better in trunk but not working like I want so I think this week can fix it and propose for merge. Cheers, Jabier.

1 0

Re: [Inkscape-devel] Website Feedback
by Martin Owens 19 Oct '15

19 Oct '15

Hi Will, This is a great question and as the Website administrator I would normally ask you to post this in the appropriate channel. But to help get an answer (especially to your question about how to help to the features you want) I'm posting it to the developers mailing list. If you reply to any of the messages, you should subscribe to the mailing list first by looking at the email footer of that message. Developers and Users: see the message below and reply. Best Regards, Martin Owens Volunteer Website Administrator On Mon, 2015-10-19 at 15:30 +0000, Anonymous User wrote: > willprot@...36... > > There is only one thing that stops me from using Inkscape over > Illustrator and I have been waiting on it and checking on it for > literally years now and that is gradient meshes. > > Coloring an image is he most basic and integral part of graphics and > it is just way too easy & convenient to accomplish in AI to pass up, > > That said is there any time line for Gradient Meshes in Inkscape? > > Years ago the SVG2 specs for it were to be finalized Aug 2015, can't > see now where that is at. > > I also see there is a way to help certain project, but > A. not sure how? and B. If the SVG 2/Grad Mesh specs are not finalized > does that mean there can be no movement regardless for that?

3 2

2Gom sync - high potential for regressions after r14226
by Krzysztof Kosiński 18 Oct '15

18 Oct '15

Hello I recently made a commit that finally synchronizes the 2Geom version used in Inkscape and the "upstream" version in 2Geom's Launchpad repository. It compiles and appears to work correctly, but since there were several potentially breaking changes in 2Geom, it has a high potential for regressions. The most important changes in 2Geom are: 1. The sign convention for cross(Point, Point) was flipped to match the one for cross(D2<SBasis>, D2<SBasis>): it is a[X]*b[Y] - a[Y]*b[X], not the other way around. I think I converted all uses, but one can never know. 2. All nearestPoint() methods were renamed to nearestTime(), since they return time (parameter) values, not points. nearestTime() for Path and PathVector returns PathTime and PathVectorTime respectively. PathTime encapsulates a curve index and a time value, while PathVectorTime encapsulated a path index, a curve index and a time value. The reason for using these types instead of extending the range of the time parameter from [0, 1] to [0, N] is twofold: - Packing these two parameters into the double type causes a loss of acuracy as the indices increase. For example, referencing a point that lies on the 32nd curve causes a loss of at least 5 bits of precision. - For PathVector, there is an unnecessary O(N) step involved in mapping the [0, N] time value to path and curve indices. In the future, there will be two additional families of methods: nearestPoint(), which will actually return the nearest point (I avoided adding until the sync is done to simplify porting to the new API), and nearestPosition(), which will compute both the nearest point and the time value. Doing the latter can often save a lot of calculations, since in many cases the point is computed from the time or vice versa. 3. SVGEllipticalArc was renamed to EllipticalArc, and the old EllipticalArc was removed. The only difference between them was that EllipticalArc would throw exceptions if the constructor parameters did not specify a valid arc, whereas SVGEllipticalArc just falls back to a straight line. Additionally, a number of other improvements were made, for example EllipticalArc no longer allocates a copy of itself when transforming it. 4. There was a major cleanup of Path: - Iterating between begin() and end_closed() will skip the linear closing segment if and only if its endpoints coincide exactly. SVGPathParser was modified to retain the old behavior of considering the closing segment degenerate if it is shorter than some specified tolerance. - Internally, the path is now stored as a copy-on-write boost::ptr_vector of Curve. This should give a performance boost, since we are no longer using boost::shared_ptr-based copy-on-write for each curve, but only for entire Paths. - PathVector is now a real class, not a typedef of PathVector, This allows several things to be implemented as methods instead of as standalone functions. - PathSink was improved. Instead of creating a switch-like structure for the result of dynamic_cast of the abstract curve type to more concrete types, please derive from PathSink. - There is a new class called CairoPathSink for outputting 2Geom paths and shapes to Cairo. 5. Circle and Ellipse were fleshed out, and contain many of the methods found in Curve and Path. 6. There is a new intersection API, exposed as a method on shapes and returning a class that contains two time values and the point of intersection. There are methods for Line, Circle, Ellipse, Path and PathVector. Please test and report and regressions, but please make sure to check whether they are really regressions - for example the eraser tool sometimes doesn't work and it has nothing to do with the 2Geom sync, but rather with some faulty code in livarot. Regards, Krzysztof

3 8