3 ms·
On second thought, 100% parity might be a bit overoptimistic as some features such as auto-wrapped text and mesh gradients rely on APIs that must be implemented
by jarek-foksa 7y ago
On second thought, 100% parity might be a bit overoptimistic as some features such as auto-wrapped text and mesh gradients rely on APIs that must be implemented upstream by Chromium (and those features are not the top priority for Google). But 95% seems sensible to me.
There should be an outline shown when you hover a path with the "Edit" tool [1], though it's a bit sloppy and needs more optimization. Most path-related commands are exposed by the "Shape" panel. To convert a node between a smooth and an edge type you must double-click it. The ability to box-transform selected nodes and to move them with arrow keys is missing but should be added soon.
My main problem with text labels is that they take a lot of horizontal space. Text labels could be shown only when the panel is wide enough to fit them, or when user hovers the icon (like it's done in Autodesk Graphic).
[1] https://i.imgur.com/FgglFOw.gif https://i.imgur.com/FgglFOw.gif
- chrismorgan 7y agoYou don’t need upstream support for all features; you can often implement them in older SVG techniques with namespaced extra data to help with editing. That’s how text wrapping has worked in Inkscape historically, though 1.0 is introducing support for the actual defined SVG functionality. Not everything is possible this way; mesh gradients can’t be emulated in vectors, for example—though you could effectively implement a canvas-backed renderer for it to polyfill it; but a lot of functionality can be implemented without upstream support.