- Inkscape Devel - Inkscape Mailman

Wiki bug template
by Alex Valavanis 21 Feb '17

21 Feb '17

Hi All, I've added a new template to the wiki for linking to Launchpad bugs. See: http://wiki.inkscape.org/wiki/index.php/Template:Bug Basically, you can just do something like: {{bug | id = 123456 | status = triaged}} to generate a color-coded link to the relevant Launchpad page. AV

1 0

About Most Suitable IDE (Integrated Development Environment) in Windows
by Niraj Dave 21 Feb '17

21 Feb '17

Hi, Which Integrated Development Environment (IDE) is most suitable in Windows operating systems for Inkscape from following: 1) Eclipse Name: (ie. Neon) Version: ? 2) Microsoft Visual Studio with VisualGDB Version: ?2) Microsoft Visual Studio with WinGDB Version: ? Please guide me..1) How to decrease compilation time? 2) Is there any automated Tools? which is most suitable? Please give detail steps to configuring development environment in windows for coding and debugging. Note: I have already generated Executable using following commands: >cmake -G "MinGW Makefiles" .. & >mingw32-make -j 2>mingw32-make install but which IDE is most suitable for Inkscape. Thank you, Niraj Dave

1 0

Inkscape 0.92.1pre1 macOS test build
by Tim Sheridan 21 Feb '17

21 Feb '17

Hi all, I've been working on getting the macOS packaging for the 0.92.x working again. The branch is here: https://code.launchpad.net/~tghs/inkscape/0.92.x_mac_packaging I've put a 10.7/i386 test build up for people to try at: https://inkscape.org/en/gallery/item/10660/Inkscape-0.92.1pre1-tghs_0-x11-1… Build info is on the file information page: https://inkscape.org/en/~tghs/★inkscape-0921pre1-tghs_0-x11-107-i386dmg As with the old official 0.91 release, this is an X11 build so you'll need XQuartz installed. Since it's not yet merged, please report any issues encountered in this thread, or to me directly. Known issues: * App not signed (probably wontfix for 0.92 as users put up with it for 0.91, but worth looking at for 0.93) * Built without poppler (need to check whether old releases included it) * Toolbar icons getting cropped slightly on the edges (not a blocker IMO, but would be nice to fix) Cheers, Tim

6 12

0.92.2 plan
by Bryce Harrington 19 Feb '17

19 Feb '17

With 0.92.1 now finished, the 0.92.x branch is reopened for targeted bugfixes, and it's time to look forward to 0.92.2. There are a few other activities that were gated on 0.92.1 which will be proceeding in parallel, most notably of which is the git migration plan, which is hard to guess how long it'll require. I figure since that's obviously going to be disruptive that we focus on completing that before initiating the 0.92.2 release. So exact dates are going to be infeasible, but to establish some basic mileposts: 0.92.1 Now Feature Freeze 0.92.2pre0 TBD Hard Freeze + String Freeze 0.92.2pre1 +2 weeks Release Candidate 0.92.2 +1 week Cut Release I am guestimating earliest we might see 0.92.2 would be late April / early May, but depending on how things go could be more of the May/June timeframe. == 0.92.2 Development Goals == 1. The replacement for DPI dialog is a top goal for 0.92.2. The wording of the dialog in particular needs review, but much of the implementation work is solid and just needs to be landed and tested. Translation of this to other languages is also quite important, and should receive special attention. A 2 week period is scheduled post-String Freeze in particular to help ensure translators have adequate time for this dialog. 2. A GPLv3 widget needs to be removed (or relicensed) to allow Inkscape to return to being covered as GPLv2. While I'd love to see this undertaken for 0.92.2, but if it isn't it doesn't need to hold up the release. Beyond this, changes that fix bugs or address user reported problems are welcome. Please try to keep patches minimal so they're easy to review, and avoid doing refactoring work. Larger works such as new user interface pieces, should be done on branches, proposed for review, and tested thoroughly on trunk before landing on 0.92.x. If you have any doubts over the appropriateness of a particular large change, please feel free to run it by me first. Provide detailed descriptions in your commit messages, including ref to bug #'s and an explanation of the user-visible problem that the patch fixes. This helps testers isolate regressions and assists in creating the release notes.

1 0

Post-Mortum: Line height bug
by Martin Owens 17 Feb '17

17 Feb '17

