https://bugs.kde.org/show_bug.cgi?id=369239
--- Comment #3 from Thomas Posch <bugs.kde....@online.posch.name> ---
They are not. key{name,command} entries are stored/transmitted in an JSON
object, which is unordered by definition [1]. The ordering by key probably is
an implementation detail of the used JSON library. I.e. restoring commands from
JSON orders them by key.
Same ordering on both sides seems like a good idea. This would also allow for
custom ordering (without having to resort to some common prefix). A protocol
change would be required however. I see two approaches:
* Add a sortIndex field and sort on both sides. {key:{name,command,idx},...}
* Send by Array. [{key,name,command},...]
I prefer the second, since this is how you express ordered data in JSON and I
expect it to lead to a simpler implementation. What is your opinion?
[1] json.org
--
You are receiving this mail because:
You are watching all bug changes.
