- Inkscape Devel - Inkscape Mailman

wiki account
by Thomas Holder 06 Jun '18

06 Jun '18

Can I please get an account for http://wiki.inkscape.org/? Username: speleo3 Thanks, Thomas

2 2

Board meeting Friday Jun 1st at 10am Pacific
by unknown＠example.com 01 Jun '18

01 Jun '18

Our monthly board meeting is scheduled for Friday, Jun 1st, at 10am Pacific in #inkscape-devel. All members are welcome. http://wiki.inkscape.org/wiki/index.php/Board_Meetings Agenda: ------- * Future meetings/hackfests. ** [[Hackfest2018 Kiel]] - Sun, 2018-09-09 until Thu, 2018-09-13 (Kiel, Germany) - Proposed ** [http://www.socallinuxexpo.org/scale/17x/ SCALE] - March 7th-10th, 2019 (Pasadena, California) ** [http://libregraphicsmeeting.org/2019/ LGM 2019] - May 30th-June 3rd (Saarbrucken, Germany) Proposed. (About two hours by train from Paris.) * Merchandise sales ** Spreadshirt ** Evaluate self-serve merchandise sales - spreadshirt, cafepress, Golden Ribbon, Think Penguin or similar [Mc] * Outreachy: Next round starts in August [https://www.outreachy.org/mentor/] * Action Items * Other Business Action Items from last meeting: ------------------------------- === Future meetings/hackfests === ♢ ACTION: Start thread on mailing list to organize next steps for event planning 2018/2019 [bryce] === Action Items === ♢ ACTION: Put together article on website about LGM event [Mc, doctormon] ♢ ACTION: Initial planning/contacts for Outreachy [bryce] === Other Business === ♢ ACTION: Follow up with prkos on requirements for inkscapeforum [bryce] Transcripts of previous meetings: --------------------------------- http://alpha.inkscape.org/board/meetings/transcripts/ Bryce

2 1

Inkscape 1.0 roadmap goal - test writing
by Bryce Harrington 01 Jun '18

01 Jun '18

Hi all, A priority for the 1.0 release is working on improving our testsuite. At the last hackfest, it was asked that the individual tasks be broken down and divvied out to people so we can distribute the work. Below, I've broken out the work as best I can and have proposed owners for each task. If you can't do a task, or would like to take on additional ones let me know. 1. Migrate the old test cases to GTest Refer to Tav's b50500c7 as an example of how to convert. Alexander Valavanis, would you be able to convert these two? + extract-uri-test.h + uri-test.h Tavmjong Bah, mind doing these? + mod360-test.h + preferences-test.h Adrian Boguszewski, would you be available to do these two? + object-test.h + sp-gradient-test.h Eduard Braun, could you try these two? + marker-test.h + sp-style-elem-test.h 2. Establish a regression SVG file collection I forget when exactly we discussed this, but the idea was to have a place to easily collect random SVG files from bug reports or community members that exhibit odd behaviors or provide stressful workloads for performance testing. The best way to structure this, I'm not sure. Probably keep them separate from the main codebase, maybe with laxer commit permissions? Marc Jeanmougin, you've been doing a lot of good work lately on setting up testing, including some render check testing in the main codebase. Would you be willing to take ownership of this task? 3. Implement new unit tests. We need additional GTests to cover a number of areas of the codebase. These need added in testfiles/src/, see the other tests there for examples. Who'd like to volunteer to work on these? * SP objects * verbs * cmdline options * UI widgets/tools * UI view * UI dialogs * live effects * etc. Bryce

2 1

Important Inkscape Vectors Meeting - This Saturday
by Ryan Gorley 31 May '18

31 May '18

Hello Vectors and Community, I'd like to invite all who are interested to attend the Inkscape Vectors meeting this Saturday, June 2, 15:00 UTC (See time conversion <https://www.timeanddate.com/worldclock/fixedtime.html?msg=Inkscape+Vectors+…>). This meeting will be conducted by chat only at: https://teams.freecreatives.org/inkscape/channels/town-square June 13th is the one year anniversary of our first meeting as a team! We've seen progress, but we're still learning and have room for improvement. Accordingly the main topic (see agenda discussion <https://gitlab.com/inkscape/vectors/general/issues/59>) of the upcoming meeting will be organization and governance for the group moving forward. Brynn will be leading the meeting. It's a big deal. I hope you'll join us! -- Ryan

1 0

New Extensions
by Tonya Sims 30 May '18

30 May '18

Hi all, I’m going to be writing tests for the newer extensions. I just want to make sure I have the right github repository. This is the one I cloned: git clone git@...3601...:inkscape/inkscape.git Is there a more updated one? I couldn’t find any in the documentation but wanted to make sure. Thanks, Tonya Sent from my iPhone

2 2

Plotter Cameo 3
by imagen imperio 25 May '18

25 May '18

Hi everybody, I want to know if there is and extention or plugin to manage Cutting ploters Cameo. Thanks, -- José Quintanilla Ramírez Imagen Imperio www.imagenimperio.net <http://imagenimperio.us/> 83993758

3 2

Survey about Inkscape UX
by JORGE LUIZ FRANZON ROSSI 23 May '18

23 May '18

Hi! I’m a Computer Science student at Federal University of Technology in Brazil and my group it’s doing a research about Inkscape. The focus of this work is at studying Human-Computer Interaction aspects, by collecting opinions from community and analyzing issues related to User Experience at Launchpad. It would be a great help if you can take a few minutes of your time to answer the questions of this form. Your identity will not be revealed and your answers are anonymous. If you wish to receive the research results, please leave your email address below. Best regards. Survey here <https://docs.google.com/forms/d/1GkAXdEQrxWpolJPgQag5nmuRsRUwaITkn8SW_w4RqK…>

1 0

Help needed: Extensions rotate path
by unknown＠example.com 18 May '18

18 May '18

Hi all, I've been refactoring the extensions code and while working on the paths support, I've become blocked on the rotate path functionality and need help. It's supposed to be able to rotate each of the points in the point list around the center x,y and it's based on the original code. But I have two problems. Firstly, I can't seem to find a way to get inkscape to output the kind of rotated path that would make writing a trustworthy test easier (and I don't know how to do the calculations by hand) And secondly, I'm not entirely sure if the original code worked or not. If you know anything about geometry or the original python, can you take a look at https://gitlab.com/inkscape/extensions/blob/master/inkex /paths.py#L92 which is the code in question and https://gitlab.com/inks cape/extensions/blob/master/tests/test_inkex_paths.py#L124 which is the respective test code. Tests can be run with `python3 setup.py test -s tests.test_inkex_paths` Best Regards, Martin Owens

1 0

Re: [Inkscape-devel] reimbursement LGM
by Jabier Arraiza 14 May '18

14 May '18

Thanks Tav! -----Original Message----- From: Tavmjong Bah <tavmjong@...8...> To: jabier.arraiza@...2893..., Inkscape-Devel <inkscape-devel@...1240... ceforge.net> Subject: Re: [Inkscape-devel] reimbursement LGM Date: Mon, 14 May 2018 13:28:39 +0200 On Thu, 2018-05-10 at 15:08 +0200, Jabier Arraiza wrote: > Hi All. > > Who is the person to send data for reimbursement from last LGM? Send it directly to accounting@...3057... > Thanks in advance. >

1 0

LGM-Hackfest Write-Up
by Jabier Arraiza 10 May '18

10 May '18

Hi all. First to all thanks to all make this happend. To me is very dificult attend conferences and code at the same time, my goal to this LGM not success but now I'm nearest with the help I recive in IRC: Allow link SVG into a SVG as image element. My second goal is make image paths work relative and I couldent get into. Short work done :(

2 10

reimbursement LGM
by Jabier Arraiza 10 May '18

10 May '18

Hi All. Who is the person to send data for reimbursement from last LGM? Thanks in advance.

1 0

GSoC Selections?
by Aditya Sher 06 May '18

06 May '18

The GSoC site shows an error in the selection menu of students , is it that no one got selected for GSoC under inkscape?

2 1

y-axis direction and origin
by Thomas Holder 05 May '18

05 May '18

Hi all, I took the liberty and assigned bug 170049 "Inverted ruler co-ordinate system" to myself. I used the patch from 2010 as a starting point, fitted it to the current code base and made it user configurable. It's been a while (7 years) that I last contributed to Inkscape development. What's the current development process? Do you guys do code review? How do I submit a pull request to the gitlab repository? I'm not a project member yet (my username is @speleo3). Thanks, Thomas

3 3

Inkscape Vectors Meeting - This Saturday
by Ryan Gorley 05 May '18

05 May '18

Hello All, This is just a friendly invitation to join the Inkscape Vectors meeting this Saturday. All are welcome to participate by video/voice/chat. Details can be found at: https://gitlab.com/inkscape/vectors/general/issues/57 Come with your ideas and enthusiasm. I look forward to seeing you there! -- Ryan

3 2

Board meeting Friday May 4th at 10am Pacific
by Bryce Harrington 04 May '18

04 May '18

Our monthly board meeting is scheduled for this Friday, May 4th, at 10am Pacific in #inkscape-devel. All members are welcome. http://wiki.inkscape.org/wiki/index.php/Board_Meetings Agenda: ------- * LGM Debrief * Future meetings/hackfests. + [https://wiki.gnome.org/GUADEC/2018 GUADEC 2018] - July 6th-11th (Ameria, Spain) GTK conference + [http://libregraphicsmeeting.org/2019/ LGM 2019] - May 30th-June 3rd (Saarbrucken, Germany) Proposed. (About two hours by train from Paris.) + SCALE * Sponsorships * Merchandise sales + Spreadshirt [cr] + Evaluate self-serve merchandise sales - spreadshirt, cafepress, Golden Ribbon, Think Penguin or similar [Mc] * Action items * Other Business Action Items from last meeting: ------------------------------- === LGM Hackfest 2018 === ♢ ACTION: LGM 2018 reminder email [Tav] ♢ ACTION: Arrange vote on a sponsored dinner at LGM 2018 [bryce] ♢ ACTION: Clarify funding rules to include contributors to inkscape-web, 2geom (maybe more?) [Tav] === Outreachy === ♢ ACTION: Initial planning/contacts for Outreachy [bryce] Transcripts of previous meetings: --------------------------------- http://alpha.inkscape.org/board/meetings/transcripts/ Bryce

1 1

Performance issue with gtk3 (especially on Windows)
by Eduard Braun 03 May '18

03 May '18

