Mac OS X: Swift migration

Nov 11, 2014 at 8:18 PM
The UI classes used by the plug-ins on Mac OS X have some hackery to make them behave better and have the same visible name. Unfortunately, this does cause some issues when editing the Interface Builder files.

I've been doing some testing of Swift code here, and found that I could remove the need for a separate library for the sound plug-in. However, if those classes were migrated to Swift, the minimum OS X version would be moved to 10.9 (it currently is 10.8). Also, the fork I linked uses a git submodule for my own Swift additions, although it only uses two functions from the framework.