- Inkscape Devel - Inkscape Mailman

problems having only macports to install Inkscape on Mac
by brynn 31 Jan '17

31 Jan '17

Hi Friends, We have this message which has gone unsolved, in the User mailing list. https://sourceforge.net/p/inkscape/mailman/message/35630257/ I've seen this same problem posted 3 or 4 other times. They follow the instructions for installing using Macports. Everything seems to have worked without producing errors or other problems. But afterwards they can't find Inkscape. In one of them, I'm trying to help a newbie who posted on Inkscape Community. She has sought support from Macport support, and apparently they are either unable or unwilling to simplify the solution for a newbie. I'd like to know the solution for this, since it seems so common. Then I (or we) can help Mac users who have this problem. In my opinion, it reflects poorly on the project not to have a solution which newbies can use. Hopefully Kirk Slowe will be successful packaging a DMG version for 0.92 or 0.92.1. But meanwhile, can anyone tell me the solution for this? Thank you very much, brynn

1 0

Inkscape 0.92 via homebew on macOS
by Tim Sheridan 31 Jan '17

31 Jan '17

If you use homebrew on macOS, then you can get Inkscape 0.92 by running: brew install caskformula/caskformula/inkscape (For non homebrew people, here's a glossary: formula => package built from source, tap => repository, cask => package redistributing an upstream binary) This formula originates from the inkscape formula in the homebrew-gui tap. However, recently the homebrew-gui tap has been deprecated. In the case of Inkscape, the cask is considered the successor package. But since the inkscape cask is limited to official releases (or third party releases nominated by the Inkscape project), the cask will stay at 0.91. So for the time being, I'll be maintaining the inkscape formula in this tap. Any contributions/improvements are welcome: https://github.com/caskformula/homebrew-caskformula Cheers, Tim

5 8

Inkscape 0.92.x stable daily PPA
by Bryce Harrington 30 Jan '17

30 Jan '17

For testers on Ubuntu, I've created a new automated PPA that builds snapshots of the current stable branch, 0.92.x: https://code.launchpad.net/~inkscape.dev/+archive/ubuntu/stable-daily Note that while these snapshots are of the stable tree, the packages aren't official releases, so there is some chance of bugs, and things can change. This PPA is intended to make it more convenient for folks to test our stable tree and help us ensure the point releases are high quality. I've only tested the Trusty package, so ymmv on other ubuntu releases but I expect they should all work as well as the official point releases. Bryce

1 0

Git Rebasing
by Martin Owens 29 Jan '17

29 Jan '17

Hi Developers, Just a heads up. I rebased the inkscape-web git repository on GitLab to sort out problems with it's cherry picks. This took 2 hours of picking through the rebasing as some of it could be automated. So I had to manually merge about two hundred of the 1600 commits to get it working. Not sure if this will bite the inkscape git repository some time in the future. But being aware of the non-linear repository created by a migration from bzr. Best Regards, Martin Owens

5 13

Fw: Lack of mac installer
by brynn 29 Jan '17

29 Jan '17

I received the original message (at the bottom) through the Contact form on Inkscape Community. Forwarding along to the list. You can see I suggested to subscribe to the list. But as of now, he isn't a subscribed. I didn't know exactly what to say about the change to depending on Macports, so hopefully you all can be more helpful. brynn -----Original Message----- From: admin@...3472... Sent: Sunday, January 29, 2017 6:42 AM To: kirk@...3473... Subject: Re: Lack of mac installer Hi Kirk, Wow, that's a fantastic offer! You've actually reached a forum which is only temporarily the official Inkscape forum, while we are working on getting the new official forum working. And for some reason which I find odd, Inkscape developers don't use bb style forums. Since I'm not a Mac user, I haven't paid very close attention to why they switched to Macports. But judging by all the complaints we've had about people trying to use Macports, maybe it would be good to have the DMG version. You'll want to subscribe to the developer's mailing list (https://inkscape.org/en/community/mailing-lists/), which is where this kind of issue is discussed and handled. I could go ahead and forward this to the list, so the people who need to know will see it. You won't be able to post to the list, until you subscribe. But you'll get any replies. And you can follow any discussion which might happen after I forward this, in the archives. The link to the archives is right beside the link to subscribe, on the page above. Actually, developers are about to release 0.92.1, so this could be good timing! Thanks for your generous offer, and I'll send this right along to the people who can answer your questions. All best, brynn -----Original Message----- From: kirk@...3473... Sent: Saturday, January 28, 2017 5:40 AM To: admin@...3472... Subject: Lack of mac installer Contact Page Form for Inkscape Community Name: Kirk Email: kirk@...3473... IP: 209.131.239.35 Message: Do you lack someone to create a dmg installer of v .92? Is that why macports is being used? I'm a mac guy and so understand why so many people have issues with macports. I'm not an expert but would like to volunteer my services to get this version created into a .dmg installer.

2 1

0.92.1 plan
by Bryce Harrington 29 Jan '17

29 Jan '17

The 0.92.x stable branch is reopened for changes. Consider it as under feature freeze but not string freeze. Bugfixes are welcome to be added. Please continue to check with me before landing things, but for the next few weeks I expect to be in rubber stamp mode and approve most anything that looks sensible. We do need to be cautious about not introducing regressions at this point. Write good changelog messages explaining the fixes in good detail please. Translation updates (and entirely new translations) are fine to land directly, no need to check with me. There are already a handful on the branch already that unfortunately came in just after I had cut the tarball. Extension updates and new extensions are probably low enough regression risk that I'll try to be liberal in approving them. The ones we have to be cautious about are the highly used extensions, since we risk breaking people's workflow. A few specifics I'm aware of, that sound worth including: + Tutorials and other .svg files we ship have the dpi scaling issue, and need updated for 0.92.1 + suv mentioned an extension to provide users a workaround to some line spacing issues, iirc. + A mechanism to backup / reset prefs settings + Fixes to some strings that were found post-string freeze + A gpl3 widget needs removed (or relicensed) I'd like to avoid maintaining a bugs-needing-fixed list, but rather focus time more on patch review and testing. I figure the important thing is to get 0.92.1 out in a timely manner, and if there's still bugs needing attention we can always do a 0.92.2 some time later on. Proposed Timing: Mon Jan 2 Feature Freeze 0.92.1pre0 Mon Jan 23 Hard Freeze 0.92.1pre1 Mon Jan 30 String Freeze 0.92.1pre2 Mon Feb 6 Release Candidate 0.92.1 Fri Feb 10 Cut Release Mon Feb 13 Announcement I know we've not got a strong history of staying to schedule, but I'm going to try hard to hit these dates at least within a day or so. That means we'll have to be strict about string changes after String Freeze, and strict about any changes after the Release Candidate. This schedule allows the weekend of Feb 11-12 for prepping website changes, finalizing packages, and so on. Anything you can think of missing from this plan? Bryce

4 6

Setting extension parameter defaults from svg objects
by Trever L. Adams 27 Jan '17

27 Jan '17

I am working with an already existing extension. One of my frustrations is that it remembers the last use. The extension sets values on the svg path directly. Is there a way that the params defined in the .inx file can be loaded from those same values? Thank you. Trever

2 1

Downloads Downtime
by Martin Owens 26 Jan '17

26 Jan '17

Dear Developers, Last night at 3:22am GMT the newly fixed web server ran it's cron jobs that had not run since November. It ran the automatic updater script, which pulled in new additions to the website without migrating the database. The database table for resources was then lacking a new "owner" string field and requests to downloads failed with an Error 500. The issue was corrected with a complete database migration at 7:42am EST and the website is working within it's known parameters. Between the issue starting and the fix, there were 241 error emails sent from the web server for 44,183 actual 500 errors. (Emails are paced). Blocking 13,228 attempts to download inkscape for windows file, 6,295 attempts at an msi file and 15,937 attempts at the portable inkscape download. >From users themselves, there were 42 emails to the website administrator. 38 in English, 2 in French, 1 in Portuguese, 1 in Indonesian and 1 from Donald Duck. 40 apologetic emails were sent back to real addresses, and two emails not sent to fake reply addresses. Best regards, Martin Owens

1 0

Trunk build broken (test case involving document-rotation)
by Bryce Harrington 25 Jan '17

25 Jan '17

[==========] Running 4 tests from 1 test case. [----------] Global test environment set-up. [----------] 4 tests from AttributesTest [ RUN ] AttributesTest.SupportedKnown [ OK ] AttributesTest.SupportedKnown (2 ms) [ RUN ] AttributesTest.NameRoundTrip [ OK ] AttributesTest.NameRoundTrip (1 ms) [ RUN ] AttributesTest.ValuesAreKnown /<<BUILDDIR>>/inkscape-trunk-0.92.0+devel+15444+85~ubuntu16.10.1/testfiles/src/attributes-test.cpp:613: Failure Value of: ids[i] > 0 Actual: false Expected: true Attribute string with enum 59 {inkscape:document-rotation} not handled [ FAILED ] AttributesTest.ValuesAreKnown (4 ms) [ RUN ] AttributesTest.ValuesUnique [ OK ] AttributesTest.ValuesUnique (2 ms) [----------] 4 tests from AttributesTest (9 ms total) [----------] Global test environment tear-down [==========] 4 tests from 1 test case ran. (9 ms total) [ PASSED ] 3 tests. [ FAILED ] 1 test, listed below: [ FAILED ] AttributesTest.ValuesAreKnown 1 FAILED TEST 3/5 Test #2: color-profile-test ............... Passed 5.74 sec 4/5 Test #3: dir-util-test .................... Passed 5.73 sec Start 5: object-set-test 5/5 Test #5: object-set-test .................. Passed 0.31 sec 80% tests passed, 1 tests failed out of 5 Total Test time (real) = 6.06 sec The following tests FAILED: 1 - attributes-test (Failed) Errors while running CTest Makefile:130: recipe for target 'test' failed ----- Forwarded message from Launchpad Buildd System <noreply@...1881...> ----- Date: Wed, 25 Jan 2017 05:27:43 -0000 From: Launchpad Buildd System <noreply@...1881...> To: Bryce Harrington <bryce@...961...> Subject: [Build #11913969] amd64 build of inkscape-trunk 1:0.92.0+devel+15444+85~ubuntu16.10.1 in ubuntu yakkety RELEASE [~inkscape.dev/ubuntu/trunk] Reply-To: Launchpad Buildd System <noreply@...1881...> * Source Package: inkscape-trunk * Version: 1:0.92.0+devel+15444+85~ubuntu16.10.1 * Architecture: amd64 * Archive: ~inkscape.dev/ubuntu/trunk * Component: main * State: Failed to build * Duration: 45 minutes * Build Log: https://launchpad.net/~inkscape.dev/+archive/ubuntu/trunk/+build/11913969/+… * Builder: https://launchpad.net/builders/lgw01-42 * Source: not available If you want further information about this situation, feel free to contact a member of the Launchpad Buildd Administrators team. -- amd64 build of inkscape-trunk 1:0.92.0+devel+15444+85~ubuntu16.10.1 in ubuntu yakkety RELEASE https://launchpad.net/~inkscape.dev/+archive/ubuntu/trunk/+build/11913969 You are receiving this email because your team Inkscape Developers is the owner of this archive. ----- End forwarded message -----

2 2

Media Caching on Inkscape.org
by Martin Owens 25 Jan '17

25 Jan '17

Hi inkscapers, The inkscape website has been under stress recently. Higher load after the release mostly. But also a broken cron, failing logrotate, low disk space (in that order of knock on effect). I've fixed the cron, which fixes the logrotate and I've got a ticket out for increasing the disk space next Monday. The web server will be down for 30 minutes while I go through the process with OSUOSL. The load issue though was troubling me. Lots of media requests. I opened a ticket with Fastly, the very kind CDN service we use. They had a look at our logs and noticed that Fastly was asking if files had changed every 3 minutes. Which is a bit often. So I've set the expires to 30 days. This shouldn't effect any of the actual pages since it's just about the media / downloads. This is also one reason why uploads never use the same filename, appending -1 and etc to make them unique. So we shouldn't have an issue. But let me know if you spot anything odd or interesting. I'll keep monitoring. Best Regards, Martin Owens Website Administrator

1 0

Re: [Inkscape-devel] Google Summer of Code 2017 - Mentors?
by Krzysztof Kosiński 25 Jan '17

25 Jan '17

I can mentor too. On Jan 24, 2017 12:05, "Martin Owens" <doctormo@...400...> wrote: On Tue, 2017-01-24 at 10:35 -0800, Josh Andler wrote: > Hey All, > > The Org application period is currently open. We've had a couple > potential students already reach out. Given those two things, who is > willing and able to Mentor for our organization this year? > > I'm willing to Admin as usual, hence my bringing this up. I'm ready to do a spot of mentoring also. Thanks Josh! Martin, ------------------------------------------------------------ ------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

1 0

Google Summer of Code 2017 - Mentors?
by Josh Andler 24 Jan '17

24 Jan '17

Hey All, The Org application period is currently open. We've had a couple potential students already reach out. Given those two things, who is willing and able to Mentor for our organization this year? I'm willing to Admin as usual, hence my bringing this up. Cheers, Josh

3 2

Re: [Inkscape-devel] User Involvement Was: Post-Mortum: Line heightbug
by C R 24 Jan '17

24 Jan '17

Sounds great to me! I'll read over what we have as well again this weekend and put some thought into the content and graphics, taking into account all suggestions made here. I think a bit of humour would be great to convey a friendly and fun atmosphere to welcome contributors while not being too cheesy. :) -C On 24 Jan 2017 6:03 a.m., "brynn" <brynn@...3133...> wrote: I think that's a brilliant idea. You're right that we have written bits > along these lines in the past, which could be extracted, dusted off, and polished to be more digestible to a more modern audience. You're right that there's probably a few different "types" of people so maybe a few different pages to message in different ways would make sense. I.e. one that talks to people who could get into coding work might focus on explaining branches and patch contributions, whereas another page might come from the angle of someone who isn't AT ALL interested in coding and instead just address good non-coding ways to contribute. Another one geared for translators, another maybe for evangelists, yet another specifically focused on usability testing. Or something like that. Would you like to take a shot at extracting the existing text and roughing it into a more useful shape? I think I could contribute verbage to the pages, or link in someone to help. Bryce __________________________________________________ Yeah sure, as long as we're waiting for OSUOSL, I have time to spare. I'll have to look in the FAQ to see what's left still there. Because now that I think of it, a lot of it has been brought to the Contribute page already, and some on the Promote page. https://inkscape.org/en/contribute/ https://inkscape.org/en/contribute/promote/ Should we split those sections up, and add more to them? I think what might be missing, to address this concern, is language that perhaps is more inviting (and maybe more warm and fuzzy?) as opposed to strictly informational. I know we had a report recently, where someone thought the info about helping with the website should be on the Contribute page, rather than Promote. I originally put it on Promote, because I was thinking that's what the website does, is promote Inkscape. Plus, it made a way to break into 2 pages evenly, while all on the same page, it's too long. Anyway, maybe there's a better way to organize all that? Ok, the only thing left in the FAQ is this: https://inkscape.org/en/learn/faq/#how-communicate-effective ly-throughout-inkscape-community-and-avoid-causing-flamewar which I deliberately left there, thinking it should probably be deleted, but not wanting to make that decision alone. I think we can definitely use that first paragraph. And maybe some other parts too? Since we have the CoC, we can probably lose the flamewar part. Hhmm....I'm thinking of an introduction to the Contribute page, which contains most of that info. Section title "So, You Want to Contribute to Inkscape? Here's how to get started" More warm and fuzzy, but maybe too corny? C R, jump in with comments too :-) All best, brynn PS - another thought - Maybe the CoC could have some language for bringing new people in without saying "patches welcome"? -----Original Message----- From: Bryce Harrington Sent: Sunday, January 22, 2017 7:51 PM To: brynn Cc: C R ; inkscape-devel Subject: Re: [Inkscape-devel] User Involvement Was: Post-Mortum: Line heightbug On Sun, Jan 22, 2017 at 08:50:49AM -0700, brynn wrote: > >"Patches welcome" has become a flippant and dismissive way to say, > >"well, fix it yourself". > > Most of my experience helping Inkscape users is in forums (approx 8 > years), as opposed to the mailing list (approx 2 or 3 years). I've > never seen this suggested in a flippant or dismissive way. > > I could see a webpage....or a section of a webpage, which has kind > of a pitch or invitation. Without looking, I don't remember > specifics, but I think parts of the faq (user faq on the website) > already do this. So it could be made into a page or section of a > page. Since people have all different kind of issues, we couldn't > provide the support info. But it could include generalized support > info, along with everything else I mentioned above. And then when > we find ourselves thinking "patches welcome", we could link to it, > rather than type it all out, every time. > > Or would that be too impersonal? If the Inkscape project is known > for being a friendly community (as someone said earlier) it could be > written in sort of a warm, fuzzy way.....if that would help? Just a > thought :-) > I think that's a brilliant idea. You're right that we have written bits along these lines in the past, which could be extracted, dusted off, and polished to be more digestible to a more modern audience. You're right that there's probably a few different "types" of people so maybe a few different pages to message in different ways would make sense. I.e. one that talks to people who could get into coding work might focus on explaining branches and patch contributions, whereas another page might come from the angle of someone who isn't AT ALL interested in coding and instead just address good non-coding ways to contribute. Another one geared for translators, another maybe for evangelists, yet another specifically focused on usability testing. Or something like that. Would you like to take a shot at extracting the existing text and roughing it into a more useful shape? I think I could contribute verbage to the pages, or link in someone to help. Bryce

1 0

Re: [Inkscape-devel] Inkscape 0.92 Portable version ?
by Gord Caswell 20 Jan '17

20 Jan '17

On 18 January 2017 at 16:47, Bryce Harrington <bryce@...961...> wrote: > > > Between this, and Eduard's request for help, I'm building it right now. > > Great, thanks for tending to it. > We've built & digitally signed the portable package, ready for upload: http://download2.portableapps.com/portableapps/inkscapeportable/InkscapePor… SHA1: 9f949bf3b77f4d529673ff43d597e7827b3b327b Gord PortableApps.com

1 0

Move Wiki to Git*b
by Martin Owens 20 Jan '17

20 Jan '17

Dear developers and wiki enthusiasts, Our current wiki hosted on wiki.inkscape.org is doing ok, but is running on an old machine that the hosting provider OSUOSL would like to retire if at all possible. Since we are moving to Git*b, this is an opportunity to also move the wiki to that service. This decreases our system-admin burden and the resources we ask from osuosl. It would also say that our wiki is more of a developer/contributor focused effort, leaving user content to the website. I expect things like hackfest planning and other plumbing to continue to use a wiki system. The process of moving it would entail waiting until our code is on git*b and then convert each of the existing pages from MediaWiki syntax to Markdown syntax. A script such as this https://bitbucket.org/wikier/mw2md could be used, but testing would be needed to see what kind of output we got. For all people involved in using and editing the wiki, I'd like your thoughts on how we should manage our wiki service going forwards. Thank you all. Best Regards, Martin Owens Website Administrator Hat

9 18

Mesh Gradients Polyfill
by Jayesh Salvi 19 Jan '17

19 Jan '17

Hello, I've implemented Javascript polyfill for SVG files that have mesh gradients in them, so that they can be rendered in browsers successfully. I ported the mesh gradient rendering code from Cairo to javascript in order to do so. The code and instructions on how to use it are available at https://github.com/zectorio/mesh-gradient-js This code could be run on SVG files created in inkscape and make them renderable in browser. Please take a look. I'm looking forward to your feedback. (There are still some rough edges, as this is still a proof-of-concept thing. But the code works for examples in samples directory) Thanks, -- Jayesh

4 4

Inkscape 0.92 Portable version ?
by Marc Jeanmougin 19 Jan '17

19 Jan '17

Hi all, For previous releases, we used to ship a portable version with portableapps, but there does not seem to be such a version for 0.92. Is it an oversight? I don't know who took care of those in the past. If no one is planning to do it, we had a portableapps developer on #inkscape-devel offering to build it Thanks, -- Marc

6 7

Todays trunk : some objects lacking after reloading files
by ivan louette 18 Jan '17

18 Jan '17

Hi That's one of the the most spectacular regression I never saw in trunk : today after reloading some of my files created with yesterdays trunk version some rectangles and even some text blocks are lacking ! Of course I didn't save these files again with the new version ;-) I work with Trunk on Kubuntu 14.04 ivan

1 0

extensions handling user-units and query-all in 0.92
by Pelle Nilsson 17 Jan '17

17 Jan '17

Hi, I just joined this list because after asking about extensions and handling of dpi etc in 0.92 on the Inkscape forums and on Launchpad I got several recommendations to bring it up with you developers here instead. (I should probably have lurked here a long time to keep updated about changes happening to Inkscape before major releases. My extensions have been online since 2008.) Either I am confused about how user-units are supposed to work (and my extension is even more confused) or there is a bug in Inkscape (possibly in inkex.py?). http://www.inkscapeforum.com/viewtopic.php?f=29&t=31525 https://answers.launchpad.net/inkscape/+question/431543 https://bugs.launchpad.net/inkscape/+bug/1654907 https://www.boardgamegeek.com/thread/299033/inkscape-extensions-boardgame-d… For testing I created a rectangle in 0.91, a 1x1-inch square at -3 inches x (I only bother with the x-coordinates in the following). Inkscape UI reports that it is at -270px. If I transform it by translate(270) it ends up at x=0, as expected. It also works in 0.92. Inkscape UI now reports -288px, but still a translate(270) works as expected, so Inkscape internally correctly understands that the user-unit in this document is 1/90 inches (I confirmed by calculating svg width and viewBox that it is indeed that). But the countersheetsextension running in 0.92 on a document from 0.91 gets confused and translates things too far. If the document was created in 0.92 it works (user-units for an A4 for instance being 1mm, and it translates properly). The extension works by reading coordinates using --query-all, and I had to make a small change to even support 0.92-documents in 0.92 (see https://github.com/lifelike/countersheetsextension/commit/aa454f5117fbd457d…), but this fails on a document created in 0.91. The calculations, done using unittouu, ends up with values as if the user-units were 1/96 inches, so in the example above the extension outputs translate(288), and the rectangle is translated 18 units too far to the right. So what I think is going on is that inkex.unittouu fails to properly calculate coordinates in user-units if they do not match some of the pre-defined values, but Inkscape internally does a better job? Trying to figure out a work-around. Perhaps write my own function to calculate user-units instead of using unittouu, or somehow detecting that the document was created using 0.91 (although I guess it will still fail for documents with any other possible user-unit lengths that might exist out there?)? Or maybe I just use the API in inkex the wrong way and what I try to do should already be possible? -- /Pelle

1 0

Independente Inkscape Survey Results
by Victor Westmann 16 Jan '17

16 Jan '17

I said previously that I would publish the results on January 31st but I believe there's no need to wait that much since the answers in the survey are the same for a couple of weeks now. So, attached, is the result of the survey. If anyone needs access anything else let me know. A nice insight we can have reading the survey is that a big part of the Inkscape Community is willing to contribute to the software with $$ to foster a number of different developments. Which is great! ;-) Happy new year! --Victor Westmann

3 4

Getting to git
by Bryce Harrington 14 Jan '17

14 Jan '17

"The time has come," the Walrus said, "To talk of many things: Of shoes — and ships — and sealing-wax— Of cabbages — and kings — And why the sea is boiling hot— And whether Inkscape should switch to gitlab or github or entirely other things." At Hackfest 2015 we broached the topic of moving to git, and while recognizing it as probably inevitable, decided to take care of a few other things like switching to cmake first, and getting a release out the door, and getting going with Gtk3 and C++-11. That release is out the door, cmake is done, Gtk3 is landed in trunk, C++-11 work is under way, and so I think it's time we start on tackling git. When we last visited this discussion, there was a consensus that yes we should move to git, and that rather than self-hosting a plain git repo (ala freedesktop), we would be better to look at an integrated platform like github or gitlab. But there was not a consensus as to which of those two to pick. So the task at hand is to discuss and deliberate the two and decide which should be our focus. Both have interesting pros and cons, and I don't think the decision is clear cut. Where should we go? In github's favor is that it holds the greater mindshare. Where we to go with it we'd potentially tap into a larger community of developers, which potentially could translate into a greater level of new participation in the project. github also seems like it's received a greater amount of polish and has some feature advantages (github's CI was seen as a huge pro last time we looked). gitlab is an up-and-comer and is actively acquiring analogous features to github. A big pro for us is that gitlab is FOSS whereas gitlab is free but proprietary. With gitlab we'd also hold the option of self-hosting, which might not matter or might be a huge advantage, it's hard to say. Both services provide broadly similar functionality and user experiences. The differences between them will be small compared with the differences we'll be facing moving from bzr+launchpad. Also, migration from github to gitlab or vice versa if we change our minds doesn't look like it'd be all that difficult. Those may be the best two options but they're not the only ones we have. There's other services, and of course git can be used serverside all on its own purely as commandline, or with cgit to provide a minimal web service. -- faqs ------------------------------------------------------------------- Why the need to move from bzr? One of the reasons why we switched from svn to bzr rather than git was because it was easier to learn; these days so many people know git and don't know bzr (and probably don't care to learn bzr) that this isn't quite such an advantage any more. git is also more actively maintained than bzr, and has a far bigger ecosystem of tutorials, tools and services. We also liked the integration between bzr and the LP bug tracker -- we'll lose this, although github/gitlab provide different integration opportunities that might compensate a bit. What services would we move? What we've discussed in the past is to keep the migration limited to VCS, branch management, and code review. The issue tracking in github/gitlab is quite different from what we've grown accustomed to in LP so changing that might be too much disruption. bzr->git is the main thing we're concerned with; transition of other services can be handled on a case by case basis. How would we undertake the transition? suv made a good point today that migration of smaller codebases first can be helpful so that the learning curve can be digested in pieces rather than in one big go. So perhaps we should begin by moving some of our more peripheral bzr repos, then maybe things like the website and then 2geom, and then do inkscape last. What about people who don't yet know git? I suspect a lot of us either already know git or have been working on learning it, that this isn't an issue. However, this transition is important enough I'd be willing to propose to the board that we fund book purchases and/or other forms of training for members that might need it. When would the transition be done? We've done some initial experimentation already. I would propose as soon as we have a strong consensus for github or gitlab that we proceed with moving the board's repository, inkscape-docs, and any other small / lesser-used repositories still relevant to Inkscape. Then second in perhaps a few months migrate inkscape-web and 2geom over. Once those are complete then migrate the inkscape repository itself over, with the goal of having the migration done. I'd like to see the transition completed prior to when we start getting heavily into the 0.93 release. Let me know your thoughts, and help us drive towards a consensus for github or gitlab. Thanks, Bryce

12 28

Requesting wiki editing powers
by tiwake walter 14 Jan '17

14 Jan '17

Because bryce said so. Also because I'd like to actually start helping out one of my favorite open source projects. Cheers tiwake

3 2

Mac Video
by Jabier Arraiza 12 Jan '17

12 Jan '17

I just see, not sure if is know yet in the mailing list so share. Install Inkscape 0.92 on Mac OS with Homebrew (Latest) https://www.youtube.com/watch?v=xi5FD2LZZlY Cheers, Jabier.

1 0

Re: [Inkscape-devel] inkscape not building on zesty (17.04)
by Marc Jeanmougin 12 Jan '17

12 Jan '17

The relevant part of the log seems to be in the detection of gmock/gtest: _______________________________________________________________________ CMake Error at /usr/src/googletest/googletest/cmake/internal_utils.cmake:149 (add_library): add_library cannot create target "gmock" because another target with the same name already exists. The existing target is a static library created in source directory "/usr/src/googletest/googlemock". See documentation for policy CMP0002 for more details. Call Stack (most recent call first): /usr/src/googletest/googletest/cmake/internal_utils.cmake:172 (cxx_library_with_type) /usr/src/gmock/CMakeLists.txt:84 (cxx_library) CMake Error at /usr/src/googletest/googletest/cmake/internal_utils.cmake:149 (add_library): add_library cannot create target "gmock_main" because another target with the same name already exists. The existing target is a static library created in source directory "/usr/src/googletest/googlemock". See documentation for policy CMP0002 for more details. Call Stack (most recent call first): /usr/src/googletest/googletest/cmake/internal_utils.cmake:172 (cxx_library_with_type) /usr/src/gmock/CMakeLists.txt:89 (cxx_library) CMake Error at /usr/src/gmock/CMakeLists.txt:106 (install): install TARGETS given target "gmock" which does not exist in this directory. _______________________________________________________________________ Anyone has an idea how to fix this? -- Mc On 01/05/2017 11:11 PM, Launchpad Buildd System wrote: > > * Source Package: inkscape-trunk > * Version: 1:0.91.0+devel+15392+77~ubuntu17.04.1 > * Architecture: i386 > * Archive: ~inkscape.dev/ubuntu/trunk > * Component: main > * State: Failed to build > * Duration: 4 minutes > * Build Log: https://launchpad.net/~inkscape.dev/+archive/ubuntu/trunk/+build/11820680/+… > * Builder: https://launchpad.net/builders/lcy01-10 > * Source: not available > > > > If you want further information about this situation, feel free to > contact a member of the Launchpad Buildd Administrators team. >

2 4

Retrospective on 0.92 release
by Bryce Harrington 11 Jan '17

11 Jan '17

With 0.92.0 now in the rear-view mirror (amazingly!) it's a good time to look at places we could improve. Overall I think it went quite well. Switching build systems was a big change, and getting two year's worth of feature work stabilized is quite an achievement. Based on the feedback I'm seeing, it looks like we made a very good choice to retire our OSX packaging. I admit I was a little worried, but suv's judgment was 100% right, and as anticipated our deliberately *not* providing it is stimulating others to step in and fill the void. With 0.93 on Gtk3 it sounds like we'll have opportunities for even better OSX packages. Release management often is a tough trade-off between staying on schedule vs. delaying to allow pulling in last minute improvements. We did a fair bit of the latter, which looks like it is paying off nicely, but it did result in a quite long release cycle. I feel bad at having to say 'no' so much these last few weeks, I hope no hard feelings! But I suspect to achieve faster releases we're going to need to be more rigorous here. I would love to hear good ideas on how we could achieve that. Part of the delay was that the CMake conversion took rather longer than I had anticipated. I suppose that's the nature of volunteer projects, and is going to hold true for most big changes we need to undertake. Something we'll need to keep in mind when updating the roadmap. All that said, cmake does seem to be working out for the most part. I figure we'll need to revisit this again later (I'm starting to see some strong buzz about a build system called Meson), but should stick with cmake for the time being. We've got other big infrastructural changes pending which now need are full attention. Another big part of the delay was blocker bugs. I found this very hard to get my hands around; the issues are legitimately troublesome problems that should be resolved, but finding people able and available to work on them was tough. Unfortunately bugs are inevitable, and I worry the shift to Gtk3, C++11, and so on are destined to give rise to more. Does anyone have ideas on how we can handle things better so there are fewer blockers? Or ways to get the blockers resolved more quickly? Compared with the above two issues, the actual technical mechanics of rolling out a release are trivial, however there is significant room for improvement. Compared with other projects I do release management for, Inkscape's process is a bit too manual and has a number of extraneous steps. There are some opportunities for automation once we move to git, and simply dropping autotools/btool/etc. will eliminate having to manually edit a bunch of different files to set version numbers. In the future where there are files that require setting version numbers or whatnot, instead of adding manual steps to the release process, what I want people to do is add a configure_file() function call to our 'dist' logic that substitutes the new release version number. (I'm looking at you, .snapcraft.yml.) By now, we've done so many releases we have the release process down to a bit of a science, and we have ample checklists and todo lists. We know quite precisely what needs to be done and when. But where we ran ran into trouble was getting those tasks assigned out and completed on schedule. Thankfully, everything ended up getting done - kudos to everyone that stepped up and pitched in! But far too often they got done only after deadlines had passed; in some cases this caused schedule targets to get postponed, in other cases it caused impacts elsewhere such as translation. Mainly I blame myself - ultimately these are all failures in performing good release management. But some how or other we need to tighten all of this up if we are going to get releases out in a more timely fashion. Does anyone have suggestions or observations that could help us improve this? Finally let me say, "Great work!" Because at the end of the day we've done it - put out a solid release with some awesome features and a good deal of attention to QA. A common theme I'm seeing in comments is the huge positive impact Inkscape has made in people's lives and careers, and the 0.92 release you've created is going to enable a lot of people to do some really great things. Bryce

6 9

Re: [Inkscape-devel] Getting to git
by Bryce Harrington 11 Jan '17

11 Jan '17

----- Forwarded message from Will Entriken <fulldecent@...400...> ----- Date: Mon, 9 Jan 2017 22:04:20 -0500 From: Will Entriken <fulldecent@...400...> To: Bryce Harrington <bryce@...961...> Subject: Re: [Inkscape-devel] Getting to git] Bryce, Thanks for keeping me in the loop. I am very glad to hear about this update. And I fully expect much more participation in the project as soon as we open this floodgate. With a good amount of focus and direction, we should be able to get to 1.0.0 quickly. Here's my two cents on the GitLab / GitHub choice. GitHub is my default choice because it is the most popular and it works well enough. The largest project I contribute to there is https://github.com/chartjs/Chart.js and GitHub has no pain points in dealing with that project. I am more than happy to pick indie/non-popular choices if they are better. And if attracting developers and casual contributions is the goal then I do not think GitLab is better. More thorough discussion: * Top 10 projects of all time on GitLab: https://gitlab.com/explore/projects/starred * Top 10 projects this week on GitHub: https://github.com/trending?since=weekly * Random projects I started: https://github.com/fulldecent?language=&page=2&q=&tab=repositories&type=sou… Projects got more exposure (measured in stars) this week on GitHub than the whole history of GitLab. And my random pet projects (which are way less notable than Inkscape) would rank displace the #1, #2 and #6 projects on GitLab. Therefore I think Inkscape would be a big fish in a small pond there. Please feel free to copy this to the mailing list. Thank you, Will William Entriken 267-738-4201 On Fri, Jan 6, 2017 at 2:32 PM, Bryce Harrington <bryce@...961...> wrote: > Hi fulldecent, > > I know you've been very active in maintaining the Inkscape mirror on > github. You'll be pleased to hear the project is finally getting around > to its git migration planning. > > We're debating gitlab vs. github as our way forward, and while we're > still pretty early in discussion currently consensus appears to be > favoring gitlab. I'd like to make sure we loop you in (and any others > you've worked with on the github mirror) to make sure we have plenty of > input and information before reaching any decisions. > > Feel free to either chime in on the mailing list with your thoughts, or > just reply to me and I'll pass them along. > > Thanks, > Bryce > > ----- Forwarded message from Bryce Harrington <bryce@...961...> ----- > > Date: Fri, 6 Jan 2017 11:21:28 -0800 > From: Bryce Harrington <bryce@...961...> > To: Ted Gould <ted@...11...> > Cc: inkscape-devel(a)lists.sourceforge.net > Subject: Re: [Inkscape-devel] Getting to git > > On Fri, Jan 06, 2017 at 08:56:50AM -0600, Ted Gould wrote: >> I think where this mindshare comes into play is less with drive-by >> contributions as much as integrations with other services. There are a >> lot of cool tools built that "just work" with Github. Some only support >> that as a backend (even though they probably just grab git and work on >> it, they just don't have an option in the UI) What I'm not sure about >> is whether we'd end up using any of those services anyway. > > True, good points. And yeah, most of the services I actually have in > mind for us just require git, so should work equally well regardless of > what we pick. > > I've used both gitlab and github for medium-sized projects, and found > them both to be usable and performant. Inkscape is larger and more > complex, but so far I haven't seen any reason that either of those > options wouldn't do the basic job as well as the other. > >> > We also liked the integration between >> > bzr and the LP bug tracker -- we'll lose this, although github/gitlab >> > provide different integration opportunities that might compensate a >> > bit. >> >> Since the last time we've discussed it LP's Git features have matured a >> lot. I don't think that they're on par with Github/Gitlab yet, but we >> should probably put into consideration just moving to Git and sticking >> with LP, as it might be a simpler transition. > > You're right it should be included as an option. If nothing else it has > familiarity and inertia to change working in its favor. I'm not sure > how compelling a case can be made for it beyond that though. > > A large chunk of our transition pain will be developers adapting to git, > and we'll have that regardless of any of the options. The other chunk > is the web interface and I suppose there's some advantage with Launchpad > of sticking with the familiar. > > However, Launchpad has remained understaffed for years, and > unfortunately it really shows. The chances of reaching parity with > github/gitlab seem slim to none. And once their development attention > moves on to the next feature development effort, ongoing maintenance of > the service is going to become an issue, as it already has in so many > other places. > > Like gitlab, launchpad is open source. I've contributed LP code > myself. I don't know if we're likely to invest development energy here, > but both gitlab and LP seem on the same level here. gitlab seems to > have a more active development community though. > >> > Let me know your thoughts, and help us drive towards a consensus for >> > github or gitlab. >> >> For me, right now, my feelings are towards Gitlab. I think that we >> should stick with a FOSS solution overall and Github doesn't have >> enough advantages to override that. > > There was a ticket on our github account with people pushing for github > adoption. I'll touch base with them to gather their input, but at this > point I agree with you it seems gitlab is looking the better option for > Inkscape. > > Bryce > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > > ----- End forwarded message ----- ----- End forwarded message -----

5 5

[Fwd: Announcing new project]
by Bryce Harrington 10 Jan '17

10 Jan '17

In honor of our recent release, I thought some of you might be interested in seeing the email that initiated this project... ----- Forwarded message from Bryce Harrington <bryce@...1...> ----- Date: Wed, 5 Nov 2003 23:16:25 -0800 (PST) From: Bryce Harrington <bryce@...1...> To: sodipodi-list(a)lists.sourceforge.net Subject: [Sodipodi-list] Announcing new project Nathan, mental, Ted and myself have decided to embark on our own direction with the Sodipodi codebase. We have attempted to do this as part of the Sodipodi project, but we believe we need to try out a new project structure to have the freedom to be able to explore some approaches radically different from Sodipodi. We have recently reworked the Sodipodi codebase to build with a C++ compiler and renamed it 'Inkscape'. We have also set up a project on Sourceforge and established a new website at http://www.inkscape.org. Our goal is the creation of a fully SVG-compliant 2D graphics editor: * Full SVG (plus XML, CSS2) compliance * Core written in C++ * Gtk-based user interface following the standards set out in the GNOME HIG * Emphasis on a small core plus modular extensions for features (a la Mozilla Firebird) * Open, community-oriented development processes that welcomes experimentation * Baseline is the Sodipodi-Hydra codebase * Removal of dead code We are aiming specifically for a general purpose XML/SVG graphics editor, and as a consequence will emphasize features that tend to fall outside the Sodipodi target userbase. We would like to welcome anyone who'd like to do some experimentation to participate with us. Subscribe at http://lists.sourceforge.net/lists/listinfo/inkscape-devel We also intend to seek use of third-party libraries in preference to custom code (where reasonable); specifically, we are exploring Cairo (formerly Xr), libcroco, Pango, the core Gtk widgets, but also other existing and widespread facilities. The extension architecture is partly intended to minimize library dependencies in the core. _______________________________________________ Sodipodi-list mailing list Sodipodi-list(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/sodipodi-list ----- End forwarded message -----

4 3

Inkscape 0.92 crashes on macOS Sierra 10.12.2
by Andreas Unterkircher 10 Jan '17

10 Jan '17

Hello, I installed Inkscape on macOS Sierra 10.12.2 using mac ports sudo port install inkscape +quartz now I have port installed inkscape The following ports are currently installed: inkscape @0.92.0_0+quartz (active) when launching Inkscape I get the below error. Should I open a ticket or is this a known problem? Thanks for any help! Best regards, Andreas inkscape 2017-01-06 23:23:09.511 inkscape[15716:580274] *** WARNING: Method userSpaceScaleFactor in class NSView is deprecated on 10.7 and later. It should not be used in new applications. Use convertRectToBacking: instead. Emergency save activated! Emergency save completed. Inkscape will close now. If you can reproduce this crash, please file a bug at www.inkscape.org with a detailed description of the steps leading to the crash, so we can fix it. (inkscape:15745): Gtk-WARNING **: ChannelsAction: missing action ChannelsAction (inkscape:15745): Gtk-WARNING **: ThresholdAction: missing action ThresholdAction (inkscape:15745): Gtk-WARNING **: OffsetAction: missing action OffsetAction (inkscape:15745): Gtk-WARNING **: PaintbucketUnitsAction: missing action PaintbucketUnitsAction (inkscape:15745): Gtk-WARNING **: AutoGapAction: missing action AutoGapAction (inkscape:15745): Gtk-WARNING **: PaintbucketResetAction: missing action PaintbucketResetAction (inkscape:15745): Gtk-WARNING **: TextFontFamilyAction: missing action TextFontFamilyAction (inkscape:15745): Gtk-WARNING **: TextFontStyleAction: missing action TextFontStyleAction (inkscape:15745): Gtk-WARNING **: TextOuterStyleAction: missing action TextOuterStyleAction (inkscape:15745): Gtk-WARNING **: TextFontSizeAction: missing action TextFontSizeAction (inkscape:15745): Gtk-WARNING **: TextLineHeightAction: missing action TextLineHeightAction (inkscape:15745): Gtk-WARNING **: TextLineHeightUnitsAction: missing action TextLineHeightUnitsAction (inkscape:15745): Gtk-WARNING **: TextLineHeightUnsetAction: missing action TextLineHeightUnsetAction (inkscape:15745): Gtk-WARNING **: TextAlignAction: missing action TextAlignAction (inkscape:15745): Gtk-WARNING **: TextSuperscriptAction: missing action TextSuperscriptAction (inkscape:15745): Gtk-WARNING **: TextSubscriptAction: missing action TextSubscriptAction (inkscape:15745): Gtk-WARNING **: TextLetterSpacingAction: missing action TextLetterSpacingAction (inkscape:15745): Gtk-WARNING **: TextWordSpacingAction: missing action TextWordSpacingAction (inkscape:15745): Gtk-WARNING **: TextDxAction: missing action TextDxAction (inkscape:15745): Gtk-WARNING **: TextDyAction: missing action TextDyAction (inkscape:15745): Gtk-WARNING **: TextRotationAction: missing action TextRotationAction (inkscape:15745): Gtk-WARNING **: TextWritingModeAction: missing action TextWritingModeAction (inkscape:15745): Gtk-WARNING **: TextOrientationAction: missing action TextOrientationAction (inkscape:15745): Gtk-WARNING **: GradientNewTypeAction: missing action GradientNewTypeAction (inkscape:15745): Gtk-WARNING **: GradientNewFillStrokeAction: missing action GradientNewFillStrokeAction (inkscape:15745): Gtk-WARNING **: GradientSelectGradientAction: missing action GradientSelectGradientAction (inkscape:15745): Gtk-WARNING **: GradientEditLinkAction: missing action GradientEditLinkAction (inkscape:15745): Gtk-WARNING **: GradientEditReverseAction: missing action GradientEditReverseAction (inkscape:15745): Gtk-WARNING **: GradientSelectRepeatAction: missing action GradientSelectRepeatAction (inkscape:15745): Gtk-WARNING **: GradientEditStopsAction: missing action GradientEditStopsAction (inkscape:15745): Gtk-WARNING **: GradientEditOffsetAction: missing action GradientEditOffsetAction (inkscape:15745): Gtk-WARNING **: GradientEditAddAction: missing action GradientEditAddAction (inkscape:15745): Gtk-WARNING **: GradientEditDeleteAction: missing action GradientEditDeleteAction (inkscape:15745): Gtk-WARNING **: MeshNewTypeAction: missing action MeshNewTypeAction (inkscape:15745): Gtk-WARNING **: MeshNewFillStrokeAction: missing action MeshNewFillStrokeAction (inkscape:15745): Gtk-WARNING **: MeshRowAction: missing action MeshRowAction (inkscape:15745): Gtk-WARNING **: MeshColumnAction: missing action MeshColumnAction (inkscape:15745): Gtk-WARNING **: MeshToggleSidesAction: missing action MeshToggleSidesAction (inkscape:15745): Gtk-WARNING **: MeshMakeEllipticalAction: missing action MeshMakeEllipticalAction (inkscape:15745): Gtk-WARNING **: MeshPickColorsAction: missing action MeshPickColorsAction (inkscape:15745): Gtk-WARNING **: MeshFitInBoundingBoxAction: missing action MeshFitInBoundingBoxAction (inkscape:15745): Gtk-WARNING **: MeshShowHandlesAction: missing action MeshShowHandlesAction (inkscape:15745): Gtk-WARNING **: MeshEditFillAction: missing action MeshEditFillAction (inkscape:15745): Gtk-WARNING **: MeshEditStrokeAction: missing action MeshEditStrokeAction (inkscape:15745): Gtk-WARNING **: MeshWarningAction: missing action MeshWarningAction (inkscape:15745): Gtk-WARNING **: MeshSmoothAction: missing action MeshSmoothAction (inkscape:15745): Gtk-WARNING **: DropperOpacityAction: missing action DropperOpacityAction (inkscape:15745): Gtk-WARNING **: DropperPickAlphaAction: missing action DropperPickAlphaAction (inkscape:15745): Gtk-WARNING **: DropperSetAlphaAction: missing action DropperSetAlphaAction (inkscape:15745): Gtk-WARNING **: ConnectorAvoidAction: missing action ConnectorAvoidAction (inkscape:15745): Gtk-WARNING **: ConnectorIgnoreAction: missing action ConnectorIgnoreAction (inkscape:15745): Gtk-WARNING **: ConnectorOrthogonalAction: missing action ConnectorOrthogonalAction (inkscape:15745): Gtk-WARNING **: ConnectorCurvatureAction: missing action ConnectorCurvatureAction (inkscape:15745): Gtk-WARNING **: ConnectorSpacingAction: missing action ConnectorSpacingAction (inkscape:15745): Gtk-WARNING **: ConnectorGraphAction: missing action ConnectorGraphAction (inkscape:15745): Gtk-WARNING **: ConnectorLengthAction: missing action ConnectorLengthAction (inkscape:15745): Gtk-WARNING **: ConnectorDirectedAction: missing action ConnectorDirectedAction (inkscape:15745): Gtk-WARNING **: ConnectorOverlapAction: missing action ConnectorOverlapAction Segmentation fault: 11 Here’s the problem report generated: Process: inkscape [15745] Path: /opt/local/bin/inkscape Identifier: inkscape Version: 0 Code Type: X86-64 (Native) Parent Process: bash [498] Responsible: inkscape [15745] User ID: 501 Date/Time: 2017-01-06 23:25:56.602 +0100 OS Version: Mac OS X 10.12.2 (16C67) Report Version: 12 Anonymous UUID: FE58439A-D8EA-56D9-19CA-D508DC350E52 Time Awake Since Boot: 2800 seconds System Integrity Protection: enabled Crashed Thread: 0 Dispatch queue: com.apple.main-thread Exception Type: EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Termination Signal: Segmentation fault: 11 Termination Reason: Namespace SIGNAL, Code 0xb Terminating Process: exc handler [0] VM Regions Near 0: --> __TEXT 0000000108d18000-00000001096ab000 [ 9804K] r-x/rwx SM=COW /opt/local/bin/inkscape Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libsystem_c.dylib 0x00007fffa41750f3 _UTF8_mbsnrtowcs + 287 1 libsystem_c.dylib 0x00007fffa416ff02 __collate_mbstowcs + 123 2 libsystem_c.dylib 0x00007fffa419979c strcoll_l + 76 3 libglib-2.0.0.dylib 0x000000010ba90f99 g_utf8_collate + 105 4 inkscape 0x0000000108f9ed33 font_factory::GetUIStyles(_PangoFontFamily*) + 221 5 inkscape 0x0000000108fa4488 Inkscape::FontLister::update_font_list(SPDocument*) + 1490 6 inkscape 0x00000001090cc6cc sp_text_toolbox_prep(SPDesktop*, _GtkActionGroup*, _GObject*) + 156 7 inkscape 0x00000001090d5f25 setup_aux_toolbox(_GtkWidget*, SPDesktop*) + 435 8 inkscape 0x00000001090d5a44 Inkscape::UI::ToolboxFactory::setToolboxDesktop(_GtkWidget*, SPDesktop*) + 518 9 inkscape 0x000000010910371f Inkscape::UI::UXManagerImpl::connectToDesktop(std::__1::vector<_GtkWidget*, std::__1::allocator<_GtkWidget*> > const&, SPDesktop*) + 201 10 inkscape 0x000000010907bac8 SPDesktopWidget::createInstance(SPNamedView*) + 794 11 inkscape 0x000000010907b795 sp_desktop_widget_new(SPNamedView*) + 11 12 inkscape 0x0000000108d6597f sp_file_new(std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> > const&) + 223 13 inkscape 0x0000000108d65c89 sp_file_new_default() + 49 14 inkscape 0x0000000108d27cba sp_main_gui(int, char const**) + 929 15 libdyld.dylib 0x00007fffa4108255 start + 1 Thread 1: 0 libsystem_kernel.dylib 0x00007fffa4236c86 __psynch_cvwait + 10 1 libsystem_pthread.dylib 0x00007fffa432096a _pthread_cond_wait + 712 2 libgc.1.dylib 0x0000000109d2c452 GC_wait_marker + 23 3 libgc.1.dylib 0x0000000109d24408 GC_help_marker + 58 4 libgc.1.dylib 0x0000000109d2aef6 GC_mark_thread + 137 5 libsystem_pthread.dylib 0x00007fffa431faab _pthread_body + 180 6 libsystem_pthread.dylib 0x00007fffa431f9f7 _pthread_start + 286 7 libsystem_pthread.dylib 0x00007fffa431f1fd thread_start + 13 Thread 2: 0 libsystem_kernel.dylib 0x00007fffa4236c86 __psynch_cvwait + 10 1 libsystem_pthread.dylib 0x00007fffa432096a _pthread_cond_wait + 712 2 libgc.1.dylib 0x0000000109d2c452 GC_wait_marker + 23 3 libgc.1.dylib 0x0000000109d24408 GC_help_marker + 58 4 libgc.1.dylib 0x0000000109d2aef6 GC_mark_thread + 137 5 libsystem_pthread.dylib 0x00007fffa431faab _pthread_body + 180 6 libsystem_pthread.dylib 0x00007fffa431f9f7 _pthread_start + 286 7 libsystem_pthread.dylib 0x00007fffa431f1fd thread_start + 13 Thread 3: 0 libsystem_kernel.dylib 0x00007fffa4236c86 __psynch_cvwait + 10 1 libsystem_pthread.dylib 0x00007fffa432096a _pthread_cond_wait + 712 2 libgc.1.dylib 0x0000000109d2c452 GC_wait_marker + 23 3 libgc.1.dylib 0x0000000109d24408 GC_help_marker + 58 4 libgc.1.dylib 0x0000000109d2aef6 GC_mark_thread + 137 5 libsystem_pthread.dylib 0x00007fffa431faab _pthread_body + 180 6 libsystem_pthread.dylib 0x00007fffa431f9f7 _pthread_start + 286 7 libsystem_pthread.dylib 0x00007fffa431f1fd thread_start + 13 Thread 4: 0 libsystem_kernel.dylib 0x00007fffa4236c86 __psynch_cvwait + 10 1 libsystem_pthread.dylib 0x00007fffa432096a _pthread_cond_wait + 712 2 libgc.1.dylib 0x0000000109d2c452 GC_wait_marker + 23 3 libgc.1.dylib 0x0000000109d24408 GC_help_marker + 58 4 libgc.1.dylib 0x0000000109d2aef6 GC_mark_thread + 137 5 libsystem_pthread.dylib 0x00007fffa431faab _pthread_body + 180 6 libsystem_pthread.dylib 0x00007fffa431f9f7 _pthread_start + 286 7 libsystem_pthread.dylib 0x00007fffa431f1fd thread_start + 13 Thread 5: 0 libsystem_kernel.dylib 0x00007fffa4236c86 __psynch_cvwait + 10 1 libsystem_pthread.dylib 0x00007fffa432096a _pthread_cond_wait + 712 2 libgc.1.dylib 0x0000000109d2c452 GC_wait_marker + 23 3 libgc.1.dylib 0x0000000109d24408 GC_help_marker + 58 4 libgc.1.dylib 0x0000000109d2aef6 GC_mark_thread + 137 5 libsystem_pthread.dylib 0x00007fffa431faab _pthread_body + 180 6 libsystem_pthread.dylib 0x00007fffa431f9f7 _pthread_start + 286 7 libsystem_pthread.dylib 0x00007fffa431f1fd thread_start + 13 Thread 6: 0 libsystem_kernel.dylib 0x00007fffa4236c86 __psynch_cvwait + 10 1 libsystem_pthread.dylib 0x00007fffa432096a _pthread_cond_wait + 712 2 libgc.1.dylib 0x0000000109d2c452 GC_wait_marker + 23 3 libgc.1.dylib 0x0000000109d24408 GC_help_marker + 58 4 libgc.1.dylib 0x0000000109d2aef6 GC_mark_thread + 137 5 libsystem_pthread.dylib 0x00007fffa431faab _pthread_body + 180 6 libsystem_pthread.dylib 0x00007fffa431f9f7 _pthread_start + 286 7 libsystem_pthread.dylib 0x00007fffa431f1fd thread_start + 13 Thread 7: 0 libsystem_kernel.dylib 0x00007fffa4236c86 __psynch_cvwait + 10 1 libsystem_pthread.dylib 0x00007fffa432096a _pthread_cond_wait + 712 2 libgc.1.dylib 0x0000000109d2c452 GC_wait_marker + 23 3 libgc.1.dylib 0x0000000109d24408 GC_help_marker + 58 4 libgc.1.dylib 0x0000000109d2aef6 GC_mark_thread + 137 5 libsystem_pthread.dylib 0x00007fffa431faab _pthread_body + 180 6 libsystem_pthread.dylib 0x00007fffa431f9f7 _pthread_start + 286 7 libsystem_pthread.dylib 0x00007fffa431f1fd thread_start + 13 Thread 8: 0 libsystem_kernel.dylib 0x00007fffa42374e2 __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fffa431f791 _pthread_wqthread + 1426 2 libsystem_pthread.dylib 0x00007fffa431f1ed start_wqthread + 13 Thread 9: 0 libsystem_kernel.dylib 0x00007fffa42374e2 __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fffa431f791 _pthread_wqthread + 1426 2 libsystem_pthread.dylib 0x00007fffa431f1ed start_wqthread + 13 Thread 10: 0 libsystem_kernel.dylib 0x00007fffa42374e2 __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fffa431f791 _pthread_wqthread + 1426 2 libsystem_pthread.dylib 0x00007fffa431f1ed start_wqthread + 13 Thread 11: 0 libsystem_kernel.dylib 0x00007fffa4237e2a kevent + 10 1 libgio-2.0.0.dylib 0x000000010b94cd8f _kqueue_thread_func + 168 2 libsystem_pthread.dylib 0x00007fffa431faab _pthread_body + 180 3 libsystem_pthread.dylib 0x00007fffa431f9f7 _pthread_start + 286 4 libsystem_pthread.dylib 0x00007fffa431f1fd thread_start + 13 Thread 12: 0 libsystem_kernel.dylib 0x00007fffa42374e2 __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fffa431f791 _pthread_wqthread + 1426 2 libsystem_pthread.dylib 0x00007fffa431f1ed start_wqthread + 13 Thread 13: 0 libsystem_pthread.dylib 0x00007fffa431f1e0 start_wqthread + 0 1 ??? 0x00007f8ad710bab0 0 + 140234290412208 Thread 14: 0 libsystem_kernel.dylib 0x00007fffa42374e2 __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fffa431f791 _pthread_wqthread + 1426 2 libsystem_pthread.dylib 0x00007fffa431f1ed start_wqthread + 13 Thread 15: 0 libsystem_kernel.dylib 0x00007fffa42374e2 __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fffa431f791 _pthread_wqthread + 1426 2 libsystem_pthread.dylib 0x00007fffa431f1ed start_wqthread + 13 Thread 16: 0 libsystem_kernel.dylib 0x00007fffa42374e2 __workq_kernreturn + 10 1 libsystem_pthread.dylib 0x00007fffa431f5fe _pthread_wqthread + 1023 2 libsystem_pthread.dylib 0x00007fffa431f1ed start_wqthread + 13 Thread 17: 0 libsystem_kernel.dylib 0x00007fffa4236c86 __psynch_cvwait + 10 1 libsystem_pthread.dylib 0x00007fffa432096a _pthread_cond_wait + 712 2 libgdk-quartz-2.0.0.dylib 0x000000010ab3e76e select_thread_func + 228 3 libsystem_pthread.dylib 0x00007fffa431faab _pthread_body + 180 4 libsystem_pthread.dylib 0x00007fffa431f9f7 _pthread_start + 286 5 libsystem_pthread.dylib 0x00007fffa431f1fd thread_start + 13 Thread 0 crashed with X86 Thread State (64-bit): rax: 0x0000000000000001 rbx: 0x00007fffacf386b8 rcx: 0x0000000000000000 rdx: 0xffffffffffffffff rdi: 0x0000000000000000 rsi: 0x00007fff56ee6c40 rbp: 0x00007fff56ee6c30 rsp: 0x00007fff56ee6be0 r8: 0x00007fff56ee6c50 r9: 0x00007fffacf386b8 r10: 0x00007f8ad14209b0 r11: 0x00007fffa4174fd4 r12: 0x0000000000000000 r13: 0xffffffffffffffff r14: 0x0000000000000000 r15: 0x00007fffacf386b8 rip: 0x00007fffa41750f3 rfl: 0x0000000000010286 cr2: 0x0000000000000000 Logical CPU: 0 Error Code: 0x00000004 Trap Number: 14 Binary Images: 0x108d18000 - 0x1096aaff7 +inkscape (0) <0B0E2418-1C75-34B4-BBB1-37F39CD03229> /opt/local/bin/inkscape 0x109d0d000 - 0x109d13fff +libgtkspell.0.dylib (0) <963CBE7F-C39B-37B9-9644-87BAB89D96FA> /opt/local/lib/libgtkspell.0.dylib 0x109d19000 - 0x109d2ffff +libgc.1.dylib (0) <EAF1C037-5DF0-3C00-BE01-60591FB6E893> /opt/local/lib/libgc.1.dylib 0x109d70000 - 0x109d73fff +libgmodule-2.0.0.dylib (0) <F465B882-F777-35FE-8E7F-376531BF5F58> /opt/local/lib/libgmodule-2.0.0.dylib 0x109d7c000 - 0x109eeffff +libgsl.19.dylib (0) <06E8A6A4-27BC-39C5-AAEA-32DA76FBBBDF> /opt/local/lib/libgsl.19.dylib 0x109f62000 - 0x109f95ff7 +libgslcblas.0.dylib (0) <F0ABEEF7-3B5C-3E24-8D22-373300803D50> /opt/local/lib/libgslcblas.0.dylib 0x109f9f000 - 0x109fa1fff +libgthread-2.0.0.dylib (0) <A2B30F65-A6B0-3C7F-A954-6B73E427718A> /opt/local/lib/libgthread-2.0.0.dylib 0x109fa6000 - 0x109fc9ff3 +libpng16.16.dylib (0) <DC288255-07B4-34C2-9735-4A16D3B3792C> /opt/local/lib/libpng16.16.dylib 0x109fd8000 - 0x10a002ff3 +libxslt.1.dylib (0) <43FEABE0-538E-39D1-8C2B-6C8585F14FB9> /opt/local/lib/libxslt.1.dylib 0x10a010000 - 0x10a02cff3 +liblzma.5.dylib (0) <232F1F35-6EC0-3FF4-A104-90DEE9724ACB> /opt/local/lib/liblzma.5.dylib 0x10a033000 - 0x10a127ff7 +libiconv.2.dylib (0) <D1DF370F-D618-3944-9662-67D25BDADA0F> /opt/local/lib/libiconv.2.dylib 0x10a13a000 - 0x10a22bfff +libxml2.2.dylib (0) <EF957A1C-6B0E-326D-9D76-33898B2EF784> /opt/local/lib/libxml2.2.dylib 0x10a25f000 - 0x10a26bfff +libpangoft2-1.0.0.dylib (0) <C5B6C56F-BDBD-3897-A7C0-839FD61C14F6> /opt/local/lib/libpangoft2-1.0.0.dylib 0x10a279000 - 0x10a2a6fff +libfontconfig.1.dylib (0) <DE093687-39B5-35CD-AB83-EB57D2CCD3BD> /opt/local/lib/libfontconfig.1.dylib 0x10a2b9000 - 0x10a2c9ffb +libz.1.dylib (0) <E1B45832-9F60-33FC-B542-FD079195106F> /opt/local/lib/libz.1.dylib 0x10a2ce000 - 0x10a2d6ffb +libpopt.0.dylib (0) <57A10603-94D9-3D78-9F67-BEA27556D1CC> /opt/local/lib/libpopt.0.dylib 0x10a2db000 - 0x10a32cff7 +libaspell.15.dylib (0) <1843FDB5-067C-392C-BE1A-3DD027483EF9> /opt/local/lib/libaspell.15.dylib 0x10a361000 - 0x10a465ff7 +libgtkmm-2.4.1.dylib (0) <DA190254-F85F-32AB-AF10-2CD44072C5E4> /opt/local/lib/libgtkmm-2.4.1.dylib 0x10a685000 - 0x10a6a4ffb +libatkmm-1.6.1.dylib (0) <3B45BCE5-6EBB-316D-994D-5451D839C8BE> /opt/local/lib/libatkmm-1.6.1.dylib 0x10a6d1000 - 0x10a6efffb +libgdkmm-2.4.1.dylib (0) <7596A77A-4391-350B-A5F7-32E84DA2CBF8> /opt/local/lib/libgdkmm-2.4.1.dylib 0x10a724000 - 0x10a732ffb +libpangomm-1.4.1.dylib (0) <95550A27-7E76-324D-AA80-1CBF9680E668> /opt/local/lib/libpangomm-1.4.1.dylib 0x10a755000 - 0x10aa3dffb +libgtk-quartz-2.0.0.dylib (0) <B36A9F83-B166-32AE-AC7F-94981FF59E45> /opt/local/lib/libgtk-quartz-2.0.0.dylib 0x10ab0a000 - 0x10ab74ff7 +libgdk-quartz-2.0.0.dylib (0) <EECF97AE-D2CA-333B-BE7C-ADFECFACDF57> /opt/local/lib/libgdk-quartz-2.0.0.dylib 0x10ab9e000 - 0x10ababffb +libpangocairo-1.0.0.dylib (0) <31D121A5-A4CC-3D7A-8836-9ECEA0FBEB24> /opt/local/lib/libpangocairo-1.0.0.dylib 0x10abbe000 - 0x10abeffff +libpango-1.0.0.dylib (0) <DCA953E8-DE6C-3B7B-90FA-5E3222D78B12> /opt/local/lib/libpango-1.0.0.dylib 0x10ac03000 - 0x10ac18ff7 +libatk-1.0.0.dylib (0) <03C99828-9087-3686-ACAA-296A1755A8AA> /opt/local/lib/libatk-1.0.0.dylib 0x10ac2b000 - 0x10ac41ff7 +libgdk_pixbuf-2.0.0.dylib (0) <F90264A7-699D-32EA-856E-48ECDF2DE9B8> /opt/local/lib/libgdk_pixbuf-2.0.0.dylib 0x10ac4c000 - 0x10ac5aff3 +libcairomm-1.0.1.dylib (0) <599010A5-EB53-3629-8F0E-338AD143E47C> /opt/local/lib/libcairomm-1.0.1.dylib 0x10ac74000 - 0x10ad18ff3 +libgiomm-2.4.1.dylib (0) <A9846A67-656D-3CC9-9B44-A63153573AEE> /opt/local/lib/libgiomm-2.4.1.dylib 0x10ae0c000 - 0x10ae3bfff +libglibmm-2.4.1.dylib (0) <1C8EB235-663F-30AD-8A87-120B2075D0A0> /opt/local/lib/libglibmm-2.4.1.dylib 0x10ae8a000 - 0x10ae8cff3 +libsigc-2.0.0.dylib (0) <7B4F6C59-7077-350C-BCB5-11BA4E0D8EED> /opt/local/lib/libsigc-2.0.0.dylib 0x10ae95000 - 0x10aeb1fff +libexif.12.dylib (0) <CFE7396E-5977-30A7-8AA7-61CB8A5AACDC> /opt/local/lib/libexif.12.dylib 0x10aed6000 - 0x10af51fff +libfreetype.6.dylib (0) <C7F1B2AA-2FCE-3577-B3C5-7F3DA8E96259> /opt/local/lib/libfreetype.6.dylib 0x10af70000 - 0x10af82ffb +libwpg-0.3.3.dylib (0) <749F6414-3997-32A2-A938-4109D02EA8D6> /opt/local/lib/libwpg-0.3.3.dylib 0x10af91000 - 0x10aff2ff3 +libvisio-0.1.1.dylib (0) <1E591CE5-9D70-33EB-8CC2-975FD1DC9E7F> /opt/local/lib/libvisio-0.1.1.dylib 0x10b03a000 - 0x10b0bbfff +libcdr-0.1.1.dylib (0) <2B912E31-337D-3483-9BB5-6B66B5EBA2FD> /opt/local/lib/libcdr-0.1.1.dylib 0x10b0e9000 - 0x10b104ff7 +librevenge-0.0.0.dylib (0) <F0AE89DA-A59C-3E00-A5EA-8BC435B6F733> /opt/local/lib/librevenge-0.0.0.dylib 0x10b121000 - 0x10b134fff +librevenge-stream-0.0.0.dylib (0) <BDCCF266-8151-3373-A687-3F601CEC88BF> /opt/local/lib/librevenge-stream-0.0.0.dylib 0x10b147000 - 0x10b15effb +libdbus-glib-1.2.dylib (0) <0C976455-856E-30BF-A94A-0A85141FF519> /opt/local/lib/libdbus-glib-1.2.dylib 0x10b16d000 - 0x10b19bffb +libdbus-1.3.dylib (0) <AE40FDCA-D8DF-3325-9CDC-375B3BAA01A0> /opt/local/lib/libdbus-1.3.dylib 0x10b1ae000 - 0x10b1dbffb +libMagick++-6.Q16.6.dylib (0) <8D0065C9-E3AD-3A6A-9E5D-82E50426932F> /opt/local/lib/libMagick++-6.Q16.6.dylib 0x10b22f000 - 0x10b351fff +libMagickWand-6.Q16.2.dylib (0) <BC13C622-9E62-32B2-B7E7-6C5A141BBFEF> /opt/local/lib/libMagickWand-6.Q16.2.dylib 0x10b36f000 - 0x10b527ff7 +libMagickCore-6.Q16.2.dylib (0) <82B3B54B-9305-354C-BD7A-78AC6D1D65FD> /opt/local/lib/libMagickCore-6.Q16.2.dylib 0x10b5c0000 - 0x10b5ecff3 +libjpeg.9.dylib (0) <252D7EA9-5071-3C24-B3BE-88CD58FFBBB6> /opt/local/lib/libjpeg.9.dylib 0x10b5f6000 - 0x10b5fcfff +libpotrace.0.dylib (0) <6D642C12-0C63-3FA4-8EB6-736AAFC80453> /opt/local/lib/libpotrace.0.dylib 0x10b600000 - 0x10b637ff7 +liblcms2.2.dylib (0) <4A6F1AC7-5494-3B27-9447-B0883941FBDA> /opt/local/lib/liblcms2.2.dylib 0x10b64e000 - 0x10b788ffb +libpoppler.66.dylib (0) <EA5CF570-8A3B-3D3A-ACBD-A78CFEA82132> /opt/local/lib/libpoppler.66.dylib 0x10b832000 - 0x10b85efff +libpoppler-glib.8.dylib (0) <D13F4C68-4E26-3FB7-897B-EEB36EA2E496> /opt/local/lib/libpoppler-glib.8.dylib 0x10b886000 - 0x10b982fff +libgio-2.0.0.dylib (0) <811B642B-1423-3FF7-92B1-0E8941D34418> /opt/local/lib/libgio-2.0.0.dylib 0x10b9f6000 - 0x10ba27ffb +libgobject-2.0.0.dylib (0) <B0E21887-A95F-36AE-85FE-BE92F161ACA9> /opt/local/lib/libgobject-2.0.0.dylib 0x10ba3a000 - 0x10bb03ffb +libglib-2.0.0.dylib (0) <4023889F-A206-3281-A947-1CBB511ABAB1> /opt/local/lib/libglib-2.0.0.dylib 0x10bb2f000 - 0x10bb37ff3 +libintl.8.dylib (0) <34C7A792-8F97-3B47-BE05-892044CF0A65> /opt/local/lib/libintl.8.dylib 0x10bb3e000 - 0x10bbf8fff +libcairo.2.dylib (0) <FD7FB725-07C2-3880-B89A-53995641A60E> /opt/local/lib/libcairo.2.dylib 0x10bc2a000 - 0x10bc30fff +libenchant.1.dylib (0) <1726CABA-767E-3F5E-991A-613B1BB7D1A5> /opt/local/lib/libenchant.1.dylib 0x10bc38000 - 0x10bc80fff +libharfbuzz.0.dylib (0) <8ACB9D5C-2519-3092-9092-B1094C37228B> /opt/local/lib/libharfbuzz.0.dylib 0x10bc99000 - 0x10bd00ffb +libpcre.1.dylib (0) <CE0F57F2-6296-3D0C-84E5-71000D9BBC8E> /opt/local/lib/libpcre.1.dylib 0x10bd0c000 - 0x10bd10ff7 +libffi.6.dylib (0) <E26DDFF3-7498-3895-B705-76E93F2B8F3F> /opt/local/lib/libffi.6.dylib 0x10bd1a000 - 0x10bd84ff7 +libpixman-1.0.dylib (0) <EDCF6634-D006-3F69-B8AB-4B9EBD8E02DF> /opt/local/lib/libpixman-1.0.dylib 0x10bd9e000 - 0x10bd9efff +libX11-xcb.1.dylib (0) <4E55DEE4-0B73-3AD5-8F2B-A94FDF5DDA60> /opt/local/lib/libX11-xcb.1.dylib 0x10bda6000 - 0x10bdb8ff3 +libxcb.1.dylib (0) <C34E8C13-DCE2-379C-A04D-DDFDC5E09836> /opt/local/lib/libxcb.1.dylib 0x10bdcf000 - 0x10bdd4fff +libxcb-render.0.dylib (0) <5B95C5D8-4997-3AAE-B39D-91207D88C19A> /opt/local/lib/libxcb-render.0.dylib 0x10bddd000 - 0x10bde3ffb +libXrender.1.dylib (0) <C9E82F90-0DCB-3825-B616-508033563038> /opt/local/lib/libXrender.1.dylib 0x10bde7000 - 0x10bed9ffb +libX11.6.dylib (0) <55DA601C-18C5-32B9-866C-33AA2139DF42> /opt/local/lib/libX11.6.dylib 0x10bf01000 - 0x10bf0bfff +libXext.6.dylib (0) <112D7EE0-6D79-3C66-94DA-7B8CE5C6BC2A> /opt/local/lib/libXext.6.dylib 0x10bf11000 - 0x10bf2aff3 +libexpat.1.dylib (0) <75CBEF91-9085-3E2D-A9C4-88EB186A51D6> /opt/local/lib/libexpat.1.dylib 0x10bf35000 - 0x10bf46ff7 +libbz2.1.0.dylib (0) <41142963-7245-3191-BBA7-A9B029742522> /opt/local/lib/libbz2.1.0.dylib 0x10bf50000 - 0x10bf51fff +libXau.6.dylib (0) <ED41CE3A-ACF6-3D52-A190-3331DD54D5F0> /opt/local/lib/libXau.6.dylib 0x10bf54000 - 0x10bf57ffb +libXdmcp.6.dylib (0) <A396DA89-BAF7-3445-A0C2-CF6BD0E4737F> /opt/local/lib/libXdmcp.6.dylib 0x10bf5e000 - 0x10bf7aff3 +libgraphite2.3.dylib (0) <779F3D92-4746-3C22-9A42-A679B6B7EFED> /opt/local/lib/libgraphite2.3.dylib 0x10bf85000 - 0x10bfedffb +libwpd-0.10.10.dylib (0) <75F31392-4DFF-331C-BF74-16D3E6B24125> /opt/local/lib/libwpd-0.10.10.dylib 0x10c02b000 - 0x10c173ff7 +libicui18n.55.dylib (0) <7C35B5BA-5E1A-362D-8A04-5BFE8154BA24> /opt/local/lib/libicui18n.55.dylib 0x10c248000 - 0x10c339ff7 +libicuuc.55.dylib (0) <E7A1BC55-C98F-3CB9-B25C-78F5D707F6AD> /opt/local/lib/libicuuc.55.dylib 0x10c39d000 - 0x10dc52fff +libicudata.55.dylib (0) <9FFCD5FF-B765-3360-B471-74096FE4F813> /opt/local/lib/libicudata.55.dylib 0x10dc58000 - 0x10dd3cfff +libfftw3.3.dylib (0) <75D855B0-A894-350B-A87D-3094E4A5A392> /opt/local/lib/libfftw3.3.dylib 0x10dd59000 - 0x10dd95ffb +libXt.6.dylib (0) <52F39EFA-ADFA-35DD-AC10-071425049543> /opt/local/lib/libXt.6.dylib 0x10ddb0000 - 0x10ddb5fff +libltdl.7.dylib (0) <64176322-5BB7-3899-BD93-EE1EB4192328> /opt/local/lib/libltdl.7.dylib 0x10ddbf000 - 0x10ddc4ff7 +libSM.6.dylib (0) <BBB7D08E-C5C6-37D3-A041-06F270C73EB9> /opt/local/lib/libSM.6.dylib 0x10ddca000 - 0x10ddd9fff +libICE.6.dylib (0) <0B8A4739-9A37-306D-B21E-027066F43A3E> /opt/local/lib/libICE.6.dylib 0x10dde3000 - 0x10de30fff +libtiff.5.dylib (0) <1FCA4D21-5691-33B7-8A63-7FF8752E7FE2> /opt/local/lib/libtiff.5.dylib 0x10de3f000 - 0x10de8dffb +libcurl.4.dylib (0) <2A8628B5-8AF0-39D4-AE3D-2B6E5FF662F0> /opt/local/lib/libcurl.4.dylib 0x10de9d000 - 0x10dec0ffb +libopenjp2.7.dylib (0) <A4974F9A-BE6B-3BFF-8479-BDE156F32036> /opt/local/lib/libopenjp2.7.dylib 0x10dece000 - 0x10df15ff7 +libssl.1.0.0.dylib (0) <BCEBF488-03B6-3DE0-ABB5-C06428F1D772> /opt/local/lib/libssl.1.0.0.dylib 0x10df33000 - 0x10e0b8877 +libcrypto.1.0.0.dylib (0) <C2B33484-A2D9-3DBA-B387-29662B7D6A69> /opt/local/lib/libcrypto.1.0.0.dylib 0x111ac8000 - 0x111accfff +libpixbufloader-png.so (0) <3FB2ED0E-3EDE-3541-A966-858590D43EDE> /opt/local/lib/*/libpixbufloader-png.so 0x111dc2000 - 0x111dc8fff +libpixbufloader-xpm.so (0) <2398FADC-B9B4-3C82-9C4E-651FD41865B9> /opt/local/lib/*/libpixbufloader-xpm.so 0x11458b000 - 0x11464fffb com.apple.AMDRadeonX4000GLDriver (1.48.16 - 1.4.8) <07F6E91A-538C-3BE4-B2BE-339954DA1759> /System/Library/Extensions/AMDRadeonX4000GLDriver.bundle/Contents/MacOS/AMDRadeonX4000GLDriver 0x11480a000 - 0x114847267 dyld (421.2) <947FC440-80F9-32F7-A773-6FC418FE1AB7> /usr/lib/dyld 0x114b99000 - 0x115094ff3 ATIRadeonX4000SCLib.dylib (1.48.16) <7349E72D-12F1-334A-B4F1-3BB406987DBD> /System/Library/Extensions/AMDRadeonX4000GLDriver.bundle/Contents/MacOS/ATIRadeonX4000SCLib.dylib 0x7fff89b61000 - 0x7fff89c8dff7 com.apple.AMDMTLBronzeDriver (1.48.16 - 1.4.8) <93E2B635-21E1-3218-8AD0-FADF097F57F3> /System/Library/Extensions/AMDMTLBronzeDriver.bundle/Contents/MacOS/AMDMTLBronzeDriver 0x7fff8b6bd000 - 0x7fff8b6bdfff com.apple.Accelerate (1.11 - Accelerate 1.11) <D700DBDF-69AE-37A2-B9C7-0961CF0B6841> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate 0x7fff8b6be000 - 0x7fff8b6d5ffb libCGInterfaces.dylib (331.5) <518D3064-6E1E-3DF6-881B-57867DFE9B1E> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/Libraries/libCGInterfaces.dylib 0x7fff8b6d6000 - 0x7fff8bbeffeb com.apple.vImage (8.1 - ???) <6408805B-67E9-3874-8D32-0BB814CE5CDA> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vImage.framework/Versions/A/vImage 0x7fff8bbf0000 - 0x7fff8bd60ff3 libBLAS.dylib (1185) <C7E42BBE-2337-3AEF-9C45-A2F2CB1A5B3E> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBLAS.dylib 0x7fff8bd61000 - 0x7fff8bd75ffb libBNNS.dylib (14) <CFDEE88D-E002-347C-BC68-83099651585B> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libBNNS.dylib 0x7fff8bd76000 - 0x7fff8c16cfef libLAPACK.dylib (1185) <2E8201CB-9A41-3D65-853E-841917FCE77B> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLAPACK.dylib 0x7fff8c16d000 - 0x7fff8c183fff libLinearAlgebra.dylib (1185) <8CC29DE1-A231-3D5E-B5F1-DCC309036FE0> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libLinearAlgebra.dylib 0x7fff8c184000 - 0x7fff8c18afff libQuadrature.dylib (3) <120F6228-A3D4-3184-89D7-785ADC2AC715> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libQuadrature.dylib 0x7fff8c18b000 - 0x7fff8c19fff7 libSparseBLAS.dylib (1185) <C35235B7-CFA6-39A7-BD6E-79F4D9CAFD36> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libSparseBLAS.dylib 0x7fff8c1a0000 - 0x7fff8c327fe7 libvDSP.dylib (600) <F59348AA-E1D3-3A27-8AB5-F546D38BFB76> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvDSP.dylib 0x7fff8c328000 - 0x7fff8c3daffb libvMisc.dylib (600) <70D4B548-47EE-3C6B-A93B-3EA6B60701E0> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/libvMisc.dylib 0x7fff8c3db000 - 0x7fff8c3dbfff com.apple.Accelerate.vecLib (3.11 - vecLib 3.11) <A395B521-8E54-30F2-B4FE-355D68900DAF> /System/Library/Frameworks/Accelerate.framework/Versions/A/Frameworks/vecLib.framework/Versions/A/vecLib 0x7fff8c69b000 - 0x7fff8d46cff7 com.apple.AppKit (6.9 - 1504.76) <AF99A491-3175-362D-B313-074A3F87E49A> /System/Library/Frameworks/AppKit.framework/Versions/C/AppKit 0x7fff8d47e000 - 0x7fff8d47efff com.apple.ApplicationServices (48 - 48) <A29F0B74-33C1-3062-B68D-12BC3881C399> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/ApplicationServices 0x7fff8d47f000 - 0x7fff8d4edff7 com.apple.ApplicationServices.ATS (377 - 422.2) <3680281F-DB99-3CA2-9C76-CABFC8DBC980> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/ATS 0x7fff8d587000 - 0x7fff8d6b6fff libFontParser.dylib (194.6) <F3DF2CF7-B25D-30BB-9EE6-1EA9F3B8A066> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontParser.dylib 0x7fff8d6b7000 - 0x7fff8d701fff libFontRegistry.dylib (196.3) <855AF921-EAE0-3D07-B161-5EF09806B643> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libFontRegistry.dylib 0x7fff8d75e000 - 0x7fff8d791ff7 libTrueTypeScaler.dylib (194.6) <D0D7DA50-DF52-3D24-AFD2-03B336AA1929> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ATS.framework/Versions/A/Resources/libTrueTypeScaler.dylib 0x7fff8d7fd000 - 0x7fff8d8a7ff7 com.apple.ColorSync (4.12.0 - 502.1) <5F244DE3-A6E8-335F-AE3B-25F0E407DD62> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/ColorSync.framework/Versions/A/ColorSync 0x7fff8d8a8000 - 0x7fff8d8f8ff7 com.apple.HIServices (1.22 - 591) <34C950CC-1084-354A-BCE6-9396EDB29DF8> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/HIServices.framework/Versions/A/HIServices 0x7fff8d8f9000 - 0x7fff8d908ff3 com.apple.LangAnalysis (1.7.0 - 1.7.0) <47D1A017-91A4-37F3-93E0-3923CD6ED2DE> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/LangAnalysis.framework/Versions/A/LangAnalysis 0x7fff8d909000 - 0x7fff8d956fff com.apple.print.framework.PrintCore (12 - 491) <B7CC15C1-AF50-37F3-8AF6-65F8CDC323F0> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/PrintCore.framework/Versions/A/PrintCore 0x7fff8d957000 - 0x7fff8d992fff com.apple.QD (3.12 - 310) <8F718290-DD82-36CE-9AF0-EFB6D31A49F4> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/QD.framework/Versions/A/QD 0x7fff8d993000 - 0x7fff8d99eff7 com.apple.speech.synthesis.framework (6.3.3 - 6.3.3) <629831B1-B13C-30F5-AE16-6BB9037E3753> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Frameworks/SpeechSynthesis.framework/Versions/A/SpeechSynthesis 0x7fff8d99f000 - 0x7fff8dbaffff com.apple.audio.toolbox.AudioToolbox (1.14 - 1.14) <A1B98513-C19E-376F-8DAF-71BB2F263C5F> /System/Library/Frameworks/AudioToolbox.framework/Versions/A/AudioToolbox 0x7fff8dbb0000 - 0x7fff8dbb0fff com.apple.audio.units.AudioUnit (1.14 - 1.14) <55C6A958-D52B-3D81-B230-EB949212B5D9> /System/Library/Frameworks/AudioUnit.framework/Versions/A/AudioUnit 0x7fff8dd19000 - 0x7fff8e0ecff7 com.apple.CFNetwork (807.2.14 - 807.2.14) <9702C8B9-2984-3DD9-9C59-A83499C2DBC4> /System/Library/Frameworks/CFNetwork.framework/Versions/A/CFNetwork 0x7fff8e106000 - 0x7fff8e106fff com.apple.Carbon (154 - 157) <E7179C37-54BF-3DAC-BD4A-ABCCBBDFDDAE> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon 0x7fff8e107000 - 0x7fff8e10afff com.apple.CommonPanels (1.2.6 - 98) <6A71E8CB-3BF7-3A49-A5F7-0579BAE1219D> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/CommonPanels.framework/Versions/A/CommonPanels 0x7fff8e10b000 - 0x7fff8e413ff7 com.apple.HIToolbox (2.1.1 - 856.11) <11F1BAA6-547C-37CB-88DE-6C4B698AFF37> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/HIToolbox.framework/Versions/A/HIToolbox 0x7fff8e414000 - 0x7fff8e417ff7 com.apple.help (1.3.5 - 49) <27C5F9FE-838F-3807-A4AC-D99470185B10> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Help.framework/Versions/A/Help 0x7fff8e418000 - 0x7fff8e41dfff com.apple.ImageCapture (9.0 - 9.0) <E3E757FD-4060-33A4-A2AC-85EFBD987FCE> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/ImageCapture.framework/Versions/A/ImageCapture 0x7fff8e41e000 - 0x7fff8e4b5ff3 com.apple.ink.framework (10.9 - 219) <B44BA36D-7549-3EB2-8CF6-E171885194FB> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Ink.framework/Versions/A/Ink 0x7fff8e4b6000 - 0x7fff8e4d0fff com.apple.openscripting (1.7 - 172) <B204BF70-C4AA-3699-8493-66E6645A92A8> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/OpenScripting.framework/Versions/A/OpenScripting 0x7fff8e4d1000 - 0x7fff8e4d2ff3 com.apple.print.framework.Print (12 - 267) <CA7E9448-0903-34C8-AAF6-9070B52BF70E> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/Print.framework/Versions/A/Print 0x7fff8e4d3000 - 0x7fff8e4d5ff7 com.apple.securityhi (9.0 - 55006) <ACD20DC1-FBDE-3E1B-91BF-867FE7849CBC> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SecurityHI.framework/Versions/A/SecurityHI 0x7fff8e4d6000 - 0x7fff8e4dcff7 com.apple.speech.recognition.framework (6.0.1 - 6.0.1) <A20B0F7B-C32A-3FF1-BB75-BAC0EE4EF889> /System/Library/Frameworks/Carbon.framework/Versions/A/Frameworks/SpeechRecognition.framework/Versions/A/SpeechRecognition 0x7fff8e5bb000 - 0x7fff8e5bbfff com.apple.Cocoa (6.11 - 22) <6A3C97E3-3905-3767-978F-C2E4C3899CD2> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa 0x7fff8e6fb000 - 0x7fff8e78bff7 com.apple.audio.CoreAudio (4.3.0 - 4.3.0) <A38A11A5-130B-39CE-BEBA-F5427F6801DC> /System/Library/Frameworks/CoreAudio.framework/Versions/A/CoreAudio 0x7fff8e78c000 - 0x7fff8e79ffff com.apple.CoreBluetooth (1.0 - 1) <76AFC4B4-A9FD-3434-B168-90087E71F5C4> /System/Library/Frameworks/CoreBluetooth.framework/Versions/A/CoreBluetooth 0x7fff8e7a0000 - 0x7fff8ea9afeb com.apple.CoreData (120 - 752.8) <FE3F152B-4C35-3A58-A0CB-D04EE5908818> /System/Library/Frameworks/CoreData.framework/Versions/A/CoreData 0x7fff8ea9b000 - 0x7fff8eb27fff com.apple.CoreDisplay (1.0 - 1) <48B568C0-1E12-34F4-943D-EAB447FBA1BE> /System/Library/Frameworks/CoreDisplay.framework/Versions/A/CoreDisplay 0x7fff8eb28000 - 0x7fff8efc2fff com.apple.CoreFoundation (6.9 - 1348.28) <A40AA224-7A50-3989-95D0-5A228A0E2FAF> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation 0x7fff8efc3000 - 0x7fff8f645fff com.apple.CoreGraphics (2.0 - 1070.13) <C6E5A0EC-CEEE-3834-B37C-E5CF9EECDD52> /System/Library/Frameworks/CoreGraphics.framework/Versions/A/CoreGraphics 0x7fff8f646000 - 0x7fff8f888fff com.apple.CoreImage (12.2.0 - 451.2.6) <FA735717-BE82-397E-B0DC-71D83682D2F7> /System/Library/Frameworks/CoreImage.framework/Versions/A/CoreImage 0x7fff8f9ed000 - 0x7fff8f9edfff com.apple.CoreServices (775.9.7 - 775.9.7) <A5C444F3-408B-3062-AF4B-BF8CD919F221> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices 0x7fff8f9ee000 - 0x7fff8fa3ffff com.apple.AE (712.2 - 712.2) <342A13C0-4A6A-3947-B66B-0F624A4A7B52> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/AE.framework/Versions/A/AE 0x7fff8fa40000 - 0x7fff8fd1bff7 com.apple.CoreServices.CarbonCore (1159.5 - 1159.5) <11CC2194-0C9C-397A-B7F9-CDAB9B68D87D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonCore.framework/Versions/A/CarbonCore 0x7fff8fd1c000 - 0x7fff8fd4ffff com.apple.DictionaryServices (1.2 - 274) <864F3808-FFDD-3C4B-A5B7-F1A6C4668A86> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/DictionaryServices.framework/Versions/A/DictionaryServices 0x7fff8fd50000 - 0x7fff8fd58ffb com.apple.CoreServices.FSEvents (1230 - 1230) <13A2FC17-8F8C-35BF-9584-59FDFB738E2B> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/FSEvents.framework/Versions/A/FSEvents 0x7fff8fd59000 - 0x7fff8fec5ff7 com.apple.LaunchServices (775.9.7 - 775.9.7) <E350E4F6-822A-3F04-B59B-468A39AF5C64> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchServices.framework/Versions/A/LaunchServices 0x7fff8fec6000 - 0x7fff8ff76fff com.apple.Metadata (10.7.0 - 1075.28) <DBB524CD-6938-3623-99C2-4B1EC1E1BE58> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/Metadata.framework/Versions/A/Metadata 0x7fff8ff77000 - 0x7fff8ffd6fff com.apple.CoreServices.OSServices (775.9.7 - 775.9.7) <E9625B0B-9AE7-3024-9FEF-FEE0A1876D9D> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/OSServices.framework/Versions/A/OSServices 0x7fff8ffd7000 - 0x7fff90047fff com.apple.SearchKit (1.4.0 - 1.4.0) <F1B3EF8D-E820-317C-AC7F-8F056C246874> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SearchKit.framework/Versions/A/SearchKit 0x7fff90048000 - 0x7fff9008eff7 com.apple.coreservices.SharedFileList (38 - 38) <E1400999-1F08-35A1-9D07-27D80A2AF89A> /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/SharedFileList.framework/Versions/A/SharedFileList 0x7fff9011b000 - 0x7fff90267ff7 com.apple.CoreText (352.0 - 544.5) <E90EA1D8-3491-3014-9043-9928C4E4349C> /System/Library/Frameworks/CoreText.framework/Versions/A/CoreText 0x7fff90268000 - 0x7fff9029dfff com.apple.CoreVideo (1.8 - 234.0) <48C31E93-87C2-31F4-97E7-9E54C1EA8E7D> /System/Library/Frameworks/CoreVideo.framework/Versions/A/CoreVideo 0x7fff9029e000 - 0x7fff9030fffb com.apple.framework.CoreWLAN (11.0 - 1200.25.1) <BEBE9C03-3B9A-3948-99E3-CC8148FA2AB5> /System/Library/Frameworks/CoreWLAN.framework/Versions/A/CoreWLAN 0x7fff9040e000 - 0x7fff90413fff com.apple.DiskArbitration (2.7 - 2.7) <16EA6D93-A2EC-31DB-BF52-C4764E7B1630> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration 0x7fff905a2000 - 0x7fff90949ff3 com.apple.Foundation (6.9 - 1349.25) <D820A498-2E62-367D-BC72-5845B14C06E3> /System/Library/Frameworks/Foundation.framework/Versions/C/Foundation 0x7fff90975000 - 0x7fff909a6fff com.apple.GSS (4.0 - 2.0) <95FAD1F9-1610-3428-B9B4-D32F67C26574> /System/Library/Frameworks/GSS.framework/Versions/A/GSS 0x7fff90a66000 - 0x7fff90b09ffb com.apple.Bluetooth (5.0.2 - 5.0.2f4) <D4B76B20-7777-39C9-8365-FC0C0DE17AB0> /System/Library/Frameworks/IOBluetooth.framework/Versions/A/IOBluetooth 0x7fff90b0a000 - 0x7fff90b9fff7 com.apple.framework.IOKit (2.0.2 - 1324.30.13) <163BE7FA-B29A-348F-8B5F-E301F2E8C964> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit 0x7fff90ba0000 - 0x7fff90ba6ffb com.apple.IOSurface (153.3 - 153.3) <3DD3BF22-0800-31F2-B179-87F87D6F0548> /System/Library/Frameworks/IOSurface.framework/Versions/A/IOSurface 0x7fff90bf8000 - 0x7fff90d51fef com.apple.ImageIO.framework (3.3.0 - 1582) <564168E7-BEC0-35E3-9BF0-59B65C17225E> /System/Library/Frameworks/ImageIO.framework/Versions/A/ImageIO 0x7fff90d52000 - 0x7fff90d56fff libGIF.dylib (1582) <040243CD-3A68-3ADC-805C-FE1D17C80028> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libGIF.dylib 0x7fff90d57000 - 0x7fff90e47ff7 libJP2.dylib (1582) <A55870F9-F27F-3BD0-BE89-981BFF63D485> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJP2.dylib 0x7fff90e48000 - 0x7fff90e6bffb libJPEG.dylib (1582) <58C01E72-10A0-313F-8139-ED6E9D087ABB> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libJPEG.dylib 0x7fff90e6c000 - 0x7fff90e93ff7 libPng.dylib (1582) <F2CC3750-3520-311B-9C66-9D86036375B7> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libPng.dylib 0x7fff90e94000 - 0x7fff90e96ff3 libRadiance.dylib (1582) <C3E9CE5C-1A25-391B-9ACB-556AA065B985> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libRadiance.dylib 0x7fff90e97000 - 0x7fff90ef0ff3 libTIFF.dylib (1582) <71ADCD24-67C9-31B5-8E48-A4B89AFBB19F> /System/Library/Frameworks/ImageIO.framework/Versions/A/Resources/libTIFF.dylib 0x7fff91ac0000 - 0x7fff91ad9ff7 com.apple.Kerberos (3.0 - 1) <49DCBE1A-130C-3FBF-AAEA-AF9A518913AC> /System/Library/Frameworks/Kerberos.framework/Versions/A/Kerberos 0x7fff922d7000 - 0x7fff9232ffff com.apple.Metal (86.18 - 86.18) <7DFE0437-25A8-3E87-8318-91573C895742> /System/Library/Frameworks/Metal.framework/Versions/A/Metal 0x7fff92c03000 - 0x7fff92c0bfff com.apple.NetFS (6.0 - 4.0) <6614F9B8-0861-338B-8FF0-8E402F96141C> /System/Library/Frameworks/NetFS.framework/Versions/A/NetFS 0x7fff92de0000 - 0x7fff92de8ff7 libcldcpuengine.dylib (2.8.5) <6AFCDCF5-7788-3EFC-B761-6C31DBF205A7> /System/Library/Frameworks/OpenCL.framework/Versions/A/Libraries/libcldcpuengine.dylib 0x7fff92fb1000 - 0x7fff92fffff3 com.apple.opencl (2.8.6 - 2.8.6) <85574B12-CEED-373A-808E-B4BC7907AC7A> /System/Library/Frameworks/OpenCL.framework/Versions/A/OpenCL 0x7fff93000000 - 0x7fff93019ffb com.apple.CFOpenDirectory (10.12 - 194) <292FCA26-B2E4-37F8-BC8C-8369ACD3345A> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/Frameworks/CFOpenDirectory.framework/Versions/A/CFOpenDirectory 0x7fff9301a000 - 0x7fff93025ff7 com.apple.OpenDirectory (10.12 - 194) <399F4633-97CE-3560-BB3C-1E30E9604878> /System/Library/Frameworks/OpenDirectory.framework/Versions/A/OpenDirectory 0x7fff93026000 - 0x7fff93028fff libCVMSPluginSupport.dylib (13.0.10) <06D7F8EC-1D2B-38C2-B3FE-7D39185370BE> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCVMSPluginSupport.dylib 0x7fff93029000 - 0x7fff9302cff7 libCoreFSCache.dylib (151.1) <1910EF80-DE30-3817-8FDF-63F3C8B4BA37> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreFSCache.dylib 0x7fff9302d000 - 0x7fff93030fff libCoreVMClient.dylib (151.1) <8C8E9295-1918-3763-A0B7-6397EB181EF4> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libCoreVMClient.dylib 0x7fff93031000 - 0x7fff93039ffb libGFXShared.dylib (13.0.10) <0257924D-0226-306C-817B-6B624AD8C80F> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGFXShared.dylib 0x7fff9303a000 - 0x7fff93045fff libGL.dylib (13.0.10) <9BDE83C8-D820-34AB-ADBB-89394EE706FB> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGL.dylib 0x7fff93046000 - 0x7fff93082fe7 libGLImage.dylib (13.0.10) <38CB2689-C869-31A4-BECB-2E4F91F1FD1C> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLImage.dylib 0x7fff93083000 - 0x7fff931f9ffb libGLProgrammability.dylib (13.0.10) <96C3D0DF-73EB-3CEF-9527-03FA8C403546> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLProgrammability.dylib 0x7fff931fa000 - 0x7fff9323aff3 libGLU.dylib (13.0.10) <0303130B-3A1D-37C3-BEA5-0A2154C842D3> /System/Library/Frameworks/OpenGL.framework/Versions/A/Libraries/libGLU.dylib 0x7fff93ba2000 - 0x7fff93bb0fff com.apple.opengl (13.0.10 - 13.0.10) <7F1E35F8-F0D1-389B-B8CC-E06E02714005> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL 0x7fff93bb1000 - 0x7fff93d57fff GLEngine (13.0.10) <BCEDD508-5670-307C-ACC0-4B4740CE6D85> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLEngine.bundle/GLEngine 0x7fff93d58000 - 0x7fff93d82ffb GLRendererFloat (13.0.10) <91FFF901-0388-3FF0-B89B-9A0D2E992F13> /System/Library/Frameworks/OpenGL.framework/Versions/A/Resources/GLRendererFloat.bundle/GLRendererFloat 0x7fff948cd000 - 0x7fff94ac8ff7 com.apple.QuartzCore (1.11 - 449.41.15) <32D80183-DCE4-34A7-AA46-DD1DE0DAA859> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore 0x7fff9502e000 - 0x7fff9534dfff com.apple.security (7.0 - 57740.31.2) <A47D7BAE-0591-3184-8E44-FB2EB08A19C2> /System/Library/Frameworks/Security.framework/Versions/A/Security 0x7fff9534e000 - 0x7fff953c4ff7 com.apple.securityfoundation (6.0 - 55132.20.1) <9407620B-B230-3320-B0B7-5AE59F1D135C> /System/Library/Frameworks/SecurityFoundation.framework/Versions/A/SecurityFoundation 0x7fff953ee000 - 0x7fff953f1ff3 com.apple.xpc.ServiceManagement (1.0 - 1) <4E24C12E-6164-3A7A-8EB8-C2523492BAE8> /System/Library/Frameworks/ServiceManagement.framework/Versions/A/ServiceManagement 0x7fff95778000 - 0x7fff957e9ff7 com.apple.SystemConfiguration (1.14 - 1.14) <D9A57D90-E54F-3E1A-AA2F-F5A694BCE4BB> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfiguration 0x7fff97e4c000 - 0x7fff97e6effb com.apple.framework.Apple80211 (12.0 - 1200.41) <360012DB-DAE7-3EEF-85F0-E5BE1DE3425D> /System/Library/PrivateFrameworks/Apple80211.framework/Versions/A/Apple80211 0x7fff97e6f000 - 0x7fff97e7efdb com.apple.AppleFSCompression (88 - 1.0) <B6E2148F-BFBF-3F1B-A7DF-0F39190B4C20> /System/Library/PrivateFrameworks/AppleFSCompression.framework/Versions/A/AppleFSCompression 0x7fff97f6f000 - 0x7fff97ffa97f com.apple.AppleJPEG (1.0 - 1) <B4C3209B-58A5-359F-A898-F61B6C40E5E9> /System/Library/PrivateFrameworks/AppleJPEG.framework/Versions/A/AppleJPEG 0x7fff9841f000 - 0x7fff9849dfff com.apple.backup.framework (1.8.3 - 1.8.3) <B2E28A7A-1727-3052-AA73-CBC108286C07> /System/Library/PrivateFrameworks/Backup.framework/Versions/A/Backup 0x7fff99123000 - 0x7fff9914affb com.apple.ChunkingLibrary (172 - 172) <83E91936-305D-32A4-A256-5582B96B1852> /System/Library/PrivateFrameworks/ChunkingLibrary.framework/Versions/A/ChunkingLibrary 0x7fff99a73000 - 0x7fff99a7cffb com.apple.CommonAuth (4.0 - 2.0) <830B940B-3523-38DE-996D-695739616D10> /System/Library/PrivateFrameworks/CommonAuth.framework/Versions/A/CommonAuth 0x7fff9a19c000 - 0x7fff9a1acfff com.apple.CoreEmoji (1.0 - 39.1) <0A46D6BF-22F3-39AD-B3DC-DE1EE5C442CC> /System/Library/PrivateFrameworks/CoreEmoji.framework/Versions/A/CoreEmoji 0x7fff9a48f000 - 0x7fff9a4bfff3 com.apple.CoreServicesInternal (276.2 - 276.2) <7D8DEF04-72F1-39F4-BBFB-09E65D7B8C10> /System/Library/PrivateFrameworks/CoreServicesInternal.framework/Versions/A/CoreServicesInternal 0x7fff9a74f000 - 0x7fff9a7d9fff com.apple.CoreSymbolication (61050) <F4B7C798-F7B7-3977-AA08-59A03F00308E> /System/Library/PrivateFrameworks/CoreSymbolication.framework/Versions/A/CoreSymbolication 0x7fff9a7da000 - 0x7fff9a918fd7 com.apple.coreui (2.1 - 430.6) <99D08D71-3E9D-300C-9EB2-A73F1B5E228C> /System/Library/PrivateFrameworks/CoreUI.framework/Versions/A/CoreUI 0x7fff9a919000 - 0x7fff9a9c9ff3 com.apple.CoreUtils (5.0 - 500.9) <5567181B-721C-339E-A3DC-579E36D92341> /System/Library/PrivateFrameworks/CoreUtils.framework/Versions/A/CoreUtils 0x7fff9aa19000 - 0x7fff9aa7eff3 com.apple.framework.CoreWiFi (12.0 - 1200.25.1) <BEFA276C-D284-3160-8641-7DD47E38C9D7> /System/Library/PrivateFrameworks/CoreWiFi.framework/Versions/A/CoreWiFi 0x7fff9aa7f000 - 0x7fff9aa8cff7 com.apple.CrashReporterSupport (10.12 - 817) <CB5251B1-5BE5-308B-B30B-0050065E04CC> /System/Library/PrivateFrameworks/CrashReporterSupport.framework/Versions/A/CrashReporterSupport 0x7fff9aafe000 - 0x7fff9ab08ff7 com.apple.framework.DFRFoundation (1.0 - 104.14) <258B6CFE-FD64-31C5-9973-2FD80597ECDA> /System/Library/PrivateFrameworks/DFRFoundation.framework/Versions/A/DFRFoundation 0x7fff9ab3e000 - 0x7fff9abb5ff7 com.apple.datadetectorscore (7.0 - 539.1) <E9892E38-3D5F-36CF-BDC5-E4E3C5516B55> /System/Library/PrivateFrameworks/DataDetectorsCore.framework/Versions/A/DataDetectorsCore 0x7fff9abf2000 - 0x7fff9ac31fff com.apple.DebugSymbols (137 - 137) <B229F3F7-250B-3151-8048-CEA7BF80FA52> /System/Library/PrivateFrameworks/DebugSymbols.framework/Versions/A/DebugSymbols 0x7fff9ac32000 - 0x7fff9ad43fff com.apple.desktopservices (1.11.3 - 1.11.3) <CCE689AA-85F3-3587-AE12-1231E8ED127E> /System/Library/PrivateFrameworks/DesktopServicesPriv.framework/Versions/A/DesktopServicesPriv 0x7fff9b027000 - 0x7fff9b458ff7 com.apple.vision.FaceCore (3.3.2 - 3.3.2) <DEB42099-6927-332C-8D3E-D45096318D25> /System/Library/PrivateFrameworks/FaceCore.framework/Versions/A/FaceCore 0x7fff9c7ad000 - 0x7fff9c7adfff libmetal_timestamp.dylib (600.0.48.32) <31DF1B9E-0BBF-308B-B78D-11CCE72DAA68> /System/Library/PrivateFrameworks/GPUCompiler.framework/libmetal_timestamp.dylib 0x7fff9c7ba000 - 0x7fff9c7c5ff3 libGPUSupportMercury.dylib (13.0.10) <99773A80-8B47-33F7-9406-96DC530FB586> /System/Library/PrivateFrameworks/GPUSupport.framework/Versions/A/Libraries/libGPUSupportMercury.dylib 0x7fff9ca79000 - 0x7fff9ca95ff3 com.apple.GenerationalStorage (2.0 - 259.2) <00BF8427-967F-3693-A86F-DA0F29B49BF3> /System/Library/PrivateFrameworks/GenerationalStorage.framework/Versions/A/GenerationalStorage 0x7fff9d193000 - 0x7fff9d209fff com.apple.Heimdal (4.0 - 2.0) <00F00E7E-7EF4-3254-86D3-ADA4F67938CF> /System/Library/PrivateFrameworks/Heimdal.framework/Versions/A/Heimdal 0x7fff9d821000 - 0x7fff9d82bfff com.apple.IOAccelMemoryInfo (1.0 - 1) <DFFA3D47-7C3A-3AA9-B818-62CB224C90DE> /System/Library/PrivateFrameworks/IOAccelMemoryInfo.framework/Versions/A/IOAccelMemoryInfo 0x7fff9d82c000 - 0x7fff9d833ffb com.apple.IOAccelerator (289.27 - 289.27) <61C7765B-EE2E-36E1-B51C-FFA13A657711> /System/Library/PrivateFrameworks/IOAccelerator.framework/Versions/A/IOAccelerator 0x7fff9d835000 - 0x7fff9d849ff3 com.apple.IOPresentment (1.0 - 25) <40934217-996A-3DDB-A8C4-484CA0F0222B> /System/Library/PrivateFrameworks/IOPresentment.framework/Versions/A/IOPresentment 0x7fff9d84a000 - 0x7fff9d86cfff com.apple.IconServices (74.3 - 74.3) <3F0BD358-D019-3083-82F2-69CCAD5E5D66> /System/Library/PrivateFrameworks/IconServices.framework/Versions/A/IconServices 0x7fff9d94f000 - 0x7fff9db05fff com.apple.LanguageModeling (1.0 - 123.2.4) <FEB98F96-A9BB-3E6C-85B4-B466825B8C92> /System/Library/PrivateFrameworks/LanguageModeling.framework/Versions/A/LanguageModeling 0x7fff9e3c9000 - 0x7fff9e442ff7 com.apple.MetalPerformanceShaders.MetalPerformanceShaders (1.0 - 1) <6A759DBA-B7DF-363B-9827-AB1D1129BB34> /System/Library/PrivateFrameworks/MetalPerformanceShaders.framework/Versions/A/MetalPerformanceShaders 0x7fff9e5c4000 - 0x7fff9e5ecfff com.apple.MultitouchSupport.framework (368.7 - 368.7) <BA3D9226-2672-3039-A105-C2639A7E22F2> /System/Library/PrivateFrameworks/MultitouchSupport.framework/Versions/A/MultitouchSupport 0x7fff9e69b000 - 0x7fff9e6a5fff com.apple.NetAuth (6.0 - 6.0) <1E7765FC-4580-3CE4-A0F1-CAA22006AE43> /System/Library/PrivateFrameworks/NetAuth.framework/Versions/A/NetAuth 0x7fff9ef21000 - 0x7fff9ef62ff7 com.apple.PerformanceAnalysis (1.145 - 145) <2D5D4A56-5F67-3BBB-9AAC-95FAC199877C> /System/Library/PrivateFrameworks/PerformanceAnalysis.framework/Versions/A/PerformanceAnalysis 0x7fff9f605000 - 0x7fff9f61ffff com.apple.ProtocolBuffer (1 - 249) <D8B7694B-B598-3728-8583-9C4CC0F05B64> /System/Library/PrivateFrameworks/ProtocolBuffer.framework/Versions/A/ProtocolBuffer 0x7fff9f639000 - 0x7fff9f65cff3 com.apple.RemoteViewServices (2.0 - 124) <4765DC2E-CF05-38CF-9564-1FBACB7E167C> /System/Library/PrivateFrameworks/RemoteViewServices.framework/Versions/A/RemoteViewServices 0x7fffa035a000 - 0x7fffa03d7ff7 com.apple.Sharing (696.1.22 - 696.1.22) <D0A5C682-8996-3851-B332-AD05301E6FA3> /System/Library/PrivateFrameworks/Sharing.framework/Versions/A/Sharing 0x7fffa03f8000 - 0x7fffa0657fe7 com.apple.SkyLight (1.600.0 - 122.8) <2B8B6734-2B70-3BD8-BB8E-3338FB2708EE> /System/Library/PrivateFrameworks/SkyLight.framework/Versions/A/SkyLight 0x7fffa0838000 - 0x7fffa0844ff7 com.apple.SpeechRecognitionCore (3.3.2 - 3.3.2) <F9F0FCED-3A72-3639-91F2-B7EF248ED1B9> /System/Library/PrivateFrameworks/SpeechRecognitionCore.framework/Versions/A/SpeechRecognitionCore 0x7fffa0f2d000 - 0x7fffa0f99ff3 com.apple.Symbolication (61080.2) <27A57DC2-FEB7-3D23-AEB5-E3E76C5AAE79> /System/Library/PrivateFrameworks/Symbolication.framework/Versions/A/Symbolication 0x7fffa1393000 - 0x7fffa1399ff7 com.apple.TCC (1.0 - 1) <956F7C1A-D457-3FE0-9CFE-3F1719F0865C> /System/Library/PrivateFrameworks/TCC.framework/Versions/A/TCC 0x7fffa1428000 - 0x7fffa15f0ff7 com.apple.TextureIO (1.41 - 1.41) <3A9D9FD9-8997-3BD1-8046-76D0BF709806> /System/Library/PrivateFrameworks/TextureIO.framework/Versions/A/TextureIO 0x7fffa1664000 - 0x7fffa1665fff com.apple.TrustEvaluationAgent (2.0 - 28) <07C1F711-A1E0-3BAC-8F4D-977516D50925> /System/Library/PrivateFrameworks/TrustEvaluationAgent.framework/Versions/A/TrustEvaluationAgent 0x7fffa1666000 - 0x7fffa17f6ff3 com.apple.UIFoundation (1.0 - 490.7) <047781ED-9E79-361F-8E04-71FF90C650F3> /System/Library/PrivateFrameworks/UIFoundation.framework/Versions/A/UIFoundation 0x7fffa2816000 - 0x7fffa2818ffb com.apple.loginsupport (1.0 - 1) <4449ACBA-27A8-3311-BD92-CB7E63583FC6> /System/Library/PrivateFrameworks/login.framework/Versions/A/Frameworks/loginsupport.framework/Versions/A/loginsupport 0x7fffa286d000 - 0x7fffa2888ff7 libCRFSuite.dylib (34) <BACC371B-6153-36B5-BC54-3BCF26FBB221> /usr/lib/libCRFSuite.dylib 0x7fffa2889000 - 0x7fffa2894fff libChineseTokenizer.dylib (21) <09E74E18-ADB2-30D2-A858-13691CB1186C> /usr/lib/libChineseTokenizer.dylib 0x7fffa2926000 - 0x7fffa2927ff3 libDiagnosticMessagesClient.dylib (102) <422911A4-E273-3E88-BFC4-DF6470E48242> /usr/lib/libDiagnosticMessagesClient.dylib 0x7fffa2928000 - 0x7fffa2b3bfff libFosl_dynamic.dylib (16.38) <8232FA8A-F16A-3DC0-AE68-B61EFCD5F4A4> /usr/lib/libFosl_dynamic.dylib 0x7fffa2b5f000 - 0x7fffa2b5ffff libOpenScriptingUtil.dylib (172) <D025E180-BB3B-3FFA-98FC-B6835354D723> /usr/lib/libOpenScriptingUtil.dylib 0x7fffa2b60000 - 0x7fffa2b64ff3 libScreenReader.dylib (477.20.6) <8158E263-B7DF-3B0C-BABE-4FE94A53DFE5> /usr/lib/libScreenReader.dylib 0x7fffa2b65000 - 0x7fffa2b66ff3 libSystem.B.dylib (1238) <FF55E335-37C3-3567-9415-A3A1473775F5> /usr/lib/libSystem.B.dylib 0x7fffa2bd2000 - 0x7fffa2bfdffb libarchive.2.dylib (41.30.3) <19B93FE5-4386-38C8-963F-7DBDAB96FEBA> /usr/lib/libarchive.2.dylib 0x7fffa2bfe000 - 0x7fffa2c7afc7 libate.dylib (1.12.13) <8A963F37-CB4F-37FB-BFA5-273917C42437> /usr/lib/libate.dylib 0x7fffa2c7e000 - 0x7fffa2c7eff3 libauto.dylib (187) <5BBF6A00-CC76-389D-84E7-CA88EDADE683> /usr/lib/libauto.dylib 0x7fffa2c7f000 - 0x7fffa2c8fff3 libbsm.0.dylib (34) <20084796-B04D-3B35-A003-EA11459557A9> /usr/lib/libbsm.0.dylib 0x7fffa2c90000 - 0x7fffa2c9eff7 libbz2.1.0.dylib (38) <6FD3B63F-0F86-3A25-BD5B-E243F58792C9> /usr/lib/libbz2.1.0.dylib 0x7fffa2c9f000 - 0x7fffa2cf5ff7 libc++.1.dylib (307.4) <BEE86868-F831-384C-919E-2B286ACFE87C> /usr/lib/libc++.1.dylib 0x7fffa2cf6000 - 0x7fffa2d20fff libc++abi.dylib (307.2) <1CEF8ABB-7E6D-3C2F-8E0A-E7884478DD23> /usr/lib/libc++abi.dylib 0x7fffa2d21000 - 0x7fffa2d31ffb libcmph.dylib (6) <2B5D405E-2D0B-3320-ABD6-622934C86ABE> /usr/lib/libcmph.dylib 0x7fffa2d32000 - 0x7fffa2d47fc3 libcompression.dylib (34) <1691D6F2-46CD-3DA6-B44F-24CDD9BD0E4E> /usr/lib/libcompression.dylib 0x7fffa2d48000 - 0x7fffa2d48ff7 libcoretls.dylib (121.31.1) <BCC32537-4831-3E9F-876E-8C9F4CF52FD3> /usr/lib/libcoretls.dylib 0x7fffa2d49000 - 0x7fffa2d4aff3 libcoretls_cfhelpers.dylib (121.31.1) <6F37C5AD-7999-3D31-A52F-7AEED935F32D> /usr/lib/libcoretls_cfhelpers.dylib 0x7fffa2e04000 - 0x7fffa2ee9ff7 libcrypto.0.9.8.dylib (64.30.2) <D41E1901-06DD-3860-BB4F-B3ACE0284C01> /usr/lib/libcrypto.0.9.8.dylib 0x7fffa3087000 - 0x7fffa30daff7 libcups.2.dylib (450) <78243BA4-43AB-3364-8111-8D54D3382621> /usr/lib/libcups.2.dylib 0x7fffa3155000 - 0x7fffa3155fff libenergytrace.dylib (15) <A1B040A2-7977-3097-9ADF-34FF181EB970> /usr/lib/libenergytrace.dylib 0x7fffa3165000 - 0x7fffa316aff7 libheimdal-asn1.dylib (498.30.1) <4ED9F6E3-83BC-3302-B004-C25399DA0333> /usr/lib/libheimdal-asn1.dylib 0x7fffa316b000 - 0x7fffa325dff7 libiconv.2.dylib (50) <42125B35-81D7-3FC4-9475-A26DBE10884D> /usr/lib/libiconv.2.dylib 0x7fffa325e000 - 0x7fffa3483ffb libicucore.A.dylib (57149.0.1) <6B5FDA93-AA88-318F-9608-C2A33D602EC7> /usr/lib/libicucore.A.dylib 0x7fffa3489000 - 0x7fffa348afff liblangid.dylib (126) <3F4530C9-8BE1-3AA7-9A82-98694D240866> /usr/lib/liblangid.dylib 0x7fffa348b000 - 0x7fffa34a4ffb liblzma.5.dylib (10) <44BD0279-99DD-36B5-8A6E-C11432E2098D> /usr/lib/liblzma.5.dylib 0x7fffa34a5000 - 0x7fffa34bbff7 libmarisa.dylib (5) <2183D484-032D-3DE5-8984-3A14006E034E> /usr/lib/libmarisa.dylib 0x7fffa34bc000 - 0x7fffa3763ff7 libmecabra.dylib (744.5) <EF046855-CB9C-32D8-B2F1-C85B526E386F> /usr/lib/libmecabra.dylib 0x7fffa3796000 - 0x7fffa380fff7 libnetwork.dylib (856.30.16) <66C6E4D6-B39C-3309-80C1-CBBE170DDD51> /usr/lib/libnetwork.dylib 0x7fffa3810000 - 0x7fffa3be0d97 libobjc.A.dylib (706) <F9AFE665-A3A2-3285-9495-19803A565861> /usr/lib/libobjc.A.dylib 0x7fffa3be3000 - 0x7fffa3be7fff libpam.2.dylib (21.30.1) <71EB0D88-DE84-3C8D-A2C5-58AA282BC5BC> /usr/lib/libpam.2.dylib 0x7fffa3be8000 - 0x7fffa3c18ff7 libpcap.A.dylib (67) <450DB888-2C0C-3085-A5F1-69324DFE902C> /usr/lib/libpcap.A.dylib 0x7fffa3c36000 - 0x7fffa3c52ffb libresolv.9.dylib (64) <A244AE4C-00B0-396C-98FF-97FE4DB3DA30> /usr/lib/libresolv.9.dylib 0x7fffa3ca2000 - 0x7fffa3deafe3 libsqlite3.dylib (253) <B5BA5C96-AB13-34A0-8237-DD52A0181DFE> /usr/lib/libsqlite3.dylib 0x7fffa3edf000 - 0x7fffa3eecfff libxar.1.dylib (357) <58BFB84B-66FE-3299-AA3D-BBA178ADEE39> /usr/lib/libxar.1.dylib 0x7fffa3ef0000 - 0x7fffa3fdfffb libxml2.2.dylib (30.11) <E12AF929-0FA5-3214-840F-C81E6AC9F36E> /usr/lib/libxml2.2.dylib 0x7fffa3fe0000 - 0x7fffa4009fff libxslt.1.dylib (15.8) <FFF5DD45-F544-34B2-BE3C-DB877DC60081> /usr/lib/libxslt.1.dylib 0x7fffa400a000 - 0x7fffa401bff3 libz.1.dylib (67) <46E3FFA2-4328-327A-8D34-A03E20BFFB8E> /usr/lib/libz.1.dylib 0x7fffa402a000 - 0x7fffa402eff7 libcache.dylib (79) <0C8092D3-600F-3ADD-A036-F225B6CDCA43> /usr/lib/system/libcache.dylib 0x7fffa402f000 - 0x7fffa403aff7 libcommonCrypto.dylib (60092.30.2) <B16E29B6-EC8D-3A8F-9A89-DD9CF35F7C4B> /usr/lib/system/libcommonCrypto.dylib 0x7fffa403b000 - 0x7fffa4042fff libcompiler_rt.dylib (62) <E992E8D9-037C-3454-A366-A25E4D31D6BB> /usr/lib/system/libcompiler_rt.dylib 0x7fffa4043000 - 0x7fffa404bfff libcopyfile.dylib (138) <64E285D9-5485-333B-AEE7-8B0C8FB9275F> /usr/lib/system/libcopyfile.dylib 0x7fffa404c000 - 0x7fffa40cffdf libcorecrypto.dylib (442.30.20) <2074B932-FD79-30A9-8E90-AF25C49F2AF1> /usr/lib/system/libcorecrypto.dylib 0x7fffa40d0000 - 0x7fffa4102fff libdispatch.dylib (703.30.5) <EA0CC14E-D559-3802-B4B2-0E8C7579AAC4> /usr/lib/system/libdispatch.dylib 0x7fffa4103000 - 0x7fffa4108ff3 libdyld.dylib (421.2) <E5A2414F-2480-3BB2-BE94-176119A80876> /usr/lib/system/libdyld.dylib 0x7fffa4109000 - 0x7fffa4109ffb libkeymgr.dylib (28) <1A318923-1200-3B06-B432-5007D82F195D> /usr/lib/system/libkeymgr.dylib 0x7fffa410a000 - 0x7fffa4116ffb libkxld.dylib (3789.31.2) <524D7C3D-73EB-3F62-ADB1-9DFBACB95924> /usr/lib/system/libkxld.dylib 0x7fffa4117000 - 0x7fffa4117fff liblaunch.dylib (972.30.7) <15FACC21-079A-3BDF-9AFB-4253EFDEB587> /usr/lib/system/liblaunch.dylib 0x7fffa4118000 - 0x7fffa411dfff libmacho.dylib (894) <A2F38EC1-C37C-3B93-B0E4-36B07C177F8C> /usr/lib/system/libmacho.dylib 0x7fffa411e000 - 0x7fffa4120ff3 libquarantine.dylib (85) <C1D7749F-5F5F-3BB9-BEFC-1F0B9DA941FD> /usr/lib/system/libquarantine.dylib 0x7fffa4121000 - 0x7fffa4122ffb libremovefile.dylib (45) <CD42974E-BE0B-39FC-9BFC-8A7540A04DC6> /usr/lib/system/libremovefile.dylib 0x7fffa4123000 - 0x7fffa413bff7 libsystem_asl.dylib (349.30.2) <EFAC72D7-CB13-3DF7-ADF3-EC6635C6F1EA> /usr/lib/system/libsystem_asl.dylib 0x7fffa413c000 - 0x7fffa413cff7 libsystem_blocks.dylib (67) <B8C3701D-5A91-3D35-999D-2DC8D5393525> /usr/lib/system/libsystem_blocks.dylib 0x7fffa413d000 - 0x7fffa41cafef libsystem_c.dylib (1158.30.7) <2F881962-03CB-3B9D-A782-D98C1BBA4E3D> /usr/lib/system/libsystem_c.dylib 0x7fffa41cb000 - 0x7fffa41ceffb libsystem_configuration.dylib (888.30.2) <4FE3983C-E4ED-3939-A578-03AD29C99788> /usr/lib/system/libsystem_configuration.dylib 0x7fffa41cf000 - 0x7fffa41d2fff libsystem_coreservices.dylib (41.4) <1A572B9E-0C47-320F-8C64-7990D0A5FB5A> /usr/lib/system/libsystem_coreservices.dylib 0x7fffa41d3000 - 0x7fffa41ebff3 libsystem_coretls.dylib (121.31.1) <4676F06D-274D-31BE-B61C-4D7A4AEF4858> /usr/lib/system/libsystem_coretls.dylib 0x7fffa41ec000 - 0x7fffa41f2fff libsystem_dnssd.dylib (765.30.11) <DC708D84-ED7D-3936-B996-A67C66B8DDAA> /usr/lib/system/libsystem_dnssd.dylib 0x7fffa41f3000 - 0x7fffa421cff7 libsystem_info.dylib (503.30.1) <9ED9121C-F111-3FAD-BC2F-C95DEE1C9362> /usr/lib/system/libsystem_info.dylib 0x7fffa421d000 - 0x7fffa423fff7 libsystem_kernel.dylib (3789.31.2) <FCEEBBD4-DF66-34D8-A32F-4F8C8E814E40> /usr/lib/system/libsystem_kernel.dylib 0x7fffa4240000 - 0x7fffa4287fe7 libsystem_m.dylib (3121.4) <266DB92B-A86F-3691-80FB-1B26AD73CFF3> /usr/lib/system/libsystem_m.dylib 0x7fffa4288000 - 0x7fffa42a6ff7 libsystem_malloc.dylib (116.30.3) <F40DEE3B-386A-3529-A3F7-98117ED55BF4> /usr/lib/system/libsystem_malloc.dylib 0x7fffa42a7000 - 0x7fffa42feffb libsystem_network.dylib (856.30.16) <4AE368E9-605D-379D-B04C-2AC7455B8250> /usr/lib/system/libsystem_network.dylib 0x7fffa42ff000 - 0x7fffa4308ff3 libsystem_networkextension.dylib (563.30.15) <EB020B0C-7DF0-3EEF-8E3C-15DA3C01D687> /usr/lib/system/libsystem_networkextension.dylib 0x7fffa4309000 - 0x7fffa4312ff3 libsystem_notify.dylib (165.20.1) <E7FD3A7C-DD07-36E2-9FA4-7561F9F114DA> /usr/lib/system/libsystem_notify.dylib 0x7fffa4313000 - 0x7fffa431bfe7 libsystem_platform.dylib (126.1.2) <3CA06D4E-C00A-36DE-AA65-3A390097D1F6> /usr/lib/system/libsystem_platform.dylib 0x7fffa431c000 - 0x7fffa4326ff7 libsystem_pthread.dylib (218.30.1) <C869ED7C-BE29-3532-8E69-3A8DA1447EDC> /usr/lib/system/libsystem_pthread.dylib 0x7fffa4327000 - 0x7fffa432aff7 libsystem_sandbox.dylib (592.31.1) <7BBFDF96-293F-3DD9-B3A4-7C168280B441> /usr/lib/system/libsystem_sandbox.dylib 0x7fffa432b000 - 0x7fffa432cfff libsystem_secinit.dylib (24) <5C1F1E47-0F7D-3E25-8DEB-D9DB1F902281> /usr/lib/system/libsystem_secinit.dylib 0x7fffa432d000 - 0x7fffa4334fff libsystem_symptoms.dylib (532.30.6) <5D990CF5-B58F-39F7-B375-99B4EC62CFBD> /usr/lib/system/libsystem_symptoms.dylib 0x7fffa4335000 - 0x7fffa4355ff7 libsystem_trace.dylib (518.30.7) <5BD4ECD4-75CA-38EA-AF5C-B481C15955F8> /usr/lib/system/libsystem_trace.dylib 0x7fffa4356000 - 0x7fffa435bffb libunwind.dylib (35.3) <9F7C2AD8-A9A7-3DE4-828D-B0F0F166AAA0> /usr/lib/system/libunwind.dylib 0x7fffa435c000 - 0x7fffa4385ff7 libxpc.dylib (972.30.7) <65E41BB6-EBD5-3D93-B0BE-B190CEE4DD93> /usr/lib/system/libxpc.dylib External Modification Summary: Calls made by other processes targeting this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0 Calls made by this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0 Calls made by all processes on this machine: task_for_pid: 1504 thread_create: 0 thread_set_state: 0 VM Region Summary: ReadOnly portion of Libraries: Total=325.6M resident=0K(0%) swapped_out_or_unallocated=325.6M(100%) Writable regions: Total=176.5M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=176.5M(100%) VIRTUAL REGION REGION TYPE SIZE COUNT (non-coalesced) =========== ======= ======= Accelerate framework 128K 2 Activity Tracing 256K 2 CG backing stores 3636K 3 CG image 92K 8 CoreAnimation 52K 7 CoreUI image data 1388K 11 CoreUI image file 180K 5 Dispatch continuations 16.0M 2 Kernel Alloc Once 8K 2 MALLOC 113.1M 31 MALLOC guard page 48K 9 Memory Tag 242 12K 2 STACK GUARD 56.1M 19 Stack 16.6M 21 VM_ALLOCATE 9376K 18 __DATA 24.8M 310 __GLSLBUILTINS 2588K 2 __IMAGE 528K 2 __LINKEDIT 126.4M 90 __TEXT 199.2M 299 __UNICODE 556K 2 mapped file 49.6M 18 shared memory 16.3M 14 =========== ======= ======= TOTAL 636.6M 856 Model: iMac17,1, BootROM IM171.0105.B11, 4 processors, Intel Core i7, 4 GHz, 32 GB, SMC 2.33f10 Graphics: AMD Radeon R9 M390, AMD Radeon R9 M390, PCIe, 2048 MB Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1867 MHz, 0x802C, 0x31364B544631473634485A2D314739453220 Memory Module: BANK 0/DIMM1, 8 GB, DDR3, 1867 MHz, 0x198, 0x4B48583138363643313153334C2F38472020 Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1867 MHz, 0x802C, 0x31364B544631473634485A2D314739453220 Memory Module: BANK 1/DIMM1, 8 GB, DDR3, 1867 MHz, 0x198, 0x4B48583138363643313153334C2F38472020 AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x14A), Broadcom BCM43xx 1.0 (7.21.171.68.1a4) Bluetooth: Version 5.0.2f4, 3 services, 27 devices, 1 incoming serial ports Network Service: Ethernet, Ethernet, en0 Serial ATA Device: APPLE HDD ST2000DM001, 2 TB Serial ATA Device: APPLE SSD SM0128G, 121.33 GB USB Device: USB 3.0 Bus USB Device: Bluetooth USB Host Controller USB Device: FaceTime HD Camera (Built-in) USB Device: Keyboard Hub USB Device: Apple Keyboard USB Device: Apple USB SuperDrive Thunderbolt Bus: iMac, Apple Inc., 28.1

4 6

Re: [Inkscape-devel] Retrospective on 0.92 release
by Joshua Facemyer 09 Jan '17

09 Jan '17

This does make me sad, as at my day job I have no choice but to use osx. And I prefer Inkscape to the Adobe options, though I have ready access to them. I do understand both sides of this debate, though. The x11 or Quartz version leaves a lot to be desired as compared to native GTK on *nix. The osxmenu project version was great... But if there is a dearth of developers for this work, understood. It would be better to focus on what can be done on the supported platforms. FLOSS supporters on osx know we have to give up many preferred apps that just aren't available. I wish I could help out here, but apart from a guided compile, I couldn't really contribute to packaging. Maybe it's finally time to run a virtual xubuntu on osx to get the tools I miss... JF ------ Original message------From: Lyndsy SimonDate: Thu, Jan 5, 2017 12:27 PMTo: Martin Owens;Bryce Harrington;inkscape-devel@...6...;Cc: Subject:Re: [Inkscape-devel] Retrospective on 0.92 release …… > Based on the feedback I'm seeing, it looks like we made a very good > choice to retire our OSX packaging. I admit I was a little worried, > but suv's judgment was 100% right, and as anticipated our > deliberately *not* providing it is stimulating others to step in and > fill the void. With 0.93 on Gtk3 it sounds like we'll have > opportunities for even better OSX packages. > We made a good call there. It's hard to say no to an entire platform, > but we really couldn't support it reasonably and people that use MacOSX > have the worst opinion of Inkscape imaginable. Look at some of the > comments about the release. I also think it was a good call, but not because macOS users "have the worst opinion of Inkscape imaginable". You're seeing a very small segment of that community; most Inkscape users on macOS aren't going to engage in a flamewar because a new version doesn't have a download link for their platform on the day of its release. If the existing dev team can't support the platform (which seems to be the case), then dropping it was absolutely the right move. If there is enough demand out there to justify packaging it in the future, let the people who want it to happen supply the resources to make it happen. On Thu, Jan 5, 2017 at 9:48 AM Martin Owens <doctormo@...400...> wrote: Firstly, Three cheers for Bryce, without whom we would have no release at all. Let me add some thoughts to your postpartum below... > Overall I think it went quite well. Switching build systems was a > big change, and getting two year's worth of feature work stabilized > is quite an achievement. Yes, it's quite the achievement. Each release build is a way for us a programmers to say "Users matter and this is a thing we think users should have" and it shows the project is not just a collection of self interested coders, but also selfless volunteers that can get a lot of these tasks done even if we don't benefit in a direct way. Releases are perhaps the most primary target for paid work, where the money comes from users. Especially given it's laborious, managerial (pointy haired boss eh bryce ;-)) and could do with more attention. Perhaps we could have a fund raising just for the next release, we'd be setting ourselves some harder deadlines and if successful, we'd have the money to pay for say a person or two to work on bugs and management aspects. > Based on the feedback I'm seeing, it looks like we made a very good > choice to retire our OSX packaging. I admit I was a little worried, > but suv's judgment was 100% right, and as anticipated our > deliberately *not* providing it is stimulating others to step in and > fill the void. With 0.93 on Gtk3 it sounds like we'll have > opportunities for even better OSX packages. We made a good call there. It's hard to say no to an entire platform, but we really couldn't support it reasonably and people that use MacOSX have the worst opinion of Inkscape imaginable. Look at some of the comments about the release. > Another big part of the delay was blocker bugs. I found this very > hard > to get my hands around; the issues are legitimately troublesome > problems > that should be resolved, but finding people able and available to > work > on them was tough. Unfortunately bugs are inevitable, and I worry > the > shift to Gtk3, C++11, and so on are destined to give rise to > more. Does > anyone have ideas on how we can handle things better so there are > fewer > blockers? Or ways to get the blockers resolved more quickly? I see tackling bugs to be a big part of the problem. We may have to have a talk about what it means to be an "Inkscape Developer" capital I, capital D. Our requirements right now are two commits to trunk ever in the past. There's no long term plan for members to retire and no bug fixing requirement to keep an active Developer status. We don't even specify in the about screen which members were active in the last ten years of development. Anyone ever is in that list. Which is good for voting, things like the board voting should be open to all alumni. But for the kinds of attribution that is rewarding to see, we don't really pay much attention and can't offer anything to bug fixers. > a more timely fashion. Does anyone have suggestions or observations > that could help us improve this? A service that does timed and shared task management might be an improvement. I noticed there was a lot of manual work with regard to task management. > huge positive impact Inkscape has made in people's lives and careers, > and the 0.92 release you've created is going to enable a lot of > people to do some really great things. Inkscape is one of those things in the world that provides millions of dollars worth of economic and social value but which takes very little money. Something Open Source projects can always be proud of. But there's space to think about having our different user groups (cnc, artists, animators, web designers, tracers etc etc) involved in sorting out the major issues they have with their respective workflows. I noticed that while a laser cutter problem is critical to workshops and school use of inkscape, it was wishlist or low priority for the project as a whole. That presents us with a problem where Inkscape is great for 90% of the work, but has critical failures for 90% of workflows at the same time. I'll keep thinking about this and I'd be happy to talk on IRC at our next meeting. Thanks again Bryce! Best Regards, Martin Owens ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's