(I'll split this from the previous thread "slow, sluggish drawing with pencil & calligraphy tool solved" which became quite lengthy with a title not really matching the topic anymore) Hi all, I did not have a lot of time to follow up on this lately but I've got some great news I want to share with you regarding the performance issues we were seeing in Inkscape master (especially on Windows due to extremely poor GTK3 rendering performance which got even worse when drawing native window decoration, i.e. GTK_CSD=0). Turns out a patchset for cairo (see [1]) greatly reduced the latency of the rendering pipeline giving Inkscape a huge boost. I just built Inkscape with the patched cairo and performance with GTK_CSD=0 is now even slightly higher than with GTK_CSD=1! Also the blocking behaviour is completely gone (i.e. UI always redraws properly with current unmodified master). Performance with master/gtk3 is still *a lot* lower than with 0.92.x/gtk2, so I hope we can continue to improve Inkscape code (Yale's changes already looked very promising and I think they were not directly related to the changes in cairo, i.e. could improve performance even more) and maybe even GTK3 code (there are some very recent developments [2] which might result in a completely overhauled OpenGL based backend for win32!) but with today's success I finally feel we have a realistic chance to make the next Inkscape fun to work with on Windows! Best Regards, Eduard [1] https://github.com/Alexpux/MINGW-packages/pull/3675 [2] https://gitlab.gnome.org/GNOME/gtk/issues/105

5 4

Location path for an imported figure
by David Carrasco de Busturia 02 May '18

02 May '18

Dear All, I am finding `Inkscape` a really good tool for importing `PDF` or `EPS` scientific plots into a blank page, and then place arrows on top of the graphs, text, make scientific drawings assemble them in the desired location and then save as a unique PDF page that can then be included as a unique `figure` in a `latex` document. Let's imagine an inkscape project that has assembled 10 plots, imported from these folders: /path1/plot_1.pdf /path2/plot_2.pdf ... /path10/plot_10.pdf We already know that in /path1/ there is also the python, gnuplot, etc source code that produces the PDF plot, for instance: /path1/plot_1.py /path2/plot_2.gnu etc Most of the times I need to continue working over the original PDF plots that I once imported into a inkscape project I made back in time. For example, change the scale and the title of the plots, and so on. In other words, I need to go to the original source code (gnuplot, python, etc) that produces those plots that have been assembled in the inkscape project. In these situations, while having the nice inkscape project in the screen with all the plots 1 to 10, it is quite hard to remember where is the location of the original PDF plot. As far as I am concerned, there is no option in the inkscape interface that allows you to know which is the original location path of the PDF plot that was once imported into the inkscape project. The closest solution I could find is the following: every time I import a new PDF of EPS, I right click and and create a link which is basically a copy-paste of the location path of the figure. This solution is quite tedious and most of the times one forgets to create the link. Once the image is imported, the next natural step is to resize it and locate in the desired place, and it is very easy to forget to create the link. For instance, if this multi PDF plots assemble project was made in Latex, the location path of all the plots would be perfectly identified, i.e. in the `\includegraphics` line. I am sure there are more than one user that misses this feature. I was wondering if it is possible to check an option in the importing process that would allow to automatically write the location path of the figure somewhere. Or any other strategy that would automatically write the location path every time a plot is imported. Would this be very costly ? Thanks a lot for all your help, All the best, David

1 0

Fw: Vectors Meeting - SATURDAY!!! - Unencrypted Edition (LOL)
by brynn 02 May '18

02 May '18

forwarding to devel list -----Original Message----- From: Ryan Gorley Sent: Tuesday, May 01, 2018 12:58 PM To: undisclosed-recipients: Subject: Vectors Meeting - SATURDAY!!! - Unencrypted Edition (LOL) Hello All, I apologize for being a little quiet for the last few weeks as I've been trying to catch up with uncompleted work from the joyful distractions of March. I'm sure you've also been busy, and I'm personally grateful for your time and talents. None of us can carry this by ourselves, every small/large contribution is felt and appreciated. We have a lot of ground to cover, but to respect your time I'd like to make an effort to keep our formal discussion to one hour (side discussions can continue afterward of course). Details are here: https://gitlab.com/inkscape/vectors/general/issues/57 I'm not the boss! If you feel like there are items that should be added to this meeting for discussion, then please add them, email me, or comment in the issue. Thank you again for your work and willingness! Ryan -- Ryan Gorley Founder + Creative Director https://dijt.co 1.801.999.1530 ×101 1.801.898.7926

2 1

Inkscape on Mac
by Rodney Little 29 Apr '18

29 Apr '18

I am a Designer and developer who works on Mac. How can I help with getting builds of Inkscape out for our loyal Mac users? Rodney Little

6 6

Spreadshirt absurdity
by C R 29 Apr '18

29 Apr '18

So the more I use Spreadshirt, the more I see it's not a serious platform for merchandising. If you add a design for a mug, Spreadshirt requires you add the ENTIRE mug category, which contains any number of hidden (and hideous) products which you have no control over. I've confirmed this with Spreadshirt customer service: To add one white mug, you must add ALL mugs. To add one men's shirt, you must add all variations. This makes it impossible to control the quantity of products for a design, so the result is that the storefront gets flooded with a hundred variations of the very few things you set up, and the only way to remove them is to remove the whole category. So, what to do? I see only a few options, and none of them are great: 1. We limit it to one or two generic designs for everything. This is really the only way that makes sense. Anything else is going to have the visitors wading through hundreds of badly auto-designed products that no one will buy. 2. We ditch Spreadshirt, and seek other options. I mean, surely there's better than this out there somewhere. :) If we stay, we risk carefully thought out designs getting lost in auto-gen rubbish, which any online retailer will tell you is death for a product line. Too many options is no options, especially when most of the options look terrible anyway. My 2p -C

5 16

Problems building on Ubuntu 16.04
by mathog 24 Apr '18

24 Apr '18

Upgraded the Ubuntu 14.04 system which had endless build problems to Ubuntu 16.04. It doesn't seem to like 16.04 much better. Different problems, but still problems. Cleaned out the build directory and did: cmake .. which failed at ... WITH_OPENMP: ON WITH_PROFILING: OFF WITH_YAML: OFF ------------------------------------------------------------------------ CMake Error: The following variables are used in this project, but they are set to NOTFOUND. Please set them or make sure they are set and tested correctly in the CMake files: POPPLER_INCLUDE_DIR used as include directory in directory /usr/local/src/inkscape_trunk used as include directory in directory /usr/local/src/inkscape_trunk used as include directory in directory /usr/local/src/inkscape_trunk used as include directory in directory /usr/local/src/inkscape_trunk <SNIP many lines> -- Configuring incomplete, errors occurred! See also "/usr/local/src/inkscape_trunk/build/CMakeFiles/CMakeOutput.log". This is at revision 15617. These poppler pieces are present ii gir1.2-poppler-0.18 0.41.0-0ubuntu1 ii libpoppler-dev:i386 0.41.0-0ubuntu1 ii libpoppler-glib-dev 0.41.0-0ubuntu1 rc libpoppler-glib4 0.12.4-0ubuntu5.2 ii libpoppler-glib8:i386 0.41.0-0ubuntu1 rc libpoppler19:i386 0.18.4-1ubuntu3.1 rc libpoppler44:i386 0.24.5-2ubuntu4.4 rc libpoppler5 0.12.4-0ubuntu5.2 ii libpoppler58:i386 0.41.0-0ubuntu1 ii poppler-utils 0.41.0-0ubuntu1 What needs to be tweaked to make this work? Thanks, David Mathog mathog@...1176... Manager, Sequence Analysis Facility, Biology Division, Caltech

3 4

Missed SOC Application(maybe do SOC next year?)
by Alexander Vegas Fairley 22 Apr '18

22 Apr '18

Hey, I missed the SOC application for this year, but I might do most of the pre-reqs anyways and hope to work with you guys next summer perhaps. I've already done a bit of professional software engineering work and academic work and am pretty opinionated about software, but generally prefer to avoid going down the rabbit hole of flame wars if at all possible. For example, I mostly agree with torvalds about C++, but I don't know that it's possible to do a GUI application that is going to work anywhere without at least looking in the direction of Bjarne Stroustroup and forcing a smile. My background is mostly in high throughput web applications, and I worked on an SVG toy application many moons ago when SVG was still a proposed feature in Firefox. While I do find distributed web applications amazing, the fact that I can't really use a computer at all these days without using some uncountable number of distributed web applications, both known and unknown to me is not something I find all that thrilling from a usability point of view. I'v already started in on some of the SOC application stuff(late, I know). I actually can't do a lot of the stuff due to the extreme difficulty of getting an open source engineering workstation that can stand up to my present circumstances, but hopefully between now and next summer that will either change or I'll have easier circumstances. I guess I'll be lurking on the list either way. Nice to e-meet you. Cheers, Alexander

2 2

Re: [Inkscape-devel] Python extension extend to all Inkscape function and width height of any element
by Lex Neva 18 Apr '18

18 Apr '18

> Although I'm currently working on an updated API which should make it > easier to discover the functionality. Come talk to me over > at https://gitlab.com/inkscape/extensions/ Oh my, that sure is an interesting repo! Just from a cursory look, I can see that there's a lot in there that I've had to implement on my own in Ink/Stitch, and a lot of other really awesome stuff. How stable an production-ready would you say that code is? I ask because I'm in a great position with Ink/Stitch: I don't actually have to wait until this ships with inkscape to start using it in my extension. We're using pyinstaller, so we could easily just bring this repo with us in our packaged installation archives. If you tell me it's even somewhat stable, I might just switch over to it now. On April 17, 2018 8:05:26 AM inkscape-devel-request(a)lists.sourceforge.net wrote: > Send Inkscape-devel mailing list submissions to > inkscape-devel(a)lists.sourceforge.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > or, via email, send a message with subject or body 'help' to > inkscape-devel-request(a)lists.sourceforge.net > > You can reach the person managing the list at > inkscape-devel-owner(a)lists.sourceforge.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Inkscape-devel digest..." > > > > ---------- > Today's Topics: > > 1. Python extension extend to all Inkscape function and width > height of any element. (Lrn Lf) > 2. Re: Spreadshirt absurdity (Mihaela) > 3. Re: Python extension extend to all Inkscape function and > width height of any element. (Martin Owens) > 4. Re: Spreadshirt absurdity (C R) > > > > ---------- > [Inkscape-devel] Python extension extend to all Inkscape function and width > height of any element. > From: Lrn Lf <lv2lrn4lf@...400...> > Date: Apr 16, 1:18 PM > To: inkscape-devel(a)lists.sourceforge.net > > Is there away to access Inkscape other function through Python to run > Inkscape basic operation of really any operation you can run by hand > through the gui. And do anyone know how to get the bounding box width and > height of a g svg element or any element that don't have that information > set as a attribute. The only solution I can fantom is iterating through the > group to find the biggest element of them all but even that can be tricky. > > > > > > ---------- > Re: [Inkscape-devel] Spreadshirt absurdity > From: Mihaela <mihaela.jurkovic@...400...> > Date: Apr 16, 1:27 PM > To: Martin Owens <doctormo@...400...>, C R <cajhne@...400...> > CC: inkscape-devel <inkscape-devel(a)lists.sourceforge.net> > > Spreadshirt published the changes, here's the notification: > > https://www.spreadshirt.com/blog/2018/04/03/your-brand-new-detail-page-has-… > > There's a way to hide the color selector with CSS. I haven't tried it yet. > > Mihaela > > On 14.04.2018 21:42, Martin Owens wrote: > > On Sat, 2018-04-14 at 17:26 +0000, C R wrote: > > Regarding the website hack, yes I can do that. There are a few > options: > > Option 1: we can import it with the snippet provided by spreadshirt: > https://freedom.support.tm/hc/en-us/articles/115001381253-Spreadshirt > -How-do-I-embed-my-Spreadshirt-shop-into-my-own-website- > > Then I can write more javascript code to hide unwelcome products. > > Option 2: I (or we) can set up a page on the Inkscape website on > which we list specific products manually, which then link through to > spreadshirt items (which bypasses the need for the spreadshirt auto > generated gallery). > > Perhaps a combination of the above would be okay too. We make a > featured item page with direct links, and a link at the bottom to > "view all designs". That link would provide access to the full > spreadshirt shop, while allowing us to control what visitors see > first. > > You could make a shop app in inkscape-web which provided an > administrator the ability to add available products from the feed API. > I expect most of it would be javascript, but python could help make you > a more concrete shop. > > Martin, > > > > ---------- > Re: [Inkscape-devel] Python extension extend to all Inkscape function and > width height of any element. > From: Martin Owens <doctormo@...400...> > Date: Apr 16, 1:59 PM > To: Lrn Lf <lv2lrn4lf@...400...>, inkscape-devel(a)lists.sourceforge.net > > On Mon, 2018-04-16 at 13:18 -0400, Lrn Lf wrote: >> Is there away to access Inkscape other function through Python to run >> Inkscape basic operation of really any operation you can run by hand >> through the gui. And do anyone know how to get the bounding box width >> and height of a g svg element or any element that don't have that >> information set as a attribute. The only solution I can fantom is >> iterating through the group to find the biggest element of them all >> but even that can be tricky. > > Hi Lrn, > > There's functions for finding the bounding box which does the right > thing in python. > > Although I'm currently working on an updated API which should make it > easier to discover the functionality. Come talk to me over at https://g > itlab.com/inkscape/extensions/ > > As for calling Inkscape from the python extension, some extensions > already do this, but I wouldn't recommend it. > > Best Regards, Martin Owens > > > > > > ---------- > Re: [Inkscape-devel] Spreadshirt absurdity > From: C R <cajhne@...400...> > Date: Apr 16, 4:38 PM > To: Mihaela <mihaela.jurkovic@...400...> > CC: Martin Owens <doctormo@...400...>, inkscape-devel > <inkscape-devel(a)lists.sourceforge.net> > > Unfortunately, this doesn't solve any of our problems. This only > affects the details page, and our main problem is Spreadshirt showing > an item listing for every item in the category. > I'm happy enough to let people choose a colour shirt after they click > on an item, as this extra doesn't force the user to wade through every > possible colour option in the store view. > > -C > > > > On Mon, Apr 16, 2018 at 6:27 PM, Mihaela <mihaela.jurkovic@...400...> wrote: >> Spreadshirt published the changes, here's the notification: >> >> https://www.spreadshirt.com/blog/2018/04/03/your-brand-new-detail-page-has-… >> >> There's a way to hide the color selector with CSS. I haven't tried it yet. >> >> Mihaela >> >> >> On 14.04.2018 21:42, Martin Owens wrote: >> >> On Sat, 2018-04-14 at 17:26 +0000, C R wrote: >> >> Regarding the website hack, yes I can do that. There are a few >> options: >> >> Option 1: we can import it with the snippet provided by spreadshirt: >> https://freedom.support.tm/hc/en-us/articles/115001381253-Spreadshirt >> -How-do-I-embed-my-Spreadshirt-shop-into-my-own-website- >> >> Then I can write more javascript code to hide unwelcome products. >> >> Option 2: I (or we) can set up a page on the Inkscape website on >> which we list specific products manually, which then link through to >> spreadshirt items (which bypasses the need for the spreadshirt auto >> generated gallery). >> >> Perhaps a combination of the above would be okay too. We make a >> featured item page with direct links, and a link at the bottom to >> "view all designs". That link would provide access to the full >> spreadshirt shop, while allowing us to control what visitors see >> first. >> >> You could make a shop app in inkscape-web which provided an >> administrator the ability to add available products from the feed API. >> I expect most of it would be javascript, but python could help make you >> a more concrete shop. >> >> 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 >

2 2

Python extension extend to all Inkscape function and width height of any element.
by Lrn Lf 16 Apr '18

16 Apr '18

Is there away to access Inkscape other function through Python to run Inkscape basic operation of really any operation you can run by hand through the gui. And do anyone know how to get the bounding box width and height of a g svg element or any element that don't have that information set as a attribute. The only solution I can fantom is iterating through the group to find the biggest element of them all but even that can be tricky.

2 1

Inkscape and Uniconverter
by Martin Owens 14 Apr '18

14 Apr '18

Dear Developers, I need your expertise or history knowlege to understand extensions that use the uniconverter: http://wiki.inkscape.org/wiki/index.php/Uniconver tor On my system (Ubuntu 16.04) the uniconverter is broken, the package python-uniconv doesn't contain the sk1lib libraries and those libraries are in fact not available at all to debian, either through apt or through pypi. There is an option to download from their website, but random debs you find online seems unseemly. So my main question is: Have we been shipping broken extensions to all our linux users? Has anyone noticed? The debian bug report about the missing library doesn't seem to have been finished, so I don't even know if up to date ubuntus contain a fix. https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=820748 I did notice the library being shipped in our MacOSX build (and probably in our windows build) is that complete? Does it work there? I'd like to get these extensions fixed as part of the inkscape- extensions-1.0 package of cleanup, code quality and refactoring work. Any information would be greatly appreciated. Best Regards, Martin Owens

3 3

slow, sluggish drawing with pencil & calligraphy tool solved
by Yale Zhang 09 Apr '18

09 Apr '18

Hi, I've identified why drawing is lagging with GTK+3. https://bugs.launchpad.net/inkscape/+bug/1723247 It's because of GTK3's motion event compression: https://bugzilla.gnome.org/show_bug.cgi?id=702392 Adding a * gdk_window_set_event_compression (window, FALSE);* in SPCanvas::handle_realize() makes things much smoother. At 1st I thought it was because the events were sitting in the queue for too long. So I added some timing code to measure the latency between when a motion event was generated in GDK to when SPCanvas::paint() is called. Actually, I detect bursts of mouse moves or redraws and only use the 1st for latency measurements since there might not be a 1 to 1 relation between motion events and redraws. I was seeing a 4 to 10ms latency for head (GTK3) but only 0.5 ms for 0.92 (GTK2). I thought I was on to something, but this mislead me for a while. Finally, I saw that the # motion events and redraws were 10x higher for GTK2. I haven't stayed up to date with the GitLab migration. I tried to push a patch to my branch simdgenius_inkscape, migrated from Bazaar, but access is denied. I just requested project access, so appreciate it if someone grants it. -Yale

4 31

Bug tracker - should we move to gitlab? Or...?
by Bryce Harrington 09 Apr '18

09 Apr '18

When we moved from Launchpad to gitlab for code hosting, we postponed the question of if we should also move issue management off Lauchpad. I think now would be a good time to start investigating this. I figure it would be appropriate to discuss moving to gitlab issues, ON a gitlab issue, so have opened the following issue there: https://gitlab.com/inkscape/infra/services/issues/1 You'll need to be logged into gitlab in order to access the ticket. Issue management is of course important to our whole community, but it's especially a critical piece of our development infrastructure. I think we need to first seek a consensus among ourselves on what will work best for development purposes before soliciting wider feedback. (Bug tracking is a topic everyone and their uncle can have an opinion on, and open discussion could get unproductive quickly. That said, if you don't have access to the bug, but wish to share your thoughts, please feel free to do so on this mailing list thread, and they'll be taken into account in the decision process.) I've opened several sub-issues for specific topics that will require individual decisions, which are linked from issue #1. Please share your thoughts on all of them! Thanks, Bryce

1 0

Roadmap 1.0
by Bryce Harrington 08 Apr '18

08 Apr '18

One of the items scheduled for today was a review of the roadmap, looking both at the next development release, and the path to releasing 1.0. With the change to gtk3, we anticipate there may be some behavioral or functional changes that users may not find desireable, but that we may not discover until the release gets into widespread use, so it has been our plan to message this development release (which we have referred to as 0.93) as more "experimental" than 0.92, and continue releases on the 0.92.x series for them. Even with this messaging, though, we worry that distributors of our software may push 0.93 as the latest release, and fail to adequately provide the 0.92.x series to users that wish to maximize stability. So, one idea discussed today would refer to this development release not as "inkscape 0.93" but as either "inkscape 1.0~alpha" or "inkscape 1.0~pre0", and treat it not as a regular release but as an alpha release for 1.0. From there we could conduct multiple further pre-releases building towards a 1.0 release in, say, a 1-year timeframe. What do you think of this change in versioning nomenclature? Regardless of how we version the releases, there was a concensus among attendees to sharpen our focus towards achieving the 1.0 release expediously, prioritizing stabilization, testing, and documentation efforts. Apart from a limited set of development tasks targeted for 1.0, most development would be strongly encouraged to be done in branches with merge deferred to post-1.0. As requested at the hackfest, I'll take the action to itemize a listing of tests needing written or ported from the old test system, and divvying them out to currently active developers willing to take care of them. For development work that does target landing in 1.0, we would require or at least urge the work be done in a manner that permits disabling or reverting it if testing finds it to be insufficiently stable. I am pretty open as to what we call the pre-1.0 releases, and would like to gather more people's thoughts before deciding a path forward. So, how does this plan sound to you? Bryce

9 18

Hackfest 2018: Actions and Toolbars
by Alex Valavanis 06 Apr '18

06 Apr '18

Hi All, Here's a summary of my work at the Boston Hackfest. Before I continue, I'd like to thank everyone who donated their money or time to support this Hackfest. This has been a really useful event - it's so much easier to deal with tricky design challenges and project management stuff when we can meet face to face. It has also brought together people with very diverse expertise across the project (UI, web, build, extensions, project management etc). This week, we've figured out a path to deliver long desired features (multipage support etc), roadmapped our final route to deliver Inkscape 1.0, done some great website design work, and handled some tricky code structure issues that I'll discuss in this message. If you're able to donate some money to support Inkscape, and future Hackfests, we really appreciate this. You can find the donation link on our website: https://inkscape.org/en/support-us/hackfests/ It would also be great to get some more of the regular contributors from our wider community to join us at future events (i.e., designers, bug-team, experienced users... not just C++ developers!). The developers can learn so much more about the project by discussing it with you. So... what have I been doing this week? == What are Actions? == Basically, an "action" is a thing that Inkscape can do (e.g., flip an object horizontally), which we can identify using an ID code (e.g., "SP_VERB_OBJECT_FLIP_HORIZONTAL"). We can then hook up buttons, menu items etc to activate these actions. In this example, we would set up our Flip Horizontal button in the select-tool toolbar so that when the user clicks it, it activates the required action. My work this week has focused on improving the way we implement actions in our code, which will 1. Allow Inkscape to run on machines with future versions of the Gtk+ library (Gtk 4+) 2. Provide much better separation between the behaviour and user interface (i.e.,, separate pieces of the code will describe what Inkscape "does", and what it "looks like") 3. Make it much easier to create new "flavours" of the Inkscape user interface - for example, an "Inkscape for Kids" or "Inkscape CAD" 4. Make it easier for "non-programmers" to create and reorganise custom toolbars and dialogs 5. Allow us to remove a lot of older "C" code that is very difficult for current "C++" developers to maintain == Where we are now? == In the Inkscape code, we have a mechanism called "verbs" that acts as a kind of action mechanism... it provides a way of using an ID code to look up the required commands to perform an action. On top of this, we have another structure called SPAction that essentially hooks up a couple of signals to the verb. Finally(ish), we use objects called GtkActions from the Gtk+ library, which let us create GUI elements (buttons etc) that we can add to our menus or toolbars that activate the required action. We have also got a few custom sub-classes of GtkAction that let us create special kinds of tool-item that can activate actions... for example, one of these creates a spin-button (a box with a number in it, and "up/down" arrows) that can also handle units, basic arithmetic, and provides a label. == What's the problem? == First, the GtkAction widget (and hence all our custom sub-classes) is deprecated and has been removed from Gtk+ 4, so we need to change. Since Inkscape 1.0 is intended as a "stable" release, we want to make it as future-proof as possible. The main reason for this deprecation is that the GtkAction widget is a slightly weird mix of paradigms: it mixes information about how to display a tool/menu item with information about behaviour. This causes some problems... what if we wanted to run a "headless" Inkscape on a system that has no display? What if we wanted to provide several different GUI options for different kinds of user to trigger the same behaviour? This is one of the reasons why we have the "verbs" system is in place, as it separates behaviour from the GUI. However, there is still quite a lot of code "overhead" needed if we want to hook up Inkscape's Verb behaviour to a GUI element. Essentially, it's "programmers only" territory. What if a designer wanted to add a new toolbar button to their Inkscape to handle a useful feature that is currently buried deep in a menu? What if a teacher wanted to strip out a lot of "advanced" behaviour from the interface to make it easier to introduce Inkscape to their class? At the moment, they have to edit the C++ code, and recompile it... a slow and complicated process! == Where are we going? == We need to move to using GActions (a feature in the Glib/GIO library). This *only* describes the action's behaviour and provides an "activated" signal that we can trigger by simply knowing the action's name. This is completely separated from the GUI. These actions can be activated very easily from a whole range of places, for example: 1. By attaching the action's name to a GUI element in the C++ code (replacing our SPAction/GtkAction code) 2. By activating the action (using its name) from a command-line interface (replacing some of our verbs code) 3. By attaching the action's name to elements in a customised GUI file 4. From external applications, using the DBus system Number 3 in the list provides some very exciting opportunities for future releases, as non-programmers will be able to make a customised user interface by drawing one in the Glade application. You then just attach the name of the required Inkscape action to each GUI element. Want a new button? Just edit Inkscape's user-interface file in Glade and see the changes immediately next time you start... no C++ knowledge needed! == What have I done so far? == I've started working through Inkscape's toolbars, and have replaced the deprecated GtkAction-based widgets with standard widgets (buttons etc). Some of these now hook up to GAction descriptions of behaviour, while others are just based on handling GUI signals (e.g., Button::clicked). So far, I have migrated the toolbars for the Select, Dropper and Connector toolbar, and have killed off a couple of the custom GtkAction-based widgets that were only used in these. In the process, I have also migrated the toolbar code to C++, which should make it a little easier for the current core developers to maintain. Since all the data is now stored as C++ member variables, rather than as GObject data, we now benefit from better compile-time and run-time type-checking that will help to safeguard against errors being introduced in the code in future. I have placed the updated toolbars in the Inkscape::UI::Toolbar namespace and made them into proper sub-classes of the Gtk::Toolbar class. == How can you help? == This important refactoring project must be done before Gtk+ 4 is widely used, and represents a major change to the way that our toolbars are implemented. It represents a couple of thousand lines of code changes and will inevitably cause some regression bugs. I will need your help in thoroughly testing that all the toolbars work correcly! All of these changes are currently in a git branch ("gtk-actions-migration") and will not be merged into the master branch until preliminary testing has been completed. In other words, this will not "mess up" your stable version of Inkscape and will never be part of the current 0.92.x release series! I intend to merge this work well in advance of the Inkscape 1.0 release, so that we have plenty of time for very thorough developer and user testing, and several preliminary bug-fix "alpha" pre-releases before the final stable release. For the very brave: please checkout the "gtk-actions-migration" branch in git, rebuild and test. Please note that this is work-in progress. Do not use this experimental branch for your regular Inkscape drawing work!!! The Node toolbar will not work... the Select, Dropper and Connector toolbars are highly experimental; all the other toolbars are "at risk"! If you don't know how to do this, check out our developer guide. For the quite brave: I'll merge this experimental branch into our master development branch in a few weeks once (a) I've completed the basic work, (b) I've had a good amount of feedback on the branch and know that it "works" to some extent. I'll message you again at this stage and ask everyone to help look for bugs. Again, this will only be visible to developers and users of our experimental "trunk" PPA in Ubuntu. For the intrepid: If you're interested in helping with the code migration - message me and I'll help to divide up the tasks. == The end == I hope this gives an insight into the work I've started doing this week, and will continue over the coming weeks. Thanks once again to everyone who has contributed time, money or even just attention and enthusiasm for the Hackfest. Best wishes, Alex Valavanis (valavanisalex) Inkscape developer

7 11

Board meeting Fri Apr 6
by Bryce Harrington 06 Apr '18

06 Apr '18

Sorry for the late notice on this one. Our monthly board meeting is scheduled for this Friday, Apr 6th, at 10am Pacific in #inkscape-devel. All members are welcome. http://wiki.inkscape.org/wiki/index.php/Board_Meetings Agenda: + Merchandise sales [crogers] + LGM 2018 [Tav] + GSoC [ScislaC] + Other Business

1 0

Hackfest / lost and found
by Máirín Duffy 06 Apr '18

06 Apr '18

Hi everyone :) We found an Asus digitizer pen in the area where the Inkscape Hackfest was found. I was wondering if any hackfest participant may have lost it? I am happy to ship it home to you. Cheers, ~m

5 6

Feeling stressed?
by Bryce Harrington 04 Apr '18

04 Apr '18

Hi all, I've been picking up a lot of indicators of stress in our project participants. Each seems to be a unique case, with a different cause, and so there can be no universal solution. But if you're feeling stressed it might help to take a look at a broader perspective, and see some of the great progress being made. We just completed a very effective Hackfest. We burned through our list of discussion topics and unblocked progress on multiple fronts, and helped get each other on the same page on several topics. I think everyone came away energized, a bit overwhelmed, and enthusiastic to get moving on some big efforts. It was an intense week. I wish everyone could have come! We want to organize future hackfests to be more convenient for you, so everyone gets a chance to benefit from face-to-face time with each other. The Inkscape 1.0 release is now visible on the horizon, which is very exciting and will be a massive achievement for our project. There is still planning to be done, and it'll be probably about a year before we reach it, but a lot of path clearing has been done the past couple weeks to ensure we can head there at full speed. Print/color management, multi-page, GActions, and more are starting to get charted out; 1.0 is not going to be the end of the road, but rather the start on some major innovations for Inkscape. It is almost overwhelming to think of all the work needed, but know that while they'll be progressing in parallel, our focus right now is the 1.0 release. People have been very understanding that we have to pace ourselves and prioritize stability right now. Several changes are afoot for our infrastructure - mailing lists, merchandise, forums, a website redesign, and bug tracking all have improvements under way. Quite a bit to do, but will strengthen both our user and contributor communities, and we have plenty of time to do them. Another bit of very good news is that Inkscape is doing well monetarily. At the start of FY2017 we had $18,414; after one year this has grown to $45,732. This is thanks both to prolific individual donors and several very generous sponsoring companies -- people believe in us and what we're doing, and are providing us with financial resources to do even more. Looking at this past month's financial data, donations appear to have picked up even more, and we've several potential sponsors that will likely pitch in once they see some plans for specific features they're interested in. All of this funding gives Inkscape a lot of flexibility to do more to improve both the software and the community. And, to boot, efforts on new fundraising sources are in process, which could kick us off in a 'virtuous circle'. At least some people are finding stress from the sheer amount of different things, and how quickly they're progressing. I sure feel it. I just want to say - pace yourself. Don't be afraid of letting others take over some of your tasks, and don't be shy about asking for load sharing if you feel overwhelmed. Please email me privately if you need help. I expect things will even out better in the next few months -- the release and the hackfest caused acceleration on a bunch of stuff, but the next few weeks should get quieter as people take time to digest. In some cases, the stress has shown itself in various discussions. Please know we're taking these seriously and working behind the scenes to improve relationships. This community wrote a remarkably good Code of Conduct for itself, well worth reading (or re-reading): https://inkscape.org/en/community/coc/ In the next week or so I'll post a plan for getting us to 1.0, with specific tasks that we'll need people to pitch in on. Meanwhile, take some time to get recentered and get the stresses eliminated. :-) Hugs and cheers, Bryce

