- Inkscape Devel - Inkscape Mailman

b schools in bangalore
by abbssm22＠gmail.com 27 Nov '19

27 Nov '19

best pgdm college in bangalore: Welcome to your future. We are the difference that makes you special. This is not just an institution, it's a springboard, and it's a catalyst. At ABBS, you will challenge yourself to learn, develop and r4e-engineer yourself to meet the demands of the country and the world. You are the future, and it is our responsibility to nurture the future.The MBA/PGDM at ABBS is specifically designed to prepare graduates in the emerging markets around the globe. The course is a transformative journey-offering unparalleled opportunity along with access to the best global management knowledge, corporate internships and placements from the finest companies in the market.this is one of the top 10 pgdm colleges in bangalore. visit:https://www.abbssm.edu.in

1 0

top 10 law colleges in bangalore
by abbslaw123＠gmail.com 27 Nov '19

27 Nov '19

law courses in bangalore:The ABBS School of Law has started from the academic year 2018 – 19 under the aegis of Samagra Sikshana Samithi Trust. The Trust started the institution with a cherished ambition to impart legal education which is a very important step towards spreading legal awareness and empowering the helpless in the society. The College is affiliated to Karnataka State Law University, Hubballi and recognized by Bar Council of India, New Delhi. The college has a Governing Council duly constituted by Samagra Sikshana Samithi Trust. All the members of the Governing Council are accomplished academicians, legal luminaries, management experts and persons of eminence in public service. Governing Council meets regularly two times a year to review academic and administrative work. [url=https://abbslaw.edu.in/]law courses in bangalore[/url] [url=https://abbslaw.edu.in/]law schools in bangalore[/url]

1 0

spam in the mailing list
by brynn 26 Nov '19

26 Nov '19

Hi Friends, I've noticed a lot of spam in the mailing list lately. Should the mailing lists be somehow linked in with website moderation? Or is there some other way? One way or another, I would ask this spam to be somehow controlled. Even just the 3 or 4 messages I've seen lately, are far too many. Thanks for listening. brynn

1 0

Re: Inkscape 1.0 course for LinkedIn Learning
by Bryce Harrington 22 Nov '19

22 Nov '19

Hi Mike, Thanks for contacting me, and double-thanks for your work at helping increase the number of Inkscape exprts. It's lovely to see the solid health of the overall ecosystem around Inkscape. It is indeed exciting to know 1.0 is coming soon, and having your tutorials available and up to date in conjunction with this release is a great goal. Inkscape is a 100% free and open source software project, and as such there's no NDAs or confidentiality agreements to deal with. (Although yes, the actual release date is sometimes embargoed to synchronize PR with packaging. But I suspect you're looking for a general estimate not the exact date.) That said, unfortunately it is difficult to predict when releases will occur with any degree of accuracy. Inkscape is a fully volunteer-driven project, and as such when there are release-critical issues the schedule can be driven by particular individuals' limited freetime availability. I hate to say, "It'll be released when it's ready to," but that's how it has always tended to end up working in practice... Due to my own limited time availability, I've handed off the release management role to Mc, who hopefully can provide some better indications about the timeframes for 1.0. I do know that the team has been hard at work at final polish, and it sounds like they're keen to get it out the door within the coming months. Beyond that, I'm not sure if you're aware, but there is a vibrant Inkscape community involved with documentation, user training, and support. They coordinate with book authors, conference organizers, and online instructors. I would encourage you to join this group, as it sounds like you're offering educational opportunities within that same space. Hopefully Maren or one of the others active in these areas can contact you with an invitation. Thanks again for your work at supporting the Inkscape ecosystem, and I hope 1.0 will bring increased opportunities for us all to spread wider knowledge of this software. Bryce On Wed, Nov 20, 2019 at 05:00:34PM -0500, Mike Rankin wrote: > Hello- > > My name is Mike Rankin, and I'm the instructor for the LinkedIn Learning > course on Inkscape > <https://www.linkedin.com/learning/inkscape-essential-training/>. At > LinkedIn, I teach courses on free and low-cost alternatives to Adobe > software, like Inkscape, GIMP, and soon Affinity Publisher). The Inkscape > course has helped many users and I'm very excited that I'll soon be able to > update it for version 1.0. > > I'm writing to see if you can share any news about when 1.0 will be > released. Any information would be a huge help for me to get the new course > done and released at the same time as the software. I understand that this > may be confidential information, so I'd be happy to enter into a > non-disclosure agreement. > > In any case, thanks for making a great piece of software and giving folks > an alternative to Adobe. > > Regards, > > Mike Rankin

2 1

Re: 8 Bugs - 1.0beta1 (32d4812, 2019-09-19) (New User - Mac OS Catalina)
by Ben Griffin 20 Nov '19

20 Nov '19

Hi folks, C Rogers, thanks for your reply. > Inkscape is a different program than Illustrator. Of course. It should be better than Illustrator, and it’s got some great features already. If you thought that was what I expected, with respect, your assumption was mistaken. > (1) Surprise Quit >> This is one thing that's just plain different about Inkscape…. Nope. It’s pretty normal for some operating systems, such as windows, where a window is an application. Not so on MacOS, where a window is (most times) merely a document within the application. It may be that you have not used MacOS much. Try opening any application on MacOS. Close the window - guess what? You have not closed the application. Not even with MS software. Why? Because to do so is a bug on MacOS. There’s nothing unique about Inkscape - it’s just either arrogance or laziness. Okay, so you’ve chosen to use a document window as your application root, and you don’t want to refactor your code to suit the UI guidelines of different OS - so, there is a is a 'lazy' way available to you - look at eg, GarageBand - which is a window-centred application. It starts, either with the last project, or it gives you a ‘choose a project to open/create new) window. You could do that. Not doing that is breaking your port to MacOS. Otherwise, it's a bug. > (2) Location of preferences menu item. > 1) BUG - Preferences is in the Edit menu rather than in the ‘Inkscape’ menu >> Inkscape is cross platform, which means that there may or may not be an Inkscape menu at all, which is a MacOS convention Again, this is laziness or arrogance, and it’s a bug. You telling me that Adobe software isn’t cross platform? Even if there is no ‘Inkscape Menu’, there’s the File menu - which is where I look for preferences. Why? Because “File” is about Files - ie, documents, - so yes, project settings, project preferences, they belong under File. Apple subsequently decided (imo correctly) that Application level preferences should be under the application. Again, go into any MacOS application that has and edit menu - and look to see what is there. ‘Preferences' isn’t one of them. It’s a bug. You may think this is merely my opinion. What you are forgetting is that there is a uniform approach to application user interface on MacOS. Every single time you make a decision to break the UX guidelines, you increase the complexity of your application, and you lose thousands - even hundreds of thousands - of potential users; you may think it’s an opinion of mine - but go look at the available UX / UI guidelines published by Apple (and Xerox before them), along with the absolutely vast budget they put into it, in order to make MacOS ‘easy’. So if you want a niche geek product, ignore what I say or just decide it’s a WONT-FIX / NOT-A-BUG. I will still use it. But I know plenty of people who will just say ‘I tried it, and it didn’t work’. Lastly, I was asked by your own documentation, to report bugs to inkscape-dev, which is what I did. If you now want me to post bugs on https://gitlab.com/inkscape/inkscape/issues <https://gitlab.com/inkscape/inkscape/issues>, the answer is sorry, bud., I did what was asked of me. I truly would like to see Inkscape become a killer app on Mac OS. But if your hearts are not into it, and you just want to keep it on Linux, fine - I’m all for free community driven software on community driven machines - it’s what I get paid to do, which is super cool. On the other hand, if you are committed to making Inkscape truly cross-platform, you have to make it conform to those platform’s own guidelines and conventions, otherwise it’s just a bad port for niche geeks like me. -B.

7 19

Vote for your favorite Inkscape About Screen!
by Maren Hachmann 18 Nov '19

18 Nov '19

It's time to vote for the About Screen for Inkscape's version 1.0! We're very proud to present you with an amazing gallery featuring 124 entries, by 96 different Inkscape artists. Thank you so much to everyone who entered! Community voting opens on November 18 and closes on December 1, 2019. Here are the rules: * If you don't have a user account on the Inkscape website yet, you need to register (https://inkscape.org/user/register/) to be able to vote. * Everyone gets 1 vote - this includes all contest entrants. * Visit the gallery and check out all the amazing works of art. * Click on one of the thumbnails to see the a larger version of the image and a description. You can also comment on the contest entry. * To cast your vote, either click on the check mark below the image or hover over the small image in the gallery to see a circle-shaped checkbox you can click on. If you accidentally vote for the wrong entry, you can change your vote by simply voting for a different one. * Voting will ONLY be accepted via the Inkscape website. * You can vote until Sunday, December 1, 2019, 23:59 (Time zone: UTC). * Once the community voting is done, the top five entries with the most votes will be passed on to the developers, who will then vote to determine the winner. * For the contest participants, ANY modifications of the files are prohibited at this point. SEE ALL ENTRIES AND CAST YOUR VOTE HERE: https://inkscape.org/gallery/=about-screen-contest/contest-for-10/ Good luck to all participants!

1 0

Re: 8 Bugs - 1.0beta1 (32d4812, 2019-09-19) (New User - Mac OS Catalina)
by C R 17 Nov '19

17 Nov '19

Sorry, replied to Ben only. Here's a forwarded reply. On Sun, 17 Nov 2019, 19:47 C R, <cajhne(a)gmail.com> wrote: > Hi, thanks for taki g the time to contact us and share your thoughts. > > > IMO the first four bugs I mention here are so major that many first time >> users will decide not to use InkScape again, which is unfortunate as it’s a >> really great app. >> > > Inkscape is a different program than Illustrator. It's not meant to be a > copy, nor is it designed as a free version of that software. As a long time > Illustrator user myself, I can say that if feature parity is what you seek, > it's going to be a bad time. I feel the same way when forced to use > Illustrator CC, because some problems they have not fixed even after all > these years. Some are things that Inkscape users would certainly miss going > to Illustrator. So with that in mind, let's proceed... > > > Using vanilla 1.0beta1 on MacOS Catalina 10.15.1 (19B88) with default >> preferences set. >> > > >> (1) Surprise Quit >> 1) Open Inkscape. >> 2) Close ‘New document 1’ >> 3) BUG - Inkscape has now quit. There is no reason why the application >> should depend upon the existence of a document window. >> > > This is one thing that's just plain different about Inkscape. There is no > main window which acts as a container for open Inkscape documents. Each > time you open a new Inkscape document it makes a window for it. It would > take a major redesign to have a container window which mirrors how > Illustrator works. So no, unfortunately this is not a bug. :) > > (2) Location of preferences menu item. >> 1) BUG - Preferences is in the Edit menu rather than in the ‘Inkscape’ >> menu >> Actually, many items in the Edit menu, which are to do with application >> level settings, should be in the Inkscape Menu. >> > > Inkscape is cross platform, which means that there may or may not be an > Inkscape menu at all, which is a MacOS convention. This is why those items > are located in the Edit menu, which is a fairly standard place to look for > preferences if you've used Adobe products and most other graphics tools on > Windows and Linux. Hopefully the placement of the preferences item is not > something which will trip you up often. If it is, I recommend learning the > hotkeys to bring it up. > > (3) Surprise Preferences panel dimensions. >> 1) Open Inkscape. >> 2) Open the preferences panel. >> 3) BUG - The panel height stretches across the entire vertical size of >> the screen, with no ‘preference tab’ content that deep. >> The panel width is unusually narrow, with some form elements being >> clipped by the panel. (Eg, System, Interface) >> Moreover, the nested tree is surprising, with the higher nodes (eg >> behaviour) showing minimal details, with no documentation / hints >> whatsoever. >> > > That does sound like a bug. I recommend reporting that one in our GitLab > bug tracker as per the instructions on the website. > > Tracker here: > https://gitlab.com/inkscape/inkscape/issues > > Our Mac OS build functions without the need for xquartz now, which was a > universal pain in the ass to install, so please bear with us while we > continue to make the new build better. > > >> (4) Panel/Dialog focus problems. >> 1) Open Inkscape. >> 2) Open the preferences panel. >> 3) Drag the preferences panel so that the traffic light (close / >> minimise / zoom) sit over the centre of ‘New document 1’ >> 4) Click once on the RED (close) traffic light. >> 5) BUG - Focus is transferred to ’New document 1’ and the preference >> panel fades. (See following cropped screenshot). >> > > > Yep, that looks like a bug too. Please report it here so our Mac team can > address it: > https://gitlab.com/inkscape/inkscape/issues > > (5) New ellipse uses previous ellipse controls. >> 1) Open Inkscape. >> 2) Give focus to ‘New document 1’ >> 3) Create a ‘pacman’ using the (very cool) pie tool. >> 4) Deselect, and draw a new ellipse. >> 5) BUG- (By default) the new ellipse is the pacman, not a new ellipse. >> 6) BUG- (If you believe that 5 is the correct behaviour) a single click >> with the ’ellipse tool' SHOULD generate the identically dimensioned >> previous shape at the mouse position. >> 7) Both of the above behaviours should be controlled by preferences. >> There is a ’style’ preference available, but default style and default >> shape are different. >> > > 5 is expected behaviour, and 6 is a wishlist item I guess? Anyway not > bugs. If you want to create exact copies of a shape at the mouse cursor, > just drag the original shape around and tap the spacebar while dragging. > This will drop new copes of the original shape. > > Inkscape remembers what shape you last made. If you want a complete circle > back, just click the complete circle button at the top of the screen and it > will be a circle from then on, until next you change it. > > Is it weird to draw multiple pie shapes? Yea, probably. :) However this > behavior is constant with the rectangle tool and star tool which you may > very well want to say, keep making rectangles with the same corner radius > over and over. It would be a pain to keep having to round corners, no? So > yea, it's weird, but it makes sense if you think about it as a unified tool > set. The fix is easy enough too. Single click, sorted. > > > >> (6) Outline Display Mode >> Outline Display should (or should be set by preference) show >> polygon/object centres. >> > > Wishlist item/feature request. I agree this would be a nice feature > though. > > >> (7) Measurement Tool (Language). >> It’s the first time I’ve heard of a starting measurement point being >> called a Knot. >> If you are going to use specialised language, provide a strong hint as to >> what that is. >> > > Well it's not a vertex or a node. We could call them handles perhaps, but > then that might be confused with the handles on bounding boxes etc. At any > rate, this is not a bug so much as a convention of the software. > >> > (8) Font sample text. >> Nearly all fonts include a sample text to show / highlight the font. >> Your font dialog does not use that, doesn’t provide a preference to allow >> for it. >> Many font names are incorrect, and likewise do not always show the >> correct sample (because the InkScape characters are not always represented) >> See ‘Baghdad’ as an example below (with Font Book overlay) >> > > Yes, this is a bug. Please report it in our GitLab bug tracker. > > https://gitlab.com/inkscape/inkscape/issues > > Thanks for taking the time to help us make Inkscape better. > > -C.Rogers > > > >> >> >> _______________________________________________ >> Inkscape Devel mailing list -- inkscape-devel(a)lists.inkscape.org >> To unsubscribe send an email to inkscape-devel-leave(a)lists.inkscape.org >> >

