I was thinking this morning that an eventual option alongside the cli might be an .app as well -- it seems, at first glance, like the biggest outstanding difference between something like Hammerspoon and this is that obb still has no clear capability for running outside of an ad-hoc manner. If there were a canonical obb.app that could startup and listen for events, it could collect various ad-hoc additional scripts and respond to those events accordingly.
What I still haven't thought through in any detail is how that would work. Could it be as simple as, ultimately, a "fancy" .cljs script that itself uses obb to create a process that can load and unload scripts and perhaps even spit out a really simple GUI? If so, then I suppose the hardest part would be thinking through the eventual API for what can be listened to, and how scripts can be loaded and unloaded.
I was thinking this morning that an eventual option alongside the cli might be an
.appas well -- it seems, at first glance, like the biggest outstanding difference between something like Hammerspoon and this is thatobbstill has no clear capability for running outside of an ad-hoc manner. If there were a canonicalobb.appthat could startup and listen for events, it could collect various ad-hoc additional scripts and respond to those events accordingly.What I still haven't thought through in any detail is how that would work. Could it be as simple as, ultimately, a "fancy" .cljs script that itself uses obb to create a process that can load and unload scripts and perhaps even spit out a really simple GUI? If so, then I suppose the hardest part would be thinking through the eventual API for what can be listened to, and how scripts can be loaded and unloaded.