October 2014 - Inkscape Devel

Powerstroke - interpolation change
by Johan Engelen 19 Oct '14

19 Oct '14

Hi all, Jabier has found a fairly common case where LPE Powerstroke is behaving unintuitive / unstable / scale-dependent. See the attachment. Both paths are exactly the same, except for a very slight (y-coord) change in the right-most width control knot. This instability happens because of how the interpolation between width knots is done. [*] The fix I propose, and committed to experimental in rev. 13620, is to do the interpolation in a 'proper' coordinate system, using the length of the path as a scaling factor for the width knot offsets. This removes the unstable behavior, and also removes the scale-dependent output (noticeable when scaling the path: the result changes if the width points scale with the same factor). Please test if you like this behavior better. (Compare the attached file in trunk and experimental.) The problem is that for some cases, this will change the result of powerstroked paths dramatically. Can we apply such changes so shortly before release? An alternative is changing it after release, which would be even worse in my opinion. regards, Johan [*] It's technical, but here goes quickly for who is interested. Knots are treated as [offset along path, width] points. The offset along path is the segment number + the location along that segment. The width is (may not be true, but for ease of discussion) in canvas coordinates. This means that the interpolation is performed in a *very* compressed coordinate system, where the x-coords may range from, say, 0 to 5, and the y-coords from 0 to 2000. This is also scale dependent; changing the scale of your path and scaling all widths accordingly will change the look of your path. (The implementation of this scaling is implemented by Jabier and I will commit it shortly.)

3 3

Procedural template for tesselation
by Jabiertxo Arraiza Cenoz 18 Oct '14

18 Oct '14

Hi to all. Attached are a procedural template for teselation. I need help testing, improving and put better strings. Also not sure if procedural template, extension or both. Procedural templates are located in experimental branch into share/extensions. If no object i put on experimental to try. Later make the same as extension for 0.48. Regards, Jabier.

5 11

Templates in experimental branch.
by Tavmjong Bah 16 Oct '14

16 Oct '14

Hi, I've replaced a large fraction of the templates in the experimental branch by "procedural" templates. This unclutters quite a bit the Templates menu as well as offering overall more options. Please test your favorite templates and give me feedback. Thanks, Tav

6 12

Daily builds - with static analysis
by unknown＠example.com 16 Oct '14

16 Oct '14

Hi all, I have set up a daily build system that checks if trunk still builds (on Ubuntu) and, more importantly, runs clang's static analyzer using scan-build. You can find the results here: http://ec2-54-69-235-61.us-west-2.compute.amazonaws.com:8080/ After some clicking, you will find these interesting pages (links may become obsolete after a new build) http://ec2-54-69-235-61.us-west-2.compute.amazonaws.com:8080/job/Inkscape_t… and http://ec2-54-69-235-61.us-west-2.compute.amazonaws.com:8080/job/Inkscape%2… As you can see, there are still some nasty bugs in trunk. For example http://ec2-54-69-235-61.us-west-2.compute.amazonaws.com:8080/job/Inkscape_t… -Johan (currently I run Jenkins on free-tier EC2, but we are working on getting something more permanent. Expect a longer email with plans in the near future)

8 15

Automate Tesselations
by Jabiertxo Arraiza Cenoz 16 Oct '14

16 Oct '14

Hello again. Attached are a ?cool svg to make teselations. Is designed to automate it ?easy. Y have a question: Automate as extension or as a procedural templete? The script recibe this inputs: width height Regards, Jabier.

1 0

Release Notes reminder
by Josh Andler 16 Oct '14

16 Oct '14

Hey All, This is just the occasional reminder to make sure the release notes are up to date. Given that development on 0.91 is getting late in the cycle if people could go over the release notes [1] for it and double check all noteworthy changes are listed that would be great. Given that a number of things have landed or changed in Experimental, we need to document these things while they are still relatively fresh in people's minds. It would be helpful if authors of any new features or fixes could create a temporary release notes page for staging this information before anything gets ported to trunk (after 0.91 is forked). Cheers, Josh [1] http://wiki.inkscape.org/wiki/index.php/Release_notes/0.91

2 1

Empty page template broken; python problems
by Tavmjong Bah 16 Oct '14

16 Oct '14