1 0

multithreaded rendering
by Yale Zhang 09 Jan '17

09 Jan '17

In my quest for a more fluid experience with fewer distractions, I've attempted to multithread the rendering. I see this has been a long standing discussion: https://bugs.launchpad.net/inkscape/+bug/200415 https://bugs.launchpad.net/inkscape/+bug/330271 I'm using a Lenovo P40 tablet and the total frame rendering time for a simple piece is 80 to 100ms (1920x1080, a few hundred vertices on 2 layers with no filter effects - only alpha compositing). This slow rendering speed makes the touchscreen zooming I recently implemented very jerky. So, I tried multithreading SPCanvas::paintRectInternal() with OpenMP by splitting the rectangle into 2 and rendering them in ||. I used mutual exclusion for some obviously thread unsafe code like the call to markRect in SPCanvas::paintSingleBuffer(). The rendering would work for a few frames before it freezes (waiting threads timeout and then exit). Then, I put other calls that I suspected were thread unsafe in mutually exclusive blocks until I discovered _root->render() isn't safe. No point in going further. Excuse my naive attempt. Can anyone guess how feasible it is to multithread the rendering? For now, I don't care if it's pixel perfect. I just need something that's decent and doesn't crash/freeze. I'm also wondering why the Cairo OpenGL backend isn't being used? GPU rendering on integrated GPUs should give a nice speedup since there should be no copying overhead. The other place to optimize is pixman. I did some profiling (rapidly zooming in and out with touchscreen) and >= 25% of the time is spent in pixman rendering. I already went ahead and ported a few to AVX2 and got ~1.3x speedup (should get more since my laptop is bottlenecked by memory bandwidth owing to having only 1 memory channel). Function Module Samples sse2_blt.part.0 libpixman-1-0.dll 4221 sse2_combine_in_u libpixman-1-0.dll 2189 sse2_fill libpixman-1-0.dll 1693 cairo_tor_scan_converter_generate libcairo-2.dll 1494 sse2_composite_over_8888_8888 libpixman-1-0.dll 1424 bits_image_fetch_separable_convolution_affine_none_a8r8g8b8 libpixman-1-0.dll 1104 feed_curve_to_cairo(_cairo*Geom::Curve const& libinkscape_base.dll 611 fast_composite_scaled_bilinear_sse2_8888_8888_cover_SRC libpixman-1-0.dll 475 fill_xrgb32_lerp_opaque_spans libcairo-2.dll 348 cairo_tor_scan_converter_add_polygon libcairo-2.dll 260 compute_face libcairo-2.dll 238 _dynamic_cast libstdc++-6.dll 209 outer_join libcairo-2.dll 179 cairo_polygon_add_edge libcairo-2.dll 178 g_hash_table_lookup libglib-2.0-0.dll 169 cairo_spline_decompose_into libcairo-2.dll 153 g_slice_alloc libglib-2.0-0.dll 138 cairo_spline_intersects libcairo-2.dll 131 feed_pathvector_to_cairo(_cairo*Geom::PathVector const&) libinkscape_base.dll 127 line_to libcairo-2.dll 119 void std::vector<Geom::Pointstd::allocator<Geom::Point> libinkscape_base.dll 116 cairo_matrix_transform_point libcairo-2.dll 110 cell_list_render_edge libcairo-2.dll 106 g_type_check_instance_is_a libgobject-2.0-0.dll 106

