- Inkscape Devel - Inkscape Mailman

Problem- (P6-Refactoring) Remove dependence on object-set.h in files in src/livarot directory.
by Kaustubh Kongile 27 Mar '23

27 Mar '23

Hello, Thank you for considering me to present my suggestions for removing the dependence on object-set.h before submitting my proposal for gsoc 2023. Here are the steps we can follow to remove the dependence on object-set.h: Identify where object-set.h is being used in the code by looking for #include statements and code that directly uses classes or functions defined in the file. Determine the functionality being used from object-set.h to find suitable alternatives. Research and find alternative solutions or libraries that provide similar functionality. Modify the code to use the alternative solution or library, replacing any references to object-set.h and modifying code that uses its classes or functions. Once we have verified the changes, we can commit them and submit them for review. I hope this information is helpful. If you have any questions or concerns, please let me know.I am not sure about the amount of time required to resolve this issue, so I would appreciate your guidance and suggestions on the matter. Best regards, Kaustubh

1 0

Developer Meeting Notes, March 26th 2023
by doctormo＠gmail.com 27 Mar '23

27 Mar '23

Hi Everyone, This is our first online meeting since the hackfest. Last week's meeting was canceled, so don't worry, you haven't missed any previous notes. Event: https://inkscape.org/cals/event/1/ Present this week: Lazur, Martin, Jonathan, Tav, Thomas, Jabier, NPJ, Marc, Mikekov, Rafael Next Meeting: Monday, April 3rd # Release Plans The alpha release has been uncertain because of reports of deadly crashes on undo. The reports have been a little anecdotal though. The general consesnsus at the meeting is that we should release the alpha right away and then re-release a new alpha if this issue can be confirmed in the latest versions after several fixes. Users can be asked to be brave so long as they understand the risks. Martin created the 1.3 and 1.3-alpha0 release objects on the website and Marc is planning on pushing the alpha out in the next two days. The mushroom about screen was used as the graphic for the alpha. We have a few outstanding merge requests which we can merge immediately. The developer team spent some time looking at these merge requests for our activity at the end of the meeting to clear the backlog for the release. # Jabier Wants to merge some branches, some are minor fixes but need to have better and more descriptions to help reviewers understand what they do, we managed to merge two and attach reviewers to three others. Martin wanted to make sure the corners LPE upgrade is scheduled for after 1.3 since it's quite large. # Jonathan Some reverse engineering of the AI format and helping Nicco putting together the ai importer. Progress is going well, text is likely to be supportable. Asked tav about the mesh gradient and having a number of nodes on the edges of the patches. Gtk4 proposal is ready and waiting to be sent to the PLC. An email got lost and has been resent to Marc and Tav was asked to push the PLC election, nominating the proctor Pono to run the election. # Marc Has been busy and sick, with appologies. # Martin Recovering from travel. Made a video for the hackfest which has been well recieved. Bug accellerator program fixes are submitted and merge request management and pushing for the alpha release. Some website fixes for the about screen contest voting. # MikeKov Looking at a bug #4186 with the new preserve path functionality and trying to work around a fitting alogorythem. We could detect when it's not going to work well and then try a different method, or try to remove the constraints but with bad output. Bug has been assigned and tagged for 1.3. #NPJ Experimenting with Apple archetecture. #Rafael Worked on bugs as part of the accelerator program. Fixed four issues this week, one fix actually fixed two issues. Currently looking into a regression in patterns, where you can't see a marker using a pattern as a context-fill. Pair up with Martin to look into the problem. #Tav Spent a little time in the last week playing with Gtk4, try out the new Gtk List View, it wasn't performing quite as expected. It only generates widgets for things which are on the screen, but this makes the scrolling weird. Made a lsit of 10,000 items, it would scroll for a little bit but then it would jump around. # Thomas Doing some experiments for how to fix menus in macOS, contuing the work from the hackfest to see if there's an upstream patch that can be created. # Team Activity We looked at five merge requests with the Approve Please tag, and merged two, and assigned the rest to reviewers for further testing. Thanks to everyone for coming to the meeting, see you all next week!

3 2

Contribute / GSoC
by Mateus Krause 23 Mar '23

23 Mar '23