2 1

Re: [Inkscape-devel] Hackfest 2018: Actions and Toolbars
by jelle 03 Apr '18

03 Apr '18

Hi all, A lot of exiting things going on here. Separating the GUI from the functionality of Inkscape and allowing to use it as a command line tool sounds really cool. Now the question that arises to me is whether that means Inkscape could be used as a service and output could get rendered to a client browser? That would allow for a wide variety of GUI's to be developed that could cater to specific uses. I could envision a touch version and probably a VR interface would be more of an option as well. Obviously the fast rendering with Cairo would be lost that way, but for limited use cases (for instance without filters) that should be fast enough I think. Cheers, Jelle

5 6

New Das Stroke LPE
by Jabier Arraiza 01 Apr '18

01 Apr '18

Hey folks, Whit the help of Lazur and the thread: http://www.inkscapeforum.com/viewtopic.php?f=22&t=24175&p=83448&hilit=s troke+dash#p83448 just do a tiny LPE to fix it. Here are the new video showing it (no audio): https://archive.org/details/dash-stroke-lpe Hope is useful since is not included in the SVG spec. With love, Jabiertxo.

1 1

Hackfest 2018: Variable fonts, refactoring, etc.
by Bryce Harrington 01 Apr '18

01 Apr '18

----- Forwarded message from Tavmjong Bah <tavmjong@...8...> ----- Date: Sun, 01 Apr 2018 03:31:32 +0200 From: Tavmjong Bah <tavmjong@...8...> To: Bryce Harrington <bryce@...961...> Subject: Hackfest 2018: Variable fonts, refactoring, etc. Bryce, can you forward this to the inkscape-devel list? SourceForge is blocking my Internet provider's mail server. Thanks. Hi, Before I start my report on the Boston Hackfest, I would like to thank Martin Owens, our Inkscape host, and Máirín Duffy, our Red Hat host. Martin did a great job of showing us around Boston and making sure we were properly fed (even cooking us a lunch!). Máirín, a designer at Red Hat, gave us great feedback on Inkscape in its current form and on our plans for future Inkscape versions. I would also like to thank the other Red Hatters, especially Matthias Clasen, who helped make this hackfest a success! And I would like to thank the many donors to the Inkscape hackfest fund that make these hackfests possible. I'll start with the item that will most excite Inkscape users: Variable Font Support in Inkscape. Variable fonts are fonts that contain "axes" that can be tweaked by the user. The simplest example would be a font that contains an axis for weight. Instead of being limited to a few discrete font weights, each requiring its own font file, a user of variable fonts can with just one file select weights with any values continuously between a minimum and maximum value. Prior to the hackfest I got rendering of variable fonts working in Inkscape. This required handling the CSS property used to set the axes and modifying the rendering code to use the axes. (I should mention that this only works with very new versions of the libraries we use to handle fonts and text.) At the hackfest I worked with Felipe on adding support to the user interface. Felipe got a prototype version working during the hackfest. Felipe and I also had discussion with Matthias, a Red Hat employee who works on GTK about Matthias' improved GTK Font Selection widget to which he has added variable font support. I spent some time experimenting with replacing the font selection in the Text and Font dialog with the native GTK widget (after getting positive feedback from the designers in the room). Speaking of Matthias. We spent time with him discussing some of the problems we have with GTK. This was very productive, both in validating our move to GActions (discussed already by Alex) as well as getting feed back on a number of other issues. Maybe the biggest blocker in getting to 1.0 is how broken floating dialogs are under the Wayland compositor, a replacement for the X11 window server. The library we use to handle floating dialogs, GDL, is not used by many projects (maybe only two). The code is complex and fixing it to work with Wayland may be too difficult. After feedback from Máirín it appears our best way forward is to replace GDL with use of the GtkNoteBook widget which handles dragging and dropping tabs. (Máirín also finds Gimp's use of tabs to dock dialogs much easier to use than our current system.) One of my biggest beefs about working on Inkscape code is how poorly documented it is. Part of the problem is that code is strewn throughout the repository so it is often hard to find the code that handles a particular thing. This also leads to code duplication as its hard to see that we already have solution to a particular problem. I've proposed a directory reorganization that better sort the code by its purpose. This, and having README files in each directory should help new developers find their way through our code base. After several round of discussion and feedback we've come up with a solid plan which I'll be implementing in the next few weeks. Part of the directory reorganization is to get all the graphical interface code into one place so we can work on isolating the GUI components from other parts. This should allow us to more easily create an efficient command-line version of Inkscape. (Alex's work on GActions should also help us give more power to the command line.) There were quite a few other very useful discussions we had: the road map, documentation, increasing diversity, our website, etc. I personally find that I am not very efficient at actual hacking during hackfests (I work best when I am in the peace and quiet of my own home) but the discussions we have during hackfests leads to great productivity afterwards. Tav ----- End forwarded message -----

1 0

Re: [Inkscape-devel] [Inkscape-user] New Das Stroke LPE
by Jabier Arraiza 01 Apr '18

01 Apr '18

I just see the spec. I hope I can improve the LPE with it. Regards, Jabier On Sun, 2018-04-01 at 14:16 +0200, Tavmjong Bah wrote: > On Sun, 2018-04-01 at 12:51 +0200, Jabier Arraiza wrote: > > Hey folks, > > > > Whit the help of Lazur and the thread: > > http://www.inkscapeforum.com/viewtopic.php?f=22&t=24175&p=83448&hil > > it > > =s > > troke+dash#p83448 just do a tiny LPE to fix it. > > > > Here are the new video showing it (no audio): > > > > https://archive.org/details/dash-stroke-lpe > > Nice! > > > Hope is useful since is not included in the SVG spec. > > If it's an LPE it doesn't need to be in the SVG spec. Have a look at > this to see what the SVG group was thinking about before it was > removed > from the SVG 2 spec: > > https://svgwg.org/specs/strokes/#StrokeDashing > > > With love, Jabiertxo. > > ------------------------------------------------------------------- > > ----------- > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Inkscape-user mailing list > > Inkscape-user(a)lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/inkscape-user

1 0

Re: [Inkscape-devel] [Inkscape-user] New Das Stroke LPE
by Jabier Arraiza 01 Apr '18

01 Apr '18

Thanks Tav for the feedback. Im working in a feature to allow use min lenght of a segment to define the aproximate lenght of the hole/dash, this allow corner perfect dashes in a rectangle with diferent ammount of dashes. I go to the link you send to catch more ideas... I realy like more a SVG spec than a LPE, mainly because Im not recreating the stroke but subdividing the segment, so we cannot handle fills without fill between many LPE. Regards. On Sun, 2018-04-01 at 14:16 +0200, Tavmjong Bah wrote: > On Sun, 2018-04-01 at 12:51 +0200, Jabier Arraiza wrote: > > Hey folks, > > > > Whit the help of Lazur and the thread: > > http://www.inkscapeforum.com/viewtopic.php?f=22&t=24175&p=83448&hil > > it > > =s > > troke+dash#p83448 just do a tiny LPE to fix it. > > > > Here are the new video showing it (no audio): > > > > https://archive.org/details/dash-stroke-lpe > > Nice! > > > Hope is useful since is not included in the SVG spec. > > If it's an LPE it doesn't need to be in the SVG spec. Have a look at > this to see what the SVG group was thinking about before it was > removed > from the SVG 2 spec: > > https://svgwg.org/specs/strokes/#StrokeDashing > > > With love, Jabiertxo. > > ------------------------------------------------------------------- > > ----------- > > Check out the vibrant tech community on one of the world's most > > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > > _______________________________________________ > > Inkscape-user mailing list > > Inkscape-user(a)lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/inkscape-user

1 0

Upcoming directory restructuring
by Tavmjong Bah 29 Mar '18

29 Mar '18

Hi all, At the hackfest we discussed a revised directory structure to better organize our code, This is a heads up that we plan on doing this reorganization in a couple of week (to give time for existing patches, etc. to land). The purpose of the reorganization is to make it more obvious where to find different pieces of code. At the moment our code tends to be distributed over lots of different directories (especially the code that manipulates SVG and the code for our 100+(!) GUI elements). The proposed directory structure can be found at: http://wiki.inkscape.org/wiki/index.php/Source_Directory_Structure You can comment on the proposed change here or on the wiki page. We also discussed a requirement that all files should have at least one or two sentences to document what their contents does. This should really help new developers (and prevent code duplication). Tav

8 14

Hackfest 2018 Boston - day 1 update
by Bryce Harrington 28 Mar '18

28 Mar '18

A recap of some discussions that have been under way... 0. On the first day I gave a presentation on modularity, and identified areas in both Inkscape the codebase and Inkscape the project, to encapsulate complexity into more easily understood chunks, with well defined and simple interfaces between them. 1. Gtk3 (and Gtk4) issues were brainstormed. We use several Gtk2 functionalities which are deprecated in Gtk3, and may be removed in Gtk4. We scoped out ideas for transitioning, such as migrating from GtkAction to GAction, and GtkMain to GtkApplication. The discussions helped clear some blockers, and Alex is now digging into the code and working out how we can do the change with minimum impact on UI appearance or behavior. Longer term, once these transitions are made, there are a number of more impactful changes that could be attempted. One scheme we scoped out was to separate the frontend and backend of Inkscape, using GActions as the interface. The backend would present a lengthy list of all of its internal operations (Actions). There would be separate sets of Document Actions (like moving a node on a Bézier curve) and Window Actions (like resizing the window). The frontend UI would translate its widget clicks and menu picks into the corresponding actions and pass them down. Apart from giving us better organized code, this could also make it easier to have multiple kinds of UI's (e.g. a simplified "kidscape" interface) or even no-UI (e.g. a headless version that processes commands through command line args or a batch language). 2. Website strategy is under heavy discussion. It's been a while since the website has had a design refresh, and whiteboard markers are flowing. Improving mobile friendliness seems important, also better use of graphics and videos is being explored, and better emphasis on using some of the great user stories out there. There's also a recognition that we have needs for something more user-facing (e.g. something "brochure-like") and something more back-office-y (the contributor community, aka "contributy"). A lot of this will need a lot more hashing out and collecting wider ideas, but I'm looking forward to seeing how this work proceeds in coming weeks and months. 3. Variable fonts. This new type of font permits e.g. sliding scale of style aspects like bold between letter forms. Some implementation work has already been done, but the hackfest has been used to hash out some remaining questions and implementation details. There's still some UX/UI questions on how it should be implemented in the interface. 4. Improved gradients using random dithering in pixman. Lots of discussions in both IRL and IRC around Mc's code to add better gradient rendering to pixman, that avoids banding by randomly dithering the colors. The patch has been proposed to pixman and some feedback's been received, but still mulling over how to actually get this feature into use. 5. Color management / CMYK. We had an in-depth discussion between coders and designers to hash out what we ought to be shooting for in terms of requirements. We discussed a "print pre-flight dialog" concept that had come up in some of the Vectors team discussions. What's needed as a next step is to flesh out the concept - workflow use cases, a mockup UI, and analysis of how data in/out flows need to work. There are a lot of ideas and user stories, that need gelled into something coherent that people can start throwing darts at. 6. SVG 2 working group, and future directions. A number of features we wanted to see included in the SVG 2 spec sound like they will get dropped. Further, this change of direction by the WG suggests it may get tougher to include artistic-oriented features in future revisions of the spec. We discussed some of the problems, but the path forward for us is unclear. --- I'm certain I've missed a number of the discussions here, and am not capturing all the work under way. Hopefully other attendees can fill in what I've missed or gotten wrong, and provide more details from my above summary. Please ask questions, too. Bryce

5 6

Future 0.92.x bugfix releases
by Bryce Harrington 26 Mar '18

26 Mar '18

Let's plan on a 0.92.4 in a few months, maybe in the May/June timeframe. As we've talked about in the past, we'll be continuing to do bugfix releases on the 0.92.x branch for the foreseeable future, and we'll be treating it as an equivalent of a 'long term stable' series for Inkscape in case changes. Some aggressive changes in 0.93 may lead to bad breakages for some users, so we want to give them a reliable fallback. So, please continue backporting good fixes from master into the 0.92.x branch, and record the changes in release notes: http://wiki.inkscape.org/wiki/index.php/Release_notes/0.92.4 If you don't have commit access to 0.92.x (or don't feel comfortable pushing to it), you can mark bugs in Launchpad with the 'backport-proposed' tag, so committers can more easily spot them. (But make sure the bug has a patch attached to it that will actually apply and build against 0.92.x.) A few release process todo's I'm aware of: * Mac builds - need a volunteer * 'make distcheck' - needs added to cmake * PPA recipe updates - needs scripted [hackfest: bryce/alex] * NEWS file update - change python script to use BeautifulSoup [bryce] * packager announcements - set up a proper mailing list [bryce] * Transition to new RSA 4096 GPG signing key [bryce] * cleanup the release documentation [bryce] * lp milestone, etc. updates - needs a LP script so its less manual Let me know if you'd like to help on any of these tasks. Bryce On Fri, Mar 23, 2018 at 10:42:17PM -0700, Bryce Harrington wrote: > Inkscape 0.92.3 is a maintenance release resolving numerous bugs and > making this the most stable release of the series. > > To download the latest packaged version of Inkscape visit: > > https://inkscape.org/release/0.92.3/ > > (Note: A build of 0.92.3 is not currently available for MacOS. The > project welcomes additional contributors with MacOS expertise.) > > Among the most reported bugs addressed were: > > * Blank pages being output when printing multiple copies of a document > * The inability to cancel during the export of large files > * Application crashes caused by dragging a path at a cap or line join > * Keyboard shortcut problems on non-Latin keyboard layouts > > Also a few performance improvements and usability enhancements of note: > > * New SVG export options from the command line > * Support for right-to-left text > * Improved ellipse controls > * Multi-line text support for the PDF+LaTeX export > * New render tile preferences for performance tuning > * Better startup performance for many Windows users > > Find out more about the release at: > > https://inkscape.org/en/news/2018/03/22/announcing-0923-release-inkscape/ > > > > > Inkscape 0.92.3 > > -~= Released 2018-03-11 =~- > > +----------------------------------------------------------------------+ > | Release Highlights | > +----------------------------------------------------------------------+ > > Inkscape 0.92.3 is mainly a stability and bugfix release, but it also > brings some small new features, like being able to set an ellipses' > radii numerically in the tool controls, or switching the writing > direction from left-to-right to right-to-left. Windows users will be > happy to learn that the long startup times many of them were seeing > could greatly be reduced. A new rendering option with an adjusted > default value can vastly improve performance when working with filters. > > Many of the bug fixes address important functionality, like printing > issues, crashes with the node tool or problems with keyboard shortcuts. > > > +----------------------------------------------------------------------+ > | Improvements | > +----------------------------------------------------------------------+ > > Command line usage > ================== > > Three new command line options controlling page size are supported when > exporting in SVG format: > > • --export-area-drawing (feature requests in bug #1597921 and bug #1722844) > • --export-area-page while using --export-id > • --export-margin > > > Text tool > ========= > > Support for switching between RTL and LTR writing directions has been > added (on narrow screens, find it by unfolding the overhang menu for the > text tool's tool controls by clicking on the triangle at the far right). > > > Circle/ellipse/arc tool > ======================= > > New fields for setting vertical/horizontal radius (Rx/Ry) were added to > the tool controls bar. (Bug #1181127) > > > PDF+LaTeX export > ================ > > Support for multi-line text with basic support for line-spacing > attribute was added. (Bug #771959) > > Please note: > > • Currently only the line-spacing of the top level text element is > considered, i.e. all lines in one text element share the same line > spacing. > • LaTeX is much more clever with respect to line spacing, so layout > might not always be exactly the same as in Inkscape. > • Make sure to use a continuously scalable font in LaTeX, otherwise > results might be unexpected. > > > Preferences > =========== > > A new renderer option called "Rendering tile multiplier" was > added. Making this value larger can speed up drawing, if you have large > areas with complex filters in your drawing or work a lot with high zoom > levels on filtered objects. Making the value smaller can make zooming > and panning in relevant areas faster on low-end hardware (if there are > no large filtered areas on the visible part of the canvas). The default > value makes your screen consist of about four tiles that are rendered > independently, if you're not using a hidpi screen (which requires more > tiles). For a more detailed explanation, see: > > https://gitlab.com/inkscape/inkscape/merge_requests/211#note_62157385. > > > Startup Performance > =================== > > The first start of Inkscape on Windows is much faster now. > > This is the result of improvements in fontconfig 2.13.0, a third party > library which handles font related tasks for Inkscape. One of the tasks > is creating an index of all fonts available on the system which is much > faster now. If the new indexing causes any issues (i.e. fonts or glyphs > not available that could be used before) make sure to let us know or > report the issue directly to the fontconfig project. > > > Extensions > ========== > > Extensions on Windows can now make use of Tkinter, without requiring > users to install it themselves. Tkinter provides functionality for > creating interactive graphical user interfaces. This is used, for > example, by the TexText extension that renders mathematical LaTeX > formulas to SVG (feature request at bug # 1735451). > > > +----------------------------------------------------------------------+ > | Regression Fixes | > +----------------------------------------------------------------------+ > > • Potentially missing command line output in Inkscape 0.92.2 on Windows 7. > (Bug #1714278) > • Extensions in the 'Raster' submenu relying on ImageMagick were > broken and caused crashes in Inkscape 0.92.2 on Windows. > (Bug #1720330) > • gcodetools were creating wrong orientation points since the dpi > change had been made for Inkscape 0.92. > (Bug #1680760) > • Regression on 0.92.2 makes it impossible to fill a powerstroke shape > (Bug #1715433) > • The preferences dialog was tiny by default. > (Bug #1360213) > • Node handles no longer get too large when selected, and they also > revert back to standard size when deselected. > (Bug #1568644) > • Export to .odg (Open Document Drawing) works again on Windows. > (Bug #1654034) > • Inkscape no longer freezes when trying to import clipart from > OpenClipart when the openclipart.org server takes too long to > respond to requests. > (Bug #1745521) > • Text that is written in vertical direction now has its marks > (e.g. accents) on the correct side again. > (gitlab commit 2abe0bb6) > • The 'Clone original' path effect works again to fill a path with a > PowerStroke applied to it (useful for drawing cartoons) > (Bug #1715433) > > > +----------------------------------------------------------------------+ > | Important bugfixes | > +----------------------------------------------------------------------+ > > • Fix crash when attempting to drag path at cap or line join. > (Bug #1691406) > • Inkscape process did not exit cleanly on Windows. > (Bugs #1412365 and #1715339; also causing #1714278) > • File extension was sometimes omitted when adding saved files to Windows' > list of "recently used documents" resulting in unusable links. > (git commit 4d599528) > • Do not crash on systems with illegal fontconfig configurations. > (Bug #1716516) > • Resolve issues when attempting to save files to non-existing > directories. Could happen for shortcuts.xml and when setting the > autosave location manually. > (Bug #1719629) > • Allow cancellation of bitmap export. > (Bug #1195929) > • Fix issues with PDF+LaTeX export: wrong stacking of text/graphics, missing > pages in PDF output. > (Bugs #771957, #1417470) > • Fix shortcuts not working as expected when a non-latin keyboard layout is > the primary keyboard layout on a system. > (Bugs #1226962, #1730246, #1734308) > • Printing multiple copies of the document resulted in one copy and many > blank pages. > (Bug #490866, #1733424) > • Fix export area when exporting single objects to SVG using the --export-id > command line switch. > (Bug #1306662, #1707368) > • Fix DXF output and Windows vector print scaling for documents with a custom > view box. > (Bug #1672066) > • Invalid output generated from extensions no longer makes Inkscape > crash. > (gitlab commit 608fa56e) > • The Ruler Live Path Effect now shows correct measurements in the default > template (and other non-px-based templates), too > (Bug #1460858) > • The Document Properties dialog now has a more compact layout, so all items > should be accessible on smaller screens > (Bug #1510831) > > > +----------------------------------------------------------------------+ > | More bug fixes | > +----------------------------------------------------------------------+ > > There were even more issues fixed than those listed above, but these > probably only affect a small portion of users, or are relevant for > development and packaging only. > > For a complete list, visit our launchpad bug tracker and see the commit > history on gitlab (all changes from August, 6th 2017 until release > date). > > > +----------------------------------------------------------------------+ > | Translations | > +----------------------------------------------------------------------+ > > The following UI translations received updates: > > • French > • German > • Icelandic > • Italian > • Korean > • Spanish > • Ukrainian > > The following installer translations received updates: > > • Korean > > > Contributing to interface translations > ====================================== > > Want to help with translations? Learn how to help at: > > https://inkscape.org/contribute/translations/ > > > +----------------------------------------------------------------------+ > | Documentation | > +----------------------------------------------------------------------+ > > > Documentation Relaunch > ====================== > > The Inkscape documentation repository, containing the man page, the > keyboard shortcut list as well as the tutorials and their respective > translation files, has been almost completely refactored (Java has been > dropped in favor of Python), and was updated to work with git and > gitlab. > > > Documentation Updates > ===================== > > The man page and the keyboard shortcut list have been updated. > > > Where to find recent documentation > ================================== > > Continuously updated man page (for command line usage), keyboard and > mouse shortcut list, tutorials and translation statistics for the > various parts of the Inkscape project are available on the inkscape.org > website: > > • Man page > • Keyboard shortcuts > • Tutorials > • Translation statistics for Inkscape 0.92 series / development branch > > Tutorials, as always, are also included with your Inkscape installation. > > > Contributing to documentation and documentation translation > =========================================================== > > Contributions to the documentation translations, as well as improvements > to its contents, are welcome at the inkscape-docs repository. > > > +----------------------------------------------------------------------+ > | Known issues | > +----------------------------------------------------------------------+ > > • DPI Change: known issues with 'Scale elements' option > (Bugs: 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) > • Line height: Changing "baseline spacing" stops working. > (Bug #1707808) > • 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) > • Performance: Using the objects dialog at least once in your Inkscape > session slows down actions such as duplicate and delete for files > with many objects. > (Bug #1431274) > > > ------------------------------------------------------------------------ > For information on prior releases, please see: > > http://wiki.inkscape.org/wiki/index.php/Inkscape > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1 > > iEYEARECAAYFAlq15TkACgkQEaMBVuDmdhFeGACffqDDMJ7PI1yYV8gVz8V1jekW > vEgAn1jy67X42/mi4eX+ebQEvz9FUkpn > =ITZ8 > -----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

