May 2017 - Inkscape Devel - Inkscape Mailman

Inkscape Hackfest: Paris edition: June 27th — July 1st
by Tavmjong Bah 07 May '17

07 May '17

Hi all, The Paris hackfest is a go with board approval and a confirmed host (thanks Mc!). The hackfest dates are June 27th through July 1st. The first four days will be for hacking with a meeting with local Inkscape users on the fifth day (TBA). The hackfest will take place at Carrefour Numérique². This is a Fablab/hackerspace located inside Paris's excellent modern science museum. They use Inkscape all the time (and love it!). See http://wiki.inkscape.org/wiki/index.php/Hackfest2017 for more details. Everyone in the Inkscape community is invited to attend! Financial support is available to Inkscape developers based on the number of years activity and number of commits to the source code. Support for others active in the Inkscape community (translators, documenters, etc.) will be handled on a case-by-case basis. For more details, see: http://wiki.inkscape.org/wiki/index.php/Hackfest2017_Attendees If you plan on attending please add your name to the above page or send me an email. The page has been seeded with those who have already expressed an interest in attending. Looking forward to seeing everyone in Paris! Tav

2 1

Please migrate to GitHub/CMake
by Ivano Arrighetta 07 May '17

07 May '17

Hello there. My name is Ivano Arrighetta and I'm Italian. I would like to suggest to migrate to GitHub for version control, and to use CMake for creating build projects for Windows and Mac OS, other than Makefiles for *nix. GitHub also offers a WebSite builder and a Wiki for each repository, other than an issue tracker. I'm pretty sure everyone would benefit from this. Bye, Ivano.

2 1

Week commits
by Jabier Arraiza 07 May '17

07 May '17

Hi all. This week do some changes to LPE and merge two branches: With the changes to LPE we have too much better response from effects, reducing to minimun the need to write on the parameter data and reshow the parameter widgets. The two branches: First of all sorry for not wait enought for a aprove check but I have a goal in a new branch in development to organice the code in LPE part of inkscape and want this merged to it. The first branch allow store the default parameter for each new live effect. I attach a screenshot time ago. The second branch is a refactor to fillet/chamfer LPE based in a new way to store data for each node in a pathvector. Specialy thanks Nathan and Tweenk for his help in development. This new way for fillet chamfer is not backward compatible, this is the reason for merge "too early" and dont launch it in 0.92. My apologyes for the problems can happends with old files. Please convert to path our previous fillet/chamfer works prior update trunk. Usage feedback are welcome ;) All the best, Jabier.

2 2

Hackfest possibility - Paris Please Respond ASAP if interested!
by Tavmjong Bah 06 May '17

06 May '17

Hi, Marc has been looking for free spaces in Paris to hold a hackfest. He's found what looks like an ideal spot: Carrefour Numérique² located at the Cité des Sciences et de l'Industrie (an excellent modern science museum) in northeast Paris. http://www.cite-sciences.fr/fr/accueil/ http://www.cite-sciences.fr/en/explore/learn/carrefour-numeriqu e2/ There are Inkscape users there and they've even written their own in- house Inkscape plug-ins to drive their CNC machines. They've hosted other open-source groups including a monthly Blender users group and twice-a-year Ubuntu parties. They can offer us a "Numeric classroom" with five tables with power and wired Internet connection from May 29th to June 2nd. The question is, is there sufficient developer interest to pursue this? Please respond if you can attend. If there is enough interest I will present this option at the board meeting Friday. Tav

8 17

Fwd: Re: Let's encrypt: is this possible?
by Miguel Lopez 06 May '17

06 May '17

-------- Forwarded Message -------- Subject: Re: [Inkscape-devel] Let's encrypt: is this possible? Date: Sat, 6 May 2017 13:51:36 -0400 From: Miguel Lopez <reptillia39@...3425...><mailto:reptillia39@...3425...> To: Martin Owens <doctormo@...400...><mailto:doctormo@...400...> Oh, ok. I never really paid attention to that as I rarely go there due to academic reasons, and I thought it didn't do this since someone brought this topic up. I guess all is clear now. On 5/6/2017 1:50 PM, Martin Owens wrote: > On Sat, 2017-05-06 at 17:43 +0000, Miguel Lopez wrote: >> Is it a option to automatically redirect to https? > It already does this, try and go to http://inkscape.org > >> On 5/6/2017 1:30 PM, Victor Westmann wrote: >>> Thank you Maren and Tobias >>> For pointing this out. I was not so sure. Sometimes I am visiting >>> the inkscape website and I noticed it points to the http version >>> instead of the https one. >>> Great to hear this. I rest my case. :)

