On 29/10/23 19:16, Tobias Klein wrote:
What makes it complicated in my case is the following.
Ezra Bible App on Android is a Cordova app. When it comes to
permissions, etc. I depend on Cordova Plugins.
The one that I had been using is this:
Hi Timothy,
yes, that's the user perspective and it is clear.
What makes it complicated in my case is the following.
Ezra Bible App on Android is a Cordova app. When it comes to
permissions, etc. I depend on Cordova Plugins.
The one that I had been using is this:
On 29/10/23 05:50, Tobias Klein wrote:
If you happen to figure out a reliable solution for >= 11 and the new
Scoped Storage model, I'd be happy to learn.
For >= 11 I am thinking about introducing a Cloud sync feature for the
sword directory. This could then work with Dropbox and maybe also
Hi Troy,
I did not re-attempt to fix the shared data path idea for Android >= 11.
Since Google introduced their scoped storage model ... I gave up on it.
On Android versions <= 10, I use the SWORD path /sdcard/Documents/sword.
On versions >= 11, I store everything in the internal app
One new good thing I've found: Google now has a system to distribute binary
libraries for C++ builds. It's called Prefab, and the example they give is
exactly why I was looking: libcurl
Here's a link:
Hi Tobias and others with Android SWORD apps.
I am trying to bundle up a new version of Bishop for Android with the
some exciting improvements in the libsword (I'll post another email
about those, Lord willing, soon), and I would like to check on the
latest status for a shared sword path for
Hi Tobias,
So, I did a bunch of reading when choosing this location and couldn't find
anything that specifically listed which folders where standard "top level"
folders under /sdcard, only that the changes to the API in newer versions of
Android prevented creation of top level folders under
Hi Troy,
I can certainly consider /sdcard/Documents as a new base also for Ezra
(haven't tried it yet).
I just did a quick search and I didn't find any official Android
documentation on that particular filesystem path. Is there something you
can point me to?
Best regards,
Tobias
On
Thanks Michael, yes, I also feel we need to not swim against the Google
flow. The problem is that the Google flow seems to turn at each new
release of Android. Be assured, my goal is to find a common means for
us to share a single install of SWORD modules and to do it the way
Google wants and
Dear Troy,
We should certainly align on the directories and keep it simple.
However, starting from Android 11 Google makes it really hard for us due
to the "Scoped Storage" concept, see
https://developer.android.com/about/versions/11/privacy/storage
I couldn't figure out a way to write to
My main thoughts on this are:
1. The less we fight the way Google wants Android to work, the better.
2. Within the constraints of the above, backward compatibility is good.
On 9/12/21 3:51 AM, Troy A. Griffitts wrote:
> Dear all,
>
> I've been updating Bishop to work on newer versions of Android
Dear all,
I've been updating Bishop to work on newer versions of Android and have
found that we are running into problems trying to create the
"Nonstandard top-level folder" 'sword' at the root of the common storage
folder.
Tobias, I know a while back you mentioned that you had to update Ezra
12 matches
Mail list logo