1 0

8 Bugs - 1.0beta1 (32d4812, 2019-09-19) (New User - Mac OS Catalina)
by Ben Griffin 16 Nov '19

16 Nov '19

Being a new user, I’m writing here, as requested by /contribute/report-bugs/ I’m one of what is probably several who have abandoned Adobe Illustrator after Adobe decided not to patch their older versions to work on 64bits. IMO the first four bugs I mention here are so major that many first time users will decide not to use InkScape again, which is unfortunate as it’s a really great app. Using vanilla 1.0beta1 on MacOS Catalina 10.15.1 (19B88) with default preferences set. (1) Surprise Quit 1) Open Inkscape. 2) Close ‘New document 1’ 3) BUG - Inkscape has now quit. There is no reason why the application should depend upon the existence of a document window. (2) Location of preferences menu item. 1) BUG - Preferences is in the Edit menu rather than in the ‘Inkscape’ menu Actually, many items in the Edit menu, which are to do with application level settings, should be in the Inkscape Menu. (3) Surprise Preferences panel dimensions. 1) Open Inkscape. 2) Open the preferences panel. 3) BUG - The panel height stretches across the entire vertical size of the screen, with no ‘preference tab’ content that deep. The panel width is unusually narrow, with some form elements being clipped by the panel. (Eg, System, Interface) Moreover, the nested tree is surprising, with the higher nodes (eg behaviour) showing minimal details, with no documentation / hints whatsoever. (4) Panel/Dialog focus problems. 1) Open Inkscape. 2) Open the preferences panel. 3) Drag the preferences panel so that the traffic light (close / minimise / zoom) sit over the centre of ‘New document 1’ 4) Click once on the RED (close) traffic light. 5) BUG - Focus is transferred to ’New document 1’ and the preference panel fades. (See following cropped screenshot). (5) New ellipse uses previous ellipse controls. 1) Open Inkscape. 2) Give focus to ‘New document 1’ 3) Create a ‘pacman’ using the (very cool) pie tool. 4) Deselect, and draw a new ellipse. 5) BUG- (By default) the new ellipse is the pacman, not a new ellipse. 6) BUG- (If you believe that 5 is the correct behaviour) a single click with the ’ellipse tool' SHOULD generate the identically dimensioned previous shape at the mouse position. 7) Both of the above behaviours should be controlled by preferences. There is a ’style’ preference available, but default style and default shape are different. (6) Outline Display Mode Outline Display should (or should be set by preference) show polygon/object centres. (7) Measurement Tool (Language). It’s the first time I’ve heard of a starting measurement point being called a Knot. If you are going to use specialised language, provide a strong hint as to what that is. (8) Font sample text. Nearly all fonts include a sample text to show / highlight the font. Your font dialog does not use that, doesn’t provide a preference to allow for it. Many font names are incorrect, and likewise do not always show the correct sample (because the InkScape characters are not always represented) See ‘Baghdad’ as an example below (with Font Book overlay)