Hello people from dev mailing list, My name is Mateus Krause and for a long time I want to contribute with Inkscape. I've been using the program for a few years now and really appreciate the work put into the project. I just found out that Google Summer of Code is open and maybe this could be a good starting point for me to help. Currently, I study Computational Mathematics at Universidade Federal de Minas Gerais (UFMG) - Brazil, and I have some knowledge and practical experience in small-medium C++ projects, using Make or C-Make, external libraries, and I think Inkscape would be a good place for me to start contributing in a bigger project with code for the first time. I would really be grateful if someone can help me with my GSoC application. The suggested project ideas that catch my attention are: P9 - Path Library Improvements, I really liked this one because of my mathematics background, and it looks fun; P12 - Customizable Appearance of Canvas Controls, it's a part I interact very often and I really see how this can improve the experience, I also have a background in web dev, so dealing with CSS would not be an issue; P5 - UI-Free Inkscape, this looks interesting because of the challenge managing dependencies. I think I have the knowledge to complete any of this tasks, so at least for me it would be a great opportunity to be familiarized helping in a big community and learn with the experience. For now, I only have gone to the "getting started with Inkscape development" page and did the basics. As part of the application, I'm looking the bug tracker to see what can I complete. Either way, I want to contribute with this project, so any guidance would be awesome. Thanks in advance. -- Mateus Krause

3 2

Hackfest notes from Pono
by Daniel Pono Takamori 17 Mar '23

17 Mar '23

Hey everyone, Here are some notes I took after collecting some questions from people at the Hackfest. I'll dump them here and here's a link to the markdown file on Nextcloud: https://office.inkscape.org/nextcloud/index.php/s/62TS2K4obzat4Rd At the end of the week I asked the people here what they liked about the project, what could be improved, how was the Hackfest and what can SFC and I do to better support the project. After I presented these comments and some of my own thoughts about them, we opened the conversation up to discussion and the bits at the bottom are the resulting conversations. Thanks again for having me, and I'm looking forward to building out the in-person events so everyone can come or participate to the best of their abilities. -Pono ## Things to celebrate about Inkscape and it's community There's a good spirit of volunteering and people taking on tasks that are interesting to them. This goes both ways though and sometimes means there are tasks that get left behind for no one to pick up. Liberal code contribution culture which has enabled lots of innovation and creativity. Receptive to new ideas. People are empowered to express themselves, regardless of their position in the world. People focused project, doesn't require lots of technical expertise and has a low bar to picking up. Mature project with lots of good momentum. People love Inkscape! ## Improvements to be made to Inkscape and it's community Diversity of participants was something that came up a lot. Working to have better outreach to make sure all groups and teams are represented. How can we get younger users and contributors? Make it easier for people to contribute non-code (I'm not sure what the processes around documentation, how-tos, etc work). We need better onboarding docs so we don't have to explain "basics" over and over again. "Inkscape on Twitch" - related to other outreach efforts Spending money... we need to come up with a more formal budget to support all teams and I (pono) think that a budget will make it easier to get money to flow since when things are within an accepted budget, it's easier to get things moving. Listening and communicating with users - surveys, forums, Rocketchat, etc. We need more dialogue with users (technical and non). How are artists, scientists and makers using Inkscape? Formalizing subgroups - with fear of over administering, how do we codify the teams so that they can operate autonomously but be included in all decision making processes? **pono idea - seats for each subteam on the PLC and more communication between groups** How do we get Inkscape in schools? This is something SFC has been thinking about in general ## Hackfest ### Things that went well Relationship building is unmatched in person. This was a great opportunity to meet and chat and the travel being handled if needed, was great. Length was good, maybe a long weekend could get more people. In person communication makes it much easier to clear up miscommunications and intentions. The venue was great and everything was made easy to focus on work and relationships. ### Things to be improved Calling it a 'Hackfest' might've discouraged teams from participating and we *need* all teams to participate. 15-25 people would be a better group. More diversity among participants, *pono let's get some scholarships for new and minority contributors* Open space and loud conversations made it hard to focus, providing quiet spaces would help. More thought into how to include remote participants. Have one with users? Does it have to be this event? More regular cadence makes it easier to get people here. ## SFC - how can we do better and what have we done well being clear about our limits SFC is not just an anonymous thing to help with managing things, we need to establish a more close relationship rewarding volunteers financial help was great and improved attendance Pono/SFC is very helpful for networking between FOSS projects, like introducing the right people and thus increasing the chances of successful collaborations Be a sparring partner for discussing policy & fundamental issues, "outside" person that can help when an outsider is need. E.g. CoC issues within the PLC, election proctor Also to escalate things within SFC if progress is slow. SFC should monitor foundations for grant opportunities & forward them to potentially relevant member projects making sure contracts and money flow smoothly SFC done a good job with mediation and spending money ## Notes during discussion hackfest rebuilds energy 5-10 is good for hacking OutreachFest colocating an event? FOSDEM! https://libregraphicsmeeting.org/ conference in Northeast? develop PenPot relationship Jabier and Adam Belis what we need from Inkscape to use PenPot for UI Scribus? Blender? subteams marin - didn't like term leader, have an organizer, contact, representative can switch off! describe as not one person, but a team collectively divvies up responsibilities if you want to be a formal group, you need to meet a set of criteria jonathan and ted thinking about it community building things graphics for teams, hat or graphics mousepads :P vectors, developers, documentaion, testing, translation, UX https://inkscape.org/user/teams/ recognized groups have duties benefits: PLC can delegate technical decisions to dev team, outreach to vectors, etc formalize duties and expectations keep outside FSA probably partners program GNOME has a Sponsors section allows relationship management *ChromeOS* ?? maybe we can talk with Google? how to package for those chromebooks schools helps schools administer the program krita and blender are on steam maybe need someone android? google funding for gtk backend? putting out more video for exposure - Chris attractive to sponsors build up vectors to make more content budget for video how does krita do it? need to try more things what do people like from Inkscape? we don't really know Youtube channel? surveys! demographics working with TuxDigital presskit press list for SFC Plausible website is contributor friendly not marketing slick friendly branding is not a singular thing it's there to tell your story "the only vector software that is a community project" more concious of public image

