Thanks, I hadn’t seen that, fun stuff! My puzzle apps are text heavy,
so I’m sticking with the OS GUI rather than drawing my own bits. Then
I keep all the OS accessibility features (e.g. high-contrast,
night-mode, text-to-voice) as well as “native app” behaviour. JNI
shouldn’t be *too* horrible, as I’m intentionally sticking to simple
types.
The overall idea is for the s7/Scheme layer to provide the business
logic + data for iOS & Android and the OS will display it. It means a
messy hybrid world of tools, but manageable I estimate. This is helped
in large part by s7.c being a single file, like sqlite3.c, which makes
it easier to integrate into each platform’s build chain
idiosyncrasies.
On 12 Jan 2022, at 17:34, Elijah Stone wrote:
On Wed, 12 Jan 2022, [email protected] wrote:
Next step is try this on Android, where the fun part will be calling
C, and hence s7, through the JNI layer!
Note you do not have to do through java, see e.g.
https://github.com/cnlohr/rawdrawandroid. Whether that makes sense is
not clear (as you would have to do the UI yourself), but it would
eliminate the need for annoying java<->c communication.
-E
_______________________________________________
Cmdist mailing list
[email protected]
https://cm-mail.stanford.edu/mailman/listinfo/cmdist
_______________________________________________
Cmdist mailing list
[email protected]
https://cm-mail.stanford.edu/mailman/listinfo/cmdist