1 0

8 Bugs - 1.0beta1 (32d4812, 2019-09-19) (New User - Mac OS Catalina)
by Ben Griffin 16 Nov '19

16 Nov '19

Being a new user, I’m writing here, as requested by /contribute/report-bugs/ I’m one of what is probably several who have abandoned Adobe Illustrator after Adobe decided not to patch their older versions to work on 64bits. IMO the first four bugs I mention here are so major that many first time users will decide not to use InkScape again, which is unfortunate as it’s a really great app. Using vanilla 1.0beta1 on MacOS Catalina 10.15.1 (19B88) with default preferences set. (1) Surprise Quit 1) Open Inkscape. 2) Close ‘New document 1’ 3) BUG - Inkscape has now quit. There is no reason why the application should depend upon the existence of a document window. (2) Location of preferences menu item. 1) BUG - Preferences is in the Edit menu rather than in the ‘Inkscape’ menu Actually, many items in the Edit menu, which are to do with application level settings, should be in the Inkscape Menu. (3) Surprise Preferences panel dimensions. 1) Open Inkscape. 2) Open the preferences panel. 3) BUG - The panel height stretches across the entire vertical size of the screen, with no ‘preference tab’ content that deep. The panel width is unusually narrow, with some form elements being clipped by the panel. (Eg, System, Interface) Moreover, the nested tree is surprising, with the higher nodes (eg behaviour) showing minimal details, with no documentation / hints whatsoever. (4) Panel/Dialog focus problems. 1) Open Inkscape. 2) Open the preferences panel. 3) Drag the preferences panel so that the traffic light (close / minimise / zoom) sit over the centre of ‘New document 1’ 4) Click once on the RED (close) traffic light. 5) BUG - Focus is transferred to ’New document 1’ and the preference panel fades. (See following cropped screenshot). (5) New ellipse uses previous ellipse controls. 1) Open Inkscape. 2) Give focus to ‘New document 1’ 3) Create a ‘pacman’ using the (very cool) pie tool. 4) Deselect, and draw a new ellipse. 5) BUG- (By default) the new ellipse is the pacman, not a new ellipse. 6) BUG- (If you believe that 5 is the correct behaviour) a single click with the ’ellipse tool' SHOULD generate the identically dimensioned previous shape at the mouse position. 7) Both of the above behaviours should be controlled by preferences. There is a ’style’ preference available, but default style and default shape are different. (6) Outline Display Mode Outline Display should (or should be set by preference) show polygon/object centres. (7) Measurement Tool (Language). It’s the first time I’ve heard of a starting measurement point being called a Knot. If you are going to use specialised language, provide a strong hint as to what that is. (8) Font sample text. Nearly all fonts include a sample text to show / highlight the font. Your font dialog does not use that, doesn’t provide a preference to allow for it. Many font names are incorrect, and likewise do not always show the correct sample (because the InkScape characters are not always represented) See ‘Baghdad’ as an example below (with Font Book overlay)

