Closed rschroll closed 10 years ago
The future is apparently the UbuntuWebView 0.2 element, which is based on Oxide. Note that it doesn't have an executeJavascript method for us to use, but there is a Messaging API that we ought to be able to use instead.
It also seems remarkably slow to load.
I think I need to do this next on my list. I've run into problems running the app on my Nexus 4, and of the errors I'm able to produce, I get this one:
I also notice that the app sometimes loads, but shows what looks like a filebrowser, not sure why it's not rendering the main.qml properly, but this might be why. I'll poke around a bit to see what works.
The warning message is (or at least should be) benign. I think there will be support for QtWebKit at least through 14.10. I would like to update anyway, but the necessary bits haven't made it, and may never make it, back to 14.04. Since I want to keep using Beru on my desktop, this is a bit of a problem. Previously, I used a conditional loader to handle this sort of issue; we could do that again if need be.
I thought so too, it was just a warning after all, and I'm not convinced that this is the problem, I'm just looking to eliminate possible reasons why I can't get the app to load on the device.
We did this in 37c3e210. We still have the deprecation warning, since the new namespace doesn't exist on 14.04.
Beru is currently using the standard QtWebKit WebView for the book page and the UbuntuWebView for the browser page. But now we're supposed to use Oxide or something. I think. Or maybe UbuntuWebView has automatically switched over?
Whatever it is we should do, we should do.