-
Notifications
You must be signed in to change notification settings - Fork 64
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Path to support labels, text, images, etc in iOS #7
Comments
Unfortunately the iOS demo is (for the moment) barebones, yeah - it was mostly done first to make sure I could even support the UIScene+Delegate APIs that modern iOS needs, which was tricky to figure out how to do. The good news is that from here on out adapting things shouldn't be too bad. I'm guessing the feature flags you hit were the If you want to jump in, the
Images are also theoretically decent to start with, but there's a custom draw handler I added and the API for that is slightly different across OS's so I might want to revisit it. Not sure. I think an |
Oh, and:
Ish, yeah. I've been aiming for somewhat of a "common" API between the two OS's for two reasons:
I'd say that in general I try to err towards the iOS-style methods, since I think people are more familiar with those. tl;dr yeah, a lot of it is my personal experience with ios/macos/tvos experience, but I'm pretty open to whatever. If it's helpful I suppose I could put together a channel somewhere for more discussion on this? |
I threw together a basic |
I would be interested to join! We are looking to build @tauri-apps for iOS/tvOS and maybe migrate our wry macOS implementation. btw; amazing work! |
Cool, I can look at setting something up today. Tauri apps might be hard on tvOS, if I'm understanding (at a glance) what you want to do, as no WebView is supported there. It's by far the least explored platform for Cacao though, so plenty of time to dig further anyway. |
FWIW, #48 adds image support for iOS. I would be curious what "core controls" people would need/want supported on iOS so that shoring up that side of things could happen. (I know this issue is old, so apologies for raising a zombie here) |
(#48 has been merged) |
I tried to add labels/text input for the iOS example and ran into a bunch of feature flags.
Is there a way to get labels/text wired up for iOS?
If not, can you give some direction on how to add it via a PR? I understand some of the code patterns, but there's still some architecture (make an Architecture.md?) that I would need to dig into to understand how to enable it properly. Also, is there a obj-c spec you're working off of or just using your ios/macos dev experience to know which NS concepts to bridge over?
The text was updated successfully, but these errors were encountered: