Return-Path: X-Original-To: apmail-cordova-dev-archive@www.apache.org Delivered-To: apmail-cordova-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 8015A17777 for ; Wed, 29 Oct 2014 18:46:43 +0000 (UTC) Received: (qmail 84864 invoked by uid 500); 29 Oct 2014 18:46:43 -0000 Delivered-To: apmail-cordova-dev-archive@cordova.apache.org Received: (qmail 84825 invoked by uid 500); 29 Oct 2014 18:46:43 -0000 Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@cordova.apache.org Delivered-To: mailing list dev@cordova.apache.org Received: (qmail 84811 invoked by uid 99); 29 Oct 2014 18:46:42 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Oct 2014 18:46:42 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of mmocny@google.com designates 209.85.223.174 as permitted sender) Received: from [209.85.223.174] (HELO mail-ie0-f174.google.com) (209.85.223.174) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 29 Oct 2014 18:46:38 +0000 Received: by mail-ie0-f174.google.com with SMTP id x19so3637835ier.33 for ; Wed, 29 Oct 2014 11:44:02 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=1KXBZCrn02dpEN9Ixlb4OypQ2IuDBJzecFzLZm1UnR4=; b=Mdth4tRMbzcrJabJYD3yqowL4ievKVUF2Bp7bX8ebuoWCnBtwqe3Hy1/S1Z/JC5pYS cqvZCu9Hi4gNz3vzVUIJoAacrUmZ3OYvNvUh7/Mzaehuad4HMQwmzUsPDsmj2YTSyNXQ oMxMYH6RmPpX/yRYRSlqZS9aUhLOlFWu1DyzaVH/M2zlGXGlw/i8LVKEUmABfpEO02BM KtaJJrEVOU72zre3uJBeD26tdBBpSUgW77ohw2G0JzvkOtpTknOc3UADx0Se2Y9E/liT kaCMJLCW057XWtjYaBDS0dnG8R0Cv3h+LNZtnjWHFwEn26I0/5+Mn0Lbo+uzSz9Wu8EK bcdw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=chromium.org; s=google; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:content-type; bh=1KXBZCrn02dpEN9Ixlb4OypQ2IuDBJzecFzLZm1UnR4=; b=C2nLctq90Ab8QUrn7Q7vE6xitksMYnuk5VTC6hBxXbbDi5K4FXy1NmcY1IZVtgu2om +LBmyFVCem4Ng2I08MOPce/D/z6oZf0fhmTO+4VR53WB/r+FCZWEgD0obJ2bwZn8W8dU zeG+pmmr04fLV5YygZf9wRJ2kYijsWriIuOsA= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:content-type; bh=1KXBZCrn02dpEN9Ixlb4OypQ2IuDBJzecFzLZm1UnR4=; b=ahkB/OCTZFhqsvE8kEE+nsnHYLgDpOqKqCQbcLYbvo4TMz9acGot3HUzk7zXxjotUp p12dGLTfJM7qFRxy2V7p84EpuQyYS5iBAf5jOqebMz1IwY/leFKfQdjMy6RdYoAb+pEZ 6D791/N3o3AMQxOUxMp4+ptIJ7FyL1+zHdtQWeUVQkvliFRyTCBCt5sLDQmBbiiS+/z1 8hpEa5fYUFePMZdrUb1py5jb+5rJ9rGQrwQk4LQLa5LUr6BqAzsPeGJ+iKx429toHv4C Ik+71xcGe2oGw0dm3NmgzOSMO1s/5rTopApp1Hj31VZ2hqQZFYnhph9hXeFuWKHg1+X4 z6/g== X-Gm-Message-State: ALoCoQkNWPbBC1pp1cTqyqcBBKDmOSEvlDxqzfBafrjDZ8Cnqtlb7ThSpUGIHiqlOIDRXWqpCczc X-Received: by 10.50.129.33 with SMTP id nt1mr40559006igb.45.1414608242464; Wed, 29 Oct 2014 11:44:02 -0700 (PDT) MIME-Version: 1.0 Sender: mmocny@google.com Received: by 10.64.59.168 with HTTP; Wed, 29 Oct 2014 11:43:42 -0700 (PDT) In-Reply-To: References: From: Michal Mocny Date: Wed, 29 Oct 2014 14:43:42 -0400 X-Google-Sender-Auth: 1lwWRiVrNVzKj_L5blVm_cymWQQ Message-ID: Subject: Re: MozillaView update, bridge questions To: dev Content-Type: multipart/alternative; boundary=047d7b4145fcc9fbd2050694251f X-Virus-Checked: Checked by ClamAV on apache.org --047d7b4145fcc9fbd2050694251f Content-Type: text/plain; charset=UTF-8 On Wed, Oct 29, 2014 at 2:18 PM, Joe Bowser wrote: > On Wed Oct 29 2014 at 10:58:08 AM Michal Mocny > wrote: > > > On Wed, Oct 29, 2014 at 1:45 PM, Joe Bowser wrote: > > > > > 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 > > > > > > > Do you mean MozillaView on 2.3? My concern here is that those devices > may > > only be on 512Mb ram and its hard to imagine an alternative webview > running > > well on that (since it loses opportunity to share system resources, it > has > > larger overheads than system webview). That said, if FF browser app is > > having success on 2.3 devices, perhaps this is no different. Perhaps > > mozilla folk have insights into FF browser app stats on 2.3 devices? > > > > Yeah, I meant 2.3. Is that what's keeping Chromium-based WebViews off > 2.3? I was hoping that KitKat and Lolipop would be killing off > Gingerbread, since we're not talking about 11% of all users instead of 25%. > Not sure KK and L will kill 2.3, but perhaps Android One etc will (cheap devices and 512 ram was previous motivation to continue shipping these old versions). > > > > > > 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 > > > > > > > Last time I took a look at the bridge I asked the same question. > Currently > > encoding looks crazy at first glance. Upon further inspection, it may be > > difficult to compete on throughput with a more cleanly implementation, > and > > thats the reason for the ugly. I'm all for an investigation into > > improvements here, but we should start with benchmarks and an > understanding > > of what would be an acceptable regression (if any). > > > > > > > > > > Thoughts? > > > > > > Joe > > > > > > --047d7b4145fcc9fbd2050694251f--