If some smart student is looking for a winter break project (as an
alternative to grinding trophies in Fallout 4, arguing Star Wars
semiotics in online forums, or marathoning ultimately disappointing
Netflix shows)...
Build Racket for the Android NDK, then make a generic shell Android app
in Java that makes the Racket APIs (GUI, filesystem, networking) work
through the Android SDK, for arbitrary apps coded in Racket.
This might be the kind of project in which you get to a milestone, like
a GUI click calling Racket code, working within a few days. After that
early milestone, then there's probably weeks or months of a combination
of tricky technical improvements (e.g., communication channel, GUI
issues, VM issues) and straightforward churning (moving somewhat
mechanically towards API completeness). The ultimate demo would be
complete DrRacket running on an Android tablet, without modification.
Then release a `raco` tool that generates an `.apk` from an arbitrary
Racket GUI program.
A variation on this would be to defer/eliminate the Racket GUI part, and
instead/first expose an Android UI API to Racket. That would give more
Android-ish UI for Racket apps written specifically for that API, but
doesn't give us DrRacket on Android tablets.
Neil V.
--
You received this message because you are subscribed to the Google Groups "Racket
Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to racket-users+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
