Well, they aren't in Android ...
https://github.com/apache/cordova-android/blob/master/framework/res/xml/config.xml
All camelCase
@purplecabbage
risingj.com
On Tue, May 14, 2013 at 6:01 PM, Filip Maj wrote:
> O.
>
> Probably capital D, as all other parameters are like that methinks.
>
> On 5/1
O.
Probably capital D, as all other parameters are like that methinks.
On 5/14/13 5:52 PM, "Jesse" wrote:
>BouncyCastle!
>
>I was referring to the the fact that iOS uses DisallowOverscroll and
>Android uses disallowOverscroll
>
>@purplecabbage
>risingj.com
>
>
>On Tue, May 14, 2013 at 5:44 PM,
BouncyCastle!
I was referring to the the fact that iOS uses DisallowOverscroll and
Android uses disallowOverscroll
@purplecabbage
risingj.com
On Tue, May 14, 2013 at 5:44 PM, Filip Maj wrote:
> That kind of makes sense. The default in the iOS browser is the elastic
> thingy, right? The defaul
That kind of makes sense. The default in the iOS browser is the elastic
thingy, right? The default on Android has no elastic behavior, instead
this color-glowy thing on top.
What's the default in the WP* browser?
On 5/14/13 5:29 PM, "Jesse" wrote:
>I am looking to add preference support to WP7
I am looking to add preference support to WP7 + WP8 for overscroll but
which way should I go?
[1] iOS default config.xml
[2] Android version ( commented by default )
Here is some conversation on the matter [3] [4]
Also, incidentally, it looks the build.phonegap team is still using
'webviewboun
Hey All,
The BB10 stuff got merged into cordova.js. The following commit breaks
plugin_loader for ios + android.
https://github.com/apache/cordova-js/commit/8d59461c6f796f2c88a0eae2467cc663897ccce9.
I am going to remove the slash for now.
-Steve
Thanks for testing it out Benn! I committed it and created an issue.
https://issues.apache.org/jira/browse/CB-3392
On Tue, May 14, 2013 at 5:33 PM, Benn Mapes wrote:
> Took a look at the request and found a few new errors with the windows
> create script since things have changed a bit. I just
that's my idea, Jeffrey, to route to sub platform bin scripts. The original
create tool would create a project which could target any blackberry
platform, not just one. The idea would be that the root bin calls the
platform bin scripts and creates a single project again which can target
the individ
If bin is top level, it requires a non-standard first parameter to distinguish
sub-platform. I know this is the same as the old way, but it's very unique to
the BlackBerry implementation.
Perhaps if this just routed to sub platform bin scripts it would be ideal.
Sent from my BlackBerry 10 smart
+1
Sent from my BlackBerry Z10 smartphone
From: Lorin Beer
Sent: Tuesday, May 14, 2013 6:17 PM
To: dev
Reply To: dev@cordova.apache.org
Subject: Re: Cordova BlackBerry project structure
ok, final word on this is to not break out the BlackBerry platforms into
separate repos. However, they will br
ok, final word on this is to not break out the BlackBerry platforms into
separate repos. However, they will break out into subdirectories in the
root of the blackberry repo:
apache/cordova-blackberry/blackberry7
apache/cordova-blackberry/blackberry10
apache/cordova-blackberry/playbook
apache/cordo
Took a look at the request and found a few new errors with the windows
create script since things have changed a bit. I just added quotes around
the variables to keep it consistent with the other commands.
I added a commit as well to fix the other changes. If someone with commit
access to the repo
Plugman's future branch was merged into master a while ago. I've deleted it
from the repo, but you'll have to delete the branch from your local repo if
you have one.
$ git branch -d future
cordova-cli still has its future branch, and is not merged yet.
Braden
I will. Im heads-down working on plugin dependencies in plugman at the
moment. Once I get that sorted for android and iOS ill take a look at your
pull and bring it up to speed.
On 5/14/13 11:29 AM, "Bryan Higgins" wrote:
>Hey Fil,
>
>I'll fill in for Jeff since he's away at BB Live this week. We
merging in a few hundred commits across cordova-blackberry, cordova-js and
cordova-docs.
Hey Fil,
I'll fill in for Jeff since he's away at BB Live this week. We just rebased
the plugman changes. Could you please take a look?
https://github.com/apache/cordova-plugman/pull/5
We split this into two commits, one of them affecting other platforms. That
was necessary to get plugins loadin
looks like I pushed from the wrong branch. Not allowed to rewind, fixing
this now.
On Tue, May 14, 2013 at 9:57 AM, Lorin Beer wrote:
> I'm not to sure what happened with docs, I'll revise right away
>
>
> On Tue, May 14, 2013 at 7:21 AM, Bryan Higgins wrote:
>
>> thanks, cordova-blackberry look
I'm not to sure what happened with docs, I'll revise right away
On Tue, May 14, 2013 at 7:21 AM, Bryan Higgins wrote:
> thanks, cordova-blackberry looks good, but the docs changes didn't get
> merged in cleanly. I see merge artifacts in getting started and plugin
> development.
>
>
> On Mon, May
thanks, cordova-blackberry looks good, but the docs changes didn't get
merged in cleanly. I see merge artifacts in getting started and plugin
development.
On Mon, May 13, 2013 at 5:30 PM, Lorin Beer wrote:
> yes, I believe I have resolved all the ones that were marked as ready to
> pull in. I'm
19 matches
Mail list logo
