You've already forked android_translation_layer
mirror of
https://gitlab.com/android_translation_layer/android_translation_layer.git
synced 2025-10-27 11:48:10 -07:00
update README regarding the last commit
This commit is contained in:
19
README.md
19
README.md
@@ -14,15 +14,15 @@ A:
|
|||||||
yep, and that *can* be tackled, see https://github.com/minecraft-linux/{mcpelauncher-linker, ...}
|
yep, and that *can* be tackled, see https://github.com/minecraft-linux/{mcpelauncher-linker, ...}
|
||||||
|
|
||||||
Q:
|
Q:
|
||||||
hey! it errors out!
|
hey! this is so basic it's useless!
|
||||||
A:
|
A:
|
||||||
yup, we need to do some reimplementing :)
|
yup, we still need to do some proper reimplementing :)
|
||||||
for the PoC (simple sample app), just some basic stuff should be enough.
|
The PoC works-ish now, though it's much less complex than even a modern sample app.
|
||||||
|
For one, it doesn't use any of the complex compat layers, it just directly subclasses Activity.
|
||||||
Google did a lot of work for us already, by making a tool that can stub
|
Second, it uses only two basic UI elements (TextView and LinearLayout), and yes these are
|
||||||
out all the source files. The stubbed out files are available in their Sdk,
|
the only ones implemented (and partially at that, only the absolutely required functionality).
|
||||||
but it would be smart to just use the tool on the much better licensed
|
Third, it doesn't do much - it just sets up it's static, non-changing UI, and since the current
|
||||||
original codebase.
|
GUI implementation is just printing stuff to stdout, we might as well let the app finish after onCreate.
|
||||||
|
|
||||||
##### Roadmap:
|
##### Roadmap:
|
||||||
|
|
||||||
@@ -30,7 +30,6 @@ first we need to gather a lot of volunteers, because the android abi is *huge*
|
|||||||
|
|
||||||
then we need to settle on language / UI toolkit.
|
then we need to settle on language / UI toolkit.
|
||||||
|
|
||||||
I would like to shim stuff to C for performance (kinda like Google already
|
I would like to shim stuff to C for performance, and use GTK 4 for UI - because
|
||||||
does with C++ on newer implementations), and use GTK 4 for UI - because
|
|
||||||
that seems like a lot of fun, and we need to be honest with ourselves, why
|
that seems like a lot of fun, and we need to be honest with ourselves, why
|
||||||
would anyone help with this project if not for fun ;)
|
would anyone help with this project if not for fun ;)
|
||||||
|
|||||||
Reference in New Issue
Block a user