Hey

Unfortunately, I don't have anything working yet for the new MozillaView,
but because MozillaView is so radically different than any other view, I've
been forced to re-think some things with our current exec script in
cordova.js, namely why we're still using a prompt-based solution for
NativeToJS API in 2014.

I know that the reason we currently do this is because Android 2.3 sucks
and addJavascriptInterface doesn't work in the Emulator, and since people
only seem to test Android 2.3 in the emulator, we have to support this for
some reason.

I'm thinking that since the performance, as well as rendering on Android
2.3.x is so sub-par, maybe we want to strongly recommend that people use
MozillaView on 4.x and switch our bridge to do something else like poll
addJavascriptInterface and have the messages be sent back that way
instead.  I don't know if there's additional drawbacks to this approach,
which is why I'm asking here.

Also, maybe it's time to re-think the encoding of the messages?  If we can
support moving JSON over the bridge we should do so instead of depending on
string encodings.  It's what's being done with Mozilla and I'm going to
have to write the MozillaView as almost a separate platform and I'll have
to override exec with it's stuff, since it's not a WebKit/Blink WebView,
and instead has a sane way to pass stuff across. :P

Thoughts?

Joe

Reply via email to