5 5

Inkscape Hackfest 2018 (Boston) Almost here!
by Martin Owens 25 Mar '18

25 Mar '18

Dear Hackers, Are we all looking forward to two weeks from now when we'll be dining on lobsters and dunken donuts? Well if you are coming, please do update the http://wiki.inkscape.org/w iki/index.php/Hackfest2018_Attendees page (or let me know and I'll do it for you) This is the rough itinerary for the week: * Sunday 25th, optional drink with local Free Software hackers at the Grendel's Den in Harvard Square. 8:00pm to 11:00pm Some touristing might be available if you like to see Harvard. * Monday 26th - Friday 30th, Hacking at the Red Hat offices near south station. Anyone lost can contact me +01 857 277 2117 (Signal App is good for anyone from abroad) * Wednesday 28th - User participation day, if we have some users available, we'll be listening to normal Inkscape users. * Thursday 29th - Tentative choice for Inkscape Dinner at Les Zygomates (http://winebar129.com) (If no one objects in the next few days, I'll book a table) Let me know what you're looking forward to working on while your here, I'd like to get a new article put together to kick things off. If you can do photography, please let me know. We'll need a group photo and someone with a nice camera and a good eye is needed sine CR isn't here. Anything else, please let me know. Thanks everyone! Best Regards, Martin Owens

7 6

Re: [Inkscape-devel] [Inkscape-user] Inkscape no fonts
by Sam 24 Mar '18

24 Mar '18

I see small boxes everywhere, i.e. in the menu, in the side bar. There is no font at all in Inkscape. I can't open Inkscape's settings because I don't know where the settings are because everything is only displayed as small boxes. Sam On 24.03.2018 14:00, Robert Funnell wrote: > On Sat, 24 Mar 2018, Sam wrote: > >> I try to run Inkscape 92.3 on OpenSuse 42.3 with snapd, but there is >> no fonts. It is running but i only see small square boxes. > > Are you saying that you see boxes when you add new text, or that you > see boxes where there's previously existing text in a drawing? > > - Robert >

2 2

Missing fonts
by Sam 24 Mar '18

24 Mar '18

Hi guys, I try to run Inkscape 92.3 on OpenSuse 42.3 with snapd 2.27.6-1.1, but there is no fonts. It is running but i only see small square boxes. Can anybody help me? Tnx Sam P.S.: I posted this post to the ML "User" by mistake, so this post exists twice. Sorry.

1 0

Inkscape 0.92.3 bugfix release
by Bryce Harrington 24 Mar '18

24 Mar '18

Inkscape 0.92.3 is a maintenance release resolving numerous bugs and making this the most stable release of the series. To download the latest packaged version of Inkscape visit: https://inkscape.org/release/0.92.3/ (Note: A build of 0.92.3 is not currently available for MacOS. The project welcomes additional contributors with MacOS expertise.) Among the most reported bugs addressed were: * Blank pages being output when printing multiple copies of a document * The inability to cancel during the export of large files * Application crashes caused by dragging a path at a cap or line join * Keyboard shortcut problems on non-Latin keyboard layouts Also a few performance improvements and usability enhancements of note: * New SVG export options from the command line * Support for right-to-left text * Improved ellipse controls * Multi-line text support for the PDF+LaTeX export * New render tile preferences for performance tuning * Better startup performance for many Windows users Find out more about the release at: https://inkscape.org/en/news/2018/03/22/announcing-0923-release-inkscape/ Inkscape 0.92.3 -~= Released 2018-03-11 =~- +----------------------------------------------------------------------+ | Release Highlights | +----------------------------------------------------------------------+ Inkscape 0.92.3 is mainly a stability and bugfix release, but it also brings some small new features, like being able to set an ellipses' radii numerically in the tool controls, or switching the writing direction from left-to-right to right-to-left. Windows users will be happy to learn that the long startup times many of them were seeing could greatly be reduced. A new rendering option with an adjusted default value can vastly improve performance when working with filters. Many of the bug fixes address important functionality, like printing issues, crashes with the node tool or problems with keyboard shortcuts. +----------------------------------------------------------------------+ | Improvements | +----------------------------------------------------------------------+ Command line usage ================== Three new command line options controlling page size are supported when exporting in SVG format: • --export-area-drawing (feature requests in bug #1597921 and bug #1722844) • --export-area-page while using --export-id • --export-margin Text tool ========= Support for switching between RTL and LTR writing directions has been added (on narrow screens, find it by unfolding the overhang menu for the text tool's tool controls by clicking on the triangle at the far right). Circle/ellipse/arc tool ======================= New fields for setting vertical/horizontal radius (Rx/Ry) were added to the tool controls bar. (Bug #1181127) PDF+LaTeX export ================ Support for multi-line text with basic support for line-spacing attribute was added. (Bug #771959) Please note: • Currently only the line-spacing of the top level text element is considered, i.e. all lines in one text element share the same line spacing. • LaTeX is much more clever with respect to line spacing, so layout might not always be exactly the same as in Inkscape. • Make sure to use a continuously scalable font in LaTeX, otherwise results might be unexpected. Preferences =========== A new renderer option called "Rendering tile multiplier" was added. Making this value larger can speed up drawing, if you have large areas with complex filters in your drawing or work a lot with high zoom levels on filtered objects. Making the value smaller can make zooming and panning in relevant areas faster on low-end hardware (if there are no large filtered areas on the visible part of the canvas). The default value makes your screen consist of about four tiles that are rendered independently, if you're not using a hidpi screen (which requires more tiles). For a more detailed explanation, see: https://gitlab.com/inkscape/inkscape/merge_requests/211#note_62157385. Startup Performance =================== The first start of Inkscape on Windows is much faster now. This is the result of improvements in fontconfig 2.13.0, a third party library which handles font related tasks for Inkscape. One of the tasks is creating an index of all fonts available on the system which is much faster now. If the new indexing causes any issues (i.e. fonts or glyphs not available that could be used before) make sure to let us know or report the issue directly to the fontconfig project. Extensions ========== Extensions on Windows can now make use of Tkinter, without requiring users to install it themselves. Tkinter provides functionality for creating interactive graphical user interfaces. This is used, for example, by the TexText extension that renders mathematical LaTeX formulas to SVG (feature request at bug # 1735451). +----------------------------------------------------------------------+ | Regression Fixes | +----------------------------------------------------------------------+ • Potentially missing command line output in Inkscape 0.92.2 on Windows 7. (Bug #1714278) • Extensions in the 'Raster' submenu relying on ImageMagick were broken and caused crashes in Inkscape 0.92.2 on Windows. (Bug #1720330) • gcodetools were creating wrong orientation points since the dpi change had been made for Inkscape 0.92. (Bug #1680760) • Regression on 0.92.2 makes it impossible to fill a powerstroke shape (Bug #1715433) • The preferences dialog was tiny by default. (Bug #1360213) • Node handles no longer get too large when selected, and they also revert back to standard size when deselected. (Bug #1568644) • Export to .odg (Open Document Drawing) works again on Windows. (Bug #1654034) • Inkscape no longer freezes when trying to import clipart from OpenClipart when the openclipart.org server takes too long to respond to requests. (Bug #1745521) • Text that is written in vertical direction now has its marks (e.g. accents) on the correct side again. (gitlab commit 2abe0bb6) • The 'Clone original' path effect works again to fill a path with a PowerStroke applied to it (useful for drawing cartoons) (Bug #1715433) +----------------------------------------------------------------------+ | Important bugfixes | +----------------------------------------------------------------------+ • Fix crash when attempting to drag path at cap or line join. (Bug #1691406) • Inkscape process did not exit cleanly on Windows. (Bugs #1412365 and #1715339; also causing #1714278) • File extension was sometimes omitted when adding saved files to Windows' list of "recently used documents" resulting in unusable links. (git commit 4d599528) • Do not crash on systems with illegal fontconfig configurations. (Bug #1716516) • Resolve issues when attempting to save files to non-existing directories. Could happen for shortcuts.xml and when setting the autosave location manually. (Bug #1719629) • Allow cancellation of bitmap export. (Bug #1195929) • Fix issues with PDF+LaTeX export: wrong stacking of text/graphics, missing pages in PDF output. (Bugs #771957, #1417470) • Fix shortcuts not working as expected when a non-latin keyboard layout is the primary keyboard layout on a system. (Bugs #1226962, #1730246, #1734308) • Printing multiple copies of the document resulted in one copy and many blank pages. (Bug #490866, #1733424) • Fix export area when exporting single objects to SVG using the --export-id command line switch. (Bug #1306662, #1707368) • Fix DXF output and Windows vector print scaling for documents with a custom view box. (Bug #1672066) • Invalid output generated from extensions no longer makes Inkscape crash. (gitlab commit 608fa56e) • The Ruler Live Path Effect now shows correct measurements in the default template (and other non-px-based templates), too (Bug #1460858) • The Document Properties dialog now has a more compact layout, so all items should be accessible on smaller screens (Bug #1510831) +----------------------------------------------------------------------+ | More bug fixes | +----------------------------------------------------------------------+ There were even more issues fixed than those listed above, but these probably only affect a small portion of users, or are relevant for development and packaging only. For a complete list, visit our launchpad bug tracker and see the commit history on gitlab (all changes from August, 6th 2017 until release date). +----------------------------------------------------------------------+ | Translations | +----------------------------------------------------------------------+ The following UI translations received updates: • French • German • Icelandic • Italian • Korean • Spanish • Ukrainian The following installer translations received updates: • Korean Contributing to interface translations ====================================== Want to help with translations? Learn how to help at: https://inkscape.org/contribute/translations/ +----------------------------------------------------------------------+ | Documentation | +----------------------------------------------------------------------+ Documentation Relaunch ====================== The Inkscape documentation repository, containing the man page, the keyboard shortcut list as well as the tutorials and their respective translation files, has been almost completely refactored (Java has been dropped in favor of Python), and was updated to work with git and gitlab. Documentation Updates ===================== The man page and the keyboard shortcut list have been updated. Where to find recent documentation ================================== Continuously updated man page (for command line usage), keyboard and mouse shortcut list, tutorials and translation statistics for the various parts of the Inkscape project are available on the inkscape.org website: • Man page • Keyboard shortcuts • Tutorials • Translation statistics for Inkscape 0.92 series / development branch Tutorials, as always, are also included with your Inkscape installation. Contributing to documentation and documentation translation =========================================================== Contributions to the documentation translations, as well as improvements to its contents, are welcome at the inkscape-docs repository. +----------------------------------------------------------------------+ | Known issues | +----------------------------------------------------------------------+ • DPI Change: known issues with 'Scale elements' option (Bugs: 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) • Line height: Changing "baseline spacing" stops working. (Bug #1707808) • 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) • Performance: Using the objects dialog at least once in your Inkscape session slows down actions such as duplicate and delete for files with many objects. (Bug #1431274) ------------------------------------------------------------------------ For information on prior releases, please see: http://wiki.inkscape.org/wiki/index.php/Inkscape

1 0

0.92.3 Release Announcement
by Ryan Gorley 23 Mar '18

23 Mar '18

Hello All, We just published the announcement for 0.92.3 on the website: https://inkscape.org/en/news/2018/03/22/announcing-0923-release-inkscape/ If anyone was waiting for this announcement to push any changes to official repos, or anything else, consider the wait over. :) Bryce, as release manager do you want to do the honors of pushing this out to the inkscape-announce and inkscape-user list? Anyone is welcome to help us promote this, please help us keep track here: https://gitlab.com/inkscape/vectors/general/issues/48 Ryan

3 2

Extensions
by Martin Owens 23 Mar '18

23 Mar '18

Dear all, I've separated out the extensions directory into a new repository: https://gitlab.com/inkscape/extensions I haven't yet removed the files from the master branch, but I will as soon as I get a couple of nods of approval from other developers and packagers as this change needs some consideration. My first job is to upgrade extensions to python3 and to do this I'm going to write tests. Please let me know if there are any extensions tests already written I can use. Best Regards, Martin Owens

8 24

Re: [Inkscape-devel] Extensions
by Lex Neva 22 Mar '18

22 Mar '18

> 4. Adding their own UI. In the cases where the current inx based UI falls > down (conditional values, and many more) the users want to able to use, > say, Kivy or even tkinter to do dialogs. This is super hard and only one I > know that works is the very recent embroidery extension which needs own > installer and is so complex I can't follow it. Oh dear! Sorry it's so confusing. As I think you understand, trying to get a cross-platform UI working is quite difficult. And for translations, we had to completely ignore inkex.localize() in favor of bundling our own translations, because we can't get our translation strings into inkscape fast enough. On the plus side, we handle units and viewbox correctly and we're 96dpi compatible already, so no work needed there. Thanks for all the work you're doing! We're happy to answer any questions you might have on how Ink/Stitch works. I follow this list, if somewhat slowly at times, but the best way to reach us is to file an issue (github. com/lexelby/inkstitch).

1 0

GtkActions in toolbars
by Alex Valavanis 17 Mar '18

17 Mar '18

Hi All, In preparation for the Hackfest, I'd like to start looking at ways to reduce (eventually eliminate!) our use of GtkAction. One of the main uses we currently have for them is in toolbars, where the tool widgets (buttons, spinbuttons etc) are all some kind of subclass of GtkAction, which has been removed from Gtk+ 4. This means that when the user clicks on the button, it triggers an "activate" signal, which is handled by a callback function. My question is basically, "what's the point?" Is there any reason why we can't just use a plain old button in most cases, and just connect up the "clicked" signal instead? If it really needs to be some kind of Action, we could migrate to the GAction API, but this may be much more difficult. Best wishes, Alex

5 11

LaTeX rendering fail
by Jakob Peder Pettersen 16 Mar '18

16 Mar '18

When running the command Extensions->Rendering->LaTeX and typing in any LaTeX expression, I get no output and Inkscape returns: *** WARNING - the DELAYBIND command has been deprecated, and will be removed in the next version. For now you can restore the behaviour by using -dREALLYDEALYBIND but if you require continued use of this command you should contact the Ghostscript developers. Commercial customers of Artifex should email their support contact, free users are encouraged to talk to us on the #ghostscript IRC channel on irc.freenode.net. Unrecoverable error: undefined in DELAYBIND PostScript/PDF Interpreter finished. Return status 65280 executed command : /usr/local/opt/ghostscript/bin/gs -q -dDELAYBIND -dWRITESYSTEMDICT -dNODISPLAY -dNOEPS /var/folders/z_/v0sm2gys3y77640_7m4t99k40000gp/T//psinQuRKci The interpreter seems to have failed, cannot proceed ! Traceback (most recent call last): File "eqtexsvg.py", line 160, in <module> e.affect() File "/Applications/Inkscape.app/Contents/Resources/share/inkscape/extensions/inkex.py", line 268, in affect self.effect() File "eqtexsvg.py", line 154, in effect svg_open(self, svg_file) File "eqtexsvg.py", line 81, in svg_open doc = inkex.etree.parse(filename) File "lxml.etree.pyx", line 3299, in lxml.etree.parse (src/lxml/lxml.etree.c:72421) File "parser.pxi", line 1791, in lxml.etree._parseDocument (src/lxml/lxml.etree.c:105883) File "parser.pxi", line 1817, in lxml.etree._parseDocumentFromURL (src/lxml/lxml.etree.c:106182) File "parser.pxi", line 1721, in lxml.etree._parseDocFromFile (src/lxml/lxml.etree.c:105181) File "parser.pxi", line 1122, in lxml.etree._BaseParser._parseDocFromFile (src/lxml/lxml.etree.c:100131) File "parser.pxi", line 580, in lxml.etree._ParserContext._handleParseResultDoc (src/lxml/lxml.etree.c:94254) File "parser.pxi", line 690, in lxml.etree._handleParseResult (src/lxml/lxml.etree.c:95690) File "parser.pxi", line 620, in lxml.etree._raiseParseError (src/lxml/lxml.etree.c:94757) lxml.etree.XMLSyntaxError: Document is empty, line 1, column 1 Using the extension Tex Text yields a similar error: Traceback (most recent call last): File "textext.py", line 210, in cb_ok self.callback(self.text, self.preamble_file, self.scale_factor) File "textext.py", line 369, in <lambda> converter_cls, old_node)) File "textext.py", line 387, in do_convert new_node = converter.convert(text, preamble_file, scale_factor) File "textext.py", line 751, in convert self.pdf_to_svg() File "textext.py", line 849, in pdf_to_svg + pstoeditOpts) File "textext.py", line 596, in exec_command % (' '.join(cmd), p.returncode, out + err)) RuntimeError: Command pstoedit -f plot-svg /var/folders/z_/v0sm2gys3y77640_7m4t99k40000gp/T/tmpAZUsxB/tmp.pdf /var/folders/z_/v0sm2gys3y77640_7m4t99k40000gp/T/tmpAZUsxB/tmp.svg -dt -ssp -psarg -r9600x9600 failed (code 1): pstoedit: version 3.70 / DLL interface 108 (built: Sep 16 2017 - release build - g++ 4.2.1 Compatible Apple LLVM 9.0.0 (clang-900.0.37) - 64-bit) : Copyright (C) 1993 - 2014 Wolfgang Glunz *** WARNING - the DELAYBIND command has been deprecated, and will be removed in the next version. For now you can restore the behaviour by using -dREALLYDEALYBIND but if you require continued use of this command you should contact the Ghostscript developers. Commercial customers of Artifex should email their support contact, free users are encouraged to talk to us on the #ghostscript IRC channel on irc.freenode.net. Unrecoverable error: undefined in DELAYBIND PostScript/PDF Interpreter finished. Return status 65280 executed command : /usr/local/opt/ghostscript/bin/gs -q -dDELAYBIND -dWRITESYSTEMDICT -dNODISPLAY -dNOEPS -r9600x9600 /var/folders/z_/v0sm2gys3y77640_7m4t99k40000gp/T//psinu3vxOs The interpreter seems to have failed, cannot proceed ! I suspect this is a bug in the respective Inkscape extensions for LaTeX output. System information: macOS 10.13.3 Inkscape 0.91 pdfTeX 3.14159265-2.6-1.40.16 (TeX Live 2015) dvips(k) 5.995 pstoedit: version 3.70 / DLL interface 108 (built: Sep 16 2017 - release build - g++ 4.2.1 Compatible Apple LLVM 9.0.0 (clang-900.0.37) - 64-bit) Best regards Jakob Peder Pettersen

2 2

Releasing Inkscape onto the Website
by Martin Owens 15 Mar '18

15 Mar '18

Dear developers, The website supports developers submitting releases using the releases app, we haven't linked to the releases app publically, but thanks to Maren and others it's a mostly complete history of Inkscape package files. To upload an inkscape package: a) Go to the website and login b) Click the "Upload Art or Resource" (or click Submit in any of your galleries to better organise your files) c) Fill in all the fields you want, make sure to include the uploaded file and gpg signature. d) Select "Inkscape Package" in the category drop down. e) Save. f) Now re-edit the new upload. This will give you the two new fields of "Release" and "Platform", these ONLY appear if: The upload is in the Inkscape Package category AND you have permission to edit releases. If you don't see these fields, make sure you join the releases team at https://inkscape.org/en /*release-team and try again. You can only have ONE resource per release, per platform. So the Inkscape 0.92.2pre0 release can have ONE Win32 MSI Package, ONE Mac OSX 10.9 DMG, etc etc. If you try to over-write, it will deny you setting the platform and release fields. We're going to try and keep the permissions to one person for each of the main platforms. So bryce can do source uploads, tgh can do Mac uploads etc etc. We make have some backups, but user wise it shouldn't need every developer to be a release team member. Let me know if you have issues. Best Regards, Martin Owens Your Friendly Website Admin