Developers, As someone how changed the line-height code prior to release, I feel somewhat responsible for the issue in 0.92. I really didn't have enough time to focus on bugs before the release, but should have spent more time on things I'd changed. I'm really sorry Inkscape. This thread isn't for figuring out how we're going to solve the issue though. I'll let the 0.91.1 discussion cover that. What I'd like to pick apart is our bug management and how a release blocker like this line-height issue didn't put an all stop on our release schedule while we figured it out. There's a couple of possibilities: 1. The bug wasn't discovered in time 2. The bug wasn't reported in time 3. The reported bug wasn't triaged in time 4. The bug wasn't prioritised as important 5. There wasn't a way to communicate a major issue to the release manager. 6. We just didn't have the resources to do the release properly and let things slide. What information can Mc and su_v add about the issue? What can we fix to make the process better? I feel bad asking for your help to really figure this out, but I think this might help us as a project overall if we know what happened and how to defend against it. Thanks everyone. Best Regards, Martin Owens

9 44

Re: [Inkscape-devel] User Involvement Was: Post-Mortum: Line heightbug
by brynn 16 Feb '17

16 Feb '17

I didn't include it in the job description part. But I was just discussing user testing of new releases (before release) and it occurred to me that perhaps an Advocacy Team could take the lead on potentially organizing user testing? I'm not sure if that makes sense, but if it does, I'll add it in. brynn -----Original Message----- From: brynn Sent: Thursday, February 16, 2017 4:49 PM To: Bryce Harrington Cc: C R ; inkscape-devel ; Martin Owens Subject: Re: [Inkscape-devel] User Involvement Was: Post-Mortum: Line heightbug I couldn't find the exact message where I mentioned making a new item on the To-Do List page about an Advocacy Team leader. But this point in the discussion was pretty close. So it's at the bottom of the list. Please feel free to tweak, or if you don't have website access, tell me what to change, and I will. https://inkscape.org/en/contribute/to-do-list/?edit_off=true All best, brynn -----Original Message----- From: Bryce Harrington Sent: Monday, January 30, 2017 12:19 PM To: brynn Cc: C R ; inkscape-devel ; Martin Owens Subject: Re: [Inkscape-devel] User Involvement Was: Post-Mortum: Line heightbug On Sun, Jan 29, 2017 at 01:29:31PM -0700, brynn wrote: > (Martin copied in, just fyi, no specific reply needed) > > Sorry, fairly long reply (tldr for most readers) Ditto, but I'll try and be brief in reply. > The sections look good. Would it make sense to reverse the order? > ____________________ > > That's interesting thought. I seem to recall my first version of > the page, the sections were reversed. I was thinking - list them > from easiest to hardest, or things that take less skill, to things > that take more skill. > > But someone else said to have the coding stuff at the top, because > that's what the project needs the most. I'm personally neutral on > this, and I'm happy to make whatever changes are needed. If you remember who that person was, might be worthwhile to loop them in on this discussion. (Heck, could have even been me!) It's certainly true coding is important but again we have the whole Develop top section devoted to it, so I really think we're ok on that count. Other things beyond coding are also critical to the project, and as most visitors to our site are probably non-coders I feel we really need to ensure we have an inviting-looking place for them, and I would worry leading with Coding might put them off. > >(E.g. the opening sentence > of Contribute and Promote ought to be more engaging.) > > I agree that would be a good idea, and I'll make a rough draft, > maybe using the first paragraph of that last bit of info in the wiki > (which I like). But C R has offered to make suggestions too. > Should I just make working page, that we could all access and tweak > on? I don't remember if C R is a website editor. Sounds like a good starting point. > >I really like the Community To-Do List page (contribute/to-do-list) and > > I had hoped that this would be a useful page. But no one seems to > be interested in those projects that are listed. Maybe because a > lot of them need significant experience with the project. I think that may be true. They did strike me as a bit advanced. I will try and help with ideas of more things we can include here. Bug me if I forget. It's also likely people just aren't aware of the page, so once we flesh it out more it would be good to evangelize it a bit (more on this below). > I don't see "non-coding" as less important. When I read the title, > I get excited, because here's something I could actually help with. > It doesn't make me feel bad about myself, and I think my self-esteem > is fairly intact. *Grin* Fair enough! > But I understand that "non-" is a negative, and > something more positive might be better. I just can't think of a > good alternative. Suggestions? What's the opposite of coding or > programming or hacking? "Other" would probably be too vague. Yeah Other would be too vague, I almost suggested General but that's also vague. I suppose since I don't have any better ideas leave it as is and if I think of something later or someone else comes up with a brilliant idea, we can tackle it then. Maybe a differing perspective would give some better ideas. > I'm not sure if the Promote page might be ill-conceived or not. All > of it really contributes to the project (everything on both > Contribute and Promote pages), but it's too much material for one > page. And Promote was the best thing I could come up with for a > page name. Open to suggestions. How about "Evangelism"? I've heard that term used in other FOSS projects and it has a nice ring to me. I do think this is an important role in the project, one that I wish we had more people engaged on. Announcing releases would be a crucial duty here, and a number of the activities the Board is engaged in would work much better if we had a better organized team focusing on this. As I've written previously, what makes FOSS projects like Inkscape successful is not vast userbases or lots of income - it's people like us contributing to the code and community in myriad ways both tangible and intangible. So a #1 purpose for an evangelism team would be contributor community building. Not necessarily like hard-sell 'recruitment' but more building connections between people and ensuring there are easily accessible on-ramps for people to join in. A lot of things would fall under such a group, from establishing presence in software and artistic communities both online and off, sending reps and presenters to artist-focused events, arranging training opportunities (both user-focused and development-focused), writing, pushing news items on our site, and more. > >The Helping Other Inkscape Users should be moved from the Promote page > to its own page. > > That section is a little longer than Spread the Word, but still > makes for a pretty short page, by itself. I guess I wouldn't have > any objections. But if it could be expanded, would be better, imo. > I just can't think of any other ways for helping other users. Ok, seems sensible. It can always be broken out later if/when there's more content for it. > >The Translations section looks fine. > > Yes, I think Maren has tweaked that page to perfection. > Unfortunately, I think she wants to take a break from website > editing, except for translation-related things. I'll try to use it > as a guide for the others. And if anyone else wants to help, of > course let us know! Understandable, and yes this would be a great area to bring in more people. > >The Bugs section I think could be made more specific to just Review and > Verify Existing Bug Reports. > > For the Bugs section, Testing, and Working with Code, I don't have > the knowledge for making all the changes you described. I can move > Report Bugs into the Testing section. But I can't make any of the > other changes to Testing that you mentioned. I just don't have that > knowledge. Yes, totally understood. I mentioned it more because it is something that "needs to be on our collective todo list" and realize drafting something sensible will be a large project. I will try and work on it as I have time and keep an eye out for folks that could assist. > I can move Packaging to the top level Develop page, and delete the > Write Extensions section, if you like. I don't follow your logic, > but it's probably because I don't understand programming. Sounds good. > Are you saying you want a page on the website, rather than a wiki > page, for Website Development? I don't have the right kind of > knowledge to be able to write such a page. All I could do is copy > the wiki page over to the website. Glad to do it, but also welcome > help in spicing it up. Right, exactly. I'm anticipating that Martin will have a place in mind to direct potential web developers to for orientation on website work, so am just suggesting we should point to that from here. Thanks, Bryce

