I hope Cocoa will be around for some time and not totally being replaced by Swift in the near future.
Cocoa is the framework, Objective-C and Swift are the languages that you use. iOS is still basically Cocoa (CocoaTouch; i.e., with the touch APIs). Cocoa is derived from NeXTstep, so all its API, like NSImage, NSPopUpButton still have an "NS" (NeXTstep) prefix, even when you write code for iOS.
I still use Objective-C. I view Swift like I view Java. Easy to write, not easy to understand what the original writer meant. Since I can express myself fully well in Objective-C, I see no point to even play with Swift. I had a lifetime ago written a C compiler for the DECsystem-20 (a 36 bit signed plus magnitude computer with 7 bit characters), so I am not that averse to different languages, but there is a time and a place for them.
http://www.fortran-2000.com/ArnaudRecipes/CompMuseum.html
Search for "kcc". (When you are old, you see yourself mentioned in web pages that have "history" and "museum" in them :-) :-).
So far, I have a Cocoa wrapper for INDIGO that perfectly operates ZWO's EAF and EFW (and by inference, anyone else's focuser and filter wheels -- I have to order a QHY one to fully test). It was a simple matter to control the ZWO EAF for example so that while you hold the mouse down, the focuser keeps moving (instead of in steps), by using the various NSButton options.
The plan is to make it so that camera images are captured in NSBitMapImageRep, so they can be trivially instered in an NSImage and displayed in an NSImageView.
May i ask if you could provide a link to the documentation RainbowAstro provides?
Here is an example of the RainbowAstro comm protocol document:
I get my copies from B. J. Jeong (he is one of the R&D managers with feet in both RainbowAstro and RainbowRobotics). Why don't you just send him an email and ask for the latest Mount Protocol document. This is from my last contact with him in 2020:
They make it available to anyone who ask, as far as I know.
You can also contact Mr. Jeong as "xuranus" on Cloudy Nights.
You will find the documentation to be refreshing straightforward and simple, not the obfuscated stuff from Meade, iOptron and SynScan. Those three are so messed up that they keep revising them, and keep making matters worse and worse -- you can see why ZWO can't keep track of the dozens of version of SynScan.
Chen