3 4

0.92 macOS packaging
by Lyndsy Simon 08 Jan '17

08 Jan '17

I'm a long-time user of Inkscape who uses macOS, and while I've not got a ton of experience in packaging software for distribution I believe I'm capable of learning it and taking responsibility for putting together and maintaining Inkscape's macOS version. Is the build workflow that was used to package 0.91 for macOS documented somewhere? That, along with a precise description of the issues that led to its discontinuation, should be enough to get started. -Lyndsy Simon

4 3

Wiki account request
by Tim Sheridan 08 Jan '17

08 Jan '17

Hi, Could someone please add an account for me on the wiki (user: Tghs, email: tghs atttt tghs dotttt net). Cheers, Tim

2 2

MacPorts Inkscape Install
by PipingDesignCentral . 06 Jan '17

06 Jan '17

>From a recent instruction: **If you have MacPorts installed you can build the X11 version using **sudo port install inkscape **or the Quartz version using **sudo port install inkscape +quartz I tried the latter after installing MacPorts and it seems to be hanging at 'Building gtk2' after 30 minutes. I must have done something wrong. Any advice? Paul [ Dozens of command lines not pasted below ] ---> Attempting to fetch gtk2-2.24.31_0+quartz.darwin_16.x86_64.tbz2 from https://packages.macports.org/gtk2 ---> Attempting to fetch gtk2-2.24.31_0+quartz.darwin_16.x86_64.tbz2 from http://sea.us.packages.macports.org/macports/packages/gtk2 ---> Attempting to fetch gtk2-2.24.31_0+quartz.darwin_16.x86_64.tbz2 from http://lil.fr.packages.macports.org/gtk2 ---> Fetching distfiles for gtk2 ---> Attempting to fetch gtk+-2.24.31.tar.xz from https://distfiles.macports.org/gtk2 ---> Verifying checksums for gtk2 ---> Extracting gtk2 ---> Applying patches to gtk2 ---> Configuring gtk2 ---> Building gtk2