1 0

Inkscape 0.92.1 now available
by Bryce Harrington 16 Feb '17

16 Feb '17

The Inkscape project announces an update to its 0.92.0 release, bringing important bug and regression fixes, updated translations, and improved documentation. Download 0.92.1 packages from: https://inkscape.org/en/download/ Inkscape 0.92.1 is a stability and bugfix release. Below lists the main changes. For a more complete list, see: https://launchpad.net/inkscape/+milestone/0.92.1 == Regression fixes == * Text: baseline-spacing related issues with regular and flowed text in legacy Inkscape SVG files (Bug #1655483 and others). * Text: Default baseline spacing stored in relative units is always converted to document units (Bug #1645016) * Path effects: Crash on ungroup if group contains elements with path effects (Bug #1657591) * Clipboard: Pasting a path effect from clipboard fails (Bug #1656093) * Clipboard: Fix copy&pasting of groups which contain elements with path effects (Bug #1656527) * Selection: Node tool can selected objects on locked layers (Bug #1656141) * Clones: Critical warnings with clones and symbols (Bug #1653184) * About screen missing for several UI languages (Bug #1659426) * Selection: Missing transformation handles after reset of rotation center (Bug #1657874) == Important bugfixes == * Bitmap images: Crash when opening files with invalid image links (Bug #1660142) * Bitmap images: Fix path separators in relative image links (Windows) (Bug #1659347) * File import: Failure to open CDR/Visio/WPG files from paths with special characters (Windows) (Bug #1656763) == Translations == * Catalan: Tutorial translation ("Basic") added * Czech: UI translation updated * English (GB): UI translation updated * French: UI translation updated * French: Man page, Readme and Keys & mouse reference updated * German: Man page and Keys & mouse reference updated * Icelandic: UI translation updated * Italian: UI translation updated * Latvian: UI translation updated * Russian: Tutorial translation ("Tracing Pixel Art") added * Russian: UI translation updated * Spanish: UI translation updated * Slovak: Tutorial translation ("Tracing Pixel Art") added * Slovak: UI translation updated * Ukrainian: UI translation updated == Documentation == * Shortcuts: Add shortcut '7' for cycling through path effect parameters in node tool (Bug #1656713) * Shortcuts: Add new Shift+I shortcut to keys and mouse reference (Bug #1644609) * Man page: Add new --no-convert-text-baseline-spacing command line option (Bug #1661811) == Known issues == * DPI Change: Dialog needs better explanation of available options (Bug #1659229) * DPI Change: Provide command line options for batch-processing legacy files (Bug #1659489) * DPI Change: known issues with 'Scale elements' option (Bugs 1653230, 1653230, 1653236, 1654342, 1654796, 1654880, 1654903, 1655005, 1655053, 1660228) * DPI Change: Default grids in documents created with Inkscape 0.91 don't scale correctly (Bug #1653893) * Renderer: Artifacts in Gaussian blur effects with default quality settings (Bug #1656383) * Node editor: Deselecting selected nodes of complex paths takes a long time (Bug #1652100) * Fill and Stroke: HSL color selector may show corrupted colors, defunct 5th slider (Bug #1635982) == Help Support Inkscape == We are already at work both on another bugfix update (0.92.2) targeted in a few months and a future development release (0.93) with more fundamental changes to the codebase. If you wish to track either of these developments, you can learn more at: https://inkscape.org/en/download/development-versions/ 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 --------------------------------------------------------------------