1 0

Proposal for accelerating the GTK4 migration
by Jonathan Neuhauser 16 Mar '23

16 Mar '23

Dear Inkscape developers, the Hackfest in Bensberg has been very productive and one of the outputs is a proposal to accelerate the GTK4 migration, as discussed during the recent development database. For this, we propose to hire two contractors for a span of 4 months, one GTK expert and one Inkscape expert. (Recently, on the PLC mailing list, I mailed around a version of the proposal including only the GTK expert. Feedback there and further discussions here have allowed to combine both into one proposal again.) Please find the proposal attached, including the job postings for both. I'll try to incorporate feedback until Sunday, March 19, so a PLC vote can be held afterwards. Feel free to contact me via email or on RocketChat. Best regards, Jonathan (joneuhauser on RocketChat)

1 1

Draft for a refactoring and improvement of the test suite
by paolo fx 14 Mar '23

14 Mar '23

Hello inkscapers, I could contribute to the development of the code in my spare time if the following idea makes sense and is of value. While talking in the #irc dev channel and in the last developer meeting, it turned out that the test suite in testfiles directory is somewhat messy and a refactoring could be desirable for some reasons. Here's my proposal. First of all, tests should be grouped in coherent and standard categories. A standard classification is: end to end testing ---> integration testing ---> unit testing This classification, translated into a dir tree would be: ---------------------------------------------------------- testfiles |______end2end_tests | |_______gui_tests | |_______cli_tests | |______integration_tests | |______unit_tests | |______CMakeLists.txt | |______CTestCustom.cmake.in | |______README.md [SUBDIR] gui_tests: empty for now, just add a TODO/FILL-ME note inside it. [SUBDIR] cli_tests: *) rendering tests are made with CLI (as the CMakeLists.txt confirms), so they should be moved inside cli_tests. Therefore, move here svg files from "rendering_tests" and move rendering_tests/test.sh as cli_tests/rendering.sh *) leave here the current content of cli_tests *) add an "images" dir containing all the graphic files [SUBDIR] integration_tests: it will contain cpp or script files in the form: operation1_operation2_..operationN.cpp (or .sh, or .py etc). [SUBDIR] unit_tests: a software unit can be meant both as: 1) (see testfiles/src/curve-test.cpp) a self-referential "concept" 2) (see testfiles/src/uri-test.cpp) as a class, or even a single function, from the API. The important thing is to separate unit tests from integration tests, which are sequences of different tasks. From what I see, the "testfiles/src" dir currently contains unit tests (if cpp files perform integration tests, they should be moved to the testfiles/integration_tests dir) In addition, do move lpe images here (inside an "images" dir). Add a note on the README that lpe stuff is here (as it partially is, actually). [FILE] CMakeLists.txt [FILE] CTestCustom.cmake.in [FILE] README.md: note: only ONE readme will be used for describing this test suite. It will describe what the tests do and how to launch them separately. It will also contain a very short mention - one or two lines - of the model (e2e tests ---> integration tests ---> unit tests) used. -------------------------------------------------------------------------- There are two possible concrete values/advantages in this new struct: 1) The reordered code would be much more readable, especially in the perspective of finding and running on the fly a specific test for a specific need or in the perspective of adding new ones, or deleting obsolete ones. 2) Integration tests could significantly speed up bug fixing, other than giving a more robust validation procedure of the released software. Let me show an example. An integration test could consist in the same steps described in a submitted bug: open a file ---> modify a curve ---> apply a filter ---> export to png In the integration_tests dir, there could be, together with test files, one (or more than one) file called "integration_test_template.cpp", which is meant as an example, with basic operations done sequentially (open, modify, filter, export etc.). Then, if another example called "integration_test_custom.cpp" is created by the developer (but not added to the source tree and added to .gitignore), it would contain code modeled on the basis of "integration_test_template.cpp" and it would be automatically compiled because as a part of the CMakeLists directives. In this way, we have a ready-to-use environment for testing the API. So, when a nasty bug is described together with its steps, a "integration_test_custom.cpp" file can be created on the fly by using chunks of code taken from "integration_test_template.cpp" in order to replicate the steps. What do you think? And do you think that the integration_tests template would be really useful? In this last case, could you share an example (or more than one) of a bug that can be managed with "integration_test_custom.cpp" so as to have a useful case study? If the idea appears good and collects approval, I can start making a fork and a new branch for it on my local clone.

