Hi all — I just filed https://github.com/babashka/obb/issues/5 but was thinking it might be less frictiony to not have all discussion via the issue. Does it seem right to you that the only way to listen for events and respond to them would be to have some kind of obbd that runs in the background?
Interesting idea. In obb eval and load-string should "just work"™️
so if jxa supports some kind of server thingie, we could use that to read from a socket or so and eval things
or we can just implement a full blown socket / nrepl server. #nbb already has this.
To put a pin in this line of reasoning — I need to read up more on nbb and jxa sounds like. I don’t have it fully thought through but it seems like in addition to the services thing discussed above, one possible distinguishing factor between the end result of the nbb approach and this is that in addition to having something that could be run as nbb script and be text-based, an obb output could be to create a .app folder with the obb / babashka binary copied inside, which then itself calls the script in question, eventually meaning that the ad-hoc scripting could be graphical on macOS and redistributable as mini .app files for users. The use case that comes to mind for me for this would be to more easily create small ‘script’-like things in CLJS that are easier for the non-tech-savvy to utilize — not unlike what Automator et al are supposed to do in the first place
oh right!
yeah, obb only needs a 1MB JS file btw, no babashka. So if you can make a .app folder that when executed launches the JS file + the script, then you're golden
https://apple.stackexchange.com/questions/224394/how-to-make-a-mac-os-x-app-with-a-shell-script
Oh, of course, osascript is the binary! Okay — I need to do a little more thinking about this. I don’t want to go too far down a rabbit hole and realize that I’m jankily trying to recreate javafx or something
I justed opened the obb discussions board: https://github.com/babashka/obb/discussions Issues that are more like questions and ideas can go there rather than Github issues, as that format offers better options for discussions.
Lovely — thanks!
I have a feeling we’re going to want a wiki for usage examples pretty soon.
We also have an examples dir, but wiki is also cool. You can just enable it in settings
What also works is doc folder with various docs
Totally. My main concern is empowering non-contributors to add their own. Not sure what the best way to do that is.
wiki is always good