- Inkscape Devel - Inkscape Mailman

Very early start on the future CAD feature of Inkscape
by Miguel Lopez 07 Mar '17

07 Mar '17

Hello guys, there is a idea that I have in mind which can be considered the very first start to CAD support of Inkscape. When I have manipulated the display units, I noticed that scale x, and scale y does change. I tried to find out what works best from Inkscape to Solidworks .dxf import, and as it turns out, the scale must be exactly 1.0 x and 1.0 y in order to achieve the correct size within Solidworks. The viable workaround to this is of course to make CAD templates, and I might make series of CAD templates. For people who are using Inkscape due to its .dxf support, they have to pay attention to the scale feature with document property. Also, sometimes they have to snap created object within the 0,0 of the workspace in order to import a vector object exactly as if the origin is the rotation point of the object. Modifying the centerpoint can be done with Solidworks, but it's a little tedious, but it can easily be done in Inkscape. There are 4 solutions I can think of for this when it comes to .dxf export, and CAD program support - Under Scale Box, there should be a checkmark which says retain 1:1 scaling when changing display unit. - If I were to export .dxf and the scale factor is not 1, then during the export process, Inkscape should automatically scale the result to 1/x where x represent the scale factor within Inkscape. Also, I wouldn't support px export in .dxf. - There should be a option to display the axis line within document property. That means the X line or horizontal line and the Y line or the height line. - Last of all, under .dxf export, I think one should have the option to always export the name of the unit being used next to the file name. That way, it would be easy to tell what's being used to avoid scaling issues within .dxf. Right now, all I have are templates, and I might try to give them out to you guys to put on the next release. I will try to talk more about this in the inkscape-devel if I can. Oh, and to Bryan or whatever the name is, I'm not in that state. I'm a university student with a very long commute and possibly suffering from unrecoverable chronic fatigue. It's unlikely I'll ever be able to go to a physical meeting as much as I want to.

1 0

Sponsors Side Page
by Martin Owens 05 Mar '17

05 Mar '17

Dear Developers, We've just finalised our revised sponsorship details. I've written a rough draft in situ to describe the different levels. https://inkscape.org/en/support-us/sponsors/?edit Please review the right side panel text, it's very rough draft so it'll need some corrections. You can edit it directly, but please don't publish yet. Bryce needs to confirm the details. Best Regards, Martin Owens

6 11

Be member of the Inkscape Developers team on Launchpad
by YuGiOhJCJ Mailing-List 05 Mar '17

05 Mar '17

Hello, I have something to commit. Can I be approved as a member of the Inkscape Developers team on Launchpad please? https://launchpad.net/~yugiohjcj Thank you. Best regards.

2 3

Is it possible to specify the filetype or filename when using the verb FileSaveAs from a DOS prompt?
by alvinpenner 04 Mar '17

04 Mar '17

This is two questions, actually, somewhat loosely related: 1. I would like to run a DOS command such as: inkscape --verb=dosomething --verb=FileSaveAs \windows\temp\testtext.svg Currently this command will present me with a SaveAs dialog with the current file name and the filetype svg. I would like to specify, in the command line, either the file type for the Save As operation, or perhaps the filename with the filetype as well, so that the operation could perform silently. Not sure what the syntax would be for this. 2. Alternately, if this is not possible, is it possible to execute verbs from inside a Python script? So, for example, if I were in the Python extension dxf_outlines.py for saving a dxf file, can I execute the verb "--verb=ObjectToPath" and get output from it? tia, Alvin -- View this message in context: http://inkscape.13.x6.nabble.com/Is-it-possible-to-specify-the-filetype-or-… Sent from the Inkscape - Dev mailing list archive at Nabble.com.

5 18

GSoC Mentoring
by Tavmjong Bah 04 Mar '17

04 Mar '17

Hi, We've been accepted to participate in this year's Google Summer of Code. We need to submit a list of mentors. If you are interested in mentoring, please reply to this email. Thanks, Tav

3 2

RSVP: Inkscape Hackfest, Portland Oregon Apr 28 - May 3, 2017
by Bryce Harrington 04 Mar '17

04 Mar '17

You're invited! We will be hosting a hackfest in Portland Oregon this spring for 5 nights. Tell me ASAP if you might be interested in joining us. We're trying something a bit different for this hackfest. We're renting a house that's been set up for business meetings, with a front unit and a rear unit. We've reserved one, and if enough people will be coming we'll grab the other as well. The event will focus on stabilization of the 0.93 branch, infrastructure development, and fundraiser planning. See the attached PDF for details, and email me offlist if you may be able to come. Bryce

1 0

gitlab migration plan
by Bryce Harrington 04 Mar '17

04 Mar '17