1 0

Bugfest - FIrst week in December.
by Tavmjong Bah 13 Nov '19

13 Nov '19

Hi, We are planning on having a "Bugfest" the first week of December. Mc has reserved a room at his institute outside of Paris where at least he and I will meet. Martin can host a meet up in Boston. Is anybody interested in joining us either in Paris or Boston? If you are, please let us know ASAP as we'll need to organize a board vote to cover travel expenses. (I envision offering up to $1000 for attending.) Remote participation is also highly encouraged! Further details at: https://wiki.inkscape.org/wiki/index.php?title=Bugfest2019 Tav

1 0

Inkscape for dinosaur track research, questions
by Jens Lallensack 04 Nov '19

04 Nov '19

Dear all, I am palaeontologist at the University of Bonn, Germany, focusing on fossil dinosaur footprints and trackways. I regularly use Inkscape for my research (for measuring, data extration, and drawing of interpretive outlines), and have cited this software in several of my papers. I am currently working on a methodological paper on how to analyze fossil footprints based on 3D models. The approach I will present in this paper includes Inkscape as an important component. The idea is to import raster images into Inkscape (different graphical 2D representations of the 3D model), align them into an image stack, and draw interpretive outlines on a separate layer. I use the Bezier curves tool to collect a number of landmark coordinates from the separate footprints, which I then export to automatically calculate a large number of measurements for statistical analysis. The paper is to be published in a peer-revied journal (currently, I have the Journal of Palaeontological Techniques in mind, https://www.jpaleontologicaltechniques.org/). I already used this method in a recent paper (https://www.tandfonline.com/doi/abs/10.1080/02724634.2018.1512501) to rapidly collect measurements of a larger number of trackways. The aim of the new methodological paper is to improve this method and to make it available to our comunity of footprint researchers. However, there are two open issues/questions regarding Inkscape. I was wondering if you could give me some advice here. Export of path node coordinates is, unfortunately, currently possible only via a plugin, which adds an additional hitch (but I understand that research is not the focus of Inkscape). Such a plugin was posted on the Inkscape Forum in 2011, with improvements added by different members (https://www.tandfonline.com/doi/abs/10.1080/02724634.2018.1512501). I simplified the code so that it returns node coordinates only (and not those of the handles), see code below. Now to my questions: 1) I need to cite the modified coord export script in my paper, and make sure that it stays available. I assume that code published in the forum is not automatically released under a free licence, and that I cannot simply distribute the script together with the paper. A possibility might be to post the modified script to the forum and provide the link in the paper. This is only an option if the link remains available for a longer time (I cannot modify the paper once published). What would be the optimal way? 2) The coordinates given by the script need to be mirrored and translated to match the coordinates displayed within Inkscape itself. I would need to improve the script so that this is done automatically. I'm not into python scripting, but would try to figure this out. Any help/hints with this would be much appreciated. Thank you very much in advance. Kind regards, Jens Lallensack ----- xyexport.py ------- #!/usr/bin/env python import inkex import sys import simpletransform import cubicsuperpath class TemplateEffect(inkex.Effect): def __init__(self): inkex.Effect.__init__(self) def effect(self): for node in self.selected.iteritems(): output_all = output_nodes = "" for id, node in self.selected.iteritems(): if node.tag == inkex.addNS('path','svg'): output_all += "" output_nodes += "" simpletransform.fuseTransform(node) d = node.get('d') p = cubicsuperpath.parsePath(d) for subpath in p: for csp in subpath: output_nodes += str(csp[1][0]) + "\t" + str(csp[1][1]) + "\n" sys.stderr.write(output_nodes) effect = TemplateEffect() effect.affect()

3 13

Board meeting Oct 4th
by Bryce Harrington 29 Oct '19

29 Oct '19

Our monthly board meeting is scheduled for Friday, Oct 4th, at 10am Pacific in #inkscape-devel. All members are welcome. http://wiki.inkscape.org/wiki/index.php/Board_Meetings I unfortunately have an all-day event for work downtown on Friday, can someone else please run the Inkscape board meeting? I should be able to attend in lurk mode. Agenda: ------- * Hackfest planning * Infrastructure - mailing list migration off SourceForge - Wiki migration off OSUOSL - Weblate service deployment * Software Release status - Inkscape 1.0beta - Inkscape 1.0 * GSoC * Bug migration off Launchpad * Other Business Action Items from last meeting: ------------------------------- Transcripts of previous meetings: --------------------------------- http://alpha.inkscape.org/board/meetings/transcripts/ Bryce

2 2

About Screen Contest: 2 weeks 6 days left to submit your entries!
by Maren Hachmann 28 Oct '19

28 Oct '19

Hi Inkscape users, there's still time to participate in the About Screen Contest for Inkscape 1.0 ! We'd love to see many more and varied entries from you! Rules and more info: https://inkscape.org/community/about-screen-contests/ Contest entries: https://inkscape.org/gallery/=about-screen-contest/contest-for-10/ So, reserve some time this week for contributing to the magical Inkscape 1.0 in this cool way :D Don't wait until the last minute! Tim Jones helps you by checking your entries for rule compliance, make sure to watch for any comments on your About Screen proposal! Looking forward to what y'all will come up with! Maren

1 0

Question about wiki account
by Tomáš Marný 10 Oct '19

10 Oct '19

Hello! Can I apply for a wiki account here? I updated the Czech translation, which was not in good condition. And I also want to update Czech terminology. Thank you for your response. Sincerely, Tomáš M.

2 1

String and Feature freeze
by Marc Jeanmougin 09 Oct '19

09 Oct '19

Hi devs and translators ! Just to make it official, we are now in feature and string freeze : - New features that have any possibility of having a bug or to need testing will be postponed to post-branching time - Any modification to strings will need to be approved and will need an email to translators ML - Dev focus should ideally be given to bugfixing ;) @Translators : the pot file should now be stable, as Maren indicated a few hours ago (only two strings changed since then), sorry for the changes Thanks all for your involvement in this release! -- Mc