Hi, I have discovered that "Empty Page" template creation is quite broken. The 'viewBox' is always the same, regardless of which page size and orientation are selected. It appears that "empty_page.py" is just pulling in the "default.svg" file and changing the <svg> 'width' and 'height' attributes without changing the 'viewBox' to match. I can patch this but am having trouble with setting attributes within <sodipodi:namedview> to match. For example, the following code attempts to simply change the 'id' of <sodipoid:namedview>: namedview = root.find(inkex.addNS('namedview', 'sodipodi')) inkex.debug( namedview.get("id") ) namedview.set("id", "NewID" ) inkex.debug( namedview.get("id") ) The debug output shows that the 'id' attribute is changed but if I then examine <namedview> with the XML editor it doesn't show the change. Any clues as to what is going on would be greatly appreciated. Tav

5 9

0.91 About Screen Contest - Developer voting time
by Josh Andler 16 Oct '14

16 Oct '14

Here are the results from the About Screen contest on DA, follow the link to see what the community has voted for. http://inkscapers.deviantart.com/blog/488191078/ All Devs (yes that includes Translators too), please chime in with your opinions, votes, as well as any comments on modifications that may need to be done. Please keep all voting and discussion on the mailing lists and let's wrap this up so we can make an announcement by next Monday (voting open through October 19th). Cheers, Josh

15 15

Release Status (Frost)
by Bryce Harrington 15 Oct '14

15 Oct '14

Here's where we're at in the release: 3. Frost. √ Experimental Branch is forked √ Mainline Branch focuses on stabilization √ Only production-ready code committed to Mainline √ Post inkscape-0.91-pre0.tar.gz Finalize any major changes to platform packaging Release Notes should be >90% filled in. Inkscape must pass >90% of 'make distcheck' √ Start an About Screen contest √ General Bug Hunt: 1500 points √ Post additional inkscape-0.91-pre*.tar.gz releases √ Packagers test creating pkgs of the -pre* releases Last time I checked make distcheck there were just a handful of warnings. I haven't checked recently but suspect we're at 90% now. How are we doing on the release notes? When I checked a couple months ago they were looking quite good so assume we're past 90% there too? For the OSX packaging I have a huge amount of notes about many things that we need to do, but essentially it sounded like we're going to postpone any major work until next release, and just use the existing X11-based scripts. su_v has pointed me at a branch with some osx stuff that needs reviewed/landed, but otherwise is there any other major OSX packaging or porting work I need to be aware of? For Windows packaging, I don't really have much in the way of notes. Sounds like the current scripts mostly just work, and modulo a few platform-specific bugs we should be good to go. There was work being done on a Win32 Installer using the WIX toolset but this sounds still in progress and not something we need to worry about for this release. Correct me if I'm wrong? Looking forward... Once the above stuff is settled we'll be entering Freeze. This is both a Feature Freeze and String Freeze. I'll post more details when we get there, but to answer what I think will be a common question - bug fixes can still be landed freely, it's just that feature work and anything that changes user visible (translatable) strings will need release manager approval (i.e. me or Josh). I don't think anyone is planning work of this type so this should be a non-issue. Probably the next question is how long until Freeze is done? I think we need to keep it going at least 30 days, to give ample time to translators. But most of the tasks for this phase are straightforward and I think we won't need much more than 30 days. After that comes Hard Freeze, where we tend to whatever release blocking critical bugs remain (hopefully none by now!) and finalizing everything for the official release. Maybe we'll have 0.91 out the door by Thanksgiving. Bryce

6 15

RFC: Inkscape Updates
by Martin Owens 15 Oct '14

15 Oct '14

Request for Comment. A feature for the 0.91 release and going forwards. The idea is for inkscape to have a way to alert our users about some goings on in the inkscape world 'in app'. This is needed because many users either download the app and fail to upgrade after that, or are not aware of anything beyond the app download. And for users who get inkscape through their package manager and are thus cut off from us. An xml file would be made generated (and cached) on inkscape.org which would be controllable by the inkscape board by vote. It would contain a list of translated alert 'items' specific for an inkscape released version, each one would contain: - unique id (int) - A subject (translated-text) - A body (translated-text) - A link (url) - Start Date (iso date) - Expire Date (iso date) - Importance (int) This file would be downloaded every so often and cached locally. (default one month between updates). Stored in ~/.cache/inkscape/alerts-${inkscape-version}-${lang}.xml When the app has been opened for a certain delayed time (default 3 seconds) it will check for alerts never shown before by id. It will then filter out any outside of the date range start-expire. It will then check the user's preference for alerts (Developer-Notice(0), Community-Update(5), Important(10), Critical(15), Never(20)) and if >= display the alert[1] saving the fact it has displayed this alert-id. [1] http://inkscape.org/en/gallery/item/704/ The importance might be reflected in an icon displayed. The user might be alerted by default to go to inkscape.org to register (and also check their alert settings if they never want to be disturbed) Your thoughts on this proposal are needed. Best Regards, Martin Owens

3 6