- Inkscape Devel - Inkscape Mailman

[Recolor]
by Arshdeep Singh 23 Sep '13

23 Sep '13

Hi all, I just wanted to shed some light on the present scenario: + Snippet to update the color changes is up and running. [ It has to be hooked to "released" signal of RecolorWheelNode ] + Handling removal of objects: This is the problem area right now. My mentor replied this morning (my time) with an approach to handle removing objects. I am going to try working with that. If this goes downhill, I'll try Sebastian idea. Either way, I plan to stick around and am determined to finish what I intended when starting with GSoC. I will gladly be an active contributor till my school-work is not intimidating and I am mostly free till February (March-April see the final submissions and exams). Regards, Arshdeep Singh Third Year, Computer Engineering Delhi Technological University Ph: +91-9654115614 https://sites.google.com/site/adsingh1729/home

1 0

Rending Multiple Times?
by Martin Owens 22 Sep '13

22 Sep '13

Hey Devs, I'm investigating bug lp:850992 (very hard to track down), and I notice something odd. Each time I group or ungroup two objects, the render code on DrawingItem is called many times. I want to know if this is expected and typical behavior since we could be wasting lots of resources re-rendering the same item ever time we click on it or move it. This is my output, some simple couts at the top of calls: Updating DrawingItem: 0xb76e338 Updating DrawingItem: 0xb77a628 Updating DrawingItem: 0xb77a6f8 Updating DrawingItem: 0xb77b000 Updating DrawingItem: 0xe49ea08 Updating DrawingItem: 0xc93c470 Updating DrawingItem: 0xb76e338 Render DrawingItem: 0xb76e338 Render DrawingItem: 0xb77a628 Render DrawingItem: 0xb77a6f8 Render DrawingItem: 0xb77b000 Render DrawingItem: 0xe49ea08 Render DrawingItem: 0xc93c470 Render DrawingItem: 0xb77a628 Render DrawingItem: 0xb77a6f8 Render Drawing: 0xb77b000 Updating DrawingItem: 0xb76e338 Render DrawingItem: 0xb76e338 Render DrawingItem: 0xb77a628 Render DrawingItem: 0xb77a6f8 Render DrawingItem: 0xb77b000 Render DrawingItem: 0xe49ea08 Render DrawingItem: 0xc93c470 Render DrawingItem: 0xb77a628 Render DrawingItem: 0xb77a6f8 Render Drawing: 0xb77b000 Updating DrawingItem: 0xb76e338 Render DrawingItem: 0xb76e338 Render DrawingItem: 0xb77a628 Render DrawingItem: 0xb77a6f8 Render DrawingItem: 0xb77b000 Render DrawingItem: 0xe49ea08 Render DrawingItem: 0xc93c470 Render DrawingItem: 0xb77a628 Render DrawingItem: 0xb77a6f8 Render Drawing: 0xb77b000 Updating DrawingItem: 0xb76e338 Render DrawingItem: 0xb76e338 Render DrawingItem: 0xb77a628 Render DrawingItem: 0xb77a6f8 Render DrawingItem: 0xb77b000 Render DrawingItem: 0xe49ea08 Render DrawingItem: 0xc93c470 Render DrawingItem: 0xb77a628 Render DrawingItem: 0xb77a6f8 Render Drawing: 0xb77b000 Updating DrawingItem: 0xb76e338 Render DrawingItem: 0xb76e338 Render DrawingItem: 0xb77a628 Render DrawingItem: 0xb77a6f8 Render DrawingItem: 0xb77b000 Render DrawingItem: 0xe49ea08 Render DrawingItem: 0xc93c470 Render DrawingItem: 0xb77a628 Render DrawingItem: 0xb77a6f8 Render Drawing: 0xb77b000 Updating DrawingItem: 0xb76e338 Render DrawingItem: 0xb76e338 Render DrawingItem: 0xb77a628 Render DrawingItem: 0xb77a6f8 Render DrawingItem: 0xb77b000 Render DrawingItem: 0xe49ea08 Render DrawingItem: 0xc93c470 Render DrawingItem: 0xb77a628 Render DrawingItem: 0xb77a6f8 Render Drawing: 0xb77b000 Updating DrawingItem: 0xb76e338 Render DrawingItem: 0xb76e338 Render DrawingItem: 0xb77a628 Render DrawingItem: 0xb77a6f8 Render DrawingItem: 0xb77b000 Render DrawingItem: 0xe49ea08 Render DrawingItem: 0xc93c470 Render DrawingItem: 0xb77a628 Render DrawingItem: 0xb77a6f8 Render Drawing: 0xb77b000 Updating DrawingItem: 0xb76e338 Render DrawingItem: 0xb76e338 Render DrawingItem: 0xb77a628 Render DrawingItem: 0xb77a6f8 Render DrawingItem: 0xb77b000 Render DrawingItem: 0xe49ea08 Render DrawingItem: 0xc93c470 Render DrawingItem: 0xb77a628 Render DrawingItem: 0xb77a6f8 Render Drawing: 0xb77b000 Updating DrawingItem: 0xb76e338 Render DrawingItem: 0xb76e338 Render DrawingItem: 0xb77a628 Render DrawingItem: 0xb77a6f8 Render DrawingItem: 0xb77b000 Render DrawingItem: 0xe49ea08 Render DrawingItem: 0xc93c470 Render DrawingItem: 0xb77a628 Render DrawingItem: 0xb77a6f8 Render Drawing: 0xb77b000 This is from /One/ group action. your thoughts? Martin,

