This adds a new menu-item to the "File" menu: "Save patch as SVG..."

It allows you to save the current Pd patch as an SVG graphics.

... which is exactly what I need - but for Purr Data. Since patch2svg is a TCL script for vanilla PD, and (https://agraef.github.io/purr-data-intro/Purr-Data-Intro.html mentions:

Purr Data is Pd-l2ork with the Tcl/Tk GUI part ripped out and replaced with modern web technology. To these ends, it uses an open-source framework called nw.js a.k.a. “node-webkit”, which is essentially a stand-alone web browser engine (Chromium) combined with a JavaScript runtime (Node.js).

... it seems, I can't really use patch2svg for Purr Data.

Then again, Purr Data should already be drawing everything in SVG, it seems, - so it seems there should be a way for it to save the patch canvas as SVG natively; but I cannot see an obvious way to do it ...

I can print to PDF from Purr Data, and then convert that to SVG using inkscape - but in that case all texts become "curves"/"paths", and are not editable as texts ...

So, I was wondering - is there a way to export a patch in Purr Data as an SVG vector image (and preferably, with text information present)?

In the meantime, you should be able to choose "Help" -> "Open DevTools", click the Elements tab, then right-click the svg element and choose "Copy Outer HTML"

Then paste it into an editor and save it with ".svg" at the end.

In the meantime, you should be able to choose "Help" -> "Open DevTools",

Nice, Chome developer console -- was looking for that as soon as I read Chromium, but could not otherwise find it

Btw, it is called "Help" -> "Show DevTools" in my PurrData 2.15.2

Oops, I forgot about the CSS styling and fonts. Let me investigate.

Yup, just tried it myself, fonts on [cnv] canvas seem fine, but not on regular objects; also some extension objects, and also abstractions, are rendered fully black. Also connector lines are missing.

Thanks for looking into this!

1. Quick-and-dirty: I can go ahead set svg presentation attributes for object background and line stroke color to sane defaults. That way when you copy the outerhtml you'll get a readable patch in the default style (but no possibility to style the exported SVG according to the GUI presets). Those attys get overridden by CSS props so that should work with the current styling system.
2. I can insert the CSS stylesheet as CDATA in the svg. That adds about 10k to the file size, probably less if the SVG is optimized/minified. This way the current style can be applied, minus editmode grid/background image.
3. I can embed dejavu font in the SVG. That adds 337k to every exported SVG, but it's the only way to guarantee that the font is correctly chosen. It can probably be minified somehow but I'm not sure how to do that.

Probably #2 is the best way to start.

<style type="text/css"><![CDATA[
svg {
    font-family: "DejaVu Sans Mono";
}

.cord.signal {
    stroke-width: 2;
    stroke: #808095;
}

.cord.control {
    stroke-width: 1;
    stroke: #565;
}

.msg .border {
    stroke: #ccc;
    fill: #f8f8f6;
}

.obj .border {
    fill: #f6f8f8;
    stroke: #ccc;
}
]]></style>

You'll just have to fish through the rest of the css stylesheet for other styles, but you get the idea...