October 2015 - Inkscape Devel

Board Meeting @ Friday Oct 2nd, 2015
by Bryce Harrington 09 Nov '15

09 Nov '15

Hi all, We'll be holding an Inkscape Committee meeting this Friday the 2nd of October, on #inkscape-devel, at 1900 UTC (Noon PDT / 9pm CEST) http://wiki.inkscape.org/wiki/index.php/Board_Meetings All in the Inkscape community are welcome to attend. Our agenda is open for any new business. Thanks, Bryce ----- Forwarded message from Tavmjong Bah <tavmjong@...8...> ----- Date: Mon, 28 Sep 2015 17:28:13 +0200 From: Tavmjong Bah <tavmjong@...8...> To: Bryce Harrington <bryce@...961...>, inkscape-board(a)lists.sourceforge.net Subject: Re: [Inkscape-board] Proposal for board meeting An IRC meeting is an excellent idea. Any day at noon PDT (9 PM CEST) is OK with me. Thursdays I have an SVG WG meeting at 1:30 PM PDT (10:30 CEST). My agenda items would be: C++11 Hackfest 2016 Paid development Tav On Sun, 2015-09-27 at 12:20 -0700, Bryce Harrington wrote: > Hi guys, > > Now that our board is re-manned, I'm thinking it'd make sense to call > a > meeting on IRC. I don't have anything major to discuss myself, but > I'll bet the rest of you have some good ideas to float. > > How does some time first week of October sound? Thursday Oct 1st? > Or > would the weekend be better? I seem to recall that before we met at > noon pacific time; would such a time be impossible for anyone? > > http://wiki.inkscape.org/wiki/index.php/Board_Meetings > > As far as agenda goes, I don't have anything to suggest - this past > year > we've accomplished so much! I figure we can just play it by ear, and > leave the agenda to "opens". > > Bryce > > > > > > --------------------------------------------------------------------- > --------- > _______________________________________________ > Inkscape-board mailing list > Inkscape-board(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-board ----- End forwarded message -----

6 15

Screen tearing on Inkscape (OS X)
by Papoj Thamjaroenporn 08 Nov '15

08 Nov '15

Dear Inkscape-devel, I recently picked up Inkscape again, and there is this screen tearing <https://en.wikipedia.org/wiki/Screen_tearing> issue I have seen on OS X, and I am wondering what the causes are and how I may be able to contribute. As far as I understand, screen tearing seems to be an issue specific to GTK2. This happens when I scroll or zoom the canvas, where screen refresh rate is not synced with canvas rendering. This happens either on X-based version (I tried using the official Inkscape app) or Quartz-based version (I tried by compiling the trunk using Quartz variants). I also found that ~suv has this exciting development on native OS X integration with GTK3. The artifacts I have seen are exactly like in this screen recording <https://inkscape.org/en/gallery/item/4556/> of Inkscape with GTK2 that ~suv posted. So, am I correct to say that GTK3 somehow eliminates this problem, even without native OS X integration? How does it do so? If we stay with GTK2 as of now, is there a way to fix the tearing issue? Regards, _______________________ Papoj "Hua" Thamjaroenporn papoj@...3117...

2 2

Re: [Inkscape-devel] Spray Tool Improvements III
by Jabier Arraiza 30 Oct '15

30 Oct '15

Hi Ivan, put reply on list. First one is not posibol to put them "exactly" because is based on a random algoritm of the tool. Second one: Great idea!!! I try to implement. Thanks for the feedback! El jue, 29-10-2015 a las 12:15 +0100, ivan louette escribió: > Then what do you think of the two following ideas : > > 1° spraying exactly contiguous squares or quadranglesto simulate > bitmaps ? > > 2° spraying objects which increase or decrease in size based on the > darkness or lightness of the background colors ? > > Le 29/10/15 11:23, Jabier Arraiza a écrit : > > Yes Ivan!!! > > > > El jue, 29-10-2015 a las 09:14 +0100, ivan louette escribió: > > > Can you spray over a bitmap image and acquire its colors like > > > this is > > > possible with clones ? > > > > > > Le 28/10/15 21:10, Jabier Arraiza a écrit : > > > > Thanks Ivan, this allow a lot of posibilities, because the > > > > color > > > > that > > > > change is only the fill, the stroke retains original color, so > > > > you > > > > can > > > > do things like this: > > > > http://i.imgur.com/wn7n95Z.png?1 > > > > > > > > Regards, Jabier. > > > > > > > > > > > > El mié, 28-10-2015 a las 20:53 +0100, ivan louette escribió: > > > > > Amazing ! I easily imaginate it combinated with some svg > > > > > filter > > > > > to > > > > > simulate organic cellular textures ! > > > > > > > > > > ivan > > > > > > > > > > Le 28/10/15 19:31, Jabier Arraiza a écrit : > > > > > > 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. > > > > > > > > > > > > > > > > > > --------------------------------------------------------- > > > > > > ---- > > > > > > ---- > > > > > > ------------- > > > > > > _______________________________________________ > > > > > > Inkscape-devel mailing list > > > > > > Inkscape-devel(a)lists.sourceforge.net > > > > > > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > > > > > > > > > > > ----------------------------------------------------------- > > > > > ---- > > > > > ---- > > > > > ----------- > > > > > _______________________________________________ > > > > > Inkscape-devel mailing list > > > > > Inkscape-devel(a)lists.sourceforge.net > > > > > https://lists.sourceforge.net/lists/listinfo/inkscape-devel >

3 5

Re: [Inkscape-devel] Inkscape-devel Digest, Vol 113, Issue 19
by Jelle 30 Oct '15

30 Oct '15

Great work guys! The spray tool improvements make it a lot more useful, but the text improvements are a bit of a breakthrough. Thanks for all the great effort. > 1. New branch SprayTool Improvements > 9. Vertical text & 'text-orientation' Cheers, Jelle

2 1

Recent changes that would result in object reordering???
by mathog 29 Oct '15

29 Oct '15

I fixed a bug today and found that the emf round trip test no longer worked. (This has nothing to do with the bug I was working on, which just changed a couple of scale factors related to dashed lines.) The round trip test works like this (sorry about the wrap): $INK --file=/usr/local/src/libUEMF/dist/test_libuemf_ref.emf --export-emf=/tmp/test1.emf $INK --file=/tmp/test1.emf --export-emf=/tmp/test2.emf $INK --file=/tmp/test2.emf --export-emf=/tmp/test3.emf $READEMF /tmp/test1.emf > /tmp/test1_emf.txt $READEMF /tmp/test2.emf > /tmp/test2_emf.txt $READEMF /tmp/test3.emf > /tmp/test3_emf.txt afterwards "diff" of any of pair of the test*_emf.txt pairs would show only the one line associated with the name change. Not anymore though. Now they differ from each other a lot. When the emf files produced are viewed in inkscape they appear to be the same. However, the text dumps of the EMF files are wildly different, apparently because the object order is no longer the same. That is, the input stage is seeing the objects in one order, and the output stage is seeing them in another. The reordering seems to be repeatable, that is, if test1.emf is loaded and saved as test9.emf, then the text dump of that is the same as test2.emf (other than the file name field.) The same test with WMF is still stable, but that is a much, much simpler and smaller test file. What has changed in Inkscape that would be causing this? Thanks, David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech

3 3

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