1 0

Join the 1.0 About Screen Art Contest!
by Maren Hachmann 07 Oct '19

07 Oct '19

Hello Inkscape Community, it's that time again! Starting October 7th (today) through November 17th we are accepting submissions for the About Screen Contest for Inkscape 1.0! This is your opportunity to contribute to this major milestone for your favorite vector graphics editor! The contest winner's artwork will be showcased in the 'Help > About' menu entry in Inkscape. You can use the current Beta version to play with the new features and to make your artwork be a good representation of what Inkscape 1.0 can do! Learn more about the contest here: https://inkscape.org/community/about-screen-contests/ Good luck to all - and, of course: Draw Freely :)

1 0

Is this a known issue? (and the dumbest bug ever)
by Josh Andler 15 Aug '19

15 Aug '19

I searched the bug tracker (perhaps using language that was too specific) but I couldn't find a report... Is a path using dashes with rounded caps supposed to ignore the rounded caps when you convert Stroke to Path? It visually does it right with butt or square caps, but rounded caps get converted as butts from how it appears. I'm seeing this in both stable and trunk and it seems... like an odd oversight. Anyone else have thoughts? Cheers, Josh

1 0

Mailman3 outage
by Bryce Harrington 14 Aug '19

14 Aug '19

The mailman3 list server was offline the past week, due to troubles it had delivering email to administrative user accounts. This generated excessive error logging to disk. I'm not 100% sure this is root caused but after clearing the queue it seems to be running happily again. I'll try and keep a closer eye on it. Bryce P.S. there's still a problem with some people unable to subscribe to the mailing lists; I doubt this change will fix chat, so this problem is still on the todo list.