4 8

Website Caching (again)and fall-back
by Martin Owens 14 Mar '18

14 Mar '18

Hi all, This is a general notice, I've switched on nginx caching for non-logged in users. 95% of all requests are to non-logged in users. Caching is set to 1 hour, if you update a cms page, upload a new resource or make a new release, there WILL be a delay to some users getting the new information. We are closely monitoring the web server and tweaking the settings as needed. Average request times have be 0.9s-1.1s but some days see spikes to 5s (for the whole day) so we want to try and reduce the common load. Page loads for HITs are down to 120ms, compared to 980ms for a MISS. I've also removed cmsplugin-history which takes up a lot of RAM. There may be some holes in the cms, so let me know if you hit one. Page caching in nginx means that if the website goes down, nginx will keep giving our users a website as much as possible. So we may see a slight improvement in fall-over, certainly for normal users. Best Regards, Martin Owens

1 0

Quick 0.92.3pre0 test needed (was Re: inkscape-0.92.3pre0 source tarball now available)
by Bryce Harrington 14 Mar '18

14 Mar '18

I am in the process of finalizing 0.92.3 for release. Would someone mind downloading the tarball, building it, running the program, and using it a bit as a quick sanity check? Download from: https://inkscape.org/en/release/0.92.3pre0/ Eduard and I have built and run it, and so I'm not expecting there are any issues, just looking for a quick thumbs up that it works as expected for a third person. Thanks, Bryce

5 9

Question about an Issue #168 "Make Issue Responsive..."
by Tonya Sims 12 Mar '18

12 Mar '18

Hi all, I'd like to work on this patch https://gitlab.com/inkscape/inkscape-web/issues/168 and have a few questions. 1. Is this non-responsiveness happening on all pages? 2. Can you direct me to the URL where it's happening? 3. Do we have any screenshots of the issue? Thank you, Tonya

1 0

Prerequisites for using Inkscape UI free, GSOC 2018
by Kuntal Majumder 11 Mar '18

11 Mar '18

Hi, I am Kuntal, some of the people might know me from IRC. I was looking into the GSOC 2018 ideas list. Loved the idea of making Inkscape go UI free [1]. I would love to give it a try, I have used CMake to compile programs in past, but never wrote a CMakeLists file. I was also working on my own build system [2], which is currently not that nicer, well I am yet to learn how to write parsers, :P. Also whenever I used Inkscape, I used to jump to and fro from Inkscape to Calculator to get the correct ratios, wouldn't that be better if we can put expressions inside text-boxes and they evaluate by themselves. If the previous mentioned idea is viable for GSOC, I would love to pitch for it. Thanks Kuntal (hellozee) [1] http://wiki.inkscape.org/wiki/index.php/Google_Summer_of_Code#P5._UI-Free_I… [2] https://github.com/hellozee/Cook

3 4

Eager Python Developer - GSoC
by Tonya Sims 11 Mar '18

11 Mar '18

Hello everyone! My name is Tonya, I'm a junior to mid level Python developer and plan on applying for GSoC I downloaded Inkscape on my Mac and played around with it. A very cool application! What are your most urgent needs? Are your extensions built in Python? I was trying to brainstorm some ideas for a new extension and may need more time unless there's something you could suggest? Also, I'm learning Django and could help out with the website, let's say a new bug tracking system (not that you need one) but just brainstorming. Anyways, looking forward to everyone's replies and will start working on my application. Cheers, Tonya Sims

4 3

Hackfest update
by Máirín Duffy 08 Mar '18

08 Mar '18

Hi everyone, I wanted to give you a heads up about a couple of things regarding the hackfestsite - - Onthe Monday, Red Hat is also going to host a SpinachCon event on the other side of the space we'll be in. It's a 4 hour event (from 1-5 pm IIRC) where free software projects can come and have their software usability tested. The organizers (including Deb Nicholson) would be more than happy to test Inkscape as part of the event if there's any interest in that. If there are specific components you'd like tested, I can help create a testing plan. - There may be another co-hosted event in the morning on Monday, still sorting the details out. - On the Tuesday and Wednesday, Red Hat is also hosting an event that will involve a workshop and hacking on amedical image processing system that we're working on with Boston University and Boston Children's Hospital. It's a really cool project. If anyone attending has an interestin learning more, you are more than welcome to get involved. I don't expect either event to be disruptive to the hackfest; it's a large space and we have two floors and a variety of different areas to work inand a lot of seating. I just wanted to let you know ahead of time, especially in case you wanted to take advantage of SpinachCon testing.If you have a preference towards the type of space you'd prefer (large conference room with door; open meet up space; lounge-y type area with couches and tables and chairs) I can note in our reservation now that's the part we'd like for the Inkscape hackfest; if you're not sure I can give youa tour when you get here on the Monday morning and we can figure out which end of the office to claim. Cheers, ~m

4 4

Any Python GSOC projects?
by Mihaela 08 Mar '18

08 Mar '18

2 1

[RESEND] Re: slow, sluggish drawing with pencil & calligraphy tool solved
by Bryce Harrington 07 Mar '18

07 Mar '18

----- Forwarded message from Mail Delivery Subsystem <MAILER-DAEMON@...62...> ----- Date: Sat, 3 Mar 2018 18:23:21 -0800 From: Mail Delivery Subsystem <MAILER-DAEMON@...62...> To: bryce@...961... Subject: Returned mail: see transcript for details The original message was received at Fri, 2 Mar 2018 13:44:02 -0800 from static-50-53-76-183.bvtn.or.frontiernet.net [50.53.76.183] ----- The following addresses had permanent fatal errors ----- <inkscape-devel(a)lists.sourceforge.net> (reason: 550 unknown user) ----- Transcript of session follows ----- ... while talking to mx.sourceforge.net.: >>> DATA <<< 550 unknown user 550 5.1.1 <inkscape-devel(a)lists.sourceforge.net>... User unknown <<< 503-All RCPT commands were rejected with this error: <<< 503-unknown user <<< 503 Valid RCPT command must precede DATA Reporting-MTA: dns; vinyl.outflux.net Arrival-Date: Fri, 2 Mar 2018 13:44:02 -0800 Final-Recipient: RFC822; inkscape-devel(a)lists.sourceforge.net Action: failed Status: 5.1.1 Remote-MTA: DNS; mx.sourceforge.net Diagnostic-Code: SMTP; 550 unknown user Last-Attempt-Date: Sat, 3 Mar 2018 18:23:21 -0800 Date: Fri, 2 Mar 2018 13:43:52 -0800 From: Bryce Harrington <bryce@...961...> To: Yale Zhang <yzhang1985@...400...> Cc: Eduard Braun <eduard.braun2@...173...>, inkscape-devel(a)lists.sourceforge.net Subject: Re: [Inkscape-devel] slow, sluggish drawing with pencil & calligraphy tool solved Hi Yale, Thanks for working on this problem, it seems to be one of our top blockers for the 0.93 release at the moment, so your work is very much appreciated. Can you update me on how things are going right now? Are there particular things you're stuck on? I probably don't know enough to offer advice myself but maybe can suggest someone that can. If the issue looks like it can't be solved quickly, perhaps for testing purposes it might help to add one or two environment variables to turn on/off pieces of the UI or codebase that are causing problems. So if someone testing the renderer can do without the toolbar, they can disable it at runtime? Something like that? In the coming weeks I'd like to produce a testing build of Inkscape, so if there are some (ugly) ways to enable testers to work around the performance bug that would help. Bryce On Fri, Feb 16, 2018 at 02:51:43AM -0800, Yale Zhang wrote: > Thanks, I couldn't find it because I was expecting the status bar to be > drawn by Cairo. I tried to increase the priority of UPDATE_PRIORITY & > SP_UPDATE_SELECTION_PRIORITY, but couldn't do so without causing the ruler > & status bar updates to starve. > I conclude that UPDATE_PRIORITY cannot have any higher priority than > GDK_PRIORITY_REDRAW. Even when those priorities are the same, the status > bar will always get drawn before canvas because SPDesktopWidget:: > setCoordinateStatus() is called before SPCanvas::addIdle(). > > > I've pushed my changes (I did some git resets instead of revert so it's > diverged). Hopefully now, you can approve? > Sorry about the back and forth over the rulers & status bar not updating. > Shouldn't have been greedy about reducing latency by 2ms by setting > UPDATE_PRIORITY = GDK_PRIORITY_EVENTS :) > > > On Thu, Feb 15, 2018 at 3:58 PM, Eduard Braun <eduard.braun2@...173...> wrote: > > > Am 15.02.2018 um 12:23 schrieb Yale Zhang: > > > > I've updated my custom cross compiler to use MSYS2 packages and finally > > saw the lack of rule/status bar updates. Unfortunately, it had nothing to > > do with using MSYS2. I just didn't look hard enough earlier :( > > The earlier versions (including the binaries) did suffer the problem but > > only when dragging large rectangles. Plus I had _INKSCAPE_DISABLE_CACHE=1, > > making the problem less noticeable. > > > > So now I know what's wrong. The ruler update priority is G_PRIORITY_LOW = > > 300, while UPDATE_PRIORITY in SPCanvas::addIdle() is GDK_PRIORITY_EVENTS = > > 0, so it's no mystery who loses. > > > > Changing UPDATE_PRIORITY back to GDK_PRIORITY_REDRAW + 10 fixes the > > problem. But the ~10ms less latency for immediate drawing (#3) now is > > reduced because a ~2ms delay is added between SPCanvas::addIdle() and > > SPCanvas::paint(). > > > > Of course, this is perfectly usable, but I have an itch to further > > improve. That 2ms latency is gone if I disable the status bar, so I'd like > > to do the status bar updates after SPCanvas::paint(). > > > > But I can't find where the status bar is being drawn. Do you? > > And also, what is SP_DOCUMENT_UPDATE_PRIORITY and > > SP_DOCUMENT_ROUTING_PRIORITY in document.cpp? I don't know if those need to > > be rebalanced. > > > > > > The coordinates are updated by calling "SPDesktop::set_coordinate_status" > > in "desktop.cpp" (which calls "SPDesktopWidget::setCoordinateStatus" in > > "desktop-widget.cpp"). > > > > > > > > -yale > > > > > > On Wed, Feb 14, 2018 at 2:30 AM, Eduard Braun <eduard.braun2@...173...> > > wrote: > > > >> Am 14.02.2018 um 11:09 schrieb Yale Zhang: > >> > >> Good, we're getting closer to the same page. Can you please tell me which > >> of my commits did you include in your testing? If dragging is still > >> lagging, it sounds like you didn't take change #2 (priorities). You > >> complained it didn't help or made things worse, but it should be quite the > >> opposite. > >> > >> > >> As I wrote: I checked out 0bde236 and built the resulting code. It should > >> therefore have contained all you latest (public) changes. > >> > >> > >> Let me get the MSYS2 headers & libs and do a build to rule out any > >> library issues. > >> > >> > >> This would certainly help... Even though you keep telling me the stock > >> builds *should* behave differently with your changes - they don't. If > >> you're able to test yourself we'll probably safe ourselves some back and > >> forth as seeing is believing. ;-) > >> > >> > >> "warn me next time it's not relocatable" - I think all you have to do to > >> relocate was regenerate immodules.cache & loaders.cache. I wonder how the > >> release packages of Inkscape & Gimp avoid this problem. > >> > >> > >> Ah, if they contain absolute paths that might have been it. As for the > >> release packages: they contain relative paths in imloaders.cache (MSYS2 > >> contains a relocation patch for gdk-pixbuf2). Earlier versions (built wit > >> devlibs) included the loaders in libgdk_pixbuf-2.0-0.dll to work around > >> this (it's a built option) > >> > >> > >> > >> Yes, my version should be quite fast, but it has little to do with the > >> GDK optimizations. You should see the same benefits with vanilla GTK > >> (GTK_CSD=1). For the optimized version, there should be no performance > >> difference for GTK_CSD because I force the rendering code path to what > >> GTK_CSD=0 uses, plus some optimizations. > >> > >> "I'm not able to resize the Window" > >> Sorry, I forgot to mention it has my optimized, but work in progress > >> libgdk-3-0.dll. Please roll back to the stock version > >> (libgdk-3-0.dll.orig). The optimized one keeps a persistent Cairo Win32 > >> surface for window updates, but resizing isn't handled. > >> > >> > >> > >> On Tue, Feb 13, 2018 at 6:27 PM, Eduard Braun <eduard.braun2@...173...> > >> wrote: > >> > >>> I was now able to build 0bde236 > >>> > >>> - With the status bar visible I'm getting super fast redraws of the > >>> status bar with some occasional redraws of the rulers but everything else > >>> is locked when moving a rect. > >>> - With the status bar hidden I'm getting more redraws now and also > >>> infrequent redraws of the whole UI, however moving the rect is still > >>> extremely sluggish. > >>> - With the status bar and rulers hidden moving the rect has a usable > >>> redraw speed, rest of the UI (now only values in select toolbar I guess) > >>> update infrequently. > >>> > >>> Comparing with your build linked before (warn me next time it's not > >>> relocatable, I had to move it to C:\Users\Yale\inkscape.gmesh ;-) ) there > >>> are some grave differences: > >>> > >>> - Redraw is in fact much faster with your version - are these the > >>> gdk changes? Or are we really on to something fundamental? > >>> This is also true for GTK_CSD=0! > >>> - Also the rest of the UI is updated much more frequently, even with > >>> the status bar visible > >>> - In your version I'm not able to resize the Window (or rather I can > >>> but the parts that were not shown initially are not redrawn and only show > >>> some graphical garbage. Is this related to you gdk changes? > >>> > >>> > >>> Am 12.02.2018 um 13:57 schrieb Eduard Braun: > >>> > >>> Am 12.02.2018 um 13:12 schrieb Yale Zhang: > >>> > >>> Eduard, please pull change #2 (fix priority inversion) before the > >>> immediate rendering changes. Without it, the lack of status bar & ruler > >>> updates are expected. > >>> > >>> > >>> I think we're running in circles here... Most of my comments (as well as > >>> yours regarding direct drawing) referred to #3. > >>> The only issue I had with #2 was that Rulers seem still to be updated > >>> with a high priority and prevented the canvas to redraw (in stock MSYS2 > >>> builds and therefore with CSD=0). > >>> > >>> > >>> Yes, I am using CSD=1 in my testing (for both optimized & original GTK). > >>> But CSD isn't the actual reason for performance difference. It's because of > >>> the rendering code path CSD=1 uses (draw to CPU memory buffer, then send to > >>> UpdateLayeredWindow()), vs CSD=0 (draw directly to GDI device context - > >>> surprisingly this is slower until my optimizations). > >>> > >>> > >>> Please note that CSD=0/1 in our stock MSYS2 builds makes a *huge* > >>> difference. If that is really not the case for your custom builds we might > >>> want to start looking into that, too. Maybe we're facing at a more > >>> fundamental difference. As MSYS2 is the official way to get GTK+ for > >>> Windows nowadays such a difference might be very relevant for many projects. > >>> > >>> Are your cross-compiled libraries using mingw-w64? Which OS are you > >>> using btw? (I'm usually testing on Windows 10 - I'd not be surprised if > >>> there's some major difference compared to e.g. Windows 7 wrt to the low > >>> level drawing functions). > >>> > >>> I'm very interested in testing your GDK-modifications and see how they > >>> behave with the MSYS2 builds, so if you could drop a patch somewhere that > >>> would be much appreciated! > >>> > >>> I did get an error from the CI build after the multithreaded rendering > >>> feature. It doesn't even get past CMake configure stage, so not very > >>> useful. That's because the build server doesn't have the Boost libs (which > >>> I use, not just the headers). > >>> > >>> > >>> I think you looked at the Linux build - Windows CI is "external" via > >>> AppVeyor and has the required Boost libraries. It's just not working in > >>> your branch right now because an upstream update broke updating but I > >>> pushed a workaround for this already in the master branch [1] (that's why I > >>> suggested to rebase) > >>> > >>> [1] https://gitlab.com/inkscape/inkscape/commit/85d7fa343f477d8f > >>> aae6cbde90ae7a243115fa37 (I messed up the rebase so it's authored by > >>> Tav, sorry for that) > >>> > >>> > >>> > >>> > >>> On Mon, Feb 12, 2018 at 2:41 AM, Eduard Braun <eduard.braun2@...173...> > >>> wrote: > >>> > >>>> Am 12.02.2018 um 10:15 schrieb Yale Zhang: > >>>> > >>>> "As noted before, when rulers are shown there still is no redraw with > >>>> this change" > >>>> It works for me on Windows with rulers. Could it be some out of date > >>>> libraries? I'm still using a custom built cross compiler & libraries (GTK > >>>> 3.22.26 & glib 2.54.2). I know you're using the MSYS 2 prebuilt libraries. > >>>> I've been wanting to use those too, but how recent are they? > >>>> > >>>> > >>>> They are usually the latest available (think of MSYS2's MINGW-packages > >>>> as arch Linux for Windows), right now gtk 3.22.26 and glib 2.54.3. > >>>> > >>>> Aside from disabling CSD they are unpatched. Just to make sure we're > >>>> not comparing apples and oranges: Are you using CSD in your builds or not? > >>>> This switch made a huge difference before, so if you're working with CSD > >>>> enabled this might be the likely explanation why some things work in your > >>>> builds that do not work in the stock builds. > >>>> > >>>> > >>>> "It seems that the immediate drawing of the canvas basically disables > >>>> drawing of the rest of the UI" > >>>> > >>>> You scared me, that would be a most grievous mistake. I just tested it > >>>> again and don't see any problem. The rulers and status bar still work when > >>>> dragging an object. Did you build my stream directly or have any other > >>>> non-trunk changes? Sorry to suggest this but here are binaries you can > >>>> test. Maybe try copying the GTK & cairo? libs to your build. > >>>> https://1drv.ms/u/s!AngRQgSreBCehy4R7D3x3Y2vIXPC > >>>> > >>>> > >>>> I used https://gitlab.com/inkscape/inkscape/commit/78d47938194fc52e > >>>> e085387d9a0dc0753f3ed6d9 as the later commits did not compile for me. > >>>> > >>>> I'll check your build this evening. > >>>> > >>>> We also have CI builds with MSYS2 available: > >>>> https://ci.appveyor.com/project/inkscape/inkscape/history > >>>> If you rebase your branch on master your branch will be built, too (as > >>>> long as there are not more errors/warnings preventing the build) > >>>> > >>>> I hope you're not suggesting to forget about immediate drawing and just > >>>> fix the drawing priorities. Using priorities would be easier to break, > >>>> while drawing immediately is fool proof. > >>>> > >>>> > >>>> I'm just saying that priorities have been tweaked before to make all UI > >>>> update properly and we should aim to retain this state. > >>>> If direct drawing is compatible with this goal (I guess it was in gtk2) > >>>> that's probably fine. > >>>> > >>>> > >>>> "Have you published [GTK3] code anywhere? " > >>>> No, I haven't had time yet. I also want to discuss the problem I posed > >>>> on StackOverflow and someone suggested IRC, but that I've never used IRC > >>>> and it sounds very 1990s. > >>>> > >>>> > >>>> It's like SMS... it just works (even today)... > >>>> A lot easier than all the modern stuff that claims to be easier than > >>>> IRC. > >>>> > >>>> I've talked to gtk devs on IRC before and it's the easiest way to get > >>>> some interaction (bug reports usually fall into oblivion sooner rather than > >>>> later). > >>>> > >>>> > >>>> BTW, the optimized GTK also disables clearing the region to be drawn > >>>> (gdk_window_clear_backing_region()). > >>>> > >>>> "Is [render cache] always slow?" > >>>> It's only much slower if drawing a big area AND the scene complexity is > >>>> low. For small areas and high complexity scenes, the overhead is much less > >>>> noticeable. > >>>> > >>>> > >>>> I see... I guess before the low complexity scenes were not that > >>>> important as redraw times were sufficiently fast anyway. > >>>> User reports of slow redrawing usually involve blurs (or less > >>>> frequently other filters). > >>>> > >>>> > >>>> For the multithreaded rendering, it's still a work in progress. AFAIK, > >>>> I've eliminated all the race conditions with ThreadSanitizer, so it should > >>>> be stable. > >>>> I just pushed some further changes to allow the rendering to be > >>>> incremental like it always has been. It should have that -fpermissive > >>>> compile error in sp-canvas.cpp fixed, but you might still need it for other > >>>> files. > >>>> > >>>> > >>>> I'll try to build this evening. > >>>> As recommended before you could check the CI to make sure your branch > >>>> is properly built, which should help with testing. > >>>> > >>>> Regards, > >>>> Eduard > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> > >>>> On Sun, Feb 11, 2018 at 8:37 AM, Eduard Braun <eduard.braun2@...173...> > >>>> wrote: > >>>> > >>>>> Hi Yale, > >>>>> > >>>>> thanks for continuing to investigate this! Some comments: > >>>>> > >>>>> > >>>>> Am 09.02.2018 um 16:02 schrieb Yale Zhang: > >>>>> > >>>>> I have an update on my progress. I've made these changes which I'm > >>>>> requesting to be merged from my simdgenius_inkscape branch > >>>>> > >>>>> 1. disable event compression (previously mentioned) > >>>>> > >>>>> 2. fix priority inversion (09f55021, previously mentioned) - without > >>>>> this, dragging objects too fast would cause no redraw. > >>>>> > >>>>> > >>>>> As noted before, when rulers are shown there still is no redraw with > >>>>> this change > >>>>> > >>>>> > >>>>> 3. draw immediately (78d47938) this partially reverts Krzysztof's > >>>>> Hack fest 2016 changes like in 0.92. This reduces latency by ~10ms > >>>>> (compare cells G22 and E22 in spreadsheet) > >>>>> > >>>>> I originally wanted to remove backing store and draw directly to the > >>>>> window surface, but I ran into this dilema so I didn't do it. > >>>>> > >>>>> https://stackoverflow.com/questions/48339792/when-drawing-to > >>>>> -a-window-are-the-previous-contents-usually-discarded-and-what > >>>>> > >>>>> > >>>>> While this change does indeed speed up drawing a lot I'm not sure it's > >>>>> for the reason we hope for: > >>>>> It seems that the immediate drawing of the canvas basically disables > >>>>> drawing of the rest of the UI (i.e. rulers, coordinates in the lower right, > >>>>> coordinates in inputs, etc). If I hide all UI elements (Ctrl+F11) I get the > >>>>> same perceived performance even without your code change. > >>>>> > >>>>> While I guess redrawing the canvas is to be preferred over redrawing > >>>>> other UI elements, not redrawing the rest of the UI at all is probably not > >>>>> desirable either. > >>>>> Also it poses the question: Why did gtk2 manage to redraw the canvas > >>>>> *and* the UI and still yield higher performance than gtk3? So I'm not sure > >>>>> we're not still missing the actual regression. :-/ > >>>>> > >>>>> > >>>>> But there is still way more speedup to be had: > >>>>> > >>>>> 1. *rendering cache slows things down 6x!* Compare cells E9 & E10 in > >>>>> the spreadsheet. > >>>>> WTH? > >>>>> > >>>>> > >>>>> Is it always slow? I guess for something simple like a rectangle it > >>>>> might not improve things, but maybe things start to change as soon as > >>>>> filters are involved (or many nodes or anything else that is not easy to > >>>>> render)? > >>>>> I admit I was not involved when the rendering cache was added and do > >>>>> not know its purpose. I tracked down the commit in which it was added [1] > >>>>> which does not explain anything either, though, so I need to continue > >>>>> digging... If anybody knows where the changes are actually explained some > >>>>> feedback is welcome. > >>>>> > >>>>> [1] https://gitlab.com/inkscape/inkscape/commit/093f4174abc07b4e > >>>>> a523617fccdd8028f2670fea > >>>>> > >>>>> > >>>>> 2. optimize GDK (maybe it's only slow on Windows) - compare cells J17 > >>>>> and J23 > >>>>> I made 2 changes: > >>>>> a. disabled layered windows - this is almost the same effect as > >>>>> setting GTK_CSD=0. I'm not clear why it speeds things up. I'm guessing it > >>>>> reduces image copying. Layered windows have to draw to CPU memory (GDI > >>>>> DIB), while non-layered windows draw directly to GPU memory (device > >>>>> dependent bitmap)? > >>>>> > >>>>> b. replace surface_content = gdk_window_get_content (window); > >>>>> in gdk_window_begin_paint_internal() > >>>>> with surface_content = CAIRO_CONTENT_COLOR_ALPHA > >>>>> > >>>>> why create/delete a surface just to get the type? > >>>>> > >>>>> > >>>>> Have you published this code anywhere? Also is there any upstream > >>>>> discussion on this yet which I could follow? > >>>>> > >>>>> > >>>>> 3. multithreaded rendering - I've updated it to work with trunk, so > >>>>> you can try it. Very little speed up for simple scenes. > >>>>> > >>>>> > >>>>> Unfortunately the code does not compile for me, excerpt from the error: > >>>>> sp-canvas.cpp:802:22: error: passing 'const boost::shared_mutex' > >>>>> as 'this' argument discards qualifiers [-fpermissive] > >>>>> > >>>>> Do you want us to compile your code with -fpermissive? > >>>>> > >>>>> > >>>>> > >>>>> -Yale > >>>>> > >>>>> > >>>>> Regards, > >>>>> Eduard > >>>>> > >>>> > >>>> > >>>> > >>> > >>> > >>> > >>> ------------------------------------------------------------------------------ > >>> 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 listInkscape-devel@...1901...://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 > https://lists.sourceforge.net/lists/listinfo/inkscape-devel ----- End forwarded message -----