3 2

ImageMagick-7
by Ken Moffat 06 Jan '17

06 Jan '17

As I mentioned last year, ImageMagick has moved onto -7. The -6 version is in maintenance mode. Much of the structure has changed, which appears to mke changing the programs which use it complex, but the headers and libraries themselves can be installed in parallel. Unfortunately, the main pkgconfig files have the same names, so if you install both versions then the pkgconfig file will be whichever version you installed last. I've been asked if you guys have any development patches to support ImageMagick-7 ? But maybe I should just ask if you have any plans to eventually support the newer version ? For the moment, I suspect the answer is no - and after looking at the code I wouldn't achieve anything in a month of sundays. So, for my own purposes I have a cunning plan : sed the Makefile in inkscape to add '6' to all the pkgconfig filenames, and then sed all users (inkscape, possibly some others) to add the 6 to the names. Dunno if I'll manage it, but it looks possible. ĸen -- `I shall take my mountains', said Lu-Tze. `The climate will be good for them.' -- Small Gods

2 2

Board Meeting @ Friday Jan 6 (TODAY)
by Bryce Harrington 06 Jan '17

06 Jan '17

Sorry for the late notice. While officially our monthly meeting was last Friday, many couldn't attend and we mostly focused just on the release. So there's interest in having another meeting today, Friday the 6th of January, on #inkscape-devel, at Noon Pacific. http://wiki.inkscape.org/wiki/index.php/Board_Meetings All in the Inkscape community are welcome to attend. Agenda: * Merchandise sales (Spreadshirt status) * Sponsorship levels (web page needed) * Inkscape forum followup * Next hackfest * 2017 budget Thanks, Bryce

1 0

Inkscape 0.92.0 now available on MacPorts
by David Evans 06 Jan '17

06 Jan '17

Inkscape 0.92.0 is now available via MacPorts both as an X11 build and as a native Quartz build. If you have MacPorts installed you can build the X11 version using sudo port install inkscape or the Quartz version using sudo port install inkscape +quartz For those who want to follow development toward 0.92.1, an inkscape-devel port is also available which builds a recent snapshot from the lp:inkscape/0.92.x release branch. The current version is 0.92.0 bzr 15301. Let me know if you have any questions, issues or comments or you can file a ticket at https://trac.macports.org/ Regards, Dave Evans

2 3

Mac-OS
by Jabier Arraiza 05 Jan '17

05 Jan '17

What about to put in Mac download page is abailable by Macports with some info? Cheers, Jabier.

2 2

Recent icon changes
by mathog 04 Jan '17

04 Jan '17

Hi All, Some time between revisions 15016 and 15387 there were substantial changes to the two rows of icons at the top (the ones just below the file/edit/view/etc.). I'm not a fan of the new ones. 1. The new icons are larger than the old ones, which is a waste of space. Possibly not an issue if you are using a huge screen. However, I tend to work on small monitors, and Inkscape already uses up a lot of real estate around the drawing, leaving in some cases (my laptop, for instance) a pretty tiny window showing the drawing. My largest display is 1280 x 1024 and with the new larger icons even at full width the "Move patterns" icon is cut off. 2. The object rotate and mirror icons, which were previously excellent, showing transforms of a dark triangle to a grey one) have been replaced with generic looking fuzzy arrows. The rotate 90 degree icon could be the "undo" icon, or vice versa. Double headed arrows like those used for symmetry operations are more commonly used to indicate either sliding or scaling in the direction indicated. I much (much, MUCH) prefer the older ones. 3. The red handles on the new scissors icon draw my eye. When I look at that row for an icon now my eyes go there first, even when I know that isn't the icon I want. Probably this is because the red handles really stand out when compared to the other icons. Not sure what the proper design term is, but the icons should all have the same "visual weight" to avoid this, and for me the scissors is "heavier". 4. Now that I look more closely, there are size changes on the icons on the left and right too. The image in each icon is the same size, but each is now surrounded by a lot more white space. Again, that is a waste of screen space. If I adjust a copy of 15016 so that the select arrow (top of left column) is in the same place as for a copy of 15387, and the bottoms of the outer windows are in the same place, in the older one the last tool visible is the text icon, whereas in the new one it is only the spiral icon. That is, there are 4 less tools shown in the same space. The same problem applies on the right, where again there are 4 more icons visible in the older version than the new. Sometimes less is more. For drawing programs like this I want the tools and such to take as little space as possible away from the drawing. These need to be big enough to read, but not any larger than that. (Note, the older version was running on Windows and the newer one on Linux.) Regards, David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech

5 9

Uploads and Caching
by Martin Owens 04 Jan '17

04 Jan '17

Dear release developers, This is a note about large uploads such as new inkscape releases. The web server's caching will kick in on the first download of a file, so make sure you hit the download button and wait for it to completely download before announcing. I think this release is hitting our servers hard, we have a 20% Bad Request ratio at the moment. This is one small behavioural thing that really helps cut down the amount of work the server needs to be. Martin,

2 1

Inkscape 0.92 is Released!
by Bryce Harrington 04 Jan '17

04 Jan '17

The Inkscape project announces a new version 0.92 of its popular vector drawing software. New features include mesh gradients, improved SVG2 and CSS3 support, new path effects, interactive smoothing for the pencil tool, a new Object dialog for directly managing all drawing elements, and much more. Infrastructural changes are also under way, including a switch to CMake from the venerable Autotools build system. -------------------------------------------------------------------- Watch our showcase at: https://www.youtube.com/watch?v=EI1hxXt9U4c Download 0.92 from: https://inkscape.org/en/download/ -------------------------------------------------------------------- Mesh gradients enable artists to create photo-realistic drawings more easily - a feature we would love to see made part of the W3C's Scalable Vector Graphics (SVG) standard; if you find this feature as cool as we do, please request that your favorite web browser adopts support for it too! Inkscape works closely with the SVG standards committee, and thanks to our many generous donors the Inkscape project sponsors an engineering representative to attend SVG working group meetings over the past few years; a welcome outcome of this participation is the improvement and addition of over a dozen SVG and CSS properties, such as paint-order, white-space, and mix-blend-mode. Live Path Effects are proving to be a vibrant ecosystem in the Inkscape project, and many innovative new ideas have been percolating over the past couple years since our last release. Spiro Live, BSpline, and Roughen essentially provide new drawing modes. The Simplify LPE cleans up vector elements non-destructively by smoothing paths, shapes, groups, clips, and masks. Perspective/Envelope and Lattice Deformation 2 enable artists to interactively deform/transform drawing elements. Other new features enable interactive mirroring, interactive rotation of copies along an arc or circle, and dozens of other additions and enhancements. All software must evolve with the times, and Inkscape is no different. To maintain consistency with the CSS standard, Inkscape's default resolution has changed from 90dpi to 96dpi; Inkscape will detect files created with previous versions and offer to convert them. A number of infrastructural changes are in process to help Inkscape keep up with progress. For 0.92 we are changing to the CMake build system, which builds faster and is easier for developers to work with. (Future infrastructure changes include switching from bzr to git, shifting from Gtk2 to Gtk3, and moving to the C++11 standard.) The above barely scratches the surface of all the new stuff included in this release. For the full story, including examples, screenshots, and videos, please see our detailed Release Notes: http://wiki.inkscape.org/wiki/index.php/Release_notes/0.92 If you're on Linux, you'll soon be able to install Inkscape 0.92 from your distribution via normal methods. We also intend to publish a distribution-independent snap file for Inkscape 0.92. If you're on Windows, we have a set of packages that we hope will let you maximize performance on your platform. For Mac OS X, no packages are available -- our old (X11/XQuartz) packaging was long overdue to be updated to current standards and is no longer being maintained. If you wish to compile Inkscape yourself, then of course, the Inkscape source code is also available from our website. The Inkscape Project thrives due to your support. We are a volunteer-driven community built from thousands of contributions of time, skill, and funds, to create a powerful open source tool that is made available for free to everyone in the world. We invite you to join our community and participate in helping advance Inkscape towards new objectives. Come help us chart out the new directions that Inkscape needs to take! Inkscape is created *by* the community *for* the community. Your donations also help further Inkscape's mission. You can donate to Inkscape's general fund, or target your donation to support our SVG Standards work or Hackfests. -------------------------------------------------------------------- Join Inkscape at: https://inkscape.org/community/ Become a donor at: https://inkscape.org/support-us/ Download Inkscape at: https://inkscape.org/download/ Watch our showcase at: https://www.youtube.com/watch?v=EI1hxXt9U4c -------------------------------------------------------------------- -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iEYEARECAAYFAlhsmJMACgkQEaMBVuDmdhHm+QCeKJBSNYW0i4aTNorwr50M1yXG 96AAoL8ZIMCFS3+x44yLOUzkyYsx+jtW =qGwR -----END PGP SIGNATURE-----

5 4

compile error on Windows 10, Inkscape rev 15382, 64 bit
by alvinpenner 03 Jan '17

03 Jan '17

this is my first attempt to compile a 64 bit version of Inkscape. Previously I had done a 32 bit version on Windows XP using cmake. - running cmake version 3.7.1 32-bit version - devlibs64 uptodate - mingw64 from the file x86_64-5.3.0-release-win32-seh-rt_v4-rev0.7z - the compile step appeared to be successful until the very end... the output is: C:\Users\penne_000\AppData\Roaming\InkscapeBZR\build>mingw32-make -j 2 [ 1%] Built target vpsc_LIB revision is 15382 [ 1%] Built target inkscape_version [ 2%] Built target util_LIB [ 2%] Built target gc_LIB [ 2%] Built target cola_LIB [ 4%] Built target avoid_LIB ... [ 26%] Built target pofiles_90 [ 26%] Built target filters_svg_h [ 26%] Built target palettes_h [ 26%] Built target patterns_svg_h [ 27%] Built target symbols_h [ 27%] Built target templates_h [ 99%] Built target inkscape_base [ 99%] Built target inkview [100%] Linking CXX executable ..\bin\inkscape.exe ../lib/libgc_LIB.a(gc.cpp.obj):gc.cpp:(.text+0x4f0): multiple definition of `Inkscape::GC::Core::init()' ../lib/libinkscape_base.dll.a(d010885.o):(.text+0x0): first defined here collect2.exe: error: ld returned 1 exit status src\CMakeFiles\inkscape.dir\build.make:201: recipe for target 'bin/inkscape.exe' failed mingw32-make[2]: *** [bin/inkscape.exe] Error 1 CMakeFiles\Makefile2:421: recipe for target 'src/CMakeFiles/inkscape.dir/all' failed mingw32-make[1]: *** [src/CMakeFiles/inkscape.dir/all] Error 2 mingw32-make[1]: *** Waiting for unfinished jobs.... [100%] Built target grid2 Makefile:126: recipe for target 'all' failed mingw32-make: *** [all] Error 2 -- View this message in context: http://inkscape.13.x6.nabble.com/compile-error-on-Windows-10-Inkscape-rev-1… Sent from the Inkscape - Dev mailing list archive at Nabble.com.

