September 2025 - Inkscape Devel

Inkscape Developer Meeting, Sept 15th 2025
by Martin Owens 15 Sep '25

15 Sep '25

Hey everyone, Event: https://inkscape.org/cals/event/1/ Attending: Mikekov, Tav, Martin Mikekov has been working on some beautifcation projects, various things like the roller, gradient editor etc. We collectively talked about the failures at the SFC regarding reimbursements and people who are still waiting on reimbursement for items months and months ago. Tav would like to get into fixing the LPE dialog and converting polylines and lines to paths. Martin is working on filter mechanics involving a new cairo surface image access class with unit testing. We reviewed some merge requests. Short meeting this week, Thanks everyone.

1 0

Forbidden attributes in per-tool and last-used styles
by Henry Wong 15 Sep '25

15 Sep '25

Hello Inkscape devs, I'm looking through the code that sets/reads desktop and tool styles (sp_desktop_set_style, sp_desktop_get_style, etc.), and have some questions on some of the attribute filtering that happens. As far as I can tell, there are two kinds of styles (except the 3dbox oddity): * The "last used style": /desktop/style * A per-tool style: /tool/<tool_path>/style For these styles, certain CSS properties are forbidden and are filtered out (e.g,. "shape-inside", "filter", "stop-opacity"). Filtering happens both when reading from the style and writing to the style. For the filters when reading (in sp_desktop_apply_style_tool <https://gitlab.com/inkscape/inkscape/-/blob/master/src/desktop-style.cpp?re…>), the list of forbidden attributes are different for the global style and per-tool style. (More attributes are forbidden for the global style than the per-tool style). There is a different list of filters when writing the styles (sp_css_attr_unset_blacklist <https://gitlab.com/inkscape/inkscape/-/blob/master/src/style.cpp?ref_type=h…>, sp_css_attr_unset_uris <https://gitlab.com/inkscape/inkscape/-/blob/master/src/style.cpp?ref_type=h…>). The rules differ between the global and per-tool style, AND the rules differ from the ones applied when reading the styles. (More attributes are forbidden for the per-tool style than the global style?) Is there a reason the rules ended up this complicated? (Especially the part where the attributes that are writable to the style differ from the set of attributes allowed to be read back.) I'm wondering whether they can be simplified to something like: * Some set of attributes are forbidden from all default styles. Apply the same filter for both reading and writing. Or * Some set of attributes are forbidden for all default styles, and a superset is forbidden for the global last-used style. But the same filters are used for both reading and writing.

2 1

Inkscape Meeting, Sept 7th 2025
by Martin Owens 07 Sep '25

07 Sep '25

Dear Devs, Another week and another great developer meeting: Event: https://inkscape.org/cals/event/1/ Attending: Tav, Martin, PBS, ftOmara, MikeKov, Rafal, Ishaan Next Event: https://inkscape.org/cals/event/64/ PBS asks Martin abou the page manager, we talked about manager objects, selected pages, and the intention of the manager and it's relationship to sp-page objects. The manager is designed to encapsulate the state of the selected page so most calls shouldn't need to know the selected page directly. PBS has been working on the GSoC project to recolor artwork project. There is a live preview mode which needs to be sorted out. the conflict between the SPObject, xml tree and the display tree. A big discussion erupts between many developers have input into how the functionality could be done. We talked about the way the xml tree and sp object tree works together. This created a debate about about abstractions and various other internal core elements for Inkscape. The general consenus is that we'd like the preview functionality split out into it's own merge request. Martin will ask Adam about the design implication of having the preview change in multiple places or just in one place at a time. Mikekov has been doing some UI beautifucation projects. And we talked about the missing event problems in macOS that might be something we need to get that reported upstream. Martin has continued to work on the rendering engine work. A long term project to improve the capabilities of the rendering engine color support. Ishaan reports that the all four people are going to India FOSS event. There's concerns about how long the process has taken with the SFC as friction continues between us voting to pay for events or materials and people getting reimbursed or getting travel booked in time. Best Regards, Martin Owens

1 0