Evan Ruff wrote:
> Well, the whole point was kind of to be able to take my exisiting GWT/
> Gears Application and fire it down into a WebView Component to gain
> more control over the chrome, resource loading, etc.
Ah.
> It doesn't look like that's really going to work with this
> implementation
Well, the whole point was kind of to be able to take my exisiting GWT/
Gears Application and fire it down into a WebView Component to gain
more control over the chrome, resource loading, etc.
It doesn't look like that's really going to work with this
implementation!
E
On Jun 29, 8:36 am, Mark M
Evan Ruff wrote:
> Huh, that seems kind of like a curious decision.
>
> So, in order to use WebView and have persistent storage, I have to use
> the Javascript -> Android Interface specifically, then either expose
> standard getDB, executeStatement, getResultSet in
> WebView#addJavascriptInterfac
Huh, that seems kind of like a curious decision.
So, in order to use WebView and have persistent storage, I have to use
the Javascript -> Android Interface specifically, then either expose
standard getDB, executeStatement, getResultSet in
WebView#addJavascriptInterface() ?
Also Mark, thanks for
Evan Ruff wrote:
> I was wondering if I can use the Gears Toolkit within WebView? I heard
> a nasty rumor that it was not available in WebView.
At least as of Android 1.1, it was not available in WebView, and I am
not aware that situation has changed.
--
Mark Murphy (a Commons Guy)
http://commo
5 matches
Mail list logo