1 0

board meeting today?
by brynn 05 May '17

05 May '17

Hi Friends, Is there a board meeting today? Thanks, brynn

1 0

website moderation policy
by brynn 02 May '17

02 May '17

Hi Friends, I've been helping to test some new moderation features which Martin has been working on (and Maren helping too), for the website. We have realized that (A) we might have different opinions about what the moderation policies should be, and (B) the current CoC might not cover them. But we all agree that the larger community should be involved, if the CoC needs to be edited. For convenience, the CoC says this: "Guidelines for User Submitted Content: Art and other content submitted to the Inkscape website should adhere to the following rules: -- Art must be your own original creation or derived from artwork available under an open licence. We cannot accept submissions that infringe copyrights. -- No nudity or graphic violence. (Note: we may allow this type of content once it is possible to tag it as such, but pornographic and/or illegal material would still be disallowed.) -- No content that is explicitly discriminatory in nature. -- No political agitation or totalitarian symbolism." Up until the moderation features are completed, installed and in use, the policy for images in the gallery has been this. As long as the image doesn't violate those 4 guidelines, it's acceptable, even though it may have nothing to do with Inkscape. After that, the gallery has been relying on a very small upload quota for members, to prevent mass spam attacks. In my opinion, resources uploaded to the website should bear some relation to Inkscape. Or more specifically, those which have no relation to Inkscape should not be allowed. Here's what I propose: >> Images should be made in whole or in part with Inkscape, or depict how >> Inkscape was utilized in user projects (such as a photo of a t-shirt which >> design was made with Inkscape). >> Any other images need to have some relation to Inkscape, the Inkscape Project >> (website, forums, hackfest), vector graphics, or marginally, FOSS. (maybe >> not FOSS?) This would exclude images like these: https://inkscape.org/en/~stacymcgraw@...1081.../%E2%98%85img-0616 https://inkscape.org/en/~KarenFechter/%E2%98%8520160319-150913+1 https://inkscape.org/en/~lgimenezborges/%E2%98%85vklsd https://inkscape.org/en/~Astro.C/%E2%98%85three-musketeers https://inkscape.org/en/~richardkwok0128/%E2%98%85testing+0 The reason I feel this way, is because there must be hundreds, if not thousands of galleries on the internet, where people can upload any kind of random photo. Why should the Inkscape website waste its resources hosting images which weren't made with Inkscape and have nothing to do with it? If the Inkscape website is going to the trouble of creating and maintaining a gallery, it ought to promote Inkscape, vector graphics, and maybe FOSS, almost, if not completely exclusively. My opinion of course ;-) So I propose the following, or something like it, should be the first item in the list of Guidelines for User Submitted Content. No doubt it could be worded better. -- Images must be created using Inkscape, in whole or in part; or depict how Inkscape was utilized for the user's project (such as a photo of a t-shirt which design was created using Inkscape). Or otherwise the image or resource must bear some relation to Inkscape, the Inkscape Project, vector graphics (or FOSS??) Does anyone have any thoughts or opinions on this? Thank you very much, brynn PS - Should this be cross posted to the user list too?

8 21

Re: [Inkscape-devel] Marketing Inkscape - Survey Preview (Ryan Gorley)
by jelle 02 May '17

02 May '17

