Some points I missed in the description:
1) A separate in-GIMP editor to modify strokes after the fact would be awesome!!
Though it could be an independent app as well. 

2) InkML is XML so you could probably have GIMP Specific garnish in there too that can be ignored by other apps! Though at the moment I can't think where it would be useful.

For reference: https://www.w3.org/TR/InkML/


As GIMP walk towards non-destructive editing in GIMP, InkML may indeed be a way to represent brush strokes so that they can be replayed with different settigns by the brush engine.

Maybe writing the current paint-core in a way that it would serialize painting parameters and have all the current custom rendering made as a GEGL node could be a path forward to get to non-destructive GIMP.

This serialization could use InkML or another protocol that would convey the same kind of information. And InkML could be used as data format to be exported from/imported to into this serialization.


Better yet - and maybe clear enough: maybe create a new paint tool that would just gather all stroke events, serialize them (InkML or otherwise), and feed then into a GEGL Node for painting - a "GEGL Painting Tool" could be an incremental way forward. InkML export/import would be incidental as above.

Regardless of these considerations, whenever non-destructive editing is worked into GIMP the ability to export/import InkML should be considered.

-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gimp/issues/1412.