DBus Monitor to pass events to input modules: First cut

[zachfeldman]

This is a working implementation of the DBus monitor applied to Input Modules!

I've folded it directly into this project instead of in a separate repo.

Try it out with RUST_LOG=debug cargo run --target x86_64-unknown-linux-gnu -p framework-inputmodule-dbus-monitor, to see debug output too, then try making a test calendar event with notification. Assuming your system uses the same DBus monitoring channel as mine, your LED Matrix module should blink when a notification comes in for a calendar event.

Some things I am working on/trying to make better:

• I know this is only one level better than calling the binary you've outputted, but I think passing Clap CLI arguments is a pretty good interface, I'm not sure if it's worth going to a level lower in the existing modules or not when you've implemented a pretty great interface there.
• I want to make this much more generic as @kiram9 and I have discussed, where a user can create a config file in their home directory, subscribe to specific events, and then have certain commands run in response to them! But wanted a working example first. This is done, you can now have this respond to any DBus message and run any command!
  • I think for this reason the CLI interface is good because it's pretty understandable to users who might configure this through a file.
• I can't seem to figure out how to make my run_inputmodule_command which calls the serial_commands function go on to the next command...it just stays on the first one. Any ideas @JohnAZoidberg ? Sorry if this is super obvious and I'm missing something! I added a new command that doesn't loop to address this!

[zachfeldman]

Github made me leave this comment for some reason...

[zachfeldman]

@JohnAZoidberg this is where I can't seem to get to the second command, it just stays on the first one.

[JohnAZoidberg]

This blinking command is implemented in software and will loop until you terminate the process.
The function call here will never exit. That's why it doesn't go to the next one.

If you reverse the order, it'll probably work fine.

[zachfeldman]

Thanks @JohnAZoidberg ! Maybe I'll implement my own one that blinks n times, than exits, that'd be fun. Appreciate the tip.

[zachfeldman]

Phew I know it's been a while since I was in this repo but I finally had some time on this 4 day weekend!

I added a new blink_n_times function and am using it here now, so it's not blocking anymore.

[zachfeldman]

@JohnAZoidberg @kiram9 FYI, I finished up a pretty decent implementation of this that let's you configure which channel you want to monitor and what commands to run through a configuration file! Eventually you could have an n of more than 1 here, but this is a decent PoC.

It is based on my packaging-process-and-systemd-service branch which hasn't been merged yet, my intention is to eventually shove this into systemd and run all of the time.

I think I'm going to pause here for now though until I receive the newer hardware so I can test it with that, but if you'd like to merge it sooner for any reason let me know, or feel free to try it yourself :).