5 7

Re: [Inkscape-devel] Removal Of Objects from Selection
by Sebastian Götte 22 Sep '13

22 Sep '13

On 09/22/2013 06:51 PM, Arshdeep Singh wrote: > Hi, > Will pulling the changes of selection.h and selection.cpp suffice to use > for my project ? > Does _notifySelected notify signals for both selection and un-selection ? the signal has three arguments: The object, the selection and a bool that indicates whether the object is now selected (true) or unselected (false). You will also need the few lines in sp-object.h containing the signal logic. Sebastian

2 1

Non-Blockers
by Martin Owens 22 Sep '13

22 Sep '13

Hey SUV, I'm interested in a list of bugs which /should/ be fixed for release, but don't block. Do we have one of those? I couldn't find an existing tag, should we make one? Basically we want to prioritize the next round of bug fixes so we can get Inkscape more ready for a good 0.49 release. Thanks for all your work with testing, it's amazing. Martin,

5 10

[Units] Finishing Up
by Matthew Petroff 21 Sep '13

21 Sep '13

I've now merged phase two of my GSoC project, unit support improvements, with the trunk. I've enjoyed my work this summer and would like to thank the Inkscape community for the opportunity. I plan on staying involved with the project for the foreseeable future. http://www.mpetroff.net/archives/2013/09/20/finishing-google-summer-of-code/ -Matthew

5 4

Admin action required
by Krzysztof Kosiński 21 Sep '13

21 Sep '13

Hello If there's an admin in the room (as in, a member of the Inkscape Administrators team on Launchpad), please do the following: 1. Give commit access to Markus Engel so he can fix further issues with the C++ification himself. 2. Approve me as administrator. Regards, Krzysztof

8 9

Weird fallback mechanism for input data in python scripts
by Alex Valavanis 21 Sep '13

21 Sep '13

