Jeff Lindsay
Jeff Lindsay
- Because [hsiafan/cocoa](https://github.com/hsiafan/cocoa) was already doing it - Because the package name already prefixes, keeping them would be redundant - Because it simplifies any other prefixing we have to do...
It is possible that generation would make a SetDelegate for ComboBox and skips it because it already exists in TextField, so that would be a generation bug. And your workaround...
I mentioned in Discord maybe we should use FFI, but we could instead model functions after that example where we would generate functions that call cgo functions defined in Objective-C...
It would be helpful if somebody could look at the functions in that coregraphics code (display and window) with the docs for each function to start putting together some rules...
Assuming we can get to a point where all the bindings are generated, I was thinking we could just have separate packages.
Yep, that sounds reasonable.
Just to document how I was planning to do this since I won't have time for it in the 0.5.0-preview, and is maybe not worth doing until 0.6.0: Now that...
The 10.x versions were more equivalent to todays major versions, they were on it for 20 years. 10.x is also no longer maintained. Otherwise, the latest minor version will be...
is this a request for a framework?
We don't generate bindings for functions yet. I can put the System Configuration framework on my list. Tell me more about your use case?