MacOS platform support?

[OlshaMB]

currently macos backend only creates window object and doesn't show the window(because macos requires NSApplication run), also it doesn't support any widgets. And the cpu usage at 99 %. So it literally impossible to go beyond a running app without the window

I am willing to contribute.

[OlshaMB]

Also is there any reason why capy ui is not using libraries for obj-c(zig-objc, mach-objc)? Can I use them to implement better support for macos?

[zenith391]

I've now made the necessary groundwork for macOS to be supported, that is, now the Objective-C runtime can be used (I chose to use zig-objc), the event loop works, and the window is shown. All that's left to do is implementing the widgets. I'll do it later sometime.

[OlshaMB]

@zenith391 How eventUserData fits into already existing backends, and how it should fit into new macOS one? I'm willing to contribute, but I'm a bit stuck with idea of eventUserData.

[geon]

I've been hacking on the macos backend, implementing bits and pieces. https://github.com/capy-ui/capy/pulls/geon

Are you @zenith391 interested in contributions?