- Inkscape Devel - Inkscape Mailman

Developer meeting, Nov 7 2024
by Jonathan Neuhauser 07 Nov '24

07 Nov '24

Present: Elendil, Ishaan Arora, Martin, Mike, René, Jabiertxof Elendil reports that the bugtracker has been pretty healthy recently. Ishaan continued working on selection cues, working on the design. Some discussion about how to implement this. Jonathan briefly presented three proposed contract development projects: 1) GTK4 cross-platform fixes, 2) Improving Windows developer experience / dev documentation, 3) Website upgrades / better use of the CDN. Help is appreciated to formulate the goals of these projects, please contact him if you can help. Some discussion on 2). The prime goal is to improve the developer experience on Windows, to attract Windows developers. Questions: How much effort is necessary to build Inkscape with Visual Studio? Can we do it with GCC, or do we need to patch msvc? Martin raises the point that another compiler increases complexity of the codebase. René thinks that we should offer a native build experience, that means using msvc. He will look into whether there is a convenient way to hook up clang or gcc with VS to make sure that's not an option. There is a certain risk that this doesn't pay off - if we fail to attract Windows developers, this infrastructure would rot. René: how many wrappers would we need to create? Martin is working on PDF export as a C++ internal extension, and is improving the new upstream Library CapyPDF at the same time. This work will occupy him for some time. He describes the relationship with upstream as good. Mike has worked on the way we develop themes; they can now be written on SASS. He's also worked on decoding LAB colors from Adobe Color files. Some technical discussion between Mike and Martin about the Color API. René has been phasing out jobs on the Intel runner. He's on a bit of a break, waiting for the new MacStadium infrastructure, so he can set it up. The donated infrastructure would be valued around 700 USD per month. On the Windows side he's looking for cloud hoster that can provide Windows infrastructure for us. Martin thinks that this is important for programs like the Bugfix Accelerator. After the meeting, we've looked at some MRs.

1 0

Seeking your thoughts on LLM-generated contributions
by Daniel Pono Takamori 04 Nov '24

04 Nov '24

Heya Inkscape Developers, Following up on an issue that came up a few months ago about code and other uses of LLMs; we at Software Freedom Conservancy have been hearing from member projects that people are asking whether they can submit code to these projects that was generated by large language models (LLMs), sometimes called AI coding assistants. We'd like to better understand the nature of these requests, how much LLM-generated code has been offered to these projects, and generally how you're feeling about the situation. To do this, we will be holding three different sessions, where you are welcome to join and share your thoughts and any details so far on these types of contributions. The sessions will all be run in the same way with the same topic - we are running three in order to hopefully allow as many people from around the world to attend as possible. Our Director of Compliance, Denver Gingerich, will be hosting some sessions at the times below for all our member projects to discuss the issue. date -d "2024-10-29 20:00 UTC" date -d "2024-11-01 14:00 UTC" date -d "2024-11-06 04:00 UTC" We'll be meeting in this room for the sessions: https://bbb.sfconservancy.org/b/oss-nnj-obi-jea We are excited to see some of you there and are looking forward to drafting appropriate recommendations based on what we hear! Thanks, -Pono

2 4

Inkscape 1.4 released!
by Marc Jeanmougin 13 Oct '24

13 Oct '24

================ = Inkscape 1.4 = ================ Thanks to all the work from our community, we are proud to announce that Inkscape version 1.4 is now released. ---------------- You can find out about the new features at: https://inkscape.org/news/2024/10/13/inkscape-launches-version-14-powerful-… and download it for your platform on: https://inkscape.org/release/inkscape-1.4/ then, if you want to support Inkscape, donate to the project at https://inkscape.org/support-us/ ---------------- Inkscape 1.4 is the latest major release of Inkscape, following more than one year of development after the 1.3 major release, and paving the way for the next version of Inkscape. The highlights of this release are: - Filter Gallery: it has never been so easy to find the best filter for your needs! This new dialog features previews, categories and search. - Modular grids & improved axonometric grids: set the grid angle by ratio for isometric designs and use modular grids to plan layouts and make icons! - Swatches dialog and palette file handling improved: quick access to dialog layout controls, search for colors, and open different palette file formats! - Unified font browser preview: when activated in the preferences, use it to quickly browse through your font collection. Try it out and give your feedback! - Customizable handles: Power users with CSS knowledge can now customize the styling and basic shape of all the handles! - Fast image clipping with the Shape Builder: raster graphics can now be clipped into multiple sections using the Shape Builder. - Affinity Designer File Import - Support for internal links in exported PDF files - A whole new icon set - There's even more: faster extensions, new templates for folding booklets, additional options in Ruler and Taper Stroke LPE, new keyboard shortcuts, changed node deletion behavior, preview in Spray tool, many new command line options, more supported color palette formats (e.g. CIELAB, Adobe Color Book and Adobe Swatch Exchange), updated translations and many bug fixes. The new features are showcased and illustrated at https://media.inkscape.org/media/doc/release_notes/1.4/Inkscape_1.4.html . ----------------------------- Join an Inkscape project team ----------------------------- Inkscape is always happy to welcome new contributors in various areas: code[1], translation[2], UX[3], testing and bug triaging[4], documentation[5] or even outreach[6]! The main ways to get involved are listed onhttps://inkscape.org/contribute/ The preferred points of contact are: [1]https://lists.inkscape.org/postorius/lists/inkscape-devel.lists.inkscape.… + https://chat.inkscape.org/channel/team_devel (or libera.chat/#inkscape-devel) [2]https://chat.inkscape.org/channel/team_translation [3]https://chat.inkscape.org/channel/team_ux [4]https://chat.inkscape.org/channel/team_testing [5]https://chat.inkscape.org/channel/documentation [6]https://chat.inkscape.org/channel/team_vectors A warm thanks to everyone involved in making this release possible! -- The Inkscape team