4 5

[Fwd: Website Feedback]
by Martin Owens 01 Jan '17

01 Jan '17

>From the inkscape website administrator inbox:

1 0

Fwd: Re: Inkscape 0.92pre5 released
by Miguel Lopez 31 Dec '16

31 Dec '16

Subject: Re: [Inkscape-devel] Inkscape 0.92pre5 released Date: Sat, 31 Dec 2016 01:35:59 -0500 From: Miguel Lopez <reptillia39@...3425...><mailto:reptillia39@...3425...> To: Bryce Harrington <bryce@...961...><mailto:bryce@...961...> Right now, I am testing a bug with the Rotate Copies feature, and I'm gonna file a report on that soon. So, there is going to be a little change, but that's not too much. I'm gonna also look at gradient mesh. Will file a bug report soon. Well, I checked gradient meshes, and it looks like there's gonna be a few more work to do. Yep, I will file 2 bug reports as soon as possible. I wish I can do more, but being fatigued everyday does not help things. Other than that, the difference between .92 and .91 is huge. I hope to see more focus on gradient mesh, and experimental forms of gradient somewhere between .92, and .94. Instead of a gradient mesh, I wish we can define gradients based on points, and lines. That would also open avenues to gradient textures/procedural textures, and would hugely benefit vector-based interior design. On 12/30/2016 3:37 AM, Bryce Harrington wrote: > The 0.92pre5 source package and Windows packages are now released and > can be downloaded from the Inkscape website: > > https://inkscape.org/en/download/development-versions > > Thanks to everyone that contributed fixes and translation updates, > packaging, and work on the marketing/outreach preparations. > > My hope is there will be no further changes between pre5 and the final > release. Please download and test this release candidate as if it was > the official 0.92.0 release. What we're looking for are issues that are > a) so severe that we need to put off the release, or b) issues caused by > recent changes that can be trivially fixed (e.g. one-liner patches that > are obviously correct). > > Barring any last minute issues, things look good for finalizing the > source package this weekend and announcing the 0.92 release early next > week. > > We'll plan on doing a point release in a month or two. This will > include both translation updates and bugfixes. > > To everyone that has contributed to the changes in 0.92: Great work! > The release is just days away. :-) > > Bryce > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel(a)lists.sourceforge.net<mailto:Inkscape-devel@...941...rge.net> > https://lists.sourceforge.net/lists/listinfo/inkscape-devel