2 1

Developer Meeting March 10th 2023
by doctormo＠gmail.com 11 Mar '23

11 Mar '23

Hi Everyone, Another week, another developer meeting. Thank you to everyone who responded with enthusiasm for having these notes available. I'm going to see how long I can continue to write them for y'all. Present: Tav, PBS, Martin, Mikekov, Jabier, Paopre, Jonathan, René, Vaibhav # Hackfest The hackfest is in a few days! Most people will arrive early on Monday, two members are arriving late in the evening and will have to book a hotel for the night as there's pretty tight restrictions on arrival at the venue. René will be giving further details about meals and other details, check the wiki for full details. This goes for leaving the venue too. We will be expected to be entirely gone by Friday and 6pm. Several people will be making their way to the city to hang out, or book into their next hotels if they're leaving at a later date. We have a bunch of ideas of things to do during the hackfest. Several people will probably want to conference seperately or hack in their hotel rooms if there's too much activity in the conference room. # Release Alpha, is held up by a few merge requests, we're trying to unclog the delay. - Marc wasn't present, but we have some questions to ask about how the release process is going. - René has everything in thanks to Mikekov - Jabier has two merge requests, we reviewed them. A Drag and drop has been tested but should be defered as it's not high priority. - PBS has a few issues he wants to fix before the alpha is released, One is an async rendering issue with rectangles not being selectable immediately after creation. The other is a missing library on windows called 'libangle' detected by lb90. - Reverting the Undo changes is critical! We looked at a reported crash together in the meeting, but this seems unrelated to the reversion. - The opengl performance on default Gtk on X11 can go down to 1fps with serious issues. It's a problem in Gtk and upstream gives approval for simply forcing gtk to use the image backend renderer. Questions were asked about what was the right course of action. # Other Items - Martin has refactored the export dialog previews to not block on loading large files. Lots of improvements to the export dialog. - The font dialog has a small issue with folders in the font dialog being created, it's creating a system folder when it shouldn't be. - Nico has made good progress with the ai importer this week. He's working about 20 hours a week and progress is steady. - Paopre asked about his proposal to reorganise the test suites so each of the unit tests, integration tests, and others into more formal and defined directories. Advised to document the proposal and present it to the developer team so we can have time to look over it. # Group Activity This week we skipped doing the merge request review and instead did some code review. Walking through the changes involved in the export dialog changes. See https://gitlab.com/inkscape/inkscape/-/merge_requests/5148 for details. Thanks everyone for coming. The next scheduled meeting will be after the hackfest, but we'll likely have one at the end of the hackfest instead. Keep up to date with the calendar at https://inkscape.org/cals/event/1/https://inkscape.org/cals/event/1/ Best Regards, Martin Owens Inkscape Developer Team

2 1

Inkscape @ Chemintzer Linux Tage 2023
by the Adib 10 Mar '23

10 Mar '23

Hello All, I really enjoyed the experience from the last two years. This year is on-site again, all lectures will be streamed too. https://chemnitzer.linux-tage.de/2023/en/ Even there is no real Inkscape booth, I will be there. As part of the Leipzig Python User Group. https://chemnitzer.linux-tage.de/2023/en/programm/beitrag/206 So if you are there I would be glad to meet in real live. :-) Regards, Adib. --

2 1

First talk to mentors
by Clair Brown 09 Mar '23

09 Mar '23

What am I supposed to do to start to talk to the mentors if I'm interested in the GSOC project of inkscape? Thank you!