2 1

Re: [Inkscape-user] Re: SVGs from Inkscape do not display correctly in Firefox or EoG
by Shlomi Fish 08 Oct '24

08 Oct '24

Hi Fernando, please reply to all / the mailing-list next time. On Mon, 07 Oct 2024 12:51:25 -0300 Fernando Lozano <fernando(a)lozano.eti.br> wrote: > All advice in this thread was misguided. Using WebP or PNG is nonsense, > I need and want vector graphics. SVG is the web standard for that and > the reason Inkscape exists. The fact that it failed with multiple > browsers and also with a standalone viewer (eog) was a clear indication > it is something with inkscape. > My advice to use WebP was given after someone else mentioned using JPEG instead of PNG. So it wasn't "nonsense" in its context. I should note that https://github.com/tdewolff/minify and similar can be used to try to minify SVGs and use them as smaller bandwidth SVGs. Despite that, I realised that the minified SVG for the logo of https://www.shlomifish.org/humour/Terminator/Liberation/ was prohibitedly large, and used webp instead, so there's that. > It was not a bug fixed many years ago, it was working fine on 1.1.1, > appeared on 1.3.2, and looks like fixed with 1.4 beta. > > Em 28/09/2024 02:59, Shlomi Fish escreveu: > > > Hi Steve / all, > > > > On Fri, 27 Sep 2024 18:49:06 -0400 > > Steve Litt <slitt(a)troubleshooters.com> wrote: > > > > Fernando Lozano said on Tue, 24 Sep 2024 16:28:56 -0300 > > > > I opened 2313610 - SVG files from Inkscape don't render in a web > > browser (nor eog) 4 [1] on Fedora bugs about this issue. It contains > > two test files, one the export from google slides, other after edits > > by Inkscape. > > For the most part, I've stopped rendering SVG inside browsers, for > > performance reasons. On anything but the simpler SVGs, the time it > > takes the browser to go through all the transitions on transitions on > > transitions takes seriously finite time. > > > > I convert to JPG, or if I need more quality PNG, and show the converted > > file in the web page. > > Note that there is also WebP and similar formats, which are smaller than > JPEG > and PNG, and look better and crispier than > JPEG: https://www.shlomifish.org/meta/FAQ/site_loads_quickly.xhtml . > > > SteveT > > > > Steve Litt > > > > http://444domains.com > > _______________________________________________ > > Inkscape Users mailing list -- inkscape-user(a)lists.inkscape.org > > To unsubscribe send an email to inkscape-user-leave(a)lists.inkscape.org -- Shlomi Fish https://www.shlomifish.org/ https://github.com/shlomif/shlomif-computer-settings/ - my dotfiles Chuck Norris helps the gods that help themselves. — https://www.shlomifish.org/humour/bits/facts/Chuck-Norris/ Please reply to list if it's a mailing list post - https://shlom.in/reply .

1 0

Meeting Oct 6th 2024
by Martin Owens 06 Oct '24

06 Oct '24

Dear Developers, This week's developer meeting was a quiet one; it was Rene, Martin, Tav and Marc. Event: https://inkscape.org/cals/event/1/ We talked about the release and making sure everything is lined up. Marc is happy about the translations system he's created. Rene has one final commit to update the windows build infra, nothing for macOS. For the future, Rene is not going to upgrade the macOS version but is going to keep the intel machine so it can be booted up during releases, We looked at a merge request outstanding which was all about tanslations. There have been a couple of crashes which have been fixed and merged in time for the 1.4.x We reviewed the locations for various projects in gitlab and if things are organised correctly. Martin has been working on the capypdf integration, between C and C++ APIs and upstream headers. The next meeting is Monday the 14th October. Best Regards, Martin Owens