2 1

Running the build on mac
by Elizabeth Kirby 07 Mar '18

07 Mar '18

Hi all, I'm trying to get inkscape to run on the mac. I downloaded a zip of the code (recently) & installed a handful of packages using ports. There was one dependency that I couldn't get to resolve using any ports package, which is libsoup. I installed it using brew & then the code will compile. It will run, but not correctly. I put in a symlink from /usr/share/inkscape to my build tree share directory & it does load the items on the right & left sides, but without any of the images that tell what they are. I would rather not have a symlink in /usr/share, but instead just have the build read from the build tree. Are there any people developing on mac out there that can share their configuration & settings & tell me what parameters need to be set & where? Thanks, Beth

3 4

Re: [Inkscape-devel] [googlefonts-discuss] Re: Variable Fonts support in Inkscape
by Felipe Sanches 07 Mar '18

07 Mar '18

2018-03-06 17:49 GMT-03:00 Khaled Hosny <khaledhosny@...3544...>: > FreeType/FontConfig/Cairo/Pango stack has more or less full variable > fonts support now, Inkscape needs to be updated to make use of the > support already available in all these libraries. > > https://blogs.gnome.org/mclasen/2018/01/03/more-fun-with-fonts/ Wow! This is super cool! I specially loved the CSS animation of the weight of the text when the cursor hovers over a button. This seems to replace Tav's opentype features selector via a GTK font-selector dialog. It also seems that we could have the innitial variable fonts support in inkscape basically hooking up to this newly improved GTK dialog. Naturally, that would require Inkscape to rely on a pretty recent version of GTK.

1 2

Inkscape PGP signatures and SHA256 checksums?
by Tom Spettigue 06 Mar '18

06 Mar '18

Hey guys. I was wondering if you guys provided PGP signatures of your guys' installer files? If so, I couldn't find the site, it'd be nice to have links to the pgp signatures and pgp signing keys right there on the download page. If you guys don't have this, it'd be a great way for us to verify that the installers that we download are genuine. SHA256 checksums (for users who understand hashing, but not PGP) would be pretty rad, too. -- Tom Spettigue Advent Information Systems, L.L.C. 1607 Capitol Avenue, Suite 220 Cheyenne, WY 82001 Mobile: (307) 298-0299 Email: tom@...3644...

1 0

Re: [Inkscape-devel] [googlefonts-discuss] Re: Variable Fonts support in Inkscape
by Felipe Sanches 06 Mar '18

06 Mar '18

I left this aside for the past 6 months and recently got back to looking at it. I think the most trivial thing would be to populate the font-styles combo-box with named instances. This would be almost not perceptible by the users, but would enable variable fonts' instances to show up there just like their non-variable counterparts do. Then there's the customization aspect of varfonts. For that, I think the bare minimum would be a bunch of sliders for selecting the coordinates of each variation axis. I feel that there must be something better than that form a user experience perspective, but I'm still not sure what would that be, so I'd leave it for a second iteration of the UI. Also, since one can get a multitude of combinations within the designspace, I think it could be practical to adopt a UI workflow similar to that of color gradients, in which once a user-defined instance is applied to a text chunk, that instance is added to a pool of var font instances that can be reused in other chunks of texto within the document. A shared varfont would then, upon tweaking of its design space coordiantes, affect all portions of the document where it was used. Finally, and this is not a varfont specific issue, I feel the urge to improve the basic text support in Inkscape in general. Yes, I know this is a somewhat vague statement. The overall direction I'd like to follow, though, would likely be something similar to the insightful ideas that are expressed in this article: https://medium.com/@getflourish/the-anatomy-of-a-thousand-typefaces-f7b9088… cheers, Felipe Sanches 2018-03-06 11:27 GMT-03:00 Pathum Egodawatta <pathumego@...400...>: > Hi Filipe! > > Hope you are doing well. Thanks for taking this on! would be aweosme to > have the VF support. > > Whats new in this? I would love to know more about the UI interactions and > tooltips. > > Cheers, > Pathum > > On Tuesday, May 30, 2017 at 1:18:41 AM UTC+5:30, Felipe Sanches wrote: >> >> I'm working on implementing Opentype Variable fonts support in Inkscape >> (based on a mix of pango and harfbuzz APIs). >> >> While testing the current pango-based text handling implementation in >> Inkscape I tried to edit some arabic text (with several ligatures, >> naturally) and I ended up finding a crasher bug. I have just reported it at: >> >> https://bugs.launchpad.net/inkscape/+bug/1694323 >> >> I'll be using this thread to liberally report ongoing progress on this >> effort. >> >> happy hacking, >> Felipe Sanches >> > -- > You received this message because you are subscribed to the Google Groups > "Google Fonts Discussions" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to googlefonts-discuss+unsubscribe@...3168... > To post to this group, send email to googlefonts-discuss@...3168... > Visit this group at https://groups.google.com/group/googlefonts-discuss. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/googlefonts-discuss/89f8f75b-071b-4c26-85f5- > 5232780a9d0d%40googlegroups.com > <https://groups.google.com/d/msgid/googlefonts-discuss/89f8f75b-071b-4c26-85…> > . > > For more options, visit https://groups.google.com/d/optout. >

2 2

Re: [Inkscape-devel] inkscape-0.92.3pre0 source tarball now available
by Martin Owens 06 Mar '18

06 Mar '18

On Sun, 2018-03-04 at 11:32 -0800, Bryce Harrington wrote: > Yes, still upload the end-user downloadable content to the website. > We have mirroring and caching set up there. > > Feel free to also copy the source tarball to the website. A bit unfair to ask Eduard to do this, if the website isn't letting you deploy files easily, then that's a tooling issue we can fix. But I can't fix it if the social protocol is to not ask for help and instead figure out a technical workaround. Regards, Martin, Website guy who can help

4 12

[RESEND] inkscape-0.92.3pre0 source tarball now available
by Bryce Harrington 05 Mar '18

05 Mar '18

----- Forwarded message from Mail Delivery Subsystem <MAILER-DAEMON@...62...> ----- Date: Sat, 3 Mar 2018 21:02:24 -0800 From: Mail Delivery Subsystem <MAILER-DAEMON@...62...> To: bryce@...961... Subject: Returned mail: see transcript for details The original message was received at Sat, 3 Mar 2018 21:01:53 -0800 from static-50-53-76-183.bvtn.or.frontiernet.net [50.53.76.183] ----- The following addresses had permanent fatal errors ----- <inkscape-devel@...6...> (reason: 550 unknown user) ----- Transcript of session follows ----- ... while talking to mx.sourceforge.net.: >>> DATA <<< 550 unknown user 550 5.1.1 <inkscape-devel@...6...>... User unknown <<< 503-All RCPT commands were rejected with this error: <<< 503-unknown user <<< 503 Valid RCPT command must precede DATA Reporting-MTA: dns; vinyl.outflux.net Received-From-MTA: DNS; static-50-53-76-183.bvtn.or.frontiernet.net Arrival-Date: Sat, 3 Mar 2018 21:01:53 -0800 Final-Recipient: RFC822; inkscape-devel@...6... Action: failed Status: 5.1.1 Remote-MTA: DNS; mx.sourceforge.net Diagnostic-Code: SMTP; 550 unknown user Last-Attempt-Date: Sat, 3 Mar 2018 21:02:08 -0800 Date: Sat, 3 Mar 2018 21:01:43 -0800 From: Bryce Harrington <bryce@...961...> To: inkscape-devel@...6... Cc: Ryan Gorley <ryan@...3508...>, Martin Owens <doctormo@...400...>, the Adib <theadib@...400...>, David Evans <devans@...2376...>, Tim Sheridan <tghs@...3462...>, Ted Gould <ted@...11...>, mrdocs <mrdocs@...715...>, Gord Caswell <ve4jhj@...400...>, Eduard Braun <Eduard.Braun2@...173...> Subject: inkscape-0.92.3pre0 source tarball now available The 0.92.3pre0 pre-release source tarball is ready for packaging. It can be downloaded from: http://alpha.inkscape.org/releases/inkscape-0.92.3pre0.tar.bz2 The 0.92.x branch should now be considered in Hard Freeze + String Freeze. Please touch base with me for any changes to code or translations from now until release. --- I'm late as usual with cutting the release, but other than that things have gone smoothly. I would very much appreciate if people could build and test and give me a thumbs up if everything looks normal. If no serious issues crop up I will cut the final release next weekend. Bryce ----- End forwarded message -----

5 7

Boston hackfest sticker: Boston Teaparty Ships version
by C R 05 Mar '18

05 Mar '18

https://www.dropbox.com/s/vzo7eq2tjc2njys/inkscape_foil_sticker_boston_hack…

5 4

Re: [Inkscape-devel] (re-)Introducing: ink/stitch, machine embroidery for Inkscape
by Lex Neva 05 Mar '18

05 Mar '18

On Sun, 2018-03-04 at 12:26 +0000, inkscape-devel-request@...349... orge.net wrote: > Very cool Lex, > I know you mentioned translations, but I'm curious about what other > issues you've hit being an extension that is distributed separately > from Inkscape. We've talked a bunch about how to decouple the release > cycle of extensions and the core, but I'm not sure that we understand > all of the problems. I'm so glad you asked! There are a few rough edges that we had to work around. In fact, one of them just came up: https://github.com/lexelby/inkstitc h/issues/18#issuecomment-370301197. In that thread, we're talking about creating a PDF printout feature that shows the colors used in a design and the order they sew in. My original plan was to use the nifty, growing list of features in the command-line interface for Inkscape. My understanding is that these features are provided specifically to act as a "standard library" of functionality that can be used by extensions. The problem with this is that extensions don't know where the Inkscape binary is. I can imagine writing code to guess, or perhaps look at the parent process, but trying to support Linux, Windows, and Mac sounds like a nightmare. End result: ink/stitch can't use this functionality. Another rough edge is that extensions don't know where the current SVG file is stored on disk. We can access the file's basename, but not the directory. This is kind of annoying because ink/stitch wants to output a machine embroidery design file (.DST, .PES, etc). ink/stitch works around this by storing all of these files in a set "output directory" specified by the user, but this is obviously not ideal. Here's where one of our users/contributors discusses his desire for the design file to save alongside the SVG: https://github.com/lexelby/inkstitch/issues/ 75 I gather that Inkscape did previously store the directory, but it was removed due to privacy concerns. Perhaps the directory can be included in the SVG _only_ when communicating with an extension, not when saving? Another possibility is that the embroidery design output functionality could be an "output" extension, but I haven't played with that. I'm under the impression that the user would have to choose a folder and file name every time they wanted to save using an output plugin, which would be a prohibitively bad user experience for ink/stitch since it's common to repeatedly re-render the design file until you get it right. "Dependency hell" is another big issue for extensions. Pyinstaller is very promising as a solution to this problem! I highly recommend mentioning it in the inkscape extension documentation. Trying to explain to users how to install python modules required by an extension is destined for failure. On Windows and Mac, the problem is even worse, as Inkscape bundles its own Python. It's very confusing for users that they can do `pip install -r requirements.txt` but then inkstitch still can't load its dependencies, because they didn't install the requirements in Inkscape's bundled Python. Installing modules for Windows's Python is especially complex. Ultimately, we desire a completely smooth, painless installation process for our users. Currently, installation involves downloading a ZIP/tarball and uncompressing it in Inkscape's extensions directory. This is pretty smooth, and we could refine it even more by distributing it as a self-extracting installer. Anything more complex than uncompressing an archive risks losing users before they even try our extension. One final thing: Inkscape's extension model is powerful and nifty, but of course it's also limiting. We've gone to a lot of lengths to work around this limitation, including popping up an entire UI of our own in one of ink/stitch's bundled extensions. Still, we constantly bump into the inability to integrate more directly with Inkscape, by adding tools or the like. I'm sure you've encountered this idea before. :) If Inkscape introduces such functionality, we'll be among the first to try it out. > Also, do you have any pictures of something embroidered using the > extension? I saw the screencasts but I'd love to see the objects they > resulted in as well. > Ted Sure! Here's a sampling of my favorite patches that I've made using ink/stitch: https://github.com/lexelby/inkstitch/tree/master/images/patches

1 0

[RESEND] Re: [Inkscape-board] Inkscape Board Meeting
by Bryce Harrington 04 Mar '18

04 Mar '18

----- Forwarded message from Mail Delivery System <Mailer-Daemon@...34...> ----- Date: Sun, 04 Mar 2018 02:23:24 +0000 From: Mail Delivery System <Mailer-Daemon@...34...> To: bryce@...961... Subject: Mail delivery failed: returning message to sender This message was created automatically by mail delivery software. A message that you sent could not be delivered to one or more of its recipients. This is a permanent error. The following address(es) failed: inkscape-board(a)lists.sourceforge.net host sfs-lb-ml.sog [172.30.20.202] SMTP error from remote mail server after RCPT TO:<inkscape-board(a)lists.sourceforge.net>: 550 Unknown user Reporting-MTA: dns; sfi-mx-1.v28.lw.sourceforge.com Action: failed Final-Recipient: rfc822;inkscape-board(a)lists.sourceforge.net Status: 5.0.0 Remote-MTA: dns; sfs-lb-ml.sog Diagnostic-Code: smtp; 550 Unknown user Date: Fri, 2 Mar 2018 15:18:03 -0800 From: Bryce Harrington <bryce@...961...> To: inkscape-board(a)lists.sourceforge.net Cc: inkscape-devel(a)lists.sourceforge.net Subject: Re: [Inkscape-board] Inkscape Board Meeting Transcript from meeting: http://alpha.inkscape.org/board/meetings/transcripts/board_meeting_2018-03-… New action items: ==== Budget 2018 ==== ♢ ACTION: Increase amount allocated to hackfests and post a v2 for the budget [bryce] ==== Madras Printer's and Lithographers' Association ==== ♢ ACTION: Find two (or three?) Inkscape people to send to the Color/Scribus meeting to learn about how we could do better color management with Inkscape. ==== Boston Hackfest ==== ♢ ACTION: Send Hackfest invites to oldtimers [Tavmjong] ==== Other Business ==== ♢ ACTION: Investigate Fastly invoice charges [scislac,bryce] Previous action items: ♢ ACTION: Analyze how we could improve internal handling of Illustrator and Corel file import [crogers] ♢ ACTION: Follow up with MPLA to clarify on funded development and general sponsorship options [bryce] ♦ ACTION: Start reaching out to people (including previous contributors) to attend the hackfest. [Tavmjong] ♦ ACTION: Arrange votes for any special case travelers for hackfest. [bryce] ♦ ACTION: Try one more time to access spreadshirt password, then email bryce for help [crogers] ♦ ACTION: Collab on markdown formatting for the board docs [bryce,tedg] ♦ ACTION: Get the word out about LGM / Inkscape and invite more attendees [Tavmjong] ♢ ACTION: Evaluate use of discorse (https://discuss.pixls.us/ ?) for support/mailing list/forum type stuff [Vector Team] ♦ ACTION: Arrange vote on Budget 2018 [bryce] ♢ ACTION: Make a list of projects for cleaning up our code base [Tav] ♦ ACTION: Decide what oldtimers to send hackfest invites to [bryce] ♢ ACTION: Collect CMYK ideas into Color_management wiki page [alface] Bryce On Thu, Mar 01, 2018 at 08:48:27AM -0800, Bryce Harrington wrote: > Our monthly board meeting is scheduled for this Friday, Mar 2nd, > at 10am Pacific in #inkscape-devel. All members are welcome. > > http://wiki.inkscape.org/wiki/index.php/Board_Meetings > > (Note that a Release Team meeting will follow immediately after. > The Vectors Team will be meeting the next day.) > > > Agenda: > > + Madras Printer's and Lithographers' Association > + Boston Hackfest (March) [doctormo] > + Merchandise sales [crogers] > + Board election process review [tedg] > + Infrastructure hosting [bryce] > + LGM 2018 [Tav] > + GSoC [ScislaC] > + Other Business > > > Action Items from last meeting: > > ♢ ACTION: Arrange vote on Budget 2018 [bryce] > ♢ ACTION: Make a list of projects for cleaning up our code base [Tav] > ♢ ACTION: Send invites to old Inkscapers to attend hackfest [bryce] > ♢ ACTION: Collect CMYK ideas into Color_management wiki page [alface] > ♢ ACTION: Analyze how we could improve internal handling of > Illustrator and Corel file import [crogers] > ♢ ACTION: Follow up with MPLA to clarify on funded development and > general sponsorship options [bryce] > ♢ ACTION: Start reaching out to people (including previous > contributors) to attend the hackfest. [tedg] > ♢ ACTION: Arrange votes for any special case travelers for > hackfest. [bryce] > ♢ ACTION: Try one more time to access spreadshirt password, then > email bryce for help [crogers] > ♢ ACTION: Collab on markdown formatting for the board docs > [bryce,tedg] > ♢ ACTION: Get the word out about LGM / Inkscape and invite more > attendees [Tavmjong] > ♢ ACTION: Evaluate use of discorse (https://discuss.pixls.us/ ?) for > support/mailing list/forum type stuff [Vector Team] > > > Bryce > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Inkscape-board mailing list > Inkscape-board(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-board ----- End forwarded message -----