Thanks everyone who provided feedback on the plan to migrate to gitlab. I've updated the plan to incorporate all the feedback (see attached diff for what changed). With 0.92.1 now out the door, this seems like an opportune time to proceed with Step 2 of the migration, if no one objects? So, Martin, Maren, jazzynico, and others who have been maintaining inkscape-related products on gitlab, would you mind sharing your experiences with gitlab, and whether you recommend for or against migrating inkscape itself at this time? Bryce ------------------------------------------------------------------------ [DONE] Migrate inkscape_web. + Keep a particular eye on performance. + Evaluate code review UX + Evaluate CI + Experiment with other features 2. Once 0.92.1 is released, we'll have a first checkpoint Checkpoint for inkscape_web. + Make recommendations for utilization of code review, CI, and other gitlab functionality. + Was performance a hinderance? Is the user experience acceptable? In general do the inkscape_web participants still feel as supportive of gitlab? + Retrospective on the 2/1/2017 hack + loss of backups - https://www.theregister.co.uk/2017/02/01/gitlab_data_loss/ - Issue itself is bad. Transparency they showed is good. - It's been a month, have they adequately sorted things out? + Is gitlab's CI build system up to the task for Inkscape? What provisions will we need to make (e.g. supplying our own build hosts) + What concerns or issues remain, that should be watched during our initial migration? + We'll ask everyone involved in inkscape_web for a thumb's up or down. If there are thumb's down, we'll halt and re-evaluate. 3. Migrate inkscape to gitlab. + All bzr committers are eligible for gitlab commit access, but will need to place a request for access + tweenk has a script to fix up discrepant author names and e-mails. Can't be shared publically since has personal info (but could be passed to a board member via pgp encrypt). + At least one dry run should be done, to ensure that revision history, branches, tags, etc. are successfully converted. + Functionality that uses 'bzr revno' (like the about screen) will need modified to use git. - Formatting for about screen should be something resembling: "Inkscape 0.92+devel (2017-01-18 f0e47570)" - git describe --tags --dirty will tell the last tag, whether there are changes to the checkout (the --dirty), the short hash of the last commit and also the number of commits since the tag. It's not too hard to clean up the tag name (remove "release-") and add the commit date. - Use the commit date rather than the author date + Issues encountered with gitlab will be recorded in our bug tracker with the 'gitlab-migration' tag. + Transition of wiki pages can start as desired (see separate plan proposal). + Bugs stay on LP for now 4. Outreach effort to bring in contributors + Assemble an outreach/advocacy team + Leverage our release marketing procedures and contacts + Coordinate with GSoC, releases, hackfests + Ensure we have reviewers/mentors on hand 5. Following the 0.93.0 release is a second checkpoint. + Review the recorded issues encountered. Collect further feedback. + How has use of gitlab affected contribution levels to the Inkscape codebase? If contribution levels have not grown then we need to reassess. + All active users of the service are asked to give thumbs up/down on their experience using gitlab. If most everyone gives thumb's up, we will proceed and stick with gitlab at least until 1.0.0. Otherwise, we need to re-evaluate our plans. + Plan follow-on work to investigate/address top issues. 6. Following the 1.0.0 release, we have another reassessment of all project technologies and services. cmake, git, gitlab, C++11, gtk3, and so on. We should then plan transitions from those to whatever is next, over the course of several 1.x releases.

6 13

Using libpotrace - any easy examples ?
by Ken Moffat 03 Mar '17

03 Mar '17

Among the changes for 0.92, I saw that libpotrace was no longer shipped, and therefore an external library was needed. Therefore, for those of us who build without that external library (I'm from BLFS - Beyond Linux From Scratch) we are apparently losing functionality compared to 0.91. But proving it to my colleagues is a different matter. My searches suggested that the Paintbucket tool would no-longer work, and that that could be confirmed by drawing a box with a foreground colour to fill it. But that continued to work, so I have been unable to prove that error on our part. Meanwhile, we had other fish to fry (/me wonders if that is the right phrase for a vegetarian to use, but whatever ...). Now that I'm back to looking at upcoming things, asking a question here looks like a nice diversion from upcoming changes in other packages (particularly firefox and its reputed requirement for rust), even if I end up showing my ignorance. So: is there a *simple* series of actions which even an artistic numpty like me can do, which will work on 0.91, but which on 0.92 *without* libpotrace will fail ? Thanks. ĸen -- `I shall take my mountains', said Lu-Tze. `The climate will be good for them.' -- Small Gods

2 2

is it possible to speed up CMake?
by alvinpenner 03 Mar '17

03 Mar '17

on Windows 10, current trunk, I normally execute the following two Cmake commands: mingw32-make -j 2 mingw32-make install The time required for this is 300 seconds, 150 seconds for each step. This time is the same no matter how small the change, even if I just insert one single blank character somewhere. Previously, using btool, the total time required for this would be about 10 seconds or so, for a complete rebuild of Inkscape. So CMake is about 30 times slower than btool, which makes it almost impossible to do diagnostic work with Inkscape, any way of speeding it up? Alvin -- View this message in context: http://inkscape.13.x6.nabble.com/is-it-possible-to-speed-up-CMake-tp4979104… Sent from the Inkscape - Dev mailing list archive at Nabble.com.

11 19

Simple Templates
by Deepti sharma 02 Mar '17

02 Mar '17

I am attaching some of the simple graphics made by using Inkscape. -- Regards Deepti Sharma Blog: https://deepti96.wordpress.com/ Github: https://github.com/dsdeeptisharma Gitlab: https://gitlab.com/u/dsdeepti "Great works are not performed by strength but by perseverance"

2 1