1 0

Inkscape Developer Survey 2024: Results
by Martin Owens 02 Oct '24

02 Oct '24

Dear devs, Big thanks to everyone who filled out the survey. I'm attaching the PDF of the results here so we can have a saved record of it. There's some really interesting comments and results. TLDR; 1. We need more windows devs 2. Build instructions are too unreliable 3. People aren't finding mentors 4. Merge requests aren't being reviewed quickly enough What prompted this survey was a view that people were bouncing off contributing this year and I wanted to know for sure what was going on. I think we certainly have build issues, but it's not the only issues new contributors are facing. Best Regards, Martin Owens

1 0

Layer issue
by Alexander Roalter 30 Sep '24

30 Sep '24

I’m not sure if this is the right place to ask, but I have the following issue and I’m not sure if it is supposed to work that way: I have a document with nested layers, let’s say + Layer A | +- Layer B | +- Layer C + Layer D +- Layer E For editing purposes, only layer A and B are visible, C, D and E are hidden. If I now use the command line interface of Inkscape to export the image in various configurations, I do the following: select-all:layers; selection-hide; select-clear select-by-id:D selection-unhide select-by-id:E selection-unhide and then export as png... Through this I want to initially hide *ALL* layers and only turn on the layers I want. But apparently, select-all:layers only selects the topmost layers A and D, but does not change the settings for B, C and E. I know that nested layers were only introduced later, could it be that select-all:layers was never updated to reflect this? Or would a new option for select all (e.g. select-all:nested-layers, or select-all:layers:depth=... ) be a sensible option? My main point is: I want to be able to switch on individual layers (because I know their ID), but I want to be able to switch off *ALL* layers before doing so, without knowing all their IDs. And I don't want to store the original SVG with all layers switched off, because in editing, I usually have some of the layers switched on (latest/last configuration I’m currently working on). -- cheers, Alex

2 1

Developer Meeting 28/09/2024
by Jonathan Neuhauser 28 Sep '24

28 Sep '24

Dear all, here are the notes from today's meeting. Dev meeting Sep 28 2024 Present: Tav, Mc, Jonathan, Martin 1.4-rc was uploaded to the website. Ravi is supposed to restart his GSoC in the upcoming week. Tav hast been working on the File dialogs. Opening: saving is working on his PC. Preview is handled by the file browser instead of ourselves. Saving is difficult, because it relies on the extension of the target file name to chose the format. There is no option to add custom fields. Tav proposes to let the export dialog decide the format to save to, and the file chooser there only decide about the filename. The settings button there can be used to set all options specific to a file format (e.g. SVG: save as plain SVG, clean up css, and so on). In general, the Import / Export system is way over-engineered. At the same time, a rework of import/export on the command line is in order. PBS's MR does the "minimum in order to get it to work", but doesn't address the proposed architectural / UX changes, so it goes into a different direction. Jonathan has worked on the Extensions system. The final target is to completely separate out python dependencies - nothing is installed by default, and extensions authors needs so specify their dependencies same as in any ordinary Python package. This makes extensions more backwards-compatible with older Inkscape versions, and allow authors to request any dependency they want. For now, the first step was splitting out inkex into a new repository (svgpie) and setting up a new pipeline and build system there. Martin is compiling Inkscape master on the new Pop!OS, seems to work. Marc has worked on the translations system, trying to simplify the workflow for translators. Some discussion related to pre-release checklists. Need to unify them - there is one written by Nathan, one written by Vectors, and one on the Wiki. After the end of the meeting, Martin and Marc worked on this Martin has received a few more responses on the Developer Survey (24 in total). Almost everyone identified as a programmer. Half of them were active in 2024, almost all of them work on Debian or Fedora/Arch. Build instructions are found, but they only work for 1/3. The vast majority of contributors are motivated by public service and personal learning. Issues raised: - developer documentation is all over the place - Python extensions need more how-to's - Windows should use the native toolchain (msvc) - Merge request take too long to approve / merge. - Code base is well-organized, but is a lot to understand. Detailed results follow on the mailing list. Martin proposes to move all developer documentation from website & wiki into the repository, to get more contributions to it and make it more organized. The website still needs to provide the required information to get started with contributing, e.g. how to check out the repository and linking to the compile instructions (then a md file in the repo). There is general agreement with this idea. We discussed (lack of) Windows developers. Consensus is we need to invest into the infrastructure - building using Windows-native tools, giving Windows dev the experience they are used to, and updating the documentation. Maybe conduct developer experience interviews? This would be target developer experience, not CI. Martin wants to talk to René first. Marc will update the install_dependencies script to not break if libspelling is not found. Best regards Jonathan

