[PATCH v2 libinput 0/4] libinput record/replay as evemu replacement

Peter Hutterer peter.hutterer at who-t.net
Thu Feb 22 05:55:26 UTC 2018

As said in v1:

    I'm, planning to replace evemu. Its API is difficult to extend
    because it ended up as a library when really it should've only ever been a
    tool. Changing it requires breaking the API anyway and at that point we
    might as well add a new tool. shipped with libinput, because that way it's
    all nicely available in the same repo, etc.
    The tool spits out JSON instead of some custom format. Not quite as nice to
    read but easier to edit (try adding/removing an extra bit on an evemu
    file...) and it has more standardised parsing tools available.

Changes to v1:
- recording multiple devices now records into the same file, makes attaching
  and keeping logs a lot easier
- added doc and a basic verification tool

I'm still not happy with the output format. The data is supposed to be
human-readable as well as machine-readable and JSON sucks at the former due
to its lack of comments [1]. So I have to shove everything into a 'desc' tag
but that forces more nesting than necessary. Any suggestions on a saner
format with wide-spread support (C and python are the minimum) would be


[1] yes, I know JSON comments can be stripped (and json-glib ignores them
for libinput-replay). But the default python parser doesn't, and neither
does the vim syntax highlighting (and I"m looking at theese files *a lot*).
Same with anything else that tries to be RFC compatible.

More information about the wayland-devel mailing list