I volunteer to test splash/icons support one more time and update the docs
where it is required.
* The old documentation refers to PG Build. Cordova implementation is based on
this idea, but there are some differences, for example we don't support gap:
prefix and platform attribute, platform sp
Github user sgrebnov commented on the pull request:
https://github.com/apache/cordova-lib/pull/57#issuecomment-48696309
Fixed 'update_build_settings' issue and force pushed, thank you Jesse
@purplecabbage
---
If your project is set up for it, you can reply to this email and have yo
On 11 Jul 2014 00:22, "Frederico Galvão"
wrote:
>
> Are you guyus against the actual implementation being suggested or are you
> against the idea as a whole?
A bit of both, assuming you didn't add this feature. See below.
> If the answer to the above is "I +1 the idea but -1 the current
> implem
I'm a bit behind on the recent tooling update so forgive me if this is a dumb
question. The very first item listed is:
Support for splash screens
Which is odd since I thought splash screens had been available for some time
now. We've had an API to hide show them. We've also had documented ways
Github user agrieve commented on the pull request:
https://github.com/apache/cordova-android/pull/105#issuecomment-48687118
I believe this issue is fixed on master. Have a look at the commit here:
https://git-wip-us.apache.org/repos/asf?p=cordova-android.git;h=445ddd8
And t
Somewhat to Joe's point, anyone who knows that they want this feature can
probably find their own work-around. ( as Frederico proves )
Joe has the strongest feelings on this, such that he keeps getting pulled
into the conversation even though he is on holiday.
I think we should shelve this conversa
Are you guyus against the actual implementation being suggested or are you
against the idea as a whole?
If the answer to the above is "I +1 the idea but -1 the current
implementation being suggested", then ignore the rest of this message, and
I'll say that I'm looking foward to this feature being r
Github user rodms10 commented on a diff in the pull request:
https://github.com/apache/cordova-plugin-globalization/pull/17#discussion_r14800265
--- Diff: src/firefoxos/GlobalizationProxy.js ---
@@ -0,0 +1,217 @@
+/*
+ *
+ * Licensed to the Apache Software Foundation (A
Github user rodms10 commented on a diff in the pull request:
https://github.com/apache/cordova-plugin-globalization/pull/17#discussion_r14800066
--- Diff: src/firefoxos/GlobalizationProxy.js ---
@@ -0,0 +1,217 @@
+/*
+ *
+ * Licensed to the Apache Software Foundation (A
Github user rodms10 commented on a diff in the pull request:
https://github.com/apache/cordova-plugin-globalization/pull/17#discussion_r14799326
--- Diff: src/firefoxos/GlobalizationProxy.js ---
@@ -0,0 +1,217 @@
+/*
+ *
+ * Licensed to the Apache Software Foundation (A
Github user rodms10 commented on a diff in the pull request:
https://github.com/apache/cordova-plugin-globalization/pull/17#discussion_r14799288
--- Diff: src/firefoxos/GlobalizationProxy.js ---
@@ -0,0 +1,217 @@
+/*
+ *
+ * Licensed to the Apache Software Foundation (A
Published.
The site diff was way larger than it should've been (mostly white space
related diff). Any site building settings I missed?
On Thu, Jul 10, 2014 at 5:24 PM, Mark Koudritsky wrote:
> Ok, added Michal's wording with the one line instruction from Anis.
> Publishing it.
>
Github user purplecabbage commented on the pull request:
https://github.com/apache/cordova-lib/pull/57#issuecomment-4825
update_build_settigns should be update_build_settings
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Ok, added Michal's wording with the one line instruction from Anis.
Publishing it.
I vaguely remember some plugins returning Just the boolean OK.
As long as we document this and are noisy about it, it's probably OK, I
guess.
On 11 Jul 2014 04:50, "julio cesar sanchez" wrote:
> I think I don't return just the ok without message on any of my plugins,
> I'll check, but you can fi
s/ettigns/ettings/g
Am 10.07.2014 21:02 schrieb "sgrebnov" :
> GitHub user sgrebnov opened a pull request:
>
> https://github.com/apache/cordova-lib/pull/57
>
> CB-7118 iOS: add target-device and MinimumOSVersion support to
> config.xml
>
> https://issues.apache.org/jira/browse/CB-7118
Github user nolanlawson commented on the pull request:
https://github.com/apache/cordova-android/pull/105#issuecomment-48660618
Hmm, sounds like you actually have a different issue. This isn't
Samsung-only from what I saw (repro'd on LG Nexus 5).
---
If your project is set up for it,
On 10 Jul 2014 19:58, bows...@gmail.com wrote:
>
>
> Completely disagree. All this will do is make things not build and
confuse users. It's our job to try and abstract this out and when we let
users control this, their apps are terrible. This feature is harmful and
shouldn't be included.
Decided
Github user hnilsen commented on the pull request:
https://github.com/apache/cordova-android/pull/105#issuecomment-48657992
True, success() doesn't keep the callback, but for us it's not important. I
changed the success() function to always keep callback, but that changed
nothing for
Github user hnilsen commented on the pull request:
https://github.com/apache/cordova-android/pull/105#issuecomment-48657793
I saw your comment, but reading from a mobile device, so I can't really
test it out. My fix is exclusively for 3.3.x, there has been made lots if
changes since t
Github user nolanlawson commented on the pull request:
https://github.com/apache/cordova-android/pull/105#issuecomment-48657215
BTW I also tried, as a workaround, to consistently execute
`callbackContext.success()` or `failure()` for every callback (since I believe
you said it might b
Github user nolanlawson commented on the pull request:
https://github.com/apache/cordova-android/pull/105#issuecomment-48656575
I think I might be hitting the same issue as you ([comment
added](https://issues.apache.org/jira/browse/CB-7104?focusedCommentId=14057854&page=com.atlassian.j
On 10 Jul 2014 19:13, "Jesse" wrote:
>
> this element is used to specify the API Level,*not* the version number of
> the SDK
>
So, if we set the target and max API to 10, we can't build Cordova on
Android, because it's targeted at 19. That's the danger. We currently use
reflection to get around
Sounds good to me.
@purplecabbage
risingj.com
On Wed, Jul 9, 2014 at 11:38 PM, Sergey Grebnov (Akvelon) <
v-seg...@microsoft.com> wrote:
> There is the following important property provided by cordova.js -
> 'cordova.platformId' which specifies the platform app runs on. Since we
> introduced s
Github user asfgit closed the pull request at:
https://github.com/apache/cordova-blackberry/pull/168
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the fea
GitHub user jsoref opened a pull request:
https://github.com/apache/cordova-blackberry/pull/168
CB-7119 cordova run --target xxx dies if blackberry10.json is empty
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jsoref/cordova-bl
this element is used to specify the API Level,*not* the version number of
the SDK
+1
max simply ensures that some new untested and potentially incompatible API
level is not used. Where is the danger Joe?
We just need to be sure that cordova-android@X.X.X somehow specifies what
API levels it suppor
GitHub user sgrebnov opened a pull request:
https://github.com/apache/cordova-lib/pull/57
CB-7118 iOS: add target-device and MinimumOSVersion support to config.xml
https://issues.apache.org/jira/browse/CB-7118
You can merge this pull request into a Git repository by running:
$
-1
I like adding min, but max and target build can really break the build,
especially when we try and use newer Chromium features. PG Build has this
only because a method that we were using was removed from Cordova and they
have to support old versions. We want people to upgrade Cordova and this
I didn't have anything in mind as far as where the settings could be made
available. I was more broaching the subject to see if it's possible or if
there would be a lot of code rewrite to make it work. I'm not as familiar
with how the CLI works or how the code decides to place certain files in
c
I think I don't return just the ok without message on any of my plugins,
I'll check, but you can fix it
If it's not documented behaviour, I'd say it's a bug. Fit it :)
On Thu, Jul 10, 2014 at 2:35 PM, Andrew Grieve wrote:
> Likely most will not be affected and the fix is easy. go for it.
>
>
> On Thu, Jul 10, 2014 at 2:30 PM, Shazron wrote:
>
> > I would like to apply this fix:
> > https://issue
Sergey, this is awesome! Once we get your changes pulled in we should also
update the documentation. I can see this being a popular little feature
for users.
Lisa
@LisaSeacat
From: "Sergey Grebnov (Akvelon)"
To: "dev@cordova.apache.org"
Date: 07/10/2014 04:23 AM
Subject:
Likely most will not be affected and the fix is easy. go for it.
On Thu, Jul 10, 2014 at 2:30 PM, Shazron wrote:
> I would like to apply this fix:
> https://issues.apache.org/jira/browse/CB-6165
>
> Essentially, right now if the plugin result is OK (or any other
> status) without a message, iOS
I would like to apply this fix:
https://issues.apache.org/jira/browse/CB-6165
Essentially, right now if the plugin result is OK (or any other
status) without a message, iOS inserts a the human readable part of
the status ordinal as the message, which I think is wrong, this is not
a message that is
Welcome Florian!
@purplecabbage
risingj.com
On Thu, Jul 10, 2014 at 6:34 AM, Andrew Grieve wrote:
> Welcome Florian, Thanks for the introduction :). Looking forward to having
> you help out.
>
>
> On Thu, Jul 10, 2014 at 6:21 AM, Florian Berton
> wrote:
>
> > Hi,
> >
> >
> >
> > My name is F
Github user clelland commented on the pull request:
https://github.com/apache/cordova-plugin-camera/pull/12#issuecomment-48635041
@confile, you can file issues on our JIRA issue tracker
[here](https://issues.apache.org/jira/browse/CB/)
You'll have to create a (free) account,
Github user clelland commented on the pull request:
https://github.com/apache/cordova-plugin-camera/pull/12#issuecomment-48634777
@woozzel, it looks like this was merged in just after v0.2.9 was released,
and the code is present in the v0.3.0 release, which is available now from
plug
Github user confile commented on the pull request:
https://github.com/apache/cordova-plugin-camera/pull/12#issuecomment-48632796
Since there is no way to send you issues I write it here.
When using Android and image as PNG from Camera auto rotation does not work
even if it i
I wanted to keep it out of the notes and link to a more detailed wiki page
because one-liner instructions are usually pretty cli-centric. The numbers
we were given last we asked was that a far minority actually use/are aware
of plugman directly. So I figure the instructions to try this change out
The instructions are still accurate and I can add them to the wiki but I
believe we can just append them to the blog post too because there is
really not a lot to it.
On Thu, Jul 10, 2014 at 12:16 PM, Michal Mocny wrote:
> Anis sent a detailed email about it a few weeks ago. I guess we should
We are experimenting with using `browserify` to package our `cordova.js`
build artefact. This is an internal change to our tooling, and is
currently still off-by-default. We would appreciate feedback since we hope
to switch to on-by-default in a future release. If you want to try it out,
please
Anis sent a detailed email about it a few weeks ago. I guess we should
paste that into our wiki, and link to that.
Anis, would you mind doing that and making sure the instructions are still
accurate? Thanks!
On Thu, Jul 10, 2014 at 11:48 AM, Mark Koudritsky wrote:
> Do we have some post abou
Do we have some post about browserify to link to from the [see instructions
here]?
On Thu, Jul 10, 2014 at 11:31 AM, Anis KADRI wrote:
> Sure. Looks good to me.
>
>
> On Thu, Jul 10, 2014 at 10:11 AM, Michal Mocny
> wrote:
>
> > Anis, Thats a good write up but I'm worried may confuse what this
Sure. Looks good to me.
On Thu, Jul 10, 2014 at 10:11 AM, Michal Mocny wrote:
> Anis, Thats a good write up but I'm worried may confuse what this does (see
> e.g. Ally's mails on this list). I propose a shorter description for the
> release notes a link to github docs?
>
> Perhaps something li
On 10 Jul,2014, at 17:15 , Anis KADRI wrote:
> I want to say that this should be default...but we won't change the API
> again and won't break plugins again.
Both could be supported at the same time, just by using a different base class
I want to say that this should be default...but we won't change the API
again and won't break plugins again.
On Thu, Jul 10, 2014 at 7:48 AM, Erik Jan de Wit wrote:
> Hi all,
>
> Created an plugin that does this:
> https://github.com/edewit/aerogear-reflect-cordova the repository also
> include
GitHub user dwardu opened a pull request:
https://github.com/apache/cordova-js/pull/73
Fixed jshint whitespace issues
Fixes:
Running "whitespace-check" task
files with whitespace issues: (to fix: `grunt whitespace-fix`)
src\cordova_b.js
src\io
Anis, Thats a good write up but I'm worried may confuse what this does (see
e.g. Ally's mails on this list). I propose a shorter description for the
release notes a link to github docs?
Perhaps something like:
"We are experimenting with using `browserify` to package our `cordova.js`
build artefa
Hi,
Yes it's a little out of date but it doesn't launch a separate activity and
instead a linked activity into the cordova one so it should not be killed.
The problem is not only with low memory phones since if you have a lot of apps
launched, the result could be the same.
Preserving the state
Github user woozzel commented on the pull request:
https://github.com/apache/cordova-plugin-camera/pull/12#issuecomment-48606463
Since confile's question isn't answered yet, I'd like to know, when this
will be available, too??
---
If your project is set up for it, you can reply to t
Welcome Florian, Thanks for the introduction :). Looking forward to having
you help out.
On Thu, Jul 10, 2014 at 6:21 AM, Florian Berton wrote:
> Hi,
>
>
>
> My name is Florian BERTON, I’m 25 years old, live in Paris and I have
> worked for 5 years on web technologies.
>
> I’m a new member of
No. We can't just adopt this or own the camera because of these reasons:
1. Looks out of date
2. Has UI elements that we'd have to maintain
3. Does not actually solve the problem (Activities in the background can
still die)
4. Makes apps more obviously look like Cordova apps.
We should instead f
Hi,
My name is Florian BERTON, I'm 25 years old, live in Paris and I have worked
for 5 years on web technologies.
I'm a new member of the Touchify team. Touchify is an online editor that let
you easily create your touch optimized sales content and control how to publish
them on any device witho
I checked onload on Android, and initialize is properly called after
application start.
Hi everybody,
I know that there is a common bug in Android (announced in Quirks) which makes
the system kill the app while using the plugin camera.
During some time I thought that it was the only way to launch camera activity.
But I just found the plugin Foreground Camera :
https://code.google.
Hi all,
Created an plugin that does this:
https://github.com/edewit/aerogear-reflect-cordova the repository also includes
a example plugin that uses this. Also have a blog describing this a bit more
http://blog.nerdin.ch/2014/07/improved-cordova-android-plugin-api.html
Cheers,
Erik Jan
Github user rizasabuncu commented on the pull request:
https://github.com/apache/cordova-js/pull/72#issuecomment-48594140
Hll spr dvm
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feat
Ace, look forward to browser/web as platform. Combined Web and Native API
plugin for Cordova! Yay!
Thanks for the clarification Michal.
On Tue, Jul 8, 2014 at 6:07 AM, Anis KADRI wrote:
> Right, browserify is just a way to package cordova.js that should make it
> easier to add the browser as a
Github user sgrebnov commented on the pull request:
https://github.com/apache/cordova-lib/pull/56#issuecomment-48583957
http://developer.android.com/guide/topics/manifest/uses-sdk-element.html#max
Future versions of Android (beyond Android 2.0.1) will no longer check or
enforc
Implemented, pls take a look:
https://github.com/apache/cordova-lib/pull/56/files
https://issues.apache.org/jira/browse/CB-7114
Thx!
Sergey
-Original Message-
From: tommy-carlos williams [mailto:to...@devgeeks.org]
Sent: Monday, July 7, 2014 5:33 PM
To: dev@cordova.apache.org
Subject: Re
GitHub user schettino72 opened a pull request:
https://github.com/apache/cordova-js/pull/72
CB-870 Add volume button event support to Android
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/schettino72/cordova-js
android-volume-
GitHub user schettino72 opened a pull request:
https://github.com/apache/cordova-mobile-spec/pull/80
Fix CB-7115: Add manual test for events volumedownbutton / volumeupbutto...
...n
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/
GitHub user sgrebnov opened a pull request:
https://github.com/apache/cordova-lib/pull/56
CB-7114 Android: add support of min/max/target SDK to config.xml
https://issues.apache.org/jira/browse/CB-7114
You can merge this pull request into a Git repository by running:
$ git pull
Github user SomaticIT commented on the pull request:
https://github.com/apache/cordova-plugin-file/pull/56#issuecomment-48574287
Understood :) !
Florian will send you ICLA and introduce himself to the Community today.
We want this two pull request to be packaged as part of
65 matches
Mail list logo