Hi All, I found some unexpected behaviour with inkex-based extensions if a non-existent SVG filename is specified. To reproduce: cd share/extensions ./gimp_xcf.py non-existent-file.svg Expected behaviour: * Script exits with an error message "Unable to open non-existent-file.svg" Actual behaviour: * Script silently falls back to reading from standard input, and appears to freeze. This appears to be caused by the fallback mechanism for obtaining data streams in the Effect.parse() function in inkex.py. At the moment, it does this: 1. Try to read file specified as a function argument e.g., my_effect.parse("this-file.svg) 2. If that file can't be opened, try to read the file specified in self.svg_file 3. If that file can't be opened, read from stdin This could lead to some weirdness e.g., e = ProcessImportantData() # Specify the wrong file name somewhere e.svg_file = "wrong-input-data.svg" # Later, try to read from the correct file, but with a typo e.parse("correct-input-data-with-typo.svg_BORK") # When we apply the effect, the "correct-input-data-with-typo.svg_BORK" file doesn't exist, and the script will silently fall back to using the wrong data file. e.effect() I have attached a patch that changes the behaviour so that the same order of precedence is maintained, but the script will fail if the specified file cannot be opened. I'm not the best Python programmer, and I don't know the precise intended behaviour of the extensions system, so please could someone review/comment? AV

1 0

Re: [Inkscape-devel] Release and Website
by Bryce Harrington 21 Sep '13

21 Sep '13

On Tue, Sep 10, 2013 at 01:32:41PM -0700, Josh Andler wrote: > If we want to go the donation to fix bugs route there will need to be > a majority consensus from the developers (translators and other > community members don't get included in this vote as they fall into > different categories). The short version of this is we really wouldn't > want to upset anyone or have ill-will or tensions arise because others > get compensated while their efforts do not. > > If the developers did want to pursue this, we could then bring this to > the attention of the board. My guess is that if we really had a large > portion of the developers wanting to see this happen, the board would > not likely oppose it. After that we could then discuss with Bradley > Kuhn from Software Freedom Conservancy how to go about implementing > this. If someone wants to try and organize a vote, feel free. I happened to meet Bradley here at LinuxCon and he raised this topic with me. He said that they analyzed all of their projects and Inkscape was at the top of the list for likely success for fundraising. It sounded like they would love to partner with us to raise moneys to help improve the project, be it feature work or stabilization. > >> > Maybe a stupid idea, but here I go :) > >> > Have you ever considered to crowd-fund bugfixing? (i.e.: getting money > >> > to pay somebody to do the work nobody else wants to do) When Inkscape started there were several bug-bounty projects in operation which we watched drift into non-success. I suspect that's why many of us have been a bit skeptical about the feasibility of bug bounties generally. But it's definitely gotten a lot of discussion. By now there must be some good "best practices" identified, so maybe it's just a matter of having someone come up with a plan. > >> > If money can be obtained from a crowdfunding campaign... is there any > >> > qualified person willing to do the job? > >> > > >> > I know it's unfair to developers who already contributed for free, but > >> > as far as I know money is not the main motivation for hackers who persue > >> > the fun aspect of development (new features, challenges). > >> > > >> > Maybe getting somebody paid to take care of the ugly stuff nobody wants > >> > to do is a fair balance and takes the stress out so regular contributors > >> > can focus on the fun stuff. These questions have been on my mind as well. And I am of a similar opinion that if money is being paid for development, let's try targeting it to the stuff we need the most that volunteers don't want to bother with. That sounds very logical. If you would indulge me to blather on a bit more on this topic... I think one problem with the bug bounty programs was that they paid on a per-bug basis. But like I think someone else pointed out, often 90% of the work is just learning the codebase; then the developer could swat a dozen bugs all at once. So, we might want to organize the work as not to fix a specific bug for $, but to fix a collection of closely related bugs for $$$. As to whom to find to do the work, there are a number of options. Hiring an existing Inkscape developer seems least-risk; they will have already climbed at least part of the learning curve and demonstrated their ability and dedication. But finding one who is available and interested could be tricky. Alternatively, we could find a cheap external developer. I think this would increase the administrative workload, and likely wouldn't result in an ongoing developer. But for particularly unenjoyable work, maybe that's acceptable. And there's probably half a dozen other ideas. We've had good success with GSoC, and so something that builds on that (Winter of Bugs?) might be worth thinking about. There are also possibilities beyond just direct paying for development. For example, if we increased our presence at conventions that might pull in more ordinary volunteer developers. Training is another avenue I think could be good. Either arranging some development tutorials ourselves, to help users graduate into developers, or even sending existing active developers to developer training classes (to learn new tricks for performance optimization, debugging, etc.) I am also a big believer in the power of bug triagers to help make bugs easier to fix, such as by helping gather stack traces or document steps to reproduce. This is another tedious job (as I know from experience), but doesn't need to be thankless, and there could be some low-cost ways of stimulating these efforts. > >> > Of course, it's not as easy as it sounds: A qualified developer who > >> > knows the code enough and can meet the technical requirements is needed. > >> > And probably also a person willing to take care of the paperwork and > >> > administrative tasks. And people willing to review the patches... I'm glad you brought up the administrative side. This may seem minor, but it's a prerequisite to finding a developer and is tedious work so could be hard to find a volunteer. We would need this person to be reliable and responsive, able to talk with the lawyers, and prepared to make tough decisions. In fact this was my main counterargument to Brad's suggestion; he indicated the conservancy would love to help on the financing/legal end, but part of the management of this would have to come from us. This has been essentially the same problem the board has run into with other proposed activities - someone needs to take the coordinator role to get it organized. So that's my thinking. Before we start really talking about a paid bug fixer, we need someone to volunteer to do coordination and administration. Or lacking a volunteer, it's an important enough role we could consider making it a part-time paid role, particularly if we could raise enough money for multiple efforts. Bryce

4 8

[Tracing] Report #9
by Vinícius dos Santos Oliveira 21 Sep '13

21 Sep '13

Hi fellow devs (and users following the progress of libdepixelize), I've been coding the B-Splines optimization code for the last several few days and I was struggling to make any progress at all. I've tried SOOO many techniques, but nothing would do. Anyway, I realized that the paper states "... by optimizing the locations of their control points". I was trying to optimize the location of all points (not only control points. Sorry for the useless email, but I just wanted to share my frustration. I'll be uploading the (hopefully) working code today. I'll need to refactor a lot of the shitty code I created. -- Vinícius dos Santos Oliveira https://about.me/vinipsmaker

2 2

Re: [Inkscape-devel] Code style question
by Markus Engel 20 Sep '13

20 Sep '13

> The main reason for asking if A is ok, is that I'mnot 100% if A is standard accepted practice by all C++ compilers, and will notcause trouble with some compilers. A is allowed according to the c++03 standard, so everycompiler should support this. > A name introduced by a declaration in a condition(either introduced by the type-specifier-seq or the > declarator of the condition) is in scope from itspoint of declaration until the end of the substatements controlled > by the condition. If the name is re-declared in theoutermost block of a substatement controlled by > the condition, the declaration that re-declares thename is ill-formed. [Example: > if (int x = f()) { > int x; // ill-formed, redeclaration of x > } > else { > int x; // ill-formed, redeclaration of x > } > —end example] > The value of a condition that is an initializeddeclaration in a statement other than a switch statement is > the value of the declared variable implicitlyconverted to type bool. If that conversion is ill-formed, the > program is ill-formed. The value of a condition thatis an initialized declaration in a switch statement is > the value of the declared variable if it hasintegral or enumeration type, or of that variable implicitly converted > to integral or enumeration type otherwise. The valueof a condition that is an expression is the value > of the expression, implicitly converted to bool forstatements other than switch; if that conversion is > ill-formed, the program is ill-formed. The value ofthe condition will be referred to as simply “the condition” > where the usage is unambiguous. But keep in mind that you may not use any additionalparentheses or logical operators. Regards, Markus

1 0