i've updated the library (version 0.02 attached).  you might want to copy
version 0.01 to someplace safe.  then copy/move version 0.02 to your 
additional libraries folder.

the changes:
1) the dummy, secure url for files kept in DirInternal seems to be either
https://appassets.androidplatform.net/public/ or https://appassets.androidplatform.net/public_data/.
documentation varies.  i originally used public_data, but i've changed to 
https://appassets.androidplatform.net/public/ to keep more in line with google's documentation.
https://developer.android.com/reference/androidx/webkit/WebViewAssetLoader
i've tested both urls.  both work, but the library now uses /public/, so that's the one you need to use 
in b4a.  there's a reminder in the tooltips when you hover over the enchanceWebView() method

2) i've added the javascript interface.  you should be able to inject javascript (without webviewextras)
now.  you had asked initially if you would be able to use webviewextras for javascript injection.  there 
was no conflict between the assetloader library and webviewextras, provided you did not use 
webviewextras' webviewclient.  for version 0.02, i thought it might be convenient if the library could
handle javascript itself.  depending on how you were using webviewextras, you don't have to load it.

3) i've added the chromeclient automatically to help with logging.  without a chromeclient, it's very 
difficult to debug a webview.  adding chromeclient was an extra step with webviewextras, but its
chromeclient is a fuller implementation.  i don't know exactly what you use webviewextras for, apart
from javascript injection, which was not difficult to add.

note: the purpose of the library was to show how to use the https:// scheme to load locally kept
files into a webview.  it extends our standard webview and, to a certain extent, can replace
webviewextras.  neither of those libraries supports the webviewassetloader api, so if you need
the https:// scheme, you have to use my library.  at least until the api has been incorporated into
a larger class.

unfortunately, google has designed the assetloader api to be used by programmers who write their 
own webview extensions from scratch.  incorporating the api into b4a involves more than just a 
1-line javaobject call.  

if you're using webview in ways that go beyond simply enchancing the ui, you might find some 
feature missing from the library that you were using.