2 2

Inkscape 0.92pre5 released
by Bryce Harrington 30 Dec '16

30 Dec '16

The 0.92pre5 source package and Windows packages are now released and can be downloaded from the Inkscape website: https://inkscape.org/en/download/development-versions Thanks to everyone that contributed fixes and translation updates, packaging, and work on the marketing/outreach preparations. My hope is there will be no further changes between pre5 and the final release. Please download and test this release candidate as if it was the official 0.92.0 release. What we're looking for are issues that are a) so severe that we need to put off the release, or b) issues caused by recent changes that can be trivially fixed (e.g. one-liner patches that are obviously correct). Barring any last minute issues, things look good for finalizing the source package this weekend and announcing the 0.92 release early next week. We'll plan on doing a point release in a month or two. This will include both translation updates and bugfixes. To everyone that has contributed to the changes in 0.92: Great work! The release is just days away. :-) Bryce

2 1

Board Meeting @ Friday Dec 30
by Bryce Harrington 30 Dec '16

30 Dec '16

Hi all, We'll be holding an Inkscape Committee meeting this Friday the 30th of December, on #inkscape-devel, at Noon Pacific. http://wiki.inkscape.org/wiki/index.php/Board_Meetings All in the Inkscape community are welcome to attend. Since I suspect many people are on vacation this week, we'll play the agenda by ear, but give focus to issues relating to the release and current status of Spreadshirt. Thanks, Bryce

3 2

0.92 release status (and 0.92.1 planning)
by Bryce Harrington 29 Dec '16

29 Dec '16

Hope everyone is having a great holiday! We're nearly done with 0.92.0 - great work everyone and thanks especially to everyone fixing up bugs and updating translations. Final RC will be cut Wed the 28th. Translation updates are ok to continue landing until then. Bug fixes please check with me and expect some friendly pushback. :-) I'd like the final RC to be identical to what we release, so we don't release with anything untested. So ideally there should be NO changes after the 28th. In practice some minor polish is probably acceptable; but if there are any significant changes we'll need to do further RC's. The 0.92.0 release will happen this weekend or very early next week, assuming we don't need further RC's. We need short turnarounds for packaging so we can get announcements out swiftly. I think we can do it. We can start planning for a 0.92.1 release. There's a healthy amount of energy going into bug fixing right now, and our users will appreciate if we continue. Some fixes will need string changes, so I'll propose we also encourage translation updates. I would like to shoot for early February with this release. Additionally, a focus for 0.92.1 could be on bug management tools. I.e., warning dialogs, workarounds, and bug reporting helper scripts. Josh mentioned that having a button to reset old prefs could work around some mesh problems, and I'm betting there's more we could do like that. Bryce

2 4

batch converting pdf to svg using Inkscape
by jelle 28 Dec '16

28 Dec '16

Hi all, I was wondering if it is possible to batch convert pdf to svg with an out put that renders the text as paths, but contains the text as metadata in the svg file so you can search on that for words, thus easily finding the right documents. Or eventually making output of the same file in a path rendered version and a text containing one(though that is sub optimal). I remember having read something about adding the text as meta data into the SVG output, so I was wondering what the status of that is. If so, is there a way to do this without the gui? Or at least without starting the whole app for every pdf to be converted? I have several hundreds to convert, so that would be nice. The tool pdf2svg does a great job of converting pdf to SVG, but only to path, which sort of defeats the purpose of conversion in the first place. I have to index the pdf text into a database and then insert that data into the SVG file as metadata. Possible, but a bit of a lot of work for a one time event. Cheers, Jelle

1 0

touch and tablet support
by Yale Zhang 28 Dec '16

28 Dec '16

Any artists out there using Inkscape on a drawing tablet? I find the lack of touch and pen support very inconvenient for serious, free hand drawing. Does anyone else find this wanting or is working on it? C R, you mentioned it in the discussion of Jabier's workspace rotation. I'm using a Lenovo P40 with the Bamboo Smart AES pen, which has 2 buttons. I'd like to use the buttons to cycle between certain tools. Preferably, panning, rotation, and scaling should work like Autodesk Illustrator, using 2 fingers: scale = Magnitude(p1 - p0) / Magnitude(p1_start - p0_start) rotation = atan2(p1.y - p0.y, p1.x - p0.x) - atan2(p1_start.y - p0_start.y, p1_start.x, p0_start.x) pan = 0.5 * (p0 + p1) - 0.5 * (p0_start + p1_start) Then single touch should be used to select and move objects. Currently, single touch is indistinguishable from the mouse - stray lines are very annoying (Wacom's palm rejection helps reduce this though). Just like pens, touch should remember the last tool used and switch to it when using it again. I started implementing these and found GTK 3 has no multi touch support on Windows and the pen support is also flaky - the source of each event is always GDK_SOURCE_MOUSE / "Virtual Core Pointer" instead of GDK_SOURCE_PEN, GDK_SOURCE_ERASER, or GDK_SOURCE_TOUCHSCREEN, meaning the pen can't remember its last used tool separately from the mouse. For now, I've managed to implement these work arounds: switch tools: bottom pen button cycles between cursor, pencil, and tweak. Double clicking top button switches to eraser. pan: hold down top pen button and drag fingers to zoom - seems the Wacom driver recognizes zoom gestures and translates it into mouse wheel zoom events -Yale

3 5

board meeting??
by brynn 28 Dec '16

28 Dec '16

Hi Friends, For planning, and considering the upcoming release -- will board meeting be this Friday (Dec 30) or next (Jan 6)? Thanks, brynn

2 1

Inkscape without gui/gtk
by Nathan Hüsken 26 Dec '16

26 Dec '16

Hey eveyone, I am looking for a solution to convert svg files to pdf on AWS lambda. Since inkscape has a commandline interface, it seems to be a good choice. But for this to work inkscape would have to run on a headless linux system. No X11, not gtk etc. So I am wondering, can inkscape be modified so that it can compile in "Headless" mode. I looked at the inkscape code, and at a first glance it does not seemt to be sooo simple. Can anyone estimate if this makes sense and how much work this would be? Thanks! Nathan

3 2

Inkscape 0.92pre4 released
by Bryce Harrington 23 Dec '16

23 Dec '16

The 0.92pre4 source package has been released and can be downloaded from Launchpad: https://launchpad.net/inkscape/0.92.x/0.92pre4 I tried to upload it to the inkscape.org website, but kept getting a server error. Hopefully Martin can investigate and get the source package properly uploaded there too. :-) This pre-release incorporates bugfixes for the recently added mesh gradient feature, tidies up build options, adds the official about screen, and includes numerous backports and translation updates. >From what I can see, the reaction to the mesh gradient feature has been quite positive, and particularly with the serious attention given to fixing issues that have been raised, there seems to be little reason not to ship it in our final release. I remain open to feedback to the contrary, but at this time I suggest we proceed under the assumption that it will be part of the release. Meanwhile, please do try the feature out and help us advocate for its adoption by web browsers and other SVG using applications. Please try to avoid making any further changes on the 0.92.x tree - consider it in final freeze before release. The one exception being translations - the mesh gradient changes were allowed to break string freeze, so due to that we'll be giving permission to translators for breaking this final freeze. Ideally, I'd like to see no other changes to the 0.92.x branch prior to release; so if you have a change you would like to see included, please run any and all changes by me first (with justification) before landing them. Packagers are encouraged to prepare binary packages for the platforms we support. Thanks, Bryce

6 10

Open Colour Systems Collection 2.0 released
by "Christoph Schäfer" 23 Dec '16

23 Dec '16

Open Colour Systems 2.0 Released ================================ freieFarbe e.V. / freeColour is pleased to announce the release of Open Colour Systems Collection (OCSC) 2.0. Following the release of OCSC 1.0, freieFarbe / freeColour has been been recognised by German authorities as a non-profit organisation. The release of OCSC is the first one after the official recognition. OCSC 2.0 comprises ten additional colour palettes. More importantly, it is now also available in Adobe's Swatch Exchange Format (ASE), as well as a Plain Text Format version with the file extension CLF. All colours have been measured from vendor-supplied colour references with a spectrophotometer. Since freieFarbe e.V. / freeColour is an advocate of the use of the CIE LAB/HLC colour model as a free and reasonable alternative to proprietary colour collections, colour values in the palette files are in CIE LAB. Download ======== SBZ: http://freiefarbe.de/wp-content/uploads/2016/12/OCSC_20_SBZ.zip SHA1 checksum: 6b2bab7dde9e5fe9e8778ee9f79f31edcaa8cef8 ASE: http://freiefarbe.de/wp-content/uploads/2016/12/OCSC_20_ASE.zip SHA1 checksum: fea350149e2b95af55f36e283fe597f279d3f79c CLF: http://freiefarbe.de/wp-content/uploads/2016/12/OCSC_20_CLF.zip SHA1 checksum: e65fd94db7f0d6484df9ce0cf0288ecd328ec655 In addition, OCSC 2.0 has been released in three RGB versions for use in LibreGraphics programmes that don't support the LAB colour model and/or one of the formats listed above (yet). The formats are: GPL (GIMP, Inkscape, Calligra Office, Krita, MyPaint), SOC (Apache OpenOffice, LibreOffice, OpenOffice.org), and XML (Scribus 1.4.x). Download ======== GPL: http://freiefarbe.de/wp-content/uploads/2016/12/OCSC_20_GPL.zip SHA1 checksum: c0eefb3a74f658c9c201d5671b4af6a085650cbb SOC: http://freiefarbe.de/wp-content/uploads/2016/12/OCSC_20_SOC.zip SHA1 checksum: 318d8fbaf391b0ec39fa433e807e3ec658381376 XML: http://freiefarbe.de/wp-content/uploads/2016/12/OCSC_20_ScrXML.zip SHA1 checksum: da456792dc89445022ab4ae1af3f5ccedc722cd6 A complete package with all supported formats is available here: http://dtpstudio.de/downloads/freeware/OCSC_20.zip SHA1 checksum: e65fd94db7f0d6484df9ce0cf0288ecd328ec655 In addition, freieFarbe / freeColour provides other colour-related software for free here: http://freecolour.org/ Colour Software Release Planned =============================== freieFarbe e.V. / freeColour also intends to release a previously closed-source colour software product written in RealBasic as Open Source under a GPL 2+ licence. fF / fC hopes to find contributors who are interested in porting the code from RealBasic to C++ and Qt, as well as merging the features of Swatchbooker and the original product. The majority of the code is UI-related, but the essential algorithms (the core of the product) are well-commented. Any assistance with respect to the organisation of the release of the source code would be welcome. About freieFarbe e.V. / freeColour: =================================== freieFarbe e.V. / freeColour is a non-profit organisation that was founded in 2016 by German and Swiss colour professionals after having worked as an informal initiative without legal status for several years. our motto is "We want to unchain colours". The organisation is looking for cooperation with colour experts, software developers and users around the globe who share our goals. You are invited to become a member and/or contribute your own project. freieFarbe e.V. / freeColour is convinced that the design world will benefit from truly free colours and better colour software. December 2016 Holger Everding Christoph Schäfer www.freiefarbe.de www.freecolour.org

1 0

unable to compile 0.92.x rev 15268 on Windows XP
by alvinpenner 22 Dec '16

22 Dec '16

1. My first attempt was using btool. This led to Bug 1651137 which I have been unable to fix. https://bugs.launchpad.net/inkscape/+bug/1651137 2. My second attempt was using cmake 3.2.1. I followed the instructions at: http://wiki.inkscape.org/wiki/index.php/Compiling_Inkscape_on_Windows This led to the following error: C:\InkscapeBZR\src>md build C:\InkscapeBZR\src>cd build C:\InkscapeBZR\src\build>cmake -G "MinGW Makefiles" .. CMake Error at debug/CMakeLists.txt:28 (add_inkscape_source): Unknown CMake command "add_inkscape_source". CMake Warning (dev) in CMakeLists.txt: No cmake_minimum_required command is present. A line of code such as cmake_minimum_required(VERSION 3.2) should be added at the top of the file. The version specified may be lower if you wish to support older CMake versions for this project. For more information run "cmake --help-policy CMP0000". This warning is for project developers. Use -Wno-dev to suppress it. -- Configuring incomplete, errors occurred! See also "C:/InkscapeBZR/src/CMakeFiles/CMakeOutput.log". ........................................................................ tia, Alvin -- View this message in context: http://inkscape.13.x6.nabble.com/unable-to-compile-0-92-x-rev-15268-on-Wind… Sent from the Inkscape - Dev mailing list archive at Nabble.com.

3 12

Re: [Inkscape-devel] [Inkscape-translator] Fwd: Inkscape 0.92pre4 released
by Bryce Harrington 21 Dec '16

21 Dec '16

On Mon, Dec 19, 2016 at 10:05:12PM +0200, Yuri Chornoivan wrote: > > Yes, they added some strings - and those are especially important as > > they concern the document conversion between 0.91 and 0.92 (units change > > to match CSS specification). Users who are presented with an English > > message might find this even more difficult to decide than in their > > native language. > > > > Could someone update the po files in the Inkscape 0.92.x repo, please? > > > > Regards, > > Maren > > Hi, > > Some relatively new strings in 0.92.x branch are actually untranslatable due > to such called "string puzzles": > > http://bazaar.launchpad.net/~inkscape.dev/inkscape/0.92.x/view/head:/share/… > > inkex.errormsg(_("Side Length 'a' (" + unit + "): " + str( params[0][0] ) )) > inkex.errormsg(_("Side Length 'b' (" + unit + "): " + str( params[0][1] ) )) > inkex.errormsg(_("Side Length 'c' (" + unit + "): " + str( params[0][2] ) )) > > extracts as > > Side Length 'a' ( > Side Length 'b' ( > Side Length 'c' ( > > That is not what expected. Good point. There are probably other instances like this where variables are being included in the translatable. I would guess the proper way to do it would be something like: inkex.errormsg(_("Side Length 'a'") + " (" + unit + "): " + str( params[0][0] ) ) > Can this be fixed before the release and the last update before the string > freeze? We're already far into string freeze, and actually very close to final freeze. This particular issue is just an error message printed to the console for one of the extension programs, so the severity of having it untranslated seems quite low. I would suggest filing a bug report to seek getting it fixed in trunk for future releases. Thanks, Bryce > Thanks in advance for your answers. > > Best regards, > Yuri > > > > > Am 19.12.2016 um 18:27 schrieb Sylvain Chiron: > > > According to the message below, it’s still possible to submit > > > translations for 0.92. > > > > > > Kind regards, > > > > > > Sylvain > > > > > > > > > -------- Message transféré -------- > > > Sujet : [Inkscape-devel] Inkscape 0.92pre4 released > > > Date : Sun, 18 Dec 2016 22:50:03 -0800 > > > De : Bryce Harrington <bryce@...961...> > > > Pour : inkscape-devel@...6... > > > > > > The 0.92pre4 source package has been released and can be downloaded > > > > > > from Launchpad: > > > https://launchpad.net/inkscape/0.92.x/0.92pre4 > > > > > > […] > > > > > > Please try to avoid making any further changes on the 0.92.x tree - > > > consider it in final freeze before release. The one exception being > > > translations - the mesh gradient changes were allowed to break string > > > freeze, so due to that we'll be giving permission to translators for > > > breaking this final freeze. > > > > > > […] > > > > > > Thanks, > > > Bryce > > > ------------------------------------------------------------------------------ > Developer Access Program for Intel Xeon Phi Processors > Access to Intel Xeon Phi processor-based developer platforms. > With one year of Intel Parallel Studio XE. > Training and support from Colfax. > Order your platform today.http://sdm.link/intel > _______________________________________________ > Inkscape-translator mailing list > Inkscape-translator(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-translator

4 4

Text tool confusion
by Maren Hachmann 21 Dec '16

21 Dec '16