1 0

Weird PDF export issue (page size)
by Alexander Roalter 26 Sep '24

26 Sep '24

Hi, lately, I came upon this weird beavior when exporting to PDF: I have to base documents of size A4, the only difference is that the 2nd document has a page definition. If I open the 1st document (empty.svg, without the page definition), and export it as PDF, I get a PDF of size A4. Uncmpressing the PDF with pdftk shows a mediabox of size [0 0 595.275591 841.889764] (divide 595.275591 by 72 and multiply by 25.4, we get 210mm, as expected) If I now open the 2nd document (page.svg, with the page definition), and export it with exactly the same settings, I get a PDF which is slightly larger. In the Acrobat reader, it shows up as 210.3×297.0 mm, and looking at the uncompressed PDF the mediabox now has a size of [0 0 596 842], i.e. rounded up to the next integer. (596 / 72 * 2.54 = 210.25555mm) The PDF export options about rounding do not have any effect. This is with Inkscape 1.3.2, I checked back with yesterday’s devel snapshot: now the empty.svg is also exported oversized (rounded up), the mediabox is now always rounded up to the next integer. -- cheers, Alex

2 1

Developer meeting 20th Sep 2024
by Martin Owens 20 Sep '24

20 Sep '24

Dear inkscape developers, Our meeting this week is as follows. Event: https://inkscape.org/cals/event/1/ Attending: Martin, Marc, René, Jonathan Next date: September 28th Martin wanted to try populating a "Roadmap" which documents in the meeting what the developer team as a whole is doing. This is an effort that KDE uses to encourage contributors and gives them a way to know what's important to the whole project, even if people can work on anything they like to. The way this would work is to have a graphic in the meeting with he roadmap and some space to draw. Jonathan thinks this kind of thing can go on our website too, with the idea that we can frame it as a direction of travel for the whole project and what we'd like to be able to do in the future. Release for 1.4 release candidate. Marc, Martin and Rene talked about the issues still outstanding and what kind of risk we would be taking. Everyone present was happy enough with the quality of the beta3 to continue with the rc schedule: Wednesday September 25th for the RC, this is the last day for any extensions patches. October 7th is the last day for translations, and October 9th is the scheduled date for release. Rene and Marc talked about a window packaging bug which adds windows CRLF end lines to all text files in the repository, this should be fixed so the release no longer shows up as a custom version. Martin wanted to embody the user's needs by saying that having a custom string in the version shouldn't block or delay the release. Marc has a patch for 1.4.x which solves the problem with gitattributes, although this doesn't cover all future cases so René we continue researching the problem. Marc has made a new process for submitting translations and it's currently in testing. And this is how it works: For each Release, we create a single merge request in gitlab targeting that branch. For example 1.4.x. This merge request is the URL we send to translators, who can then submit their translations to the merge request by creating a new comment with the po file attached. Marc has made a system which consumes the comments, adds them as a new commit to the merge request with a credit to the author and then submits a reply comment with the total statistics so users can see if they have submitted correctly. When ready, the translations will be merged into the branch. This can be done multiple times, so we can progressively add translations for betas and release candidates as we move alone the process. The 1.4.x and master branches will be tested and the translation team will be brought in to make sure everything is set up and working correctly and the new system works as a contributor experience. Marc will ask Maren to compile a message for the translations team at the weekend when this live test will be ready to deploy. Jonathan Sent an email to the SFC on the hiring team for the Adobe Illustrator file format and is waiting to hear back. Marc and Jonathan talk about Hactoberfest, it's a way to get first time contributors into open source development; if they contribute a certain number of commits then they get a t-shirt. Except this year, there's no more t-shirts. They have decent ways of dealing with spam so we can add the tag. Marc already added the tag and we part of the program now. spam and accepted tags allow us to tag things positively and negatively. All contributions are welcome, not just code. Because they've ran out of t-shirts we should fund our own. We need to order some t-shits so that we can have them for this event, but also for other things. Martin will make some generic t-shirts and ask for reimbursement if the project decides to fund them, he says that he can use them for his own supporters and projects if not so there's no risk either way. Martin talked about the color stuff and including capypdf into inkscape directly with the C++, Marc recommended including the library as a submodule and gave instructions for how to do this using mason. The gtkmm4 build is an instructive example. Martin explored the developer survey results so far; 21 people responded, the survey will be kept open another week for any stranglers to add their thoughts to it. We'll document the final results after that. Thanks to everyone who came to today's meeting.

1 0