Hello there,
I wrote my own code to synchronize my Kobo with a self-hosted NextCloud instance. I am aware that there exists some solution that does this already but I was curious to develop on the Kobo, and it was a fun project.
Now the code fully works (tested via netcat in the Kobo itself) and I'm happy with it. However, one last thing remain: how to start the executable from the Kobo, and not from a netcat terminal
I have spent some time reading this forum, and I've seen a couple of solutions which all look great (and creative!) but I can't really implement then:
-
Kobo Cloud /
Wallabako udev rules. It looked easy to implement, but my opinion is that it's a bit unreliable and also I don't really trigger it myself. I need to connect/disconnect from the WiFi or reboot.
I have tried to watch the bus for other kind of events (e.g. on press, on access to a specific settings section, etc) but to no avail.
- fmon / Kute File Monitor: I was really impressed by how creative this is. However I'd like my program to be standalone, and not to depend on another one's code, and I don't think re-implementing this myself would be wise.
- Use NickelDbus / NickelMenu. Same cons as fmon / KFM.
- Go hardcore and use
NickelHook to reimplement a NickelMenu like behavior. This looks to be too much effort for what started with a sync script, though I admire the effort and reading the code was really interesting!
I feel like it can't be
that hard to start a simple binary from the user's point of view?
If you have any suggestions or see things I've missed I'd be more than happy to hear!!
Thanks
AK