1 0

Re: Beta-blockers ?
by Patrick Storz 14 Aug '19

14 Aug '19

Hi Marc, thanks for planning this thoroughly! Answers below. Am 12.08.2019 um 21:13 schrieb Marc Jeanmougin: > == Extensions (Martin, Patrick, others) == > > What is the state of extensions (#156) ? In particular, their > translatability (#333) ? Is the current submodule commit in a "good > state" ? What to do with the old uniconvertor extensions, do we update > them to uniconvertor 2.0rc5 ? While Martin and others did (and are still doing) a great job on the bundled Python extensions I'm currently working on the extension implementation in Inkscape itself. I just finished one big part (.inx format updates and the internal logic in Inkscape to parse preferences/parameters form it while also creating nice GUIs) which is ready for review at https://gitlab.com/inkscape/inkscape/merge_requests/808 As Martin already mentioned translations are basically handled as before (still use inkscapes .pot/.po files), only the way we mark strings for translation in the.inx changed. Once the MR is merged it will be a trivial job to update the .inx files with some search&replace, although the code should be fully backwards-compatible to earlier .inx files. Regarding splitting the translations of extensions into the extension repo (and also allowing third-party extensions to ship their own translations): The current MR implements the syntax, but the actual functionality is not included yet. However I realized while working on it, that I already have done most of the required refactoring, minimizing the effort that remains for finishing the feature. If we feel like this is a welcome feature for 1.0 already, we can probably implement it in time instead of delaying it until 1.1 as I initially planned. I'm starting to think that this would actually be nice, as we can offer a finished feature in 1.0 instead of just syntax for a feature that is not implemented yet. > == Gtk General interface stuff (all) == > > Do we still have interface problems like toolbars not showing up or > menus needing two clicks, or anything of the sort, on any platform ? Is > #195 still reproducible ? I'm not aware of anything specific right now that prevents usage. In general there's still a fundamental "glitchiness" to gtk3 on Windows, but I'm afraid that's just how gtk3 works on Windows these days. We'll certainly get some questions about it, but I wouldn't know what to do to significantly improve this until the release. > == Packaging (RdH, Patrick, others) == > > Approximately how much work is still needed for macOS stable dmg > production or windows packaging ? > > What happens with the ubuntu bionic "dependency wait" ? ( > https://launchpadlibrarian.net/437056488/buildlog.txt.gz ) Updating our existing Windows packaging for 1.0 should be easy (once I can motivate myself to do it). I always planned to look into cpack and investigate if it can produce proper installers, so we might eventually get rid of our own packaging and reduce the overhead of maintaining it, but that might need some more work. > == Performance (all) == > > Do we still have these massive performance problems as soon as the > Objects dialog (or XML ?) has been opened ? I'm not aware anybody pushed a fix? Didn't retest, though. Apart from that performance stil lseems worse than 0.92.x (at least on Windows), but also here I wouldn't really know what to do. It's usable, but it's not good. One particular performance issue (I know there were multiple reports, but not sure we have an actual issue for it and GitLab throws 500 errors at me): Selecting a new font takes a very long time (a few seconds at least, some take 10-20 seconds). Not sure if this is exclusive to Windows? It does not happen in 0.92.x, though (with the same version of fontconfig/harfbuzz/pango/...), so it's either something we're doing, or something gtk3 is doing differently from gtk2. I think performance wasn't always bad in master, though. I think it started either with the variable fonts support or after the SPStyle refactor. > > == Text (Tav, Jabier, others) == > > How usable is the text tool ? Do we implement the "hamburger" toolbar ? > Do we still have issues with variable font sliders ? How understandable > are our text tools, and are users able to "just write text" without > surprises ? (with line heights for instance ?) Tbh, I can't use the text toolbar myself anymore... Either I'm to stupid or we really *should* do something about usability. It never behaves as expected and always sets properties in ways that were not intended. One line-height related issue that also needs attention is https://gitlab.com/inkscape/inkscape/issues/244 > == SVG2 (Tav, all) == > > I'm not sure we have discussed enough the transition between SVG1.1 and > SVG2. If we start producing svg2 documents that are not svg1.1-valid, > should we use version="2" in <svg> ? how will it be understood by other > renderers ? When and how do we intend to switch the 1.2 flawed text into > the newly flawed text, how will we handle old documents, and how do we > ensure they will render exactly the same ? Do we provide a way to save > in "valid SVG1.1 document without SVG2 stuff" ? I'd say we should always produce SVG1.1 fallbacks, even if we use SVG2 features? Maybe we can then add an option to disable the compatiblity shims and produce a "pure" SVG2 document. I know some switches are available, but Tav can probably comment better on what is implemented and what isn't. > == Documentation (Maren) == > > I saw https://gitlab.com/inkscape/inkscape-docs/documentation/issues/2 , > do we have more stuff to update ? By the way, how do we sync the > inkscape/inkscape repo with the inkscape/inkscape-docs ? As Maren mentioned already there's a lot to update content-wise. I've handled most of the technical side and meant to make a call for help at some point, but didn't get the chance to do it yet. Once content is updated I typically copy the CI-generated files manually and push the update to the inkscape repo. Basically this can wait till shortly before 1.0, but we can certainly schedule a preliminary update for the beta(s). Cheers, Patrick

1 0

Beta-blockers ?
by Marc Jeanmougin 14 Aug '19

14 Aug '19

Hi all, The toolbar bug seems fixed for most systems and only seems to appear on wayland (at least I can't trigger it on xorg), and is now reported upstream at https://gitlab.gnome.org/GNOME/gtk/issues/2000 The translation system seems better (#311), so … do anyone see any issue that would need to be fixed before releasing a beta ? -- Mc

4 5

new forum is open!
by brynn 01 Aug '19

01 Aug '19

Hi Friends, As far as I can tell, the new forum is officially open! I've blocked new registrations on Inkscape Community, with a banner on the index page linking to the new forum. brynn

1 0

opening new forum this week
by brynn 30 Jul '19

30 Jul '19

Hi Friends, The new forum is opening this week! I'm planning to start the transition from Inkscape Community to the new forum, on July 31 (in my part of the world). Because by the time it's August 1st for me, it's either already, or almost August 2nd for half the world. Martin, can you please plan to release the posting block on the new forum, on July 31 ? Would you please let me know when it's done? And then I'll block all new posting on Inkscape Community. I hope to heck I've thought of everything. But I'm sure there will be some surprises. Any and all comments or concerns are still totally welcome. All best, brynn

1 1

Inkscape booth at Kielux - help present Inkscape in Kiel!
by Maren Hachmann 22 Jul '19

22 Jul '19

Hi, I'm looking for a second person to staff the Inkscape booth in Kiel at Kieler Open Source und Linux Tage on September 20th and 21st this year. As I'm also presenting at and co-organizing the event, it would be really good if there were someone else who can help, even if only for a few hours. You don't need to be an expert in Inkscape, but you should bring some motivation and enthusiasm for the program and its capabilities. More info about the event is available at: https://kielux.de There will also be some very interesting talks and workshops, and you'll have direct access to Inkscape stickers (at least those are planned) and fresh info about the latest developments :) If you'd like to join me, please reply to this email! Hope to hear from you Maren

1 0

Re: moderators need ability to curate the description in gallery
by Josh Andler 15 Jul '19

15 Jul '19

Ok. I will go ahead and file it either tonight or in the morning. Once I've done that I'll link it here so anyone following can make sure my request looks right and add any notes they deem appropriate. Cheers, Josh On Sun, Jul 14, 2019 at 1:21 PM Martin Owens <doctormo(a)gmail.com> wrote: > On Sun, 2019-07-14 at 12:34 -0700, Josh Andler wrote: > > Including your email in case you haven't followed this thread. What > > are your thoughts on this? > > Hi Josh, > > I think this is a reasonable moderation request. A tool that could be > added, it would probably edit the urls in the text, since they get > auto-converted in the template. But changing the colon to a semi colon > should do the trick. > > If this is the settled solution, an issue should be made in the > inkscape-web tracker. > > Best Regards, Martin Owens > >

1 0

moderators need ability to curate the description in gallery
by brynn 14 Jul '19

14 Jul '19

Hi Friends, Reference the 3 images uploaded by this member: https://inkscape.org/~yendrifernando/ The images appear to be made with Inkscape, but in my opinion, the links in the description are spam. As a moderator, I would like to be able to edit the description (via Curate) and remove only the "www.". In that way, the description still tributes the inspiration for the images to that website (as the member appears to intend), without having an active link to the website. Breaking the link removes the spam. Martin and I have had an extended private discussion about this. But he disagrees with giving moderators the ability to edit the description. He says that we need to have a community discussion about it. I'll have to be honest and say that I don't understand his position, or even really know exactly what his position is. Even if I did, I wouldn't try to represent it. So he'll have to do that. Our discussion ranged far and wide over moderation subjects, but none of his arguments really hit home to me, as a good reason not to allow moderators to edit (curate) the description. So it seems we've hit a stalemate. I'll be honest again and say that I'm not sure if the purpose of this discussion is to repeat our discussion publicly, or just to get opinions on curating the description. Because a lot of his concerns seemed to be about potentially overly aggressive moderation. Or maybe it's both? But I think I'm a fair moderator and can train fair moderators, so I'm ready either way :-) Martin, I hope this is a fair introduction of the issue? All best, brynn

2 3