Suggestion: Remove AppKit code (macOS SDK)

[louwers]

The macOS AppKit based SDK has been unmaintained since the fork. It is full of deprecated constructs. It is written in Objective-C which I think a lot of macOS developers are either trying to get away from, or have abandoned completely.

I am not sure if anyone is actually using this code at this point. I have nothing against keeping dead code around until someone comes along to revive it, but in this case I think the chances are slim. So I suggest we get rid of the AppKit related code.

We would keep macOS as a platform for development, as well as a target for MapLibre Native Core. We would just get rid of the SDK for macOS specifically.

[ntadej]

Do we have any minimal examples how to render the map on a Metal texture inside an app? I think this is the biggest piece that is needed. Then anyone can wrap the Core on their own.

[louwers]

Sort of? https://github.com/maplibre/maplibre-native/blob/main/platform/macos/src/MLNMapView%2BMetal.mm

[louwers]

Well not a Metal texture, we use a MTKView.

[sargunv]

I was using exactly this example to help me prototype Compose desktop support with MLN, but I haven't done a whole lot with it yet

As long as there's some example for rendering to a Metal view on macOS, I'm fine with dropping the AppKit SDK

[ianthetechie]

Yeah, I'm in agreement here too. In fact, I'd love to add support to the SwiftUI DSL if macOS support is finally back. Last I remember, there wasn't a macOS target in the SPM build, but maybe that's changed now.

[ethanc8]

What are the requirements for the current macOS support other than AppKit? I'm wondering if it can be ported to GNUstep.

[louwers]

That is an interesting idea. It may be possible, but it's I think it is way too niche to be maintained as part of this repo.