1 0

Flatpak for Inkscape 0.92
by Matthias Vogelgesang 15 Feb '17

15 Feb '17

Hi, is anyone of you interested in a Flatpak recipe or hosting the repo and/or bundle for Inkscape 0.92? You can find the flatpak-builder recipe at https://github.com/matze/inkscape-flatpak Personally I do not have the resources to host the repo (93 MB) nor the bundle (18 MB) for a large amount of users. However I think it adds value for distro users that do not support snaps. Best regards, Matthias P.S.: I know there used to be a Flatpak for Inkscape but I haven't found anything at all about it. -- Matthias Vogelgesang | bloerg.net

3 7

Feedback on measuring tool
by Bryce Harrington 15 Feb '17

15 Feb '17

----- Forwarded message from mike abbey <mabbey1985@...400...> ----- Date: Thu, 9 Feb 2017 17:30:07 -0500 From: mike abbey <mabbey1985@...400...> To: Bryce Harrington <bryce@...961...> Subject: Re: [Inkscape] [Inkscape-devel] Inkscape 0.92.1pre2 (release candidate) now available that would be fine. make sure that they all know that they do great work. i use it to make a few scrollsaw patterns and it does everything i need for that and more. thanks for all the hard work. On Thu, Feb 9, 2017 at 2:06 PM, Bryce Harrington <bryce@...961...> wrote: > Great to hear Mike, do you mind if I forward your email along to the > development list? I didn't work on that feature myself but am betting > those who have would love to hear your feedback. > > Thanks, > Bryce > > On Thu, Feb 09, 2017 at 06:55:16AM -0500, mike abbey wrote: > > i have to tell you that with the measuring tool in the .92, well, i love > > it. in .91 holding the mouse to make it stay was a pain. but now click > > click and it stays on its own. with the awesome work you and your team > have > > done with this i would never go to a paid program. keep up the good work. > > > > On Wed, Feb 8, 2017 at 5:45 PM, Bryce Harrington < > bryce@...961...> > > wrote: > > > > > On Wed, Feb 08, 2017 at 02:33:27PM -0800, Bryce Harrington wrote: > > > > This is a pre-release for the upcoming stable bugfix release 0.92.1. > > > > Download it at: > > > > > > > > https://inkscape.org/en/download/development-versions > > > > > > > > The release is: > > > > > > > > 0.92.1pre2 Source Tarball Bzip > > > > https://inkscape.org/en/gallery/item/10661/inkscape-0. > > > 92.1pre2.tar.bz2 > > > > > > > > We are now in final freeze prior to release. Barring any last minute > > > > issues, 0.92.1 will be identical to the above tarball except for the > > > > version number. We'll let things settle for a few days and hopefully > > > > finalize the release this weekend. > > > > > > And release notes are here: > > > > > > http://wiki.inkscape.org/wiki/index.php/Release_notes/0.92.1 > > > > > > > == Translations == > > > > > > > > Translation work is done. Please hold off on further updates until > > > > we're ready to start work on 0.92.2. > > > > > > > > > > > > == Future Releases == > > > > > > > > 0.92.2-targeted bugfixing work can begin on the 0.92.x branch once > > > > the 0.92.1 tarball's been cut, probably this weekend. A schedule > will > > > > be established at that time as well, targeting a 0.92.2 release in > > > > April. > > > > > > > > A 0.92.3 release sometime around July seems likely. I'm hoping to > > > > continue with subsequent point releases on a roughly 2-3 month > interval, > > > > so users can depend on the 0.92 series as a 'long term stable' (LTS) > > > > product. > > > > > > > > Work towards 0.93 is already underway in Inkscape's trunk repository. > > > > In order to modernize Inkscape for ongoing maintenance, there are > > > > several large transitions we need to undertake, including a move to > > > > Gtk3, re-engineering the Mac OS X installation packaging, > introduction > > > > of C++-11 code constructs, dropping of our legacy automake build > system, > > > > migration of the project to git, and more. We had elected to hold > off > > > > on these transitions for 0.92 so that release could focus on long > term > > > > stability first and foremost, with 0.93's focus being on taking the > more > > > > aggressive steps to move Inkscape forward. > > > > > > > > I am hoping a 0.93 release can be achieved within the calendar year, > > > > though much work remains. Assistance with testing is invaluable and > I > > > > hope many people will join in following the trunk codebase; however, > I > > > > know that building Inkscape can be a challenge, and we lack nightly > > > > builds on a few platforms, so I may attempt some form of interim > > > > snapshot preview release this summer to enable some broader testing > > > > before we're too far through 0.93's development cycle. > > > > > > > > Bryce > > > > > > > -----BEGIN PGP SIGNATURE----- > > > > Version: GnuPG v1 > > > > > > > > iEYEARECAAYFAlibnLcACgkQEaMBVuDmdhEKOwCeKgWKHLllZtGTsb877b9+8WQz > > > > hmEAnAhKdRKjn25SYLVBGMZ5pfuHMj1f > > > > =aOtL > > > > -----END PGP SIGNATURE----- > > > > > > > > > > ------------------------------------------------------------ > > > ------------------ > > > > 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 > > > > > > > > > ------------------------------------------------------------ > > > ------------------ > > > Check out the vibrant tech community on one of the world's most > > > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > > > _______________________________________________ > > > Inkscape-announce mailing list > > > Inkscape-announce(a)lists.sourceforge.net > > > https://lists.sourceforge.net/lists/listinfo/inkscape-announce > > > > ----- End forwarded message -----