Hi again, I've just tried out the most recent revision (0.92.x r15273, compiled on Linux Mint 18, 64bit), and I've got a couple of questions about the line height / font size settings. In a new document I made a new text (normal one, consisting of text and tspans for each line, by clicking). - The first thing I noticed was that the button 'set lineheight on part of selection' was enabled by default. I thought the 'default' is rather that one sets the line height for the whole text, and that setting it for single spans is more of a 'special designer feature' that I wouldn't ever need (sorry...). - Then I noticed the hover text of the button, which refers to 'part of selection' - wouldn't that set the line height for the *whole* selection, hopefully? (important for translation, too...) - Now, whenever I change the lineheight of a text, this reenables that button (I had been looking for a way to enable it by clicking, or selecting something in vain before...), although I only want to change the lineheight for the whole text. When I then deactivate the button, the lineheight switches back to the default line-height, unsetting the line height for the whole text. It does seem to change the lineheight style property for the whole text object in the xml, but it also does so for each span inside, if nothing is selected. I expected it would only do that globally, and the tspans inside inherit. Is it intended that the button self-activates when there is no selection but the line-height is changed? How do I set the line-height for the whole non-flowed text, without setting it for each span inside? Is that even possible (after text creation, if I set it before starting to write, then it works only on the main object, probably because the rest doesn't exist yet...). How can I keep the lineheight of a span, while still changing the lineheight for the whole object? (They get lost when I change the setting without having selected anything...) For flowed texts, the feature seems to work a tiny bit more in line with my expectations. Only, when I set a line-height for a span, and then change the line-height for the whole object afterwards, the setting for the span seems to be lost. I'd have expected it to stay until I remove it, even if its effect would not be visible. - The first line height I got in a new document (default template for German, so mm) was something like 55 mm. This was not what I had in my text tool's preferences settings (last used style, and I didn't have any line-height values like that). In 0.91, it's a unitless 1.2. In a flowed text in 0.92pre, it starts with 1000% (corresponding to 21mm). Could the default rather be set to a unitless 1.2 or something more reasonable? - Why is the font size shown in the text tool's toolbar a different one than the one in the XML (both say they're in px)? I only have two font sizes in the document, and no transforms, so shouldn't they be the same? Is maybe a different unit used for displaying the value? It looks correct in Firefox, and there is no unit field for the font size. The ratio is 5.33333, btw. (tool bar size : xml size). In 0.91, both values match. In my preferences, the unit for font size is px. - The font size field seems to have lost its scroll sensitivity. Changing a font size is only possible by typing or selecting, no longer by scrolling when hovering over the field, which I find rather painful. Could someone please bring that ability back? Sorry for the length of this. I wasn't sure if all of this merits a bug report, or if it's maybe even intended (but if it is, it's extremely confusing...). Regards, Maren

1 0

Re: [Inkscape-devel] [Inkscape-docs] Website: Bad Gateway and server errors, even on login
by Martin Owens 20 Dec '16

20 Dec '16

On Mon, 2016-12-19 at 16:36 +0100, Jabier Arraiza wrote: > Not sure if undertand but if help, I still couldent upload a image. Looks like the webserver has run out of space :-( 30GB used up, 9GB on logs, 13GB on media files. It'll need some cleaning. Martin,

5 6

Re: [Inkscape-devel] [Inkscape-translator] Fwd: Inkscape 0.92pre4 released
by Maren Hachmann 20 Dec '16

20 Dec '16

Yes, they added some strings - and those are especially important as they concern the document conversion between 0.91 and 0.92 (units change to match CSS specification). Users who are presented with an English message might find this even more difficult to decide than in their native language. Could someone update the po files in the Inkscape 0.92.x repo, please? Regards, Maren Am 19.12.2016 um 18:27 schrieb Sylvain Chiron: > According to the message below, it’s still possible to submit > translations for 0.92. > > Kind regards, > > Sylvain > > > -------- Message transféré -------- > Sujet : [Inkscape-devel] Inkscape 0.92pre4 released > Date : Sun, 18 Dec 2016 22:50:03 -0800 > De : Bryce Harrington <bryce@...961...> > Pour : inkscape-devel@...6... > > The 0.92pre4 source package has been released and can be downloaded > from Launchpad: > > https://launchpad.net/inkscape/0.92.x/0.92pre4 > > […] > > Please try to avoid making any further changes on the 0.92.x tree - > consider it in final freeze before release. The one exception being > translations - the mesh gradient changes were allowed to break string > freeze, so due to that we'll be giving permission to translators for > breaking this final freeze. > > […] > > Thanks, > Bryce > > ------------------------------------------------------------------------------ > Developer Access Program for Intel Xeon Phi Processors > Access to Intel Xeon Phi processor-based developer platforms. > With one year of Intel Parallel Studio XE. > Training and support from Colfax. > Order your platform today.http://sdm.link/intel > _______________________________________________ > Inkscape-translator mailing list > Inkscape-translator(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-translator >

2 1

Fwd: Conversion between text line heights modes now works fine !
by ivan louette 18 Dec '16

18 Dec '16

Conversion from a text line height mode to another one now works fine with recent changes ! I can now convert a text block line height from % mode to unit defined modes without having to re-adjust anything. Kubuntu 14.04 Thanks a lot ! ivan

1 0

Re: [Inkscape-devel] Website Feedback
by Martin Owens 14 Dec '16

14 Dec '16

On Wed, 2016-12-14 at 21:21 +0000, Anonymous User wrote: > I am trying to download Inkscape onto 15 chrome books but it says > that Inkscape is only available through roll app and is going to > charge $8/month. As to my understanding, Inkscape is free and I have > had no problem downloading the program to my macbook and a PC > computer. Is there any way that we are able to receive a discount > from that $8/month for 15 students (Total $720 for 15 students for 6 > months)? We are working on a graphic designing project and all of the > students only have chrome books. Please let me know what the next > steps would include. Thank you. Dear Joreev, Inkscape is free. Looking into this roll-app, it's a service that runs the program on a server in the cloud and when they offer you Inkscape, what you're paying for is that cloud based service and not Inkscape itself. We certainly have never gotten any money from roll-app or support. It's the chromebooks that are the problem. These are devices that deliberately stop the owner from having real freedom to run what ever programs they wish. It is the same story for Apple iPads and it seriously upsets me. Google's argument is that a chromebook is ONLY for websites, not for programs. When they offer 'apps' they're really just cleverly packaged websites. So you don't need to have any ability to install your own programs. To do this properly, you'd have to use something like Crouton to install Ubuntu on the computers. Once you have an operating system on them, you can install Inkscape for free within that. but of course, this will require, permission, technical skill and patience to do for all the machines you have. You may have to conclude that Inkscape is not available for your chromebooks. Sorry I don't have any better advice. Best Regards, Martin Owens Volunteer Website Administrator

1 0

Re: [Inkscape-devel] Website Feedback
by Martin Owens 14 Dec '16

14 Dec '16

On Wed, 2016-12-14 at 08:24 +0000, Website User wrote: > Hello, Am i allowed to make Inkscape tutorials video (with ads) ? > I'm planning to make some videos. For now i use Inkscape as my > project base. Thank in advance. Dear Thank in advance, You can make inkscape tutorials using inkscape or featuring inkscape. Inkscape is Free and Open Source, which means you are guaranteed fundamental freedom to make things with, and of it. This includes making money from ads. You may even be so bold as to sell Inkscape itself to your friends ;-) but few people do. If you'd like to display the Inkscape Logo, we do have a trademark policy which is basically that you should try and not represent the project or claim endorsement etc. Read more about it here: https://inkscape.org/en/about/trademark-policy/ Good luck with your videos. Best Regards, Martin Owens Volunteer Inkscape Website Administrator

1 0

Re: [Inkscape-devel] Fwd: You have a new Clipart Comment
by Maren Hachmann 12 Dec '16

12 Dec '16

You could just move it to inkscape.org, into your gallery there. Only make sure you select the correct licence, and give attribution. The licence allows to make derivations, and the trademark policy (basically) says that as long as it's not misrepresenting the project, it's okay (more details here: https://inkscape.org/en/about/trademark-policy/). Maren Am 12.12.2016 um 19:39 schrieb Victor Westmann: > Ok. I'll erase it from there. Thanks for clearing it up for me. > > > On Dec 12, 2016 9:40 AM, "Maren Hachmann" <maren@...3165... > <mailto:maren@...3165...>> wrote: > > Victor seems to be referring to this one: > https://openclipart.org/detail/263647/inkscape-webstore > <https://openclipart.org/detail/263647/inkscape-webstore> > Open Clipart is purely public domain, so if the Inkscape Logo is there, > people may think it's PD, too. The logo is CC-By-SA, and trademarked. > > Maren > > Am 12.12.2016 um 18:06 schrieb Ted Gould: > > > > I don't see the Inkscape logo in that image, but yes it is > trademarked. > > For the most part you can use the Inkscape logo in anything you > want as > > long as you aren't trying to use it to confuse another product with > > Inkscape. So don't make your own vector editor and call it > lnkscape and > > use the logo :-) > > > > When we trademarked the logo we were really careful with the terms of > > use, we realize that Inkscape community is made up of a ton of > artists. > > We really wanted them to be able to use the logo in their art if > they wish. > > > > Ted > > > > On Mon, 2016-12-12 at 08:50 -0800, Victor Westmann wrote: > >> > >> I made a small tribute to inkscape. But I used the logo. > >> > >> Do I need to delete it? > >> > >> Logo is ttademark right? And not public domain right? > >> > >> ---------- Forwarded message ---------- > >> From: "Openclipart" <love@...3456... > <mailto:love@...3456...> <mailto:love@...3456... > <mailto:love@...3456...>>> > >> Date: Dec 12, 2016 7:59 AM > >> Subject: You have a new Clipart Comment > >> To: <victor.westmann@...400... <mailto:victor.westmann@...400...> > <mailto:victor.westmann@...400... <mailto:victor.westmann@...400...>>> > >> Cc: > >> > >> j4p4n said: > >> > >> Is this public domain_? > >> > >> This is for a comment on the clipart at : > >> https://openclipart.org/detail/237886 > <https://openclipart.org/detail/237886> > >> <https://openclipart.org/detail/237886 > <https://openclipart.org/detail/237886>> > >> Love your favorite clipart & artists. > >> Try the New Openclipart for Android : > >> http://openclipart.org/for/android > <http://openclipart.org/for/android> > <http://openclipart.org/for/android > <http://openclipart.org/for/android>> > >> > ------------------------------------------------------------------------------ > >> Check out the vibrant tech community on one of the world's most > >> engaging tech sites, SlashDot.org! http://sdm.link/slashdot > >> _______________________________________________ > >> Inkscape-devel mailing list > >> Inkscape-devel(a)lists.sourceforge.net > <mailto:Inkscape-devel@lists.sourceforge.net> > >> <mailto:Inkscape-devel@lists.sourceforge.net > <mailto:Inkscape-devel@lists.sourceforge.net>> > >> https://lists.sourceforge.net/lists/listinfo/inkscape-devel > <https://lists.sourceforge.net/lists/listinfo/inkscape-devel> > > > > > > > ------------------------------------------------------------------------------ > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > > > > > > > > _______________________________________________ > > Inkscape-devel mailing list > > Inkscape-devel(a)lists.sourceforge.net > <mailto:Inkscape-devel@lists.sourceforge.net> > > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > <https://lists.sourceforge.net/lists/listinfo/inkscape-devel> > > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel(a)lists.sourceforge.net > <mailto:Inkscape-devel@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > <https://lists.sourceforge.net/lists/listinfo/inkscape-devel> >

1 0

Fwd: You have a new Clipart Comment
by Victor Westmann 12 Dec '16

12 Dec '16

I made a small tribute to inkscape. But I used the logo. Do I need to delete it? Logo is ttademark right? And not public domain right? ---------- Forwarded message ---------- From: "Openclipart" <love@...3456...> Date: Dec 12, 2016 7:59 AM Subject: You have a new Clipart Comment To: <victor.westmann@...400...> Cc: j4p4n said: Is this public domain_? This is for a comment on the clipart at : https://openclipart.org/ detail/237886 Love your favorite clipart & artists. Try the New Openclipart for Android : http://openclipart.org/for/android

3 2

Inkscape, spotted in a production environment
by C R 09 Dec '16

09 Dec '16

https://youtu.be/lfmrvxB154w?t=3m11s -C

2 1

Re: [Inkscape-devel] Survey Published!
by Victor Westmann 08 Dec '16

08 Dec '16

I don't understand why a simple survey bother people so much. Really. Lgbtq is how some people identify themselves. It is relevant to understand where people are from. Again, the survey is independent and unofficial. If you're not happy go ahead and create yours. This is to check some demographics, age, country and all that is written in the survey. I care. To me this is important. If you really dislike the idea is fine. Just don't fill the survey. Simple as that. Giving random answers is not very clever. Just don't answer it. This subject is too small and unimportant to have such attention don't you think so? On Dec 4, 2016 3:03 PM, "Tobias Ellinghaus" <houz@...173...> wrote: > Am Sonntag, 4. Dezember 2016, 15:48:49 CET schrieb brynn: > > [...] > > > I think at best, we can call this information "anecdotal". It can't > really > > be used to guide development or solve problems. I'm sorry to be so > > negative, and I would love it if someone can show me a positive side. > > Besides that I also have a hard time seeing why some of the questions are > relevant. Age, gender (when did LGBTQ become a gender?), country? Who > cares? I > left those blank or gave random answers as they are not relevant. > > > All best, > > brynn > > Tobias > > [...] > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > >

5 4

Re: [Inkscape-devel] [Fwd: Animation LPE In Inkscape]
by Jabier Arraiza 08 Dec '16

08 Dec '16

Hi Josh, welcome to inkscape development! Try to reply inline: (Not english) On Wed, 2016-12-07 at 20:10 +0100, Jabier Arraiza wrote: > -------- Forwarded Message -------- > > Date: Tue, 06 Dec 2016 19:02:20 -0600 > Subject: [Inkscape-devel] Animation LPE In Inkscape > To: inkscape-devel(a)lists.sourceforge.net > From: sup_dude00 <sup_dude00@...36...> > > Hi all, > > > > > > > > My name is Josh (bobsicle0 elsewhere on the internet), and I've > > been > > using inkscape for nearly 3 years now. Some time ago I was thinking > > about SVG animation with SMIL, and what tools were available to > > work > > with SVG animation. I remembered that inkscape didn't have > > animation > > capabilities. > > > > > > > > Recently I had a bit of an inspiration that animation capabilities > > (even crudely) might be somewhat straightforward to add as an LPE > > in > > inkscape. I realize that it will probably take more than a LPE to > > actually display SVG animations in inkscape, but for now, that's > > not > > my intent. My intent is to allow the user access to the SVG/SMIL > > animation tags through a LPE. > > > > > > > > For a visual indication of what the animation will look like, the > > element being animated could draw a path to show the motion of the > > node/object's motion rather than actually showing the animation > > (showing the actual animation would presumably require modification > > of inkscape's SVG rendering). The drawn motion path would be > > similar > > to what you see in the Bend and Envelope Deform LPEs, but instead > > drawn to show the path of motion. > > > > > > > > I'm brand new to inkscapes code structure, and what is/isn't > > possible > > with LPEs. I've dug around as much as I could on the wiki and > > elsewhere and read the stuff about inkscape development. So far, > > I've > > done the following: > > > > bazaar checkout of inkscape's trunk, > > > > sucessfully built inkscape in the inkup VM enviroment, > > > > renamed a copy of lpe-skeleton.cpp/.h to lpe-animation.cpp/.h, > > > > renamed the appropriate things inside lpe-animation.cpp/.h, > > > > modified the necessary files (as per the wiki) to register the new > > LPE in inkscape, > > > > added a few new test parameters to lpe-animation.cpp to make sure > > they would show up as expected in the LPE dialog, > > > > and finally sucessfully recompiled. > > > > > > > > Everything is working just fine. From this point on though, I'm > > pretty stuck, and I have a few questions. > > > > > > > > Is it possible to modify SVG element tags from within a LPE, such > > as > > adding "animate" or "animateTransform"? > > Yes but maybe need to modify inkscape to allow this attributes > > > > What's the next step to take? Really what I mean is, is there a > > list > > of things that can be modified about the path that is passed in to > > the LPE and how can those things can be modified in code You cam modify the element, also you also can modyfy or add other svg tags as in meassure line LPE and the not merged branch mirror_improvements (in dev) > > > > Is there any other advice you'd like to give? I'm a very open > > person > > when it comes to criticism and recommendations. I think we need a low level way than a LPE to handle animation. Also need a SMIL/CSS parser, we currently use one for CSS but dont know his state on animation. Anyway if you want to try, think for the same price of show a direction you can move the element inside inkscape. > > > > > > I appreciate any help you guys can offer. I do a lot of LPE works and I can help you in the process. Ping me when you want! IRC #inkscape-devel -> jabiertxof Jabiertxo.

3 2

Re: [Inkscape-devel] Animation LPE In Inkscape
by sup_dude00 07 Dec '16

07 Dec '16

Thanks, brynn. I'm excited for this project as well!You bring up a good point about google moving to deprecate SMIL. That must be frustrating for those who produce content using SMIL. I suppose if it's possible, I could add some sort of CSS fallback to the animation, to make it work for chrome (and IE?) users.Regards,Josh (bobsicle0) -------- Original message --------From: brynn <brynn@...3133...> Date: 12/6/16 10:11 PM (GMT-06:00) To: sup_dude00 <sup_dude00@...36...>, inkscape-devel(a)lists.sourceforge.net Subject: Re: [Inkscape-devel] Animation LPE In Inkscape Hi Josh, I'm not a developer, but I just wanted to say Welcome to the Community! Also, I can say that what you're proposing sounds exciting, and I hope it can be done. Because at least one browser has proposed ending support for SMIL, it would be awesome to (be able to) show its usefulness, to hopefully prevent being dropped. Unfortunately, I can't help with any of your technical questions. But I'm sure you'll get plenty of response soon enough. Welcome aboard and good luck with your work! All best, brynn ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today.http://sdm.link/xeonphi _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

1 0

Animation LPE In Inkscape
by sup_dude00 07 Dec '16

07 Dec '16

Hi all, My name is Josh (bobsicle0 elsewhere on the internet), and I've been using inkscape for nearly 3 years now. Some time ago I was thinking about SVG animation with SMIL, and what tools were available to work with SVG animation. I remembered that inkscape didn't have animation capabilities. Recently I had a bit of an inspiration that animation capabilities (even crudely) might be somewhat straightforward to add as an LPE in inkscape. I realize that it will probably take more than a LPE to actually display SVG animations in inkscape, but for now, that's not my intent. My intent is to allow the user access to the SVG/SMIL animation tags through a LPE. For a visual indication of what the animation will look like, the element being animated could draw a path to show the motion of the node/object's motion rather than actually showing the animation (showing the actual animation would presumably require modification of inkscape's SVG rendering). The drawn motion path would be similar to what you see in the Bend and Envelope Deform LPEs, but instead drawn to show the path of motion. I'm brand new to inkscapes code structure, and what is/isn't possible with LPEs. I've dug around as much as I could on the wiki and elsewhere and read the stuff about inkscape development. So far, I've done the following: bazaar checkout of inkscape's trunk, sucessfully built inkscape in the inkup VM enviroment, renamed a copy of lpe-skeleton.cpp/.h to lpe-animation.cpp/.h, renamed the appropriate things inside lpe-animation.cpp/.h, modified the necessary files (as per the wiki) to register the new LPE in inkscape, added a few new test parameters to lpe-animation.cpp to make sure they would show up as expected in the LPE dialog, and finally sucessfully recompiled. Everything is working just fine. From this point on though, I'm pretty stuck, and I have a few questions. Is it possible to modify SVG element tags from within a LPE, such as adding "animate" or "animateTransform"? What's the next step to take? Really what I mean is, is there a list of things that can be modified about the path that is passed in to the LPE and how can those things can be modified in code? Is there any other advice you'd like to give? I'm a very open person when it comes to criticism and recommendations. I appreciate any help you guys can offer. Regards, Josh (bobsicle0)

2 1

bzr commit access
by Alexander Brock 06 Dec '16

06 Dec '16

Hi, I made some changes to Inkscape which were merged: Recursive unlinking of clones: https://code.launchpad.net/~inkscape+alexander/inkscape/clones/+merge/310065 Moving boolean operation code to the ObjectSet class: https://code.launchpad.net/~inkscape+alexander/inkscape/move-boolops/+merge… Node angle measurement: 14213 [merge] committer: Krzysztof Kosiński <tweenk.pl@...400...> branch nick: trunk timestamp: Wed 2015-06-24 22:55:25 +0200 message: Merge node angle measurement by Alexander Brock I re-wrote the offset_cubic code which computes a cubic bezier with constant distance to a given cubic bezier: https://code.launchpad.net/~inkscape+alexander/inkscape/offset-cubic-improv… It got approved by Jabiertxof and I'd like to merge it, can I have commit access to do so? Best Regards, Alexander

3 3

imagemagick-7
by Ken Moffat 05 Dec '16

05 Dec '16

There was a report to BLFS that not all packages which could use ImageMagick recognized the changes in IM7. So we reverted to IM6. Now that I've had time to look at this, inkscape is a major package in this category. ImageMagick-7 has changed a lot of things. And as somebody who uses ImageMagick tools, I don't want to be stuck with the old version. Can I fix that ? Probably not, particularly with the move to cmake (I have no idea how to deal with different versions of a package in cmake, unlike configure scripts where there are usually things to copy). Perhaps I can start to take a look when I get some time. But what I will need is an idiot's guide to what IM brings to inkscape, so that in the (unlikely) event that I produce a patch I can test it to see if it works. For the moment, all I know is that inkscape can use IM - but the details/benefits elude me. Any pointers, pretty please ? ĸen -- `I shall take my mountains', said Lu-Tze. `The climate will be good for them.' -- Small Gods

3 4

Where is macOS built for Inkscape 0.92pre?
by Atsuyoshi Suzuki 05 Dec '16

05 Dec '16

Hi, all. Is not a development binary (0.92pre) for macOS available yet? Is there no plan to provide a development package for macOS in the first place? Thanks. -- Atsuyoshi Suzuki

2 1

Survey Published!
by Victor Westmann 04 Dec '16

04 Dec '16

Ok! So against all odds I went ahead and published my personal, independent and unofficial Inkscape survey! I tried LimeSurvey, SurveyMonkey and some others but they all had annoying limitations (needed to be a subscriber, accepted only 100 answers, allowed me to write only 10 questions (or so)) and those services were not working out for me. So I went ahead and published 9 questions Inkscape users should answer to fill my own survey. Don't you guys be worried I'll take all the onus to process and show this data later. I MADE SURE TO STATE THAT THE SURVEY IS INDEPENDENT AND UNOFFICIAL. So, again, no worries. The name of the community was not used by me by any means. :-) I published in Twitter, Facebook communities (a few) and Google Plus. Please take a look: https://goo.gl/forms/ttE6iB2IE7VCqtnb2 The reason I'm using Google Forms is because it's easy for people to submit their answers, questions look good and all the survey takes less than 1 minute to answer. Hope you all have an amazing weekend! --Victor Westmann

5 8

missed meeting
by brynn 03 Dec '16

03 Dec '16

Hi Friends, Sorry for missing the board meeting yesterday. Since it was only announced a day ahead, and I happened not to be online Thursday, I just didn't see it in time. Looking at http://wiki.inkscape.org/wiki/index.php/Board_Meetings it doesn't indicate that the meeting is held (a) monthly (30 days) or (b) every 4 weeks, or (c) first Friday of every month, or (d) other. It just gives the date of the next meeting. If we could set it up on any kind of regular routine, we could individually set up reminders locally. This might be even better than posting a custom time/date for me (as well as doctormon). Because I might forget to look at that page. But if I have a reminder popping up on my own desktop, I won't miss that! But the best reason for setting a regularly occuring meeting time/date, is that no one has to remember to remind everyone else. I've read the transcript, and just wanted to fill in a couple of issues about the forum. First, regarding the suggestion to use HostGator as a host (I guess was suggesting because it could be no cost), if I typed 10 lines of no-no-no-no-no-no-no- it wouldn't be enough! Correct, nothing is overtly blocking on the forum project. While OSUOSL has still not given us a firm "yes" or "no", we've been operating as if it's going to be yes (while still looking at other options). Specifically we're waiting for 1 or 2 things. Technically, OSUOSL has asked me for the size of the attachments folder (the one that's outside of the DBs), which I've asked Courtney for (twice now, and I guess it's time for a 2nd reminder). Presumably they need that before they could give us a firm "yes" or "no" on hosting the forum. However, they seem to be having some internal problems (personnel-wise, I think), and they seem just as happy to wait as long we're content to wait. It would be nice if Courtney could give us the first set of DBs and whatever other files are needed, so we could practice installing. As soon as he does that, we can inform OSUOSL about the size of that file (because that file will be included in what Courtney sends us). However, I suspect that OSUOSL can get a general enough idea about how much space we'll need, without knowing the specific size of that file. I think it's more their internal issues that is holding up the "yes" or "no". And the way it's going with Courtney's response time, we might get an answer from OSUOSL before we get the first backups. And that wouldn't be a bad thing, because then Courtney could securely load everything directly. My next action item is to send Courtney another reminder, which I'll do shortly. Mihaela, my server has just been upgraded, and now I could give you your own access (without sharing mine). You might be able to figure out how to give him secure access to a single directory. I can see how to give him FTP access to a single dir, but I still think there is a need for security (SFTP or SSH) and I don't see that. But you might understand something that I don't. Plus, my host gave me an OK on setting up a new domain or sub-domain, so we could even test it live. Although if you'd still rather do it yourself locally, that's fine too. But I wanted to mention the new options. Apologies for missing the meeting, brynn

1 0

Website Data Use
by Martin Owens 03 Dec '16

03 Dec '16

Here is the latest inkscape.org cache use between 2014 and November 2016. https://inkscape.org/en/~doctormo/%E2%98%85fastly-cache-use-2014-to-201 6 You can see we use 40TB per month, an awful lot. Best Regards, Martin Owens

3 3

Re: [Inkscape-devel] Winner: About screen contest
by C R 01 Dec '16

01 Dec '16

An option to turn it off in preferences would be fine with me, but it auto-disappears when the GUI loads... So I'm not getting why folks think it would be a burden? It's not like it would add any notable time to the startup. Maybe a fraction of a second? Part of good UX is to let the user know what's happening if there is a wait involved. The faster you show the user something, the faster the program feels. This isn't just some tradition, and it's certainly not just a Windows thing. :) My 2p. -C On 1 Dec 2016 9:34 pm, "Bryce Harrington" <bryce@...961...> wrote: > > On Thu, Dec 01, 2016 at 07:53:48PM +0100, Tobias Ellinghaus wrote: > > Am Donnerstag, 1. Dezember 2016, 13:36:13 CET schrieb Martin Owens: > > > On Thu, 2016-12-01 at 14:23 +0000, C R wrote: > > > > Will this graphic be featured on the loading screen as well (when > > > > it's implemented)? > > > > > > Yes. > > > > > > The about screen graphic will also be featured on the inkscape.org home > > > page and on some merchandise in the shop. The shop stuff will have to > > > be tested to get it right. > > > > How long does Inkscape take to start for you? Here it's coming up basically > > instantaneous. So I wonder if a loading screen is really needed, or if the > > work to add that should maybe be spent in fixing slowness in startup instead, > > like caching icons, querying fonts in a separate thread, ... > > Inkscape also starts up acceptably fast for me on my system, and > I would not like to see it burdened with a startup screen. But I know > it is considered traditional and fairly common on Windows. I am -1 to > adding it in general (I'd rather see attention going into speeding up > the load), but would be open to a compromise of having a build option to > enable/disable it, and leave it to packagers to decide whether to have > it or not for the platform in particular. > > Bryce > > > ------------------------------------------------------------------------------ > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel

1 1

Winner: About screen contest
by Martin Owens 01 Dec '16

01 Dec '16

Thanks for everyone's vote, the results are as follows: 1. https://inkscape.org/en/~artelnjeru01/%E2%98%85about-092-2-good (#4) 2. https://inkscape.org/en/~Mikhael/%E2%98%85space-inkscape (#1) 3. https://inkscape.org/en/~artelnjeru01/%E2%98%85about-092-11 (#2) 4. https://inkscape.org/en/~bajinra/%E2%98%85draw-freely-in-sticker-sty le (#3) Congratulations to artelnjeru01! Please pass around the good news to all. The entrants this year were really VERY good, even those that didn't make this round of voting. I'm going to leave the committing of the winning entry to the repository to someone else. If you'd like to do this job, please download the svg directly from the above link. We can select a developer's about screen for trunk too, any of the entrants can be considered and I don't think we need a vote on that. Or we can keep the machine robot we have now, both are good. Best Regards, Martin Owens Voting details, instant runoff vote: { 'tie_breaker': ['4', '2', '3', '1'], 'winner': '4', 'voters': 16, 'quota': 9, 'candidates': set(['1', '3', '2', '4']), 'rounds': [ { 'tallies': {'1': 5.0, '3': 3.0, '2': 3.0, '4': 5.0}, 'tied_losers': set(['3', '2']), 'loser': '3' }, { 'tallies': {'1': 6.0, '2': 3.0, '4': 7.0}, 'loser': '2' }, { 'tallies': {'1': 6.0, '4': 9.0}, 'winner': '4' } ] }

7 12

Inkscape Board Meeting Nov 4th
by Bryce Harrington 01 Dec '16

01 Dec '16

Meeting time this Friday, Nov 1st at noon Pacific in #inkscape-devel. Everyone's more than welcome to attend! http://wiki.inkscape.org/wiki/index.php/Board_Meetings Agenda: * SVG 2 news [Tav] * Merchandise sales [bryce] - Spreadshirt account's ready to go - Next need shirt designs * Sponsorship levels followup [bryce] * Inkscape forum followup SFC has been kind enough to establish the Spreadshirt account for us; next step is to arrange login access for administrators. If this sounds interesting please come to the meeting, or contact me directly. Bryce

7 13

Re: [Inkscape-devel] Inkscape Board Meeting Dec 2nd
by C R 01 Dec '16

01 Dec '16

Possibly, though I think we should rather not make a contest for something as permanent as this. Don't mind collecting renditions, but having a contest implies a winner will be chosen from the things submitted, and feelings might get hurt if no one is chosen. So I'd say let's wait until we have (internally), something we can live with, and then it can go in with the other submissions, so at least we have a fall back just in case. -C On Thu, Dec 1, 2016 at 10:38 AM, Marker <info@...2893...> wrote: > I think, if web team is not exausted, it could be cool a Inky contest. > > On Thu, 2016-12-01 at 08:05 +0000, C R wrote: >> I don't have the inky mockups done for this one. I'll try to have >> them >> done by the next one. >> Thanks for the patience. Busy time of year for me! >> -C >> >> On Thu, Dec 1, 2016 at 7:15 AM, Bryce Harrington >> <bryce@...961...> wrote: >> > The Inkscape Board will hold its monthly meeting this Friday, Dec >> > 2nd at >> > noon Pacific in #inkscape-devel. Any community member is welcome >> > to >> > attend! >> > >> > http://wiki.inkscape.org/wiki/index.php/Board_Meetings >> > >> > Agenda: >> > * Merchandise sales [bryce] >> > * Sponsorship levels followup [bryce] >> > * Inkscape forum followup >> > * Mesh gradient feature followup [tav] >> > >> > Bryce >> > >> > ----------------------------------------------------------------- >> > ------------- >> > _______________________________________________ >> > 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

2 2

Re: [Inkscape-devel] Inkscape Board Meeting Dec 2nd
by Jabier Arraiza 01 Dec '16

01 Dec '16

Anyway is good be sure we have one thats feet the min requeriments. Maybe this one can be the base, exposing the SVG and the contest is fork it. Cheers, Jabier On Thu, 2016-12-01 at 12:01 +0100, Marker wrote: > Maybe we can do a contest with 8 2turn winers to get more options for > final result. > > On Thu, 2016-12-01 at 10:47 +0000, C R wrote: > > Possibly, though I think we should rather not make a contest for > > something as permanent as this. > > Don't mind collecting renditions, but having a contest implies a > > winner will be chosen from the things submitted, and feelings might > > get hurt if no one is chosen. > > So I'd say let's wait until we have (internally), something we can > > live with, and then it can go in with the other submissions, so at > > least we have a fall back just in case. > > > > -C > > > > On Thu, Dec 1, 2016 at 10:38 AM, Marker <info@...2893...> wrote: > > > I think, if web team is not exausted, it could be cool a Inky > > > contest. > > > > > > On Thu, 2016-12-01 at 08:05 +0000, C R wrote: > > > > I don't have the inky mockups done for this one. I'll try to > > > > have > > > > them > > > > done by the next one. > > > > Thanks for the patience. Busy time of year for me! > > > > -C > > > > > > > > On Thu, Dec 1, 2016 at 7:15 AM, Bryce Harrington > > > > <bryce@...961...> wrote: > > > > > The Inkscape Board will hold its monthly meeting this Friday, > > > > > Dec > > > > > 2nd at > > > > > noon Pacific in #inkscape-devel. Any community member is > > > > > welcome > > > > > to > > > > > attend! > > > > > > > > > > http://wiki.inkscape.org/wiki/index.php/Board_Meetings > > > > > > > > > > Agenda: > > > > > * Merchandise sales [bryce] > > > > > * Sponsorship levels followup [bryce] > > > > > * Inkscape forum followup > > > > > * Mesh gradient feature followup [tav] > > > > > > > > > > Bryce > > > > > > > > > > ------------------------------------------------------------- > > > > > ---- > > > > > ------------- > > > > > _______________________________________________ > > > > > 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 > > > > ------------------------------------------------------------------- > > ----------- > > _______________________________________________ > > Inkscape-devel mailing list > > Inkscape-devel(a)lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/inkscape-devel

1 0

Including BSD-Licenced code in Inkscape
by Alexander Brock 01 Dec '16

01 Dec '16

Hi, TLDR: I want to include 3-clause BSD licenced code in Inkscape. I want to improve curve fitting in Inkscape. I was told that Inkscape uses the GSL for root finding etc. so I thought I might implement curve fitting using the headers <gsl/gsl_multifit_nlinear.h> This works but I'd like to improve it by providing derivatives to the solver instead of relying on numerical differentiation. I researched Autodiff tools and found that most require libraries which are difficult to build on windows. At work I use Ceres solver. I extracted the autodiff code (jet.h) from the source code and modified slightly so it works without futher dependencies. Ceres is licenced under the 3-clause BSD licence: http://ceres-solver.org/license.html May I include the modified source code in Inkscape? Best Regards, Alexander

5 6

Contest Results and Developer Voting
by Martin Owens 01 Dec '16

01 Dec '16

Dear developers, The about screen contest for 0.92 is complete and we have our three runner ups for us developers to choose from: https://inkscape.org/en/gallery/=about-screen-contest/contest-for-092+0 / Each of the three are marked as "Next Round", please email to the mailing list with your choices. Simply put your numbers in order of preference, so 3214 would mean 3 is my first choice, 2 is my second choice etc. You don't have to rank all numbers if you don't want to. You'll notice that I've chosen 4 items, this is because 1 and 3 are so similar and I wanted to give us a better choice. Thanks to all our artists and voters, I think this round has been really good. I actually voted for "Ngarai Sianok" and a lot of people loved "Freedom Machine" (see comments on those items). So I'll be adding a few of these to the website front page when 0.92 is released, to replace the current set of images. Best Regards, Martin Owens

19 53

Inkscape Shop
by Martin Owens 29 Nov '16

29 Nov '16

Dear Developers, We've been playing with the settings for the inkscape shop, the conservancy backed spreadshirt account. I'm looking for comments from others about the look of it and what kinds of things we've added to start. https://shop.spreadshirt.com/inkscape-shop/ There's a few restrictions with what we can do, for instance vector art doesn't support gradients / blur etc. But we'll keep playing with the settings to get a good result and then maybe order a few things to test. What do you think? Best regards, Martin Owens

8 20

Inkscape Shop Results
by Martin Owens 28 Nov '16

28 Nov '16

Dear all, I just got delivery of my inkscape items, one cup and one hat. The cup can be seen here: https://inkscape.org/en/~doctormo/%E2%98%85in kscape-cup-natural-setting It's a good cup, for a simple logo it doesn't justify the $15, but for a more complex artwork it might. The hat looks about as silly as you could imagine, my wife has denied me the right to post that picture. But at $28 it's the least likely product for us to have on the shop. Bryce has gotten a couple of t-shirts and I hope he posts a photo too with a review. There's someone else who ordered some items from Texas, we don't know who, but if that's you, we'd love for you to post a review when your items arrive. Best Regards, Martin Owens

4 3

Mesh gradient test and comment
by Nicolás Guarín-Zapata 28 Nov '16

28 Nov '16

Hello, I have tested the Mesh gradient tool and it works. Although the nodes and node handles should be differentiable as mentioned before (https://sourceforge.net/p/inkscape/mailman/message/35501606). I would also mention that it would be great if the "central" nodes can be group to a single node in the case of conic gradient. Of course, this won't be necessary when one is working with a ring and not a circle, but in some cases it might be useful (see HSV_mesh.png, where this proves useful). I attached a couple of images that I generated using the mesh gradient tool Best, -- Nicolás Guarín-Zapata PhD Student - Purdue University Computational Multi-Scale Material Modeling Lab https://engineering.purdue.edu/~zavattie/ Linux user #514760

2 1

Re: [Inkscape-devel] New Extension and video showcase
by C R 27 Nov '16

27 Nov '16

Looks awesome Jabier! I can see this being useful for cell-shading comics, and it masks the issue Inkscape has where a small gap is rendered between adjacent fill edges. Thanks for the demo! -C On 26 Nov 2016 10:25 pm, "Jabier Arraiza" <jabier.arraiza@...2893...> wrote: Hi all. I just do a tiny extension on inkscape.org extension page. The extension is called:stroke-color-as-fill and do this. But it bring posibilities to cool efects, so i do a large showcase video. At the start I add a show case to add Delaunay triangulation in 2 steps to any inkscape art. Also you can use after my extension to fix the rouding precission triangles. I try now to fix the problem with custom markers to alow using it in a saved document (middle of the video problem) Take acount you can use a base biger than ~40px to allow more resolution (more pieces,triangles...) -bus slowest- to the output https://inkscape.org/en/~jabiertxof/%E2%98%85stroke-color-as-fill Bye , Jabier. ------------------------------------------------------------ ------------------ _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-devel

1 0

New Extension and video showcase
by Jabier Arraiza 26 Nov '16

26 Nov '16

Hi all. I just do a tiny extension on inkscape.org extension page. The extension is called:stroke-color-as-fill and do this. But it bring posibilities to cool efects, so i do a large showcase video. At the start I add a show case to add Delaunay triangulation in 2 steps to any inkscape art. Also you can use after my extension to fix the rouding precission triangles. I try now to fix the problem with custom markers to alow using it in a saved document (middle of the video problem) Take acount you can use a base biger than ~40px to allow more resolution (more pieces,triangles...) -bus slowest- to the output https://inkscape.org/en/~jabiertxof/%E2%98%85stroke-color-as-fill Bye , Jabier.

1 0

Survey
by Victor Westmann 26 Nov '16

26 Nov '16

Hi Guys, I was just wondering if we could run a simple and quick survey to our users to get to know them better and to know what they know about the software and how much are they involved with the project (software and community), This is just a draft so improvements and thoughts are more than welcome: https://docs.google.com/spreadsheets/d/1CcV6rEYq5iIzZKkx_qPU6G5rp0O5D UM0EfQ3hD_Gt4o/edit?usp=sharing What do you guys think? This initiative took place inspired in the "State of JS" survey: http://stateofjs.com/2016/introduction/ Cheers! --Victor Westmann

6 9

Inkscape for embroidery
by Michael Soegtrop 26 Nov '16

26 Nov '16

Dear Inkscape Developers, I added a few features to Inkscape for use in embroidery, because the commercial tools available don't offer the artistic flexibility I want. I would like to have your opinion on if you think it makes sense to integrate such functionality into the Inkscape mainline, or if it would be too much of a stretch. It boils down to some LPEs and an export format. The commercial tool I have from Bernina (a Swiss sewing machine manufacturer) is based on Corel Draw. Below is a list of the additions I did / I am working on. Please let me know what you think about this. With these additions, Inkscape offers substantially more flexibility than affordable commercial SW (and affordable here means 500..1000$). Best regards, Michael 1.) Ways to fill an area with clusters of contours Inkscape already offers 2 path interpolation LPEs which allow this. I plan to add a 3rd one which creates a set of equidistant inset/outset paths. 2.) A way to connect sub path of a path into one continuous path I added an LPE to do this with various options of end interpolation. Maybe if I use bool-ops I need to extend it with some sort of sorting, cutting and auto reversing mechanism to keep the connections short. 3.) A way to cut a path into stitches (straight line segments) in a controlled way. I added an LPE to do this, but it is quite primitive as yet. 4.) Bool ops on paths because in embroidery you cannot simply hide an object below another one. I just added a bool-op LPE for this - needs some additional work to cut contours against a closed path. 5.) A tool to convert graphics output to some format an embroidery / sewing machines can read. I wrote an external tool to convert HPGL to a common embroidery format (stitch/DST), but could also integrate this into Inkscape. 6.) Maybe a tool to hide connections between path segments below filled areas. For a sewing machine it is quite complicated to do a "pen up" - it has to cut the threads, so one typically hides connection paths below some embroidery to avoid thread cutting. Currently I do this semi-manually. Doing this automatically might be quite complicated.

11 32

duplicate directories/files in 92pre3 on Windows
by alvinpenner 26 Nov '16

26 Nov '16

n Windows 10 I have installed Inkscape-0.92pre3-1-r15195.exe, 32 bit exe file. The directory listing for C:\Program Files (x86)\Inkscape\share\ is almost identical to the directory listing for C:\Program Files (x86)\Inkscape\share\inkscape\ that is, about 2/3 of the sub-directories are duplicated. not all the files are duplicated, but some are, for example here are a few files that show up twice: C:\Program Files (x86)\Inkscape\share>dir/s css* Volume in drive C is Acer Volume Serial Number is F465-C324 Directory of C:\Program Files (x86)\Inkscape\share\attributes 10/20/2016 04:55 PM 18,316 cssprops 10/20/2016 04:55 PM 3,413 css_defaults 2 File(s) 21,729 bytes Directory of C:\Program Files (x86)\Inkscape\share\inkscape\attributes 10/20/2016 04:55 PM 18,316 cssprops 10/20/2016 04:55 PM 3,413 css_defaults 2 File(s) 21,729 bytes .......................................................................... on Windows XP, I have unpacked Inkscape-0.92pre3.7z (32 bit 7-zip file) As far as I can tell, the 375 Python files in the directory E:\Inkscape-0.92pre3\inkscape\share\extensions are an exact duplicate of the 374 files in the directory E:\Inkscape-0.92pre3\inkscape\share\inkscape\extensions I don't remember seeing this before, don't know when it started. Cheers, Alvin -- View this message in context: http://inkscape.13.x6.nabble.com/duplicate-directories-files-in-92pre3-on-W… Sent from the Inkscape - Dev mailing list archive at Nabble.com.

2 3

Mac 0.92preX
by Jabier Arraiza 23 Nov '16

23 Nov '16

Anyone can share a prerelease on mac? Thanks in advance. Jabier.

1 0

Questions about building 0.92pre3
by Ken Moffat 22 Nov '16

22 Nov '16

I've now done a couple of builds and DESTDIR installs of 0.92pre3 : the dependencies (for gtk2) seem to be the same as for 0.91, at least on (BLFS-7.10)¹ x86_64 linux. But there are a few things which puzzle me - I really don't grok cmake, but at least inkscape now builds fine with a separate build dir in the conventional cmake manner. But I looked at the files to work out what options were available, and from the claimed defaults I guessed I might have to turn off a few (gnome_vfs, libcdr, libvisio, libwpg) - but in fast those were all correctly turned off without any action on my part. That makes me even more surprised that WITH_DBUS defaults to OFF. It isn't something I particularly care about, but it seems a common enough addition and doesn't need any odd dependencies (that is, I could turn it on and build without adding anything new on my reasonably-complete system). But what really puzzles me are the new libs since 0.91 - in my case in /usr/lib/inkscape. What is expected to use these ? I noticed them because by default they are static, although when I added -DBUILD_SHARED_LIB=ON I got (unversioned) .so libs. For libraries only used within a package, I have no objection to static libs, it's just installing them in /usr/lib which mainly worries me (and technically does not apply here): those might accidentally get linked into something else, particularly if there is no shared lib because of some fubar in my build - and then after a vulnerability fix I would end up with old code in something - the old zlib problem. In this case, any package using them needs to look for them in $PREFIX/$LIBDIR/inkscape, (sorry for the 'configure' naming) but are they really useful ? And if they are, should not the directory be versioned in case things change ? And finally, is it *acceptable* to you guys to make them shared, or will you tell my users that it is unsupported if they get problems with .so libs ? Finally, it was disappointing to have to download gtest - not everybody normally runs tests (and I have no idea what the 1 test does, I couldn't find it - like I said, I don't grok cmake ;) For a prerelease it isn't a problem, but it would be nice not to have to do it for a release (i.e. let people build without running tests). Bu the script to download it was at least convenient (although perhaps users behind the Great Firewall might not appreciate it). I very much doubt that I can produce useful "usage" comments (I keep having to google every time I build it with a new compiler / glibc / gtk / whatever and th en try to test it), but for the moment I won't be installing it until I get clarification about the purpose of the libs. I've also got another slightly older system (gcc-6.1, gtk+-3.18) where I can test the experimental gtk3 build if that would be useful ? But overall, this has been much less painful then when I last looked at using cmake for inkscape, so thanks for all the fixes. 1. http://www.linuxfromscratch.org/blfs/ ĸen -- `I shall take my mountains', said Lu-Tze. `The climate will be good for them.' -- Small Gods

2 6

Gradient banding - bounty idea?
by Máirín Duffy 22 Nov '16

22 Nov '16

Hi Inkscape developers! There is an old open ticket about gradient banding issues in Inkscape - https://bugs.launchpad.net/inkscape/+bug/180693 - and the Fedora Design Team hit it pretty hard when putting together the Fedora 25 background in Inkscape. It's a difficult problem because there aren't many workarounds. We weren't able to fully remove the banding in our final version. We're designers without much development experience so we can't fix the problem, but we have a lot of interest in doing whatever we can to help. One of our team members suggested trying a crowdfunding approach like Krita has done, e.g. - https://www.kickstarter.com/projects/krita/krita-2016-lets-make-text-and-ve… I wanted to run this idea by you and see what you think about it. We don't want to apply any unwanted pressure, and realize anyone taking on the bug who isn't already a part of your team would need mentorship / help from you, so I don't think it'd be a good idea to try this unless you were willing to be involved. Let me know what you think about this, or if you have any other ideas on how we might be able to help! Thanks!! ~m

5 5

cannot perform 'bzr pull' command on Inkscape trunk, Windows 10
by alvinpenner 22 Nov '16

22 Nov '16

I normally update my trunk using the pull command. Recently (within the last week) it has started failing with the error: C:\Users\username\AppData\Roaming\InkscapeBZR>bzr pull Using saved parent location: bzr+ssh://bazaar.launchpad.net/~inkscape.dev/inkscape/trunk/ Connected (version 2.0, client Twisted) bzr: ERROR: [Error 5] Access is denied: 'c:\\users\\penne_~1\\appdata\\local\\temp\\tmpizpzsf.pag' C:\Users\username\AppData\Roaming\InkscapeBZR>bzr revno 15264 my most recent successful pull was: C:\Users\username\AppData\Roaming\InkscapeBZR>bzr version-info revision-id: marcjeanmougin@...3449... date: 2016-11-11 21:05:31 +0100 build-date: 2016-11-22 06:49:20 -0500 revno: 15238 branch-nick: InkscapeBZR I ran these commands from an administrator DOS window, although it would not normally be necessary to do so. thanks in advance, Alvin -- View this message in context: http://inkscape.13.x6.nabble.com/cannot-perform-bzr-pull-command-on-Inkscap… Sent from the Inkscape - Dev mailing list archive at Nabble.com.

2 4

Fw: Survey
by Brynn 22 Nov '16

22 Nov '16

Sorry, I somehow sent this reply only to Victor, so now I'm forwarding it to the list, since that's what I meant in the first place. Apologies, brynn -------------------------------------------------- From: "Brynn" <brynn@...3133...> Sent: Monday, November 21, 2016 10:54 PM To: "Victor Westmann" <victor.westmann@...400...> Subject: Re: [Inkscape-devel] Survey > Hi Victor, > I'll be glad to change a few things which I'm clear about. But a > few of my questions are things I really don't understand. Especially for > lines 27 and 30, I'm not sure if you want to ask about tools in the main > toolbar or general features. > But most importantly, I don't understand composing/compiling a > survey without having some purpose for the survey. I mean, it makes sense > to have some understanding of the user base, but it seems backwards to > make a survey and then come up with a reason for it later. You must have > some reason to have brought up this idea? > Plus I'm looking at it from the point of view of convincing users > to take the time to fill out a survey. If all I can say is "please fill > it out, just because", they won't be very motivated. But if you can tell > them it has some purpose, you'll be more likely to get a response. > Theoretically, we already have a means for users to make requests > and report issues (Launchpad). So using the survey for those 2 reasons > won't fly very far. Deciding about the future development? Well, not to > my understanding. As far as I understand, future development is guided > primarily by the developers who do the work. And again, performing a > survey first, and finding a reason for it 2nd, seems backwards. > So I remain puzzled.... > > All best, > brynn > __________________________________________________ > > From: Victor Westmann > Sent: Monday, November 21, 2016 8:42 PM > To: Brynn > Subject: Re: [Inkscape-devel] Survey > > > Hi brynn > Thanks for your comments. Feel free to change the survey in order to > improve it. I agree with all of your observations so far. > Thanks. > > > On Nov 21, 2016 6:34 PM, "Brynn" <brynn@...3133...> wrote: > > Several comments and questions: > > For the question on line 9, how is "Personal" different from "Hobbyist"? > > For the question on line 24, would lack of a theme really prevent someone > from using Inkscape? > > The question on line 27 might be confusing. Do you mean which tool out of > the 20 in the main toolbar? Or does it mean "features" more than "tools"? > Also, that seems like an odd way of wording the question. Maybe I don't > understand it? > > I don't understand the question on line 30. What is meant by "Features", > "Usability", "Themes", "Ease of Use", etc.? Also, isn't "usability" and > "ease of use" the same thing? (whatever they are?) > > I wonder if asking Inkscape users how to fix something will be productive? > Only users who either are already developers, or have sufficient coding > skills would be able to answer. Right? > > For the question on line 36, what is your purpose for asking about those 6 > things, and not any number of other abilities of Inkscape? > > Since part of your stated purpose is to learn "how much are they involved > with the project (software and community)", I wonder if you might want to > ask which part or parts of the community they're involved with - mailing > list, forum, IRC, Launchpad, other, or none? Perhaps ask how much time > they spend with each part? And maybe ask if they are primarily asking for > support or offering support? Maybe ask to self-rate their knowledge of > Inkscape - beginner, intermediate, advanced? > > Also, don't forget to offer this survey to forum users ;-) > > What do you think you might use the results for? That might inform other > questions. Although having said that, probably the shorter the survey is, > the better. > > All best, > brynn > ____________________________________________________________ > > From: Victor Westmann > Sent: Sunday, November 20, 2016 11:46 PM > To: Inkscape-Devel > Subject: [Inkscape-devel] Survey > > > Hi Guys, > > > I was just wondering if we could run a simple and quick survey to our > users to get to know them better and to know what they know about the > software and how much are they involved with the project (software and > community), > > > This is just a draft so improvements and thoughts are more than welcome: > https://docs.google.com/spreadsheets/d/1CcV6rEYq5iIzZKkx_qPU6G5rp0O5DUM0EfQ… > > > What do you guys think? > > > This initiative took place inspired in the "State of JS" survey: > http://stateofjs.com/2016/introduction/ > > > Cheers! > > > > > > --Victor Westmann > > > > ------------------------------------------------------------------------------ > > > > > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-devel

1 0

Fwd: Re: Survey
by Miguel Lopez 21 Nov '16

21 Nov '16

-------- Forwarded Message -------- Subject: Re: [Inkscape-devel] Survey Date: Mon, 21 Nov 2016 02:10:33 -0500 From: Miguel Lopez <reptillia39@...3425...><mailto:reptillia39@...3425...> To: Victor Westmann <victor.westmann@...400...><mailto:victor.westmann@...400...> I would probably put bugs/incomplete features under 24 since that's the only reason I switch to Adobe Illustrator besides the features Inkscape lacks while Illustrator have. And speaking of that, gonna report my gradient mesh findings (I have responded to a e-mail, and I get nothing in return) and a bug while working on my work which forces me to import .svg on Illustrator to continue working as if nothing happened. On 11/21/2016 1:46 AM, Victor Westmann wrote: Hi Guys, I was just wondering if we could run a simple and quick survey to our users to get to know them better and to know what they know about the software and how much are they involved with the project (software and community), This is just a draft so improvements and thoughts are more than welcome: https://docs.google.com/spreadsheets/d/1CcV6rEYq5iIzZKkx_qPU6G5rp0O5DUM0EfQ… What do you guys think? This initiative took place inspired in the "State of JS" survey: http://stateofjs.com/2016/introduction/ Cheers! --Victor Westmann ------------------------------------------------------------------------------ _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net<mailto:Inkscape-devel@...2164...e.net> https://lists.sourceforge.net/lists/listinfo/inkscape-devel

3 3

Build issues on Mac with Trunk
by John Cliff 20 Nov '16

20 Nov '16

Hi all, Building trunk on mac fails currently, following issues: src/ui/dialog/filter-effects-dialog.cpp fails as the check for GTK version at line 26 is checking gtk version but the feature its using is gtkmm. Mac ports has gtk3 v3.22.3 but the gtkmm3 port is only 3.16. So the version check passes, but gdkmm/seat.h isnt found. Have currently bodged it by upping the gtk version being checked for in my build, but needs fixing properly. Same issue occurs in desktop-events.cpp, device-manager.cpp, same bodge works for them. The changes made to src/widgets/eraser-toolbar.cpp in revision 15159 breaks it on mac, reverting it to 15158 builds ok. the rest of the build seems to build ok, but its then failing on linking, but its too late to try fix that now, just wanted to document the above before I forget where the issues were. Standard X11 build btw not the quartz one. Thanks to MC and Su_v for helping me get this far :) Cheers John

4 5

Inkscape branding guidelines tagline
by Mihaela 20 Nov '16

20 Nov '16

4 7

[Fwd: Website Feedback]
by Martin Owens 20 Nov '16

20 Nov '16

Question from a website user.

2 1

Mesh gradient status and plea for help with testing.
by Tavmjong Bah 19 Nov '16

19 Nov '16

Hi, Mesh gradients are included in SVG 2 but their remaining in the specification is on shaky grounds.[1] We need to generate suitable SVG content using meshes in order to generate enough buzz to get the browser vendors to take notice. With that goal in mind, we would like see meshes enabled in the 0.92.x release but need help with testing. I've just checked into trunk the final GUI improvements to mesh handling. Please test and give me feedback. (And share any cool content you creat!) I will be merging the changes into 0.92.x in the next couple of days. For more information on how to use meshes see: http://wiki.inkscape.org/wiki/index.php/Mesh_Gradients Thanks, Tav [1] http://tavmjong.free.fr/svg2_status.html

9 23

DPI Switcher updated
by Jabier Arraiza 18 Nov '16

18 Nov '16

There is a new version of DPI Switcher extension. If you instaled previously please upgrade it. https://inkscape.org/en/~jabiertxof/%E2%98%85dpi-switcher-909690-experi mental-extension Cheers, Jabier.

1 0

Inkscape 0.48 download?
by jelle 18 Nov '16

18 Nov '16

Hello Webmasters, As the new widgets for setting percentages are completely unusable on interactive white boards due to their low precision input, I reverted back to Inkscape 0.48 which is more tolerant for finger input (has two separate input fields, a slider and a text field rather than a blob). However, the link to the legacy 0.48 has been removed and at the many schools I work, there is an occaissional outbreak of virus which means disks get wiped and a fresh winXP is installed (yes, really, working in China is bliss). Same infestations also regularly force me to wipe my USB sticks with the installation files for 0.48. Harddisk corruption due to 40 plus temperatures have destroyed my last copy of 0.48 install files. So now I'm without. Could you please recreate a link to the good ole 0.48 for legacy widget users and possible other finger input and shaky hands people, so they can install a usable version of Inkscape? Cheers, Jelle

2 1