1 0

[RESEND] Re: [Inkscape-board] Inkscape Board Meeting
by Bryce Harrington 04 Mar '18

04 Mar '18

----- Forwarded message from Mail Delivery Subsystem <MAILER-DAEMON@...62...> ----- Date: Sat, 3 Mar 2018 18:23:21 -0800 From: Mail Delivery Subsystem <MAILER-DAEMON@...62...> To: bryce@...961... Subject: Returned mail: see transcript for details The original message was received at Fri, 2 Mar 2018 15:18:14 -0800 from static-50-53-76-183.bvtn.or.frontiernet.net [50.53.76.183] ----- The following addresses had permanent fatal errors ----- <inkscape-devel(a)lists.sourceforge.net> (reason: 550 unknown user) ----- Transcript of session follows ----- ... while talking to mx.sourceforge.net.: >>> DATA <<< 550 unknown user 550 5.1.1 <inkscape-devel(a)lists.sourceforge.net>... User unknown Reporting-MTA: dns; vinyl.outflux.net Arrival-Date: Fri, 2 Mar 2018 15:18:14 -0800 Final-Recipient: RFC822; inkscape-devel(a)lists.sourceforge.net Action: failed Status: 5.1.1 Remote-MTA: DNS; mx.sourceforge.net Diagnostic-Code: SMTP; 550 unknown user Last-Attempt-Date: Sat, 3 Mar 2018 18:23:19 -0800 Date: Fri, 2 Mar 2018 15:18:03 -0800 From: Bryce Harrington <bryce@...961...> To: inkscape-board(a)lists.sourceforge.net Cc: inkscape-devel(a)lists.sourceforge.net Subject: Re: [Inkscape-board] Inkscape Board Meeting Transcript from meeting: http://alpha.inkscape.org/board/meetings/transcripts/board_meeting_2018-03-… New action items: ==== Budget 2018 ==== ♢ ACTION: Increase amount allocated to hackfests and post a v2 for the budget [bryce] ==== Madras Printer's and Lithographers' Association ==== ♢ ACTION: Find two (or three?) Inkscape people to send to the Color/Scribus meeting to learn about how we could do better color management with Inkscape. ==== Boston Hackfest ==== ♢ ACTION: Send Hackfest invites to oldtimers [Tavmjong] ==== Other Business ==== ♢ ACTION: Investigate Fastly invoice charges [scislac,bryce] Previous action items: ♢ ACTION: Analyze how we could improve internal handling of Illustrator and Corel file import [crogers] ♢ ACTION: Follow up with MPLA to clarify on funded development and general sponsorship options [bryce] ♦ ACTION: Start reaching out to people (including previous contributors) to attend the hackfest. [Tavmjong] ♦ ACTION: Arrange votes for any special case travelers for hackfest. [bryce] ♦ ACTION: Try one more time to access spreadshirt password, then email bryce for help [crogers] ♦ ACTION: Collab on markdown formatting for the board docs [bryce,tedg] ♦ ACTION: Get the word out about LGM / Inkscape and invite more attendees [Tavmjong] ♢ ACTION: Evaluate use of discorse (https://discuss.pixls.us/ ?) for support/mailing list/forum type stuff [Vector Team] ♦ ACTION: Arrange vote on Budget 2018 [bryce] ♢ ACTION: Make a list of projects for cleaning up our code base [Tav] ♦ ACTION: Decide what oldtimers to send hackfest invites to [bryce] ♢ ACTION: Collect CMYK ideas into Color_management wiki page [alface] Bryce On Thu, Mar 01, 2018 at 08:48:27AM -0800, Bryce Harrington wrote: > Our monthly board meeting is scheduled for this Friday, Mar 2nd, > at 10am Pacific in #inkscape-devel. All members are welcome. > > http://wiki.inkscape.org/wiki/index.php/Board_Meetings > > (Note that a Release Team meeting will follow immediately after. > The Vectors Team will be meeting the next day.) > > > Agenda: > > + Madras Printer's and Lithographers' Association > + Boston Hackfest (March) [doctormo] > + Merchandise sales [crogers] > + Board election process review [tedg] > + Infrastructure hosting [bryce] > + LGM 2018 [Tav] > + GSoC [ScislaC] > + Other Business > > > Action Items from last meeting: > > ♢ ACTION: Arrange vote on Budget 2018 [bryce] > ♢ ACTION: Make a list of projects for cleaning up our code base [Tav] > ♢ ACTION: Send invites to old Inkscapers to attend hackfest [bryce] > ♢ ACTION: Collect CMYK ideas into Color_management wiki page [alface] > ♢ ACTION: Analyze how we could improve internal handling of > Illustrator and Corel file import [crogers] > ♢ ACTION: Follow up with MPLA to clarify on funded development and > general sponsorship options [bryce] > ♢ ACTION: Start reaching out to people (including previous > contributors) to attend the hackfest. [tedg] > ♢ ACTION: Arrange votes for any special case travelers for > hackfest. [bryce] > ♢ ACTION: Try one more time to access spreadshirt password, then > email bryce for help [crogers] > ♢ ACTION: Collab on markdown formatting for the board docs > [bryce,tedg] > ♢ ACTION: Get the word out about LGM / Inkscape and invite more > attendees [Tavmjong] > ♢ ACTION: Evaluate use of discorse (https://discuss.pixls.us/ ?) for > support/mailing list/forum type stuff [Vector Team] > > > Bryce > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Inkscape-board mailing list > Inkscape-board(a)lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/inkscape-board ----- End forwarded message -----

1 0

[RESEND] Re: inkscape-0.92.3pre0 source tarball now available
by Bryce Harrington 04 Mar '18

04 Mar '18

Hoping SF is back online... ----- Forwarded message from Mail Delivery Subsystem <MAILER-DAEMON@...62...> ----- Date: Sun, 4 Mar 2018 11:32:58 -0800 From: Mail Delivery Subsystem <MAILER-DAEMON@...62...> To: bryce@...961... Subject: Returned mail: see transcript for details The original message was received at Sun, 4 Mar 2018 11:32:24 -0800 from static-50-53-76-183.bvtn.or.frontiernet.net [50.53.76.183] ----- The following addresses had permanent fatal errors ----- <inkscape-devel@...6...> (reason: 550 unknown user) ----- Transcript of session follows ----- ... while talking to mx.sourceforge.net.: >>> DATA <<< 550 unknown user 550 5.1.1 <inkscape-devel@...6...>... User unknown <<< 503-All RCPT commands were rejected with this error: <<< 503-unknown user <<< 503 Valid RCPT command must precede DATA Reporting-MTA: dns; vinyl.outflux.net Received-From-MTA: DNS; static-50-53-76-183.bvtn.or.frontiernet.net Arrival-Date: Sun, 4 Mar 2018 11:32:24 -0800 Final-Recipient: RFC822; inkscape-devel@...6... Action: failed Status: 5.1.1 Remote-MTA: DNS; mx.sourceforge.net Diagnostic-Code: SMTP; 550 unknown user Last-Attempt-Date: Sun, 4 Mar 2018 11:32:41 -0800 Date: Sun, 4 Mar 2018 11:32:14 -0800 From: Bryce Harrington <bryce@...961...> To: Eduard Braun <eduard.braun2@...173...> Cc: inkscape-devel@...6..., Ryan Gorley <ryan@...3508...>, Martin Owens <doctormo@...400...>, the Adib <theadib@...400...>, David Evans <devans@...2376...>, Tim Sheridan <tghs@...3462...>, Ted Gould <ted@...11...>, mrdocs <mrdocs@...715...>, Gord Caswell <ve4jhj@...400...> On Sun, Mar 04, 2018 at 01:51:36PM +0100, Eduard Braun wrote: > Am 04.03.2018 um 06:01 schrieb Bryce Harrington: > >The 0.92.3pre0 pre-release source tarball is ready for packaging. It > >can be downloaded from: > > > > http://alpha.inkscape.org/releases/inkscape-0.92.3pre0.tar.bz2 > > > >The 0.92.x branch should now be considered in Hard Freeze + String Freeze. > >Please touch base with me for any changes to code or translations from > >now until release. > > > >--- > > > >I'm late as usual with cutting the release, but other than that things > >have gone smoothly. I would very much appreciate if people could build > >and test and give me a thumbs up if everything looks normal. If no > >serious issues crop up I will cut the final release next weekend. > > > >Bryce > > Thanks Bryce! > > As you did not publish a schedule this time you're probably only late > according to your own private schedule - If you hadn't mentioned it nobody > would have noticed. ;-) True. :-) > Windows binaries and installers are available at [1] (64-bit) and [2] > (32-bit). > Do you want them on the website Bryce? (I noticed you uploaded the tarball > to alpha.inkscape.org -- do we even want to add a release to the releases > app on the website for the pre-release then? I think it can only consume > gallery items...) Yes, still upload the end-user downloadable content to the website. We have mirroring and caching set up there. Feel free to also copy the source tarball to the website. Going forward, I'm going to stage the source tarballs on alpha. It makes the dist machinery cleaner and more easily automated it can just scp the files up directly to the webserver. And if I need to re-upload the tarball I can do it without needing to rename it, which has been a problem in the past. I don't think we have any particular bandwidth limits for alpha, but for stuff we know is going to get tons of hits probably best if we have it going through Fastly. Bryce > [1] https://ci.appveyor.com/project/inkscape/inkscape/build/INKSCAPE_0_92_3_PRE… > [2] https://ci.appveyor.com/project/inkscape/inkscape/build/INKSCAPE_0_92_3_PRE… > > Regards, > Eduard ----- End forwarded message -----

1 0

Testing
by Bryce Harrington 04 Mar '18

04 Mar '18

Sourceforge has been broken much of the week, but their twitter claims it's back online. Checking to see if our lists work once again... Bryce

1 0

Re: [Inkscape-devel] inkscape-0.92.3pre0 source tarball now available
by Eduard Braun 04 Mar '18

04 Mar '18

Am 04.03.2018 um 06:01 schrieb Bryce Harrington: > The 0.92.3pre0 pre-release source tarball is ready for packaging. It > can be downloaded from: > > http://alpha.inkscape.org/releases/inkscape-0.92.3pre0.tar.bz2 > > The 0.92.x branch should now be considered in Hard Freeze + String Freeze. > Please touch base with me for any changes to code or translations from > now until release. > > --- > > I'm late as usual with cutting the release, but other than that things > have gone smoothly. I would very much appreciate if people could build > and test and give me a thumbs up if everything looks normal. If no > serious issues crop up I will cut the final release next weekend. > > Bryce Thanks Bryce! As you did not publish a schedule this time you're probably only late according to your own private schedule - If you hadn't mentioned it nobody would have noticed. ;-) Windows binaries and installers are available at [1] (64-bit) and [2] (32-bit). Do you want them on the website Bryce? (I noticed you uploaded the tarball to alpha.inkscape.org -- do we even want to add a release to the releases app on the website for the pre-release then? I think it can only consume gallery items...) [1] https://ci.appveyor.com/project/inkscape/inkscape/build/INKSCAPE_0_92_3_PRE… [2] https://ci.appveyor.com/project/inkscape/inkscape/build/INKSCAPE_0_92_3_PRE… Regards, Eduard

1 0

wiki account
by Jan 03 Mar '18

03 Mar '18

hi I need a wiki account to enhance a few articles.

2 1

(re-)Introducing: ink/stitch, machine embroidery for Inkscape
by Lex Neva 02 Mar '18

02 Mar '18

Hi folks! I'd like to reintroduce you to ink/stitch, formerly known as inkscape-embroidery. A lot has happened in the past couple of months, and we now have a thriving and growing open source community around the extension! The coolest new thing is that ink/stitch is available is a self-contained ZIP containing every Python dependency and all needed shared libraries. There's also a Windows version and a Mac build is in the works. I think you folks might be especially interested in our solution for creating the ZIP/tarball archive. We're using the excellent Pyinstaller, which seems especially well-suited to packaging inkscape extensions. Our goal is to avoid the kind of dependency hell that normally plagues extensions, especially those like ink/stitch that have their own GUI. Pyinstaller packages everything into a native executable. Interestingly, inkscape does not support native executables as extensions and requires an interpreter! We get around this by including a basic stub Python script that executes the real extension binary and forwards the results back to inkscape. Another interesting tidbit for inkscape devs is our localization support. Ink/stitch is currently available in three languages, but the INX is not yet localized. This is because inkscape's localization support for INX files depends on the extension translations being bundled with inkscape. This obviously doesn't work for an extension with a fast release cycle. We're exploring our options. We'd love it if you'd check out project it and perhaps even give it a spin. If you're interested in contributing, that'd be even cooler! Right now, more folks with programming skills would be especially helpful as we have a long feature request backlog, but any contributions would be awesome. Here's ink/stitch: https://github.com/lexelby/inkstitch Happy hacking, Lex On March 1, 2018 7:41:07 AM inkscape-devel-request(a)lists.sourceforge.net wrote: > Send Inkscape-devel mailing list submissions to > inkscape-devel(a)lists.sourceforge.net > > To subscribe or unsubscribe via the World Wide Web, visit > https://lists.sourceforge.net/lists/listinfo/inkscape-devel > or, via email, send a message with subject or body 'help' to > inkscape-devel-request(a)lists.sourceforge.net > > You can reach the person managing the list at > inkscape-devel-owner(a)lists.sourceforge.net > > When replying, please edit your Subject line so it is more specific > than "Re: Contents of Inkscape-devel digest..." > > > > ---------- > Today's Topics: > > 1. Re: Wacom smartpad support - request for ideas (Martin Owens) > > > > ---------- > Re: [Inkscape-devel] Wacom smartpad support - request for ideas > From: Martin Owens <doctormo@...400...> > Date: Feb 28, 9:39 PM > To: Peter Hutterer <peter.hutterer@...3641...> > CC: inkscape-devel(a)lists.sourceforge.net, Benjamin Tissoires > <benjamin.tissoires@...400...> > > >> > I'm sorely tempted to buy one of these things to hack on it to be >> > honest. >> if you do, buy a folio. we don't know if that works yet :) > > OK I got the small folio, got a friendly discount at B&H so only $120. > >> our file format atm is just a json file with the raw data >> (x/y/pressure in >> arrays that are the strokes). we can produce whatever we want from >> that. I >> hear the mp3 patent has expired ;) > > Unfortunatly inkscape doesn't support mp3s ;-P > > 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 >

2 1

Hackfest in Three and a bit weeks
by Martin Owens 01 Mar '18

01 Mar '18

Dear developers, The 2018 Inkscape hackfest will begin in three weeks. If you are coming, please add your name to the Attendees page right away: http://wiki.inkscape.org/wiki/index.php/Hackfest2018_Attendees I'm hoping that both Alex Valavanis and Krzysztof can come to the hackfest and we hopefully will resolve anything to do with funding at the meeting tomorrow. If you think you might come, but aren't sure yet, please add yourself with a MAYBE tag to the list, so I know if the even is going to be as small as it looks like it's going to be. Thanks everyone! Best Regards, Martin Owens

1 0

Inkscape Hackfests!
by Tavmjong Bah 01 Mar '18

01 Mar '18

Hi Inkscapers, As you hopefully are aware, Inkscape will be having our main 2018 hackfest in Boston at the end of March and a mini-hackfest in Seville at the end of April (at the Libre Graphics Meeting). All members of the Inkscape community are encouraged to attend! Financial support is available based on past contributions to Inkscape (see "Attendees" page below for details). Please add your name to the "Attendees" page if you are thinking about attending. While you can "walk-in" at LGM, we'll have to provide a list of who is attending the Boston Hackfest to our hosts before the hackfest starts. Even if you can't attend, you can still propose topics for discussion/work on the "Topics" page. And you can contribute financial support at: https://inkscape.org/en/support-us/hackfests/ Here's a list of relevant web pages: Boston Hackfest: http://wiki.inkscape.org/wiki/index.php/Hackfest2018 http://wiki.inkscape.org/wiki/index.php/Hackfest2018_Attendees http://wiki.inkscape.org/wiki/index.php/Hackfest2018_Topics Seville Hackfest: http://wiki.inkscape.org/wiki/index.php/Hackfest2018_LGM http://wiki.inkscape.org/wiki/index.php/Hackfest2018_LGM_Attendees http://wiki.inkscape.org/wiki/index.php/Hackfest2018_LGM_Topics Hoping to see you at one of the Hackfests, Tav

1 0

Inkscape Board Meeting
by Bryce Harrington 01 Mar '18

01 Mar '18

Our monthly board meeting is scheduled for this Friday, Mar 2nd, at 10am Pacific in #inkscape-devel. All members are welcome. http://wiki.inkscape.org/wiki/index.php/Board_Meetings (Note that a Release Team meeting will follow immediately after. The Vectors Team will be meeting the next day.) Agenda: + Madras Printer's and Lithographers' Association + Boston Hackfest (March) [doctormo] + Merchandise sales [crogers] + Board election process review [tedg] + Infrastructure hosting [bryce] + LGM 2018 [Tav] + GSoC [ScislaC] + Other Business Action Items from last meeting: ♢ ACTION: Arrange vote on Budget 2018 [bryce] ♢ ACTION: Make a list of projects for cleaning up our code base [Tav] ♢ ACTION: Send invites to old Inkscapers to attend hackfest [bryce] ♢ ACTION: Collect CMYK ideas into Color_management wiki page [alface] ♢ ACTION: Analyze how we could improve internal handling of Illustrator and Corel file import [crogers] ♢ ACTION: Follow up with MPLA to clarify on funded development and general sponsorship options [bryce] ♢ ACTION: Start reaching out to people (including previous contributors) to attend the hackfest. [tedg] ♢ ACTION: Arrange votes for any special case travelers for hackfest. [bryce] ♢ ACTION: Try one more time to access spreadshirt password, then email bryce for help [crogers] ♢ ACTION: Collab on markdown formatting for the board docs [bryce,tedg] ♢ ACTION: Get the word out about LGM / Inkscape and invite more attendees [Tavmjong] ♢ ACTION: Evaluate use of discorse (https://discuss.pixls.us/ ?) for support/mailing list/forum type stuff [Vector Team] Bryce

1 0

Wacom smartpad support - request for ideas
by Peter Hutterer 01 Mar '18

01 Mar '18

Benjamin Tissoires and I have been working on a project called Tuhi that communicates with the wacom smartpad devices and pulls the data off them. https://github.com/tuhiproject/tuhi/ Devices working so far are the Bamboo Spark, Slate and the Intuos Pro Paper. Smartpad devices aren't traditional graphics tablets [1] but instead have a paper notepad on top of a sensor with a special pen. You draw on the paper, the sensor registers the drawings and stores it in a custom vector-based format in the device. Later, you connect the device over bluetooth to the host and fetch the drawings from the firmware. This is the bit that tuhi does, and it exposes the drawings as a simple json-based vector format overa session DBus API. To interact, you basically connect to the dbus daemon, tell it to listen to the device and then get notified about new drawings. Then you can fetch the drawings one-by-one as needed. Tuhi only has a commandline client for debugging and we don't intend to ship that client, it's for debugging only. Eventually, we may have a standalone application similar to Wacom's Inkspace (yeah, confusing, isn't it?). This app would be a gallery-style application that displays the drawings and exports them to the desired formats. That's a fairly straightforward process. But right now what we're interested in is whether inkscape has interest in a plugin-style implementation that talks to the tuhi daemon. Or whether there are use-cases where the standalone application is insufficient and some tighter integration is needed. Or other use-case you can think of that we haven't yet. Any comments appreciated! Cheers, Peter [1] the intuos pro paper is when you plug it in, let's ignore that for now

