objc-lisp-bridge VS ffigen5

Awesome! I've recently been going down the rabbit hole of working with Cocoa in SBCL. I've seen your work as well as https://github.com/fiddlerwoaroof/objc-lisp-bridge.

Interestingly, all the AppleScript functionality is built on an objective-c api called ScriptingBridge and it’s relatively easy to use a real programming language for the same sorts of things. JavaScript is natively supported by Script Editor, but there’s bindings for Ruby and Python too. I’ve wrapped it up in Common Lisp for my own use: https://github.com/fiddlerwoaroof/objc-lisp-bridge/blob/mast...

This tool doesn’t always work because plists can contain arbitrary Objective-C objects. However, there’s a relatively nice objective-c API that can be used to decode them losslessly that I used to extract data from Safari’s reading list l:

https://github.com/fiddlerwoaroof/objc-lisp-bridge/blob/mast...

I've done some work trying to modernize CCL's interface to Cocoa and other MacOS APIs, but had put that effort on hold waiting for the Arm64 CCL port. But it seems that the M1 port of CCL is now in doubt. My impression is that there's almost no one left who understands the implementation well enough to bootstrap it for a new architecture.

The only one of these problems I have some kind of solution for is that of building newer interfaces: over the last couple of years I've been tinkering off-and-on to extend the experimental command line tool that generates CCL's FFI interfaces so that it can read recent macOS framework headers. The code is not pretty but it works well enough to build working interfaces to newer frameworks like SceneKit. I've managed to use the resulting interfaces to write a few neat demos using CCL, such as an interactive cel-shaded version of the Utah teapot. But I don't believe the demos are portable: although I haven't checked, I suspect they will run on macOS 10.14 with CCL 1.12 only.