Ryan, The interesting thing about SVG is that it can be used for both web and print graphics design without a need for conversion. The main lack for print graphics design are CMYK and spot colour support in SVG 1.1, which if I'm correct should be addressed in SVG 2.0. Unfortunately SVG 2.0 is dropping support for SVG fonts, which would have been the nail in the coffin of PDF otherwise. For a brief moment SVG was bound to be the choice of archiving around the world, but that was not in the interests of the companies that contributed to the standard. Just link your 14 MB hanyul opentype font for those 20 characters of Chinese to load or generate a separate font file for every page rather than embed it into the document (or maybe that can be done using base64 encoding). Sadly SMIL got dropped likewise. CSS animation is the bomb,... duh or javascript (if not blocked by the users that are fed up with agressive ads and CSS bloat). However, the SVG standard still allows to be used for a single document type work flow for all 2d graphics design types. Multi page document types would be a great addition and to my idea could be fairly easily be incorporated by adding objects in page groups like is now done with layers. I guess that having layers and page groups would be more of a hassle as each page would need to have those layers embedded into their group and during saving as standard SVG they need to get separated into single pages as SVG doesn't do multi page docs. It's a pity I'm a lousy coder though if I'd started 8 years ago with it it might have been implemented by now and I been a better coder (I would think). I can imagine that making links to pages and clicking them might unhide this page layer while hiding the active layer. Wonderful visions of multiple documents opened in one instance of Inkscape (joy) that can be tabbed, viewed in multiple open windows so you could select links on the other page etc. CMYK is a nastier problem because as I understand it Cairo (the renderer) doesn't support that. I believe that the only feasible way is to make things in Inkscape, export a bitmap, import it into Scribus (because it doesn't support SVG filters) and have the 32 bit .png be converted to CMYK .tif if you actually need black (~140MB for A4 at 200 dpi). I'm not sure what happens to CMYK info that gets exported from Inkscape to PDF, though my business cards look pretty good, so it may actually retain the CMYK info. It may also have been converted by the printer, but as they were Chinese I didn't discuss much with them. Both aspects have been a long standing wish from the graphics designers user base of Inkscape, but they are considered hard to implement or just not that sexy or both. Personally, I've been using Inkscape for the past 8 years as a single work flow tool to create both print and web graphics. What is lost to many is that this is an enormous time saver for designers and it allows for a higher productivity. Or at least ideally. If anything I consider full CMYK support the main issue. If I only could sent my Inkscape document straight to a output device, I could dramatically cut my production time. In print, where many things need to be completed before the customer enters your office that would greatly improve the usability.

1 0

Freelance work wanted
by Jabier Arraiza 02 May '17

02 May '17

Hi all. Im searching fot the developer that made the PDF import in inkscape to send contact to Sayan. At the end there is our conversations. Cheers, Jabier. > Sounds good, Jabier. Thank you so much! > > On Tue, May 2, 2017 at 7:12 PM, Marker <info@...2893...> wrote: > > > Hi Sayan. > > > > I could do a recuest to him in Inkscape developer mailing list. ¿Is > > ok? > > > > Cheers, Jabier. > > > > > > On Tue, 2017-05-02 at 18:33 +1000, sayan wrote: > > > Hi Jabier, > > > > > > Thank you for your response! > > > > > > If you could contact this developer (or give me their launchpad > > > profile > > > link if you have), it would be a great help! > > > > > > Thank you very much! > > > > > > On Tue, May 2, 2017 at 5:55 PM, Marker <info@...2893...> wrote: > > > > > > > > > > > Hi, > > > > > > > > Is great to hear you and your interest. Im available but maybe > > you > > > > prefer contact first with the current developer of the PDF > > import. > > > > I > > > > could try to contact with him/her. > > > > > > > > Also Im not a english speaker... > > > > > > > > Thanks for your interest over Inkscape. > > > > > > > > Cheers, Jabier. > > > > > > > > > > > > On Tue, 2017-05-02 at 02:13 +0000, Sayan Bhattacharyya wrote: > > > > > Hi, > > > > > > > > > > I found you on the Inkscape top commits list. We are looking > > to > > > > > customise the Inkscape command line tool for Ubuntu for our > > > > > business > > > > > application. Specifically, we are interested in the PDF -> > > SVG > > > > > conversion utility and wanted to check if you would be > > available > > > > > to > > > > > work > > > > > with us on a fixed price contract? > > > > > > > > > > The project will be in different phases. If you are available > > for > > > > > contractual work to customise Inkscape source code for > > clients, > > > > > we > > > > > would > > > > > love to hear from you! Once you get back to us, we can > > discuss > > > > > the > > > > > project and scope post the execution of an NDA. > > > > > > > > > > Thanks, > > > > > Sayan > > > > > Founder and CTO, Desygner > > > > > > > > > > > > > -- > Sayan > Hi, > > I found you on the Inkscape top commits list. We are looking to > customise the Inkscape command line tool for Ubuntu for our business > application. Specifically, we are interested in the PDF -> SVG > conversion utility and wanted to check if you would be available to > work > with us on a fixed price contract? > > The project will be in different phases. If you are available for > contractual work to customise Inkscape source code for clients, we > would > love to hear from you! Once you get back to us, we can discuss the > project and scope post the execution of an NDA. > > Thanks, > Sayan > Founder and CTO, Desygner

1 0

Fwd: Re: Any chance we can make some docs material? (targeting the moon)
by Miguel Lopez 01 May '17

01 May '17

I have made videos of workarounds, and anyone making a workaround docs can use my video without my permission. I will upload them soon. Those docs can be deleted once Inkscape gets certain features, and I will delete those videos the minute Inkscape supports certain features. For now I have this - https://www.youtube.com/watch?v=k5TkIETfQa4 The point of the video is to show users how they can make a easily accessible editable mask in Inkscape without ever having to release mask. It also shows how to get some fade-out effect usually made with raster programs. There's the issue of the mask showing over the target object, and if I hide the editable mask layer, so does the mask goes to black. The one I will upload after are 2 Gradient Stroke workarounds videos - With Profile LIne, and without profile line 1 tangency line workaround video utilizing spiro, b-spline, and regular bezier path Way later I will do a shoe render, and how to use clip and masks in order to generate a extremely realistic-looking shoe that is 100 percent vector, but some of those results can easily be achieved with raster programs. I will also try to generate a warped pattern, and show how to achieve that. I know I'm not the best person to make a tutorial. On 4/29/2017 6:36 PM, Victor Westmann wrote: Hi Miguel, I think this is a GREAT advantage for the entire Inkscape project. It makes all the sense of the world to help users do all the needed workarounds and, if they want, help send funds to the project ($$) and/or a bug request on Gitlab(is it at Gitlab really?). Amazing. The more transparent we are (and we really are) the better. --Victor Westmann 2017-04-29 10:39 GMT-07:00 Miguel Lopez <reptillia39@...3425...<mailto:reptillia39@...3425...>>: I want to put out something regarding documentations. What about workarounds to Inkscape limitations as part of the documentation? Some users really need some answers to the limitation of Inkscape. There's another idea I have in mind. For making tutorials shorter, we can use existing tutorials of our own and linking to them as part of advanced section of Inkscape tutorials. Advanced users should already know the program in and out to know how to apply them for advanced rendering. Some of those might need workarounds though. My only issue with those workaround is the amount of time they require, and the tax on limited resources. Otherwise, if those weren't a issue, they would be fantastic though they're still not a replacement to what other programs has to offer. I can offer making workaround docs if anyone wants me to show how to work around Inkscape limits. For example : 1) Gradient Stroke - 1a) Method 1 (If profile line aren't needed) - Duplicate and then adjust stroke width, and then convert to path. Every strokes must be converted to path. You copy and paste the path that is going to get removed by applying the path difference. You repeat the process, and then you get every individual stroke which can be colored as however you please. 1b) Method 2 (If profile line is needed) You apply the same thing to the above, but you are not going to use stroke width. Instead, you are going to use power stroke to emulate profile line with gradient stroke. 2) Realistic Rendering of convulated objects like a shoe. 2a) This involves series of clipping, blurring, gradient mesh and brushing. Right now, Inkscape users can only use gradient mesh for basic overall lighting, and some bit of coloring using filtering since gradient mesh is underdeveloped in Inkscape. You apply blur to brushes in order to emulate shading. Doing this a lot can give very sastifying result within Inkscape, but also drains so much of rendering speed within Inkscape even with a powerful computer. But results are literally comparable to raster programs, and in some way even better because well, it's scalable. 3) The lack of warp tool for textures workaround 3a) As of now, we do have lattice tool, and the tweak liquifying tool. Those two can be used as a workaround to the lack of warp tool. Lattice deformation tool should had the option of allowing users to tweak the tangency line though instead of the tangency line being tangent to the horizontal and vertical direction. This is not something that can have a decent workaround since it requires duplicating so many objects and then tweaking it would be a major pain. For complicated textures, it can't be done within Inkscape unless you have a infinite amount of time and resource, and as we all know that's not possible. 4) For people who have trouble with tangency snapping (I'm one of those), and no that snapping option does not help one bit. 4a) The obvious workaround involves using the show handles. You can make tangent line utilizing the result of the show handles LPE. Also, this enables users to be able to create perpendicular, and tangent spiro path. 5) The lack of ease regarding manipulating mask/clip 5a) The workaround to this is well, using the clone as the masking/clipping source while retaining the original for clipping/masking at another location. This workaround works because you can always manipulate the source object, and hide it. It is almost exactly like as if you were manipulating transparency mask within Krita or Photoshop or GIMP. After testing it, it's beautiful really when you change between layer/group. 6) PDF export limitation 6a) The obvious workaround here is well, export to png and then convert to pdf. Of course, some rasterization would be needed if one has to convert to pdf, literally at times. I think those are the 6 issues that could be addressed via docs tutorial for those who are desperate to find a solution to those. They can always resort to Krita for those (except 6 because pdf export is not planned), but that's not a option if they have to create a vector render. If there's anything I miss regarding workarounds, lemme know. I can probably add more workarounds if I miss anything as I know the program in and out from a user perspective. On 4/29/2017 11:54 AM, C R wrote: >> I don't mean to slow anyone's roll here. But wouldn't it make more sense to put >> any kind of energy towards documentation into the much discussed, direly needed, >> user-focused, step by step manual? Rather than starting from scratch on a whole >> different kind of project? > Yea, this actually makes a lot of sense as a first step. > >> There are many books out there already, which amount to a series of tutorials. >> It's not a bad thing. I just think this kind of project is better suited for a >> single author, or maybe a small team. And I think the project needs the manual >> much, more more than the community needs another book of tutorials. > I agree. I think the book could be a lot of things in one. But I agree > with finishing what we already have before starting something new. > > >> As far as I understand, all that's needed is an English translation of...well >> can't find a link to the French version. Here's a link to whatever has been >> translated already: >> https://fr.flossmanuals.net/start-with-inkscape/introduction/ > I can't help with translation, unfortunately. But I'd like to see this > finished. So +1 for the suggestion. > >> Once we have the translation, we'll be off and running to update and finish it! >> By the way, is there anything those of us who can't translate, can do, to help >> the translators? > I volunteer to help this effort in what ways are needed. > >> And won't such a new book of tutorials have to be published? A big obstacle to >> writing any book is getting it published. You almost have to have an invitation >> from a publisher to be certain a book will get published. Or publish it >> yourself, which is not easy eitiher. > Books done in Scribus can be "published" in a variety of ways, opened > in browsers, laptops, eReaders, or just printed out. We could sell > printed copies along with other Inkscape stuff. Maybe copies signed by > members of the project would be kinda cool. No idea what the market is > for it, but the idea that we could do all of these at once is > attractive, and why I recommend Scribus. > > -C > >> Just my opinion :-) >> >> brynn >> >> -----Original Message----- >> From: Maren Hachmann >> Sent: Friday, April 28, 2017 4:01 PM >> To: Inkscape-Docs ; Inkscape Devel List >> Subject: Re: [Inkscape-devel] Any chance we can make some docs material? >> (targeting the moon) >> >> Would it make sense to use gitlab's new subgroups feature for this? >> >> The inkscape-docs team could be a sub-team of Inkscape, that way. There >> are only 4 members as of now, so changing wouldn't be so difficult as it >> might be later on. >> >> Maren >> >>> Am 28.04.2017 um 16:14 schrieb Martin Owens: >>>> On Fri, 2017-04-28 at 12:39 +0100, C R wrote: >>>>> I'd love to quit my job and just do docs. :) Unfortunately, that's >>>>> what it would probably take to get docs going to the extent we'd >>>>> like. >>>>> It's been discussed before, but never gone anywhere because of lack >>>>> of time/hands involved. >>>>> >>>>> Yes, we should use Scribus to do it. In fact, it should probably be a >>>>> github project to attract contributors. This way we can patch what >>>>> needs to be patched when stuff changes in subsequent releases. >>>> Sounds like you have a solid step one Chris. >>>> >>>> Here's the inkscape-docs group on gitlab, EVERYONE should join, there >>>> should be a button to join: >>>> >>>> https://gitlab.com/inkscape-docs >>>> >>>> And here's the new book/manual/docs project where files can be put: >>>> >>>> https://gitlab.com/inkscape/manuals >>>> >>>> I recommend using the wiki attached to the project to plan the >>>> adventure slowly. Add a bit at a time and don't rush to have something >>>> "complete" but have something small produced. >>>> >>>> Best Regards, Martin Owens >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Check out the vibrant tech community on one of the world's most >>>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >>>> _______________________________________________ >>>> Inkscape-devel mailing list >>>> Inkscape-devel(a)lists.sourceforge.net<mailto:Inkscape-devel@lists.sourceforge.net> >>>> https://lists.sourceforge.net/lists/listinfo/inkscape-devel >>>> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Inkscape-devel mailing list >> Inkscape-devel(a)lists.sourceforge.net<mailto:Inkscape-devel@lists.sourceforge.net> >> https://lists.sourceforge.net/lists/listinfo/inkscape-devel >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Inkscape-devel mailing list >> Inkscape-devel(a)lists.sourceforge.net<mailto:Inkscape-devel@lists.sourceforge.net> >> https://lists.sourceforge.net/lists/listinfo/inkscape-devel > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Inkscape-devel mailing list > Inkscape-devel(a)lists.sourceforge.net<mailto:Inkscape-devel@lists.sourceforge.net> > https://lists.sourceforge.net/lists/listinfo/inkscape-devel ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Inkscape-devel mailing list Inkscape-devel(a)lists.sourceforge.net<mailto:Inkscape-devel@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/inkscape-devel

7 7