1 0

Inkscape 0.92.1pre2 (release candidate) now available
by Bryce Harrington 12 Feb '17

12 Feb '17

This is a pre-release for the upcoming stable bugfix release 0.92.1. Download it at: https://inkscape.org/en/download/development-versions The release is: 0.92.1pre2 Source Tarball Bzip https://inkscape.org/en/gallery/item/10661/inkscape-0.92.1pre2.tar.bz2 We are now in final freeze prior to release. Barring any last minute issues, 0.92.1 will be identical to the above tarball except for the version number. We'll let things settle for a few days and hopefully finalize the release this weekend. == Translations == Translation work is done. Please hold off on further updates until we're ready to start work on 0.92.2. == Future Releases == 0.92.2-targeted bugfixing work can begin on the 0.92.x branch once the 0.92.1 tarball's been cut, probably this weekend. A schedule will be established at that time as well, targeting a 0.92.2 release in April. A 0.92.3 release sometime around July seems likely. I'm hoping to continue with subsequent point releases on a roughly 2-3 month interval, so users can depend on the 0.92 series as a 'long term stable' (LTS) product. Work towards 0.93 is already underway in Inkscape's trunk repository. In order to modernize Inkscape for ongoing maintenance, there are several large transitions we need to undertake, including a move to Gtk3, re-engineering the Mac OS X installation packaging, introduction of C++-11 code constructs, dropping of our legacy automake build system, migration of the project to git, and more. We had elected to hold off on these transitions for 0.92 so that release could focus on long term stability first and foremost, with 0.93's focus being on taking the more aggressive steps to move Inkscape forward. I am hoping a 0.93 release can be achieved within the calendar year, though much work remains. Assistance with testing is invaluable and I hope many people will join in following the trunk codebase; however, I know that building Inkscape can be a challenge, and we lack nightly builds on a few platforms, so I may attempt some form of interim snapshot preview release this summer to enable some broader testing before we're too far through 0.93's development cycle. Bryce

3 9