2 1

March 2nd Meeting notes
by Martin Owens 03 Mar '23

03 Mar '23

Developer meeting for March 2nd, Next meeting is March 10th https://inkscape.org/cals/event/1/ Big thanks to everyone who came to this week's developer meeting. Attending: Marc, Jonathan, Martin, NPJ, René, Mikekov, Nicco # Hackfest The hackfest is a week and a half away! Pono is coming to the hackfest, this will be good and it'll be great to see him in person. SFC will pay in advance for the hackfest using an international wire transfer. The money will need to be there by next week if we want this all to work out. But this is good news that there are no further discussions needed to sort this out. Reviews of the wiki as well as the developer introduction page are planned activities. Especially to help GSoC students with their common questions. Marc is planning on working on dithering at the hackfest, other developer have various activities planned for their time at the hackfest. There's no set developer meeting during the hackfest, but every day will be a meeting. Streaming options and interviews are also planned. # Releases and Release Planning Marc has been busy but is planning on releasing an Alpha version this weekend. He wants to check on the windows store release, but is confident that windows builds can be created. René has a specific set of fixes that need to make it into the release because all builds are broken for macOS at the moment. The alpha will wait for this merge request to be complete, and is expected to be complete later today. The openmp library update fixes the latest macOS specific crashes which was only found because someone opened the about screen. Marc needs help uploading things to the Ubuntu PPA regarding cpack. May need to reach out to Ubuntu maintainers to get the process working well. René will remove dithering support in the macOS release because it's not stable and is causing problems. He will also be making an ARM build of the macOS package using our own CI builder infrastructure which should mean we have these builds for alpha. Mikekov has a few merge requests that need attention and wanted clarification on what is acceptable to merge during freeze. At this point we wouldn't stop changes to strings, but we don't want large untestable changes, so most additions will be made on a case by cases basis, but the size of mikekov's changes should be ok. # Importer Project Nicco, Jonathan and Martin did an on-boarding session on Monday, and Jonathan has been working with Nicco all week to guide the creation of the new extension. There's work done on the environment and the testing framework to make sure the entire process is tested and that it fits in with how our existing extensions work. Nicco has been looking into the format specification and putting together the priority for what pieces should be worked on first. Basic shapes are expected to be working by the hackfest time frame. The type of python dialect/parsing programming which is not-object-orientated is interesting to Nicco. Waiting on getting a message out through the Vectors team. # Bug Accelerator Program Martin has published the first blog post detailing the work done for the program last month (Feb). This is the tail end of the month and Rafael will become available this month (March) Other developers are happy with the progress. Instructions have been made on how to encourage and prioritize bugs. Please use the Inkscape 1.3 tag, and increase the priority on issues which should be fixed first. # Gtk4 Upgrade Proposals Jonathan is going to bring the proposal to the hackfest so it can be worked on in person. Mikekov is concerned about the instability and lack of commit access that will be available during the upgrade. Reassurances have been made that the upgrade would not take years to complete and this is one of the reasons we want to commit paid resources to pushing it through at a quicker pace, so we don't block valuable contributions that would otherwise go to waste while Gtk4 upgrades were proceeding. Martin recommends doing a risk assessment at the point where all Gtk3 compatible actions have been completed and the fork to a gtk4 branch is needed. Everyone agrees that Inkscape's main branch should never be in a state where it doesn't compile. Although we might want to freeze work on the UI folder during the upgrade process. # Vectors There's some discussion that the vectors team doesn't have the resources it needs to respond to requests from the developer team and we wonder how we can help. Maybe we need to do more recruitment, or do join activities to raise excitement. It's hard to know what might help. René proposed that the developer team may want to request the production of a release video if there are no objects from the vectors team. Although Martin was more cautious and wanted to instead see if the vectors team could be encouraged or resourced rather than circumvented. This will need to be an ongoing conversation with the members of the vectors team. # Other work - Martin has been working on speeding up the rendering pipeline, specifically the way bounding boxes are calculated over and over again. - Jonathan did a pdfimport frenzy to find issues and ended up opening 11 new bug reports. This might indicate we need more testers for 1.3 to improve our coverage. - Marc wants the old-files text fix to be tested more rigorously before it's accepted. - René says the performance of test running is getting worse and we're not sure why. - NPJ reports that macOS is very fast and wants to congratulate us all on a job well done. # Merge request review We looked at four merge requests. One was given back to the developer (mikekov) and three others were moving code around by new contributors who never go back with comments and so were closed. Thanks everyone! See you all next week.

2 1