2 7

List issues
by Maren Hachmann 28 Feb '18

28 Feb '18

Does anyone know why some list emails arrive so late lately? Within the last week, I think at least 10 emails arrived after > 4 days only (I can exclude a mail server issue on my side, as I get the same emails at the same times on my web-based email account). Has there been a major sourceforge outage? What's the status of the mailing list move to our own server? Maren

3 4

Fw: Visitor analytics
by brynn 28 Feb '18

28 Feb '18

Resending this. Apparently I used the wrong email address to send this from, so it didn't go to the list. -----Original Message----- From: brynn Sent: Sunday, February 25, 2018 12:25 PM To: Martin Owens ; Ryan Gorley ; inkscape-devel(a)lists.sourceforge.net Subject: Re: [Inkscape-devel] Visitor analytics What I like the best about it (Piwik/Matomo) is that it seems to only report on what I refer to as human visitors. Personally I find that much more useful. (Although I could imagine that some sites (or webmasters, owners) might be more interested in aalllll the traffic.) So that's the sandcats.io script that I see in Firefox's No Script? So already, visitors haven't been notified about the site using this tracking? So the login via github has to do with sandstorm, from what I can tell? Because I just log in on the page where I installed it, on my site. brynn -----Original Message----- From: Martin Owens Sent: Sunday, February 25, 2018 2:12 AM To: brynn ; Ryan Gorley ; inkscape-devel(a)lists.sourceforge.net Subject: Re: [Inkscape-devel] Visitor analytics On Sun, 2018-02-25 at 01:24 -0700, brynn wrote: > Whatever a Piwik "sandcat sandstorm grain" is, it's probably very > different from > what I'm using on my site. That's just the way it's deployed. It's easier to do that then to set it up raw although it comes with it's own oddness hence the login restrictions. The graphs even now are interesting. Martin,

4 7

Re: [Inkscape-devel] Boston hackfest stickers
by C R 28 Feb '18

28 Feb '18

I've heard three mentions in support of Boston Tea Party ships. I'll do a variation with that and then we can maybe take a vote on which version works better. I'm not married to either idea. Just want folks to be happy with the results. :) More soon. -C On Tue, Feb 20, 2018 at 4:58 PM, Máirín Duffy <duffy@...43...> wrote: > > On 02/20/2018 10:48 AM, Martin Owens wrote: >> >> Although I fear we're putting too much pressure on you, your design was >> really nice tbh. It doesn't have to scream boston if it doesn't want >> to. > > Totally, sorry, didn't mean to exert pressure at all. Just that the building > is in a bit odd of a place so you know the lay of the land. Honestly design > looks good enough that it doesn't really matter I think if ppl recognize it > or not. > > ~m

3 2

Visitor analytics
by Mihaela 28 Feb '18

28 Feb '18

6 5

Daily Inkscape Builds?
by Miguel Lopez 25 Feb '18

25 Feb '18

Hi Inkscape developers, users, and supporters, There's a open-source software named Krita which offers daily-builds from trunk, and I was wondering if this sort of thing was possible for Inkscape. Thank you for reading.

7 20

no access to Inkscape code repository on Gitlab
by alvinpenner 24 Feb '18

24 Feb '18

Hi, Is it just me, or have the permissions changed for browsing the Inkscape code on Gitlab? I have a shortcut for accessing Inkscape: https://gitlab.com/inkscape/inkscape I use this regularly just for curiosity. This link no longer works, unless I am signed in to Gitlab, which I typically am not. Even worse, if I use this link, and then go to the link that says: Explore projects on GitLab.com (no login needed) I find that the Inkscape project no longer exists. That is to say, many Inkscape-related projects are found, but Inkscape itself does not exist or cannot be found. just checking, Alvin -- Sent from: http://inkscape.13.x6.nabble.com/Inkscape-Dev-f2781808.html

9 26

MacOS build on Github to consider
by Jared Meidal 22 Feb '18

22 Feb '18

About four years ago some discussion occurred around rejuvenating a build system for MacOS. I have since noticed a individual in that discussion has code and build instructions open on Github, and has continued to develop here: https://github.com/valerioa/Inkscape-MacOS-Curated-Build After trying out the build, I like the ability to work without X11 in a native app appearance. I'm not an app developer, but would like to raise attention to this as a project which has gone a long way to benefit Mac users. --Jared

4 3

Re: [Inkscape-devel] Inkscape liveAnimate idea
by openInvent 22 Feb '18

22 Feb '18

Hey all someone told me a way to view same document at different zoom levels using the window duplicate function. I was able to use it somewhat but in ubuntu the window doesnt stay on top some times or it isnt dockable. Also I used the tutorial files from help and I was trying to LIVE ANIMATE that file using vokoscreen that comes with ubuntu studio... And It was very laggy on my slow pc running off 2GB RAM and a Live DVD. I really think with a RAID 0 of 10k Hard Drives it would be fine. Anyways I am kinda suggesting that I be able to dock or split a window. I was liking the horizontal spilt I could move animated objects on lower screen and they would move above in the larger screen without the cursor showing. I wish I could disable the UI or the cursor with a hotkey and set other hotkeys to affect scale or rotation or like switch layers like press space to swap group file or unhide a top layer etc. Any suggestions? I know Inkscape isnt a animation suite but its simple for little things like a Puppeteer App especially if you can do post production and use a chromakey background. Example like handwriting Words onto a music video etc. It seems that my emails get "lost" you can snail mail me at the address below and I will reply with sticker gifts.(tiny.cc/oisticker) Ember AR Leona 250 S. Lyon Ave Ste E 108 Hemet, CA 92543 Sent with ProtonMail Secure Email. -------- Original Message -------- On February 22, 2018 1:25 AM, Maren Hachmann <maren@...3165...> wrote: >Am 18.01.2018 um 21:30 schrieb Bryce Harrington: >>Do we have a wiki page setup for discussing/brainstorming bug tracker >> ideas? Maybe that'd be a good starting point? >> > > Now we have: > >http://wiki.inkscape.org/wiki/index.php/Bug_Reporting_Workflow > > Maren > > >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

Re: [Inkscape-devel] Hackfest location confirmed?
by Máirín Duffy 21 Feb '18

21 Feb '18

If you need any help w Red Hat brand elements let me know! Cheers,~m Sent from my Samsung Galaxy smartphone. -------- Original message --------From: Martin Owens <doctormo@...400...> Date: 1/20/18 8:42 AM (GMT-05:00) To: C R <cajhne@...400...>, inkscape-devel <inkscape-devel(a)lists.sourceforge.net> Subject: Re: [Inkscape-devel] Hackfest location confirmed? On Sat, 2018-01-20 at 12:57 +0000, C R wrote: > Hey everyone. Working on the sticker for the Boston hackfest. > Did we ever get confirmation on the location? The page still says, > RedHat Boston Office, but did we ever confirm? I'd like to include > the > location on the swag stickers. It is confirmed! 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

7 8

Boston hackfest stickers
by C R 19 Feb '18

19 Feb '18

These are modeled after the Paris engraved ones I did last year. This time however, I thought the venue was a better thing to put on the sticker rather than a local tourist attraction, which in this case, no one might actually see. So here it is, the Boston Hackfest sticker sample: https://www.dropbox.com/s/trkgrniaf4g33iz/inkscape_foil_sticker_boston_hack… Any thoughts? Wish it were a famous landmark instead? Lemme know. -C

8 15

Some guests for Boston Hackfest
by Máirín Duffy 19 Feb '18

19 Feb '18

Hi, I spoke to Matthias Clasen from the upstream GTK+ project and he has kindly offered to attend the hackfest for a day or two. If there are specific days you think his input would be most valuable, I can pass that on to him. Bill Sanford from our Desktop QA team is, among many other things, responsible for testing Inkscape for our desktop product. He is also interested in attending, and if you have specific questions or things you'd like to hear from him, please let me know. Cheers, ~m

4 9

inkscape sticker graphics
by C R 18 Feb '18

18 Feb '18

Someone asked for the original files to print a set of their own. I've included the sample mockup, flattened vector print layer, 40mm dieline, and some (c) and font information on different layers in the svg. It's here in case someone would like to add it to the inkscape archives, or use it to print their own stickers: https://inkscape.org/en/~C.Rogers/%E2%98%85inkscape-silver-foil-sticker-40mm -C

2 1

Twitter...
by Tavmjong Bah 13 Feb '18

13 Feb '18

Who's got access to the Twitter account? If you have access can you announce both Inkscape's GSoC participation and the upcoming Boston hackfest? I've taken care of our G+ account. Thanks, Tav

4 3

Google Summer of Code - 2018
by Tavmjong Bah 13 Feb '18

13 Feb '18

Hi all, Inkscape has been accepted as a mentoring organization for this year's Google Summer of Code. Students, time to develop your proposals. https://summerofcode.withgoogle.com/organizations/5174841905250304/ Tav

1 0

Variables in Inkscape
by Robert Van Den Bergh 12 Feb '18

12 Feb '18

Hey, Is it possible to create variables in Inkscape that link to a database? Kind regards, Rob

3 2

new moderation procedure?
by brynn 09 Feb '18

09 Feb '18

Hi Friends, This is something which has never been discussed. But recently we've had some images being reported by a regular member, which moderators have approved, and they remain in the gallery. In one case they reported a member. Should we contact a member who reports an image, thank them for helping, and explain our decision, why we decided not to delete the image? In this particular case, I'm thinking we may need to contact him or her, just to try and prevent more unnecessary reports. But in general, I wonder if we should take the time to explain our motivation, since the member is taking the time to help us. (Hah, for these recent reports, maybe I should try to recruit him or her as a moderator....?) Thanks for any comments :-) brynn

2 1

Update on Inkscape hosting
by Bryce Harrington 09 Feb '18

09 Feb '18

As many of you already know, we've been looking for sponsors for providing hosting for some of our ancillary services (mailing lists, wiki, forums, et al). I put out a CFP to hosting providers a few months back, and with ample help from Ryan we've received a couple good offers. I'm currently in discussion with the Software Freedom Conservancy to get the legal/administrative bits sorted out, so not everything is 100% nailed down just yet. However that's proceeded to a point that I'm starting to turn attention to the more technical end of things. To refresh your memory, here's the background statement from the CFP: """ We currently have various services hosted at a number of different locations with widely varying administrative capacities. We would like to centralize the administration of these services, such as consolidating them onto one platform. We also want room and flexibility to easily install additional services as we grow. Services high on our priority list to migrate soon include mailing lists, Mattermost, and wiki. Bug tracking, web forum and gitlab are potential secondary priorities. Our Django-based main website may also be worth consolidating at some point in the future. """ Mailing list migration will be the first focus, possibly also with some DNS services. This would finally get us off SourceForge, allowing us to close that down. After that, I'm pretty open to what comes next; we can play it by ear depending on opportunities and manpower availability. If you have something you wish to put time into setting up and/or administrating, contact me to sort out details. While in the CFP I had preferred physical hosting, the virtual hosting provided by the cloud service providers offering sponsorship to us does have some advantage in terms of flexibility - being able to spin up VMs on a per-service basis, or temporary ones for development and testing. One common industry best practice I'd like us to adopt is to switch to use of automated scripts for setting up the systems and services. I.e., using cloud-config to bootstrap the raw VMs, and then something like Ansible or Puppet to do automatic configuration management. We can then consolidate the service setup scripts in a git repository. More on this later. I've added a new "Inkscape Infrastructure" subgroup for holding this configuration management repository. This will be a sysadmin-oriented repository - i.e. more focused on the setup/administrative end, not so much on the data or code. I'll work up some policy/procedure for membership management of this group, for now I'll handle it manually. I'm also going to move our 'credentials' repository into this Inkscape Infrastructure subgroup. Last board meeting we discussed migrating the credentials git repo, so that it's not hosted as a branch of the inkscape codebase (which causes it to take a long time to checkout). So this will implement that change. Bryce

3 4

Fwd: HLC-Farbatlas
by Maren Hachmann 07 Feb '18

07 Feb '18

Hi there, Christoph has asked me to forward his message, as it didn't get through: -------- Weitergeleitete Nachricht -------- Betreff: HLC-Farbatlas Datum: Wed, 7 Feb 2018 06:32:39 +0100 Hi all, After a year of hard work freieFarbe/freeColour is pleased to announce the completion of its first major project, the "HLC Colour Atlas", which is a truly open colour system based on mathematics and unrestricted by copyrights or trademarks. It has been created by colour professionals from Germany and Switzerland. The atlas comprises the following elements: - a printed reference (A4, ring binder) of 2040 colours, based on the intuitive HLC colour model (Hue, Lightness, Chroma), with increments of 10 between each hue. It also includes colours that can't be reproduced in regular CMYK workflows (spot colours). Unlike commercial products, its colour precision is extremely high, with a DeltaE00 of 0.5, i.e. colour differences between two copies of the atlas can only be measured but not perceived, even by a trained eye. Each atlas is being produced with a Fogra-certified high-end proof printer on Fogra-certified paper by a Fogra-certified company. Each copy is also being shipped with a production record (ISO 12647-7:2016); - a printed introduction and usage instructions in German and English; - colour palettes with LAB values for Adobe software (ASE format) and in Swatchbooker's SBZ format, as well as sRGB versions for LibreOffice (SOC), GIMP (GPL) and Scribus 1.4.x (XML). Please note that Scribus 1.5.x already includes the SBZ file, and an sRGB version is being shipped with LibreOffice since version 5.4.x, as well as the current officially stable Scribus 1.4.6. - A PDF master file of the atlas with layers for different output targets (e.g. sRGB, ISOCoatedV2); - XSLX files with colour conversion tables and QC report; - a CxF v.3 file which includes the colour data in spectral values. All files are available for download here: https://www.freiefarbe.de/thema-farbe/software/ The latter is important, because we want to enable others to create their own reliable references without having to ask for permission or paying licence fees. Thus, an ink manufacturer can simply load the CxF file into its formulation software and create the correct mix for his particular inks. Manufacturers of other colourants (e.g. paint, textile colours or plastics) can do the same, provided their software is supporting CxF, which is an open standard. This is also the reason for us not to publish any mixing recipes, because all necessary data to reliably recreate a colour are in the CxF file, so the recipes can be created and customised by software. Whilst the digital files are available for free download under a CC licence, the printed reference needs to be paid for, because production and certification are quite labour-intensive (introductory offer: EUR 99.-- until 31 March 2018, later: EUR 149.-- plus VAT and shipment costs; see: https://shop.proof.de/index.php?language=en). freieFarbe/freeColour are convinced that the "HLC Colour Atlas" is not only a true and open alternative to Pantone, HKS etc., but we also think that the very high quality standard of our printed reference will be hard to match. Our next step is to fill in the necessary paperwork to make this open colour system a DIN SPEC with the German industrial standards organisation DIN (April/May 2018). From there it will hopefully be moved on to ISO to make it an international standard (time frame unknown). Special credits go to Matthias Betz, Holger Everding, Jan-Peter Homann and Eric A. Soder, who did all the heavy lifting, as well as Gregory Pittman, who wrote a Scribus script that reduced the creation of the print PDF for the Atlas to a matter of seconds. freieFarbe/freeColour is also grateful to ColorLogic GmbH, Epson Deutschland GmbH and GMG GmbH & Co KG for generous technical support. The high quality of the atlas is owed to the producer, Proof GmbH. Christoph

1 0

0.92.3 Release Planning Meeting ~ Feb 2nd
by Bryce Harrington 07 Feb '18

07 Feb '18

After the last board meeting we discussed maybe starting 0.92.3 in Feb. I'd like to hold a kickoff meeting following this Friday's board meeting to get started. Hopefully this should be a straightforward release but worthwhile to touch base with everyone just in case. For this meeting I want to just get a handle on the status of everything and flag tasks needing done. I'd like to also get a rough timeline figured out. Date: Fri, 2nd Feb, 2018. Time: 11:00 PST / 19:00 UTC / 20:00 CET Where: #inkscape-devel on freenode What: http://wiki.inkscape.org/wiki/index.php/Release_notes/0.92.3 Agenda: + Status of the 0.92 tree - Any pending patches we should track? - Are there more fixes worth cherrypicking from trunk? - Are the release notes up to date? + Status of platform packaging - Any new issues compared with 0.92.2? - Are all 0.92.2 packagers available for this go around? + Release cycle plans - One pre-release? - Rough dates + Conditions that might cause release delay + Looking forward --- 0.93 - Dependency versions needing revved? - Remaining licensing issues? - GTK+ 3 stabilization / Windows performance bug - Other stabilization work needed? + Next meeting? - March 2nd following board meeting? + Other business Bryce

1 1

inkscape-docs has a new home
by Eduard Braun 06 Feb '18

06 Feb '18

Hi all, I'm happy to announce that the former "inkscape-docs" (i.e. manpages, keys and mouse reference and tutorials) has a new home! You can now find the "Inkscape Documentation" at https://gitlab.com/inkscape/inkscape-docs/documentation After migrating the repo to GitLab some time ago I finally got around and tweaked some last bits, so it's now in a production-ready state again. Obviously there's still a lot to do (on my short list: getting updated docs onto the website and make translation statistics work again, preferably using some CI automation) but I think the repo is at a point were contributions should be possible without too much effort again and I'd appreciate any help in getting it updated in time for the 0.92.3 release! If you have any questions let me know! Happy documenting, Eduard

2 2

Boolean Operation LPE Question
by Miguel Lopez 06 Feb '18

06 Feb '18

Hi everybody on the mailing list, I have noticed on a inkscape development build that there doesn't seem to be a easy way to use boolean operation LPE. Copy and pasting, and pressing the button doesn't seem to work. Right now, I don't believe this is a bug as I'm thinking that it's a work in progress and thus no need to treat it as a bug, but I could be wrong. Is this a work in progress? Thanks, Miguel Lopez.

1 0

numpy: include, give warning or ...?
by Maren Hachmann 05 Feb '18

05 Feb '18

Hi there, the .deb packages for Ubuntu do not seem to include a dependency for numpy, but the gcodetools depend on it. It's included in the snap, and also seems to be present for Windows and macOS versions. Some other extensions give warnings when it's missing (measure, perspective, dxf_outline,...) So, my question is: Should the gcodetools also just output a warning message with install instructions, like the other extensions do, because there's a reason why numpy cannot be made a dependency? Or could numpy be made a dependency? (I guess that's more a question to packagers - do we make any recommendations anywhere? Or do they need to figure it all out by themselves?) Maren

6 10

Inkscape Board Meeting
by Bryce Harrington 03 Feb '18

03 Feb '18

Our monthly board meeting is scheduled for this Friday, Feb 2nd, 10am Pacific time in #inkscape-devel. All members are welcome. http://wiki.inkscape.org/wiki/index.php/Board_Meetings (Note that a Release Team meeting will follow immediately after. The Vectors Team will be meeting the next day, Saturday the 3rd.) Agenda: + Madras Printer's and Lithographers' Association + Boston Hackfest (March) [doctormo] + Merchandise sales [crogers] + Board election process review [tedg] + Infrastructure hosting [bryce] + LGM 2018 [Tav] + GSoC [ScislaC] + Other Business Action Items from last meeting: ♦ ACTION: Re-ping Madras Printer's and Lithographer's Assoc. [bryce] ♢ ACTION: Find out who did the Indian language translation [Tav/Moini] ♢ ACTION: Calls for fundraising for the hackfest [bryce/Moini] ♦ ACTION: Arrange vote for Boston hackfest [bryce] ♦ ACTION: Arrange vote for LGM [bryce] ♦ ACTION: Port credential repo changes from bzr to git [doctormo] ♦ ACTION: Move credentials repo to a new git project [bryce] ♦ ACTION: Ping Brett regarding DigitalOcean [bryce] ♦ ACTION: Investigate CloudScale.ch [bryce] ♢ ACTION: Kickoff the 0.92.3 release [bryce] ♢ ACTION: Arrange vote on Budget 2018 [bryce] ♦ ACTION: Connect with Diego about CMYK planning [bryce] ♦ ACTION: Kickoff GSoC 2018 registration [ScislaC] ♢ ACTION: Make a list of projects for cleaning up our code base [Tav] ♢ ACTION: Pursue the RedHat option for the hackfest [doctormo] ♢ ACTION: Send invites to old Inkscapers to attend hackfest [bryce] ♢ ACTION: Collect CMYK ideas into Color_management wiki page [alface] Bryce

1 1