Skip to content
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

Android status #586

Open
Superbelko opened this issue Feb 2, 2019 · 0 comments
Open

Android status #586

Superbelko opened this issue Feb 2, 2019 · 0 comments

Comments

@Superbelko
Copy link
Contributor

I found that the current state of the build scripts and (the only) example is unacceptable. The build scripts have hardcoded paths and outdated, the only android sample is too dirty to be helpful, and I found no mention about FreeType dependency until I tried to run the app on the device and see it immediately crash.

So what I think we need

Clean-up:

  • Get rid of hardcoded paths in build scripts
  • Make them platform independent (the whole process works just fine on Windows)
  • Migrate to newer CMake gradle toolchain (yes it uses CMake that doesn't support D yet, but that can be simply forwarded to dub/whatever other external command, or just make custom build tasks for gradle instead)
  • Clean-up android example directory structure, add instructions

Input:

  • Make basic JNI wrappers for virtual keyboard (if there is none yet) and possibly other crucial input services that doesn't have native API's
  • Use that wrappers to allow showing virtual keyboard when tapping on text fields
  • Add support for non-fullscreen apps?
  • ???

Any other android related feedback is welcomed. So by the time someone will going to do this work there will be some sort of to-do list ready.

Of course all of the above is just my thougths and should be treated just as a wishlist, no obligations are made and no one forced to do any of these happen. There is no intent to make the dlangui a viable alternative to real android UI frameworks, but at least it should be somewhat usable unlike how it is now.

@Superbelko Superbelko mentioned this issue Feb 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant