Hi Troy,
Would you mind trying once more with the latest version (Beta 5), which
is available in the App Store now.
I made some fixes, but I am still not sure whether it will work on your
device. In case there are issues I'd be interested in the adb debug log
mentioned below.
Best regards,
Tobias
On 1/23/21 5:00 PM, Tobias Klein wrote:
Hi Troy,
Could you let me know which specific Android version you are using on
your tablet.
Also, would you mind sending me a debug log by:
1) Running adb logcat | grep NODE
2) Starting up the Ezra Project app
Best regards,
Tobias
On 1/22/21 3:21 AM, Troy A. Griffitts wrote:
Hi Tobias! Excited you got things compiled. Some things work for me
on a Samsung Tab A and some things don't. They all seem like details
now that you have a full stack compiled and deployed! Looking forward
to see what becomes of it. Here's my screenshot.
On January 21, 2021 12:39:32 PM MST, Tobias Klein
<cont...@tklein.info> wrote:
Hi all,
I'm glad to announce the first working test candidate of Ezra Project on
Android (tagged Ezra Project 0.17.0-Beta3).
Here is a link to the app, which is now in the "open testing phase".
https://play.google.com/store/apps/details?id=de.ezraproject.cordova
Note that the app requires at least Android 7 and a 10" display.
Here's some technical background info:
The code base of Ezra Project only needed slight modifications to
support running with a Cordova wrapper as an Android app.
The pure cordova part now lives here:
https://github.com/ezra-project/ezra-project-cordova
That repository simply includes the main Ezra Project repository as a
submodule.
The following additional aspects were added on Android:
- Write permission handling on startup
- Added an option to keep the screen on (it otherwise turns off after a
short time without user interaction)
- Added platform-specific startup code
- Added platform-specific full screen handling
There is still some work left to replace certain mouse-dependent
features with a touch-screen compatible UX.
Under the hood, a major refactoring of the "backend functionality" was
required first. All functionality that is directly interacting with the
filesystem was moved to a separate process (Sword, Settings, i18n,
Database). The architecture is the same in the Electron app and the
Cordova app. For each, frontend and backend are separated in two
different processes and interacting with each other via an IPC layer.
This IPC layer is in detail a bit different for Electron and Cordova,
but behaves the same from an interface perspective.
I'd be happy about feedback!
Best regards,
Tobias
------------------------------------------------------------------------
sword-devel mailing list:sword-devel@crosswire.org
http://crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
_______________________________________________
sword-devel mailing list: sword-devel@crosswire.org
http://crosswire.org/mailman/listinfo/sword-devel
Instructions to unsubscribe/change your settings at above page
