Mailing-List: contact dev-help@cordova.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cordova.apache.org
Received-SPF: pass (nike.apache.org: domain of bowserj@gmail.com designates
 209.85.210.172 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CAASJe79vhOSxCPP0sdXqOsLUSrPBeqHiqkRadhoFdfoJObfDPQ@mail.gmail.com>
References: 
 <0962B0BEF842A24191AD9BE41A8DD2FC02AE43D1@ch-mailsrv.rd.francetelecom.fr>
	<CABiQX1Wd52=PshVeaR94KqZxH-CZ8eK6UHer12YsNo43s2dUsQ@mail.gmail.com>
	<CAASJe79vhOSxCPP0sdXqOsLUSrPBeqHiqkRadhoFdfoJObfDPQ@mail.gmail.com>
Date: Fri, 22 Mar 2013 11:50:05 -0700
Message-ID: 
 <CAOBL_k41n_+74AYJptHo2oq1MhC__W9MAVpryLYW1MGPXo_LKg@mail.gmail.com>
Subject: Re: request focus
From: Joe Bowser <bowserj@gmail.com>
To: dev <dev@cordova.apache.org>
Content-Type: text/plain; charset=ISO-8859-1

-1

I don't want anything public until we have a process to decide on what
we should or should not support.  We've been burned in the past by
making certain things public, and then not being able to change those
methods because someone somewhere depends on it for their app.
Architectural flexibility be isn't useful if it removes our
flexibility to change things!  This is something that has driven us
nuts in the past, and that's why we by default try to make things
private.

If it's private and undocumented, we should reserve the right to
change it without having to go through the pain of the deprecation
policy.  You're free to maintain your local copy and make it public,
but it's private right now because we may want to change this in the
future, and did not plan for it to be a public api call.


On Fri, Mar 22, 2013 at 11:21 AM, Lorin Beer <lorin.beer.dev@gmail.com> wrote:
> I've messed around with programmatic view manipulation in native apps, on
> droid and iOS primarily. There's no reason that I'm aware of that these
> methods need to be private, and making sure that plugins/native code can
> change the view layout is important for overall architecture flexibility.
> It may not be the most common use case, but it's certainly an important one.
>
> +1 from me
>
>
> On Fri, Mar 22, 2013 at 7:38 AM, Andrew Grieve <agrieve@chromium.org> wrote:
>
>> Sounds good to me!
>>
>>
>> On Thu, Mar 21, 2013 at 9:09 PM, <denis.vergnes@orange.com> wrote:
>>
>> > Hi all,
>> >
>> >
>> >
>> > We have an android application mixing native views and a CordovaWebView.
>> > The problem is the CordovaWebView request the focus when launching the
>> > application even in our case it should not be the view selected by
>> > default. Unfortunately there is no easy way to override this behavior
>> > because inside CordovaWebView constructors a call to a private method
>> > setup is done where the focus is requested by calling
>> > requestFocusFromTouch which is also final. I would like to submit a pull
>> > request for at least change the visibility of setup to protected in
>> > order to override this behavior. How does it sound? Did I miss something
>> > about why setup is private?
>> >
>> >
>> >
>> > BR
>> >
>> >
>> >
>> > Denis
>> >
>> >
>>