-1 to using requestLocalFileSystem. RLFS is a standard, and what we're
adding here is not a part of it. I think there is value in keeping
Cordova-specific logic separate so that it's easy for devs to know when
they are using an API that is Cordova-specific (as opposed to a polyfill).
That said, I
I tend to agree. Keeping this as a standalone extension will give us a
clear 'thing' to allow devs to shim out if they want to be browser
compatible. Also, in favor in async.
Brings up a deeper philosphical discussion: should we be providing shims
for functionality so that our community user land
Apologies I think there is another thread about this but I'd like to
understand more about what we're thinking here. There's been discussion
that we should make this configurable. I disagree. I think we need to
target highest available level possible, as we always have in the past, and
take
+1
On 7 Nov 2013, at 9:35 pm, Brian LeRoux b...@brian.io wrote:
Apologies I think there is another thread about this but I'd like to
understand more about what we're thinking here. There's been discussion
that we should make this configurable. I disagree. I think we need to
target highest
Feels like we're starting to regress rather often on the CLI these past two
releases. This is due to not running tests (or indeed writing them).
Thats fine. Stuff happens. A gentle reminder:
- If there is a bug: write a test
- If you are adding or refactoring code: run the tests
That is all.
I think the highest level is not what developers need.
When you create a product/app you want your app to run on as many devices
as possible and not only the latest.
Am 07.11.2013 11:36 schrieb Brian LeRoux b...@brian.io:
Apologies I think there is another thread about this but I'd like to
Also: wonder if it is time to revisit this as just Ripple. The new version
of Ripple is pretty awesome.
On Thu, Nov 7, 2013 at 11:54 AM, Brian LeRoux b...@brian.io wrote:
Feels like we're starting to regress rather often on the CLI these past
two releases. This is due to not running tests
Brian wrote:
Feels like we're starting to regress rather often on the CLI these past two
releases.
This is due to not running tests (or indeed writing them).
Thats fine. Stuff happens. A gentle reminder:
- If there is a bug: write a test
- If you are adding or refactoring code: run the
I can code up a quick sample integration to see what cordova serve (powered
by ripple) would look like.
On Thu, Nov 7, 2013 at 7:16 AM, Josh Soref jso...@blackberry.com wrote:
Brian wrote:
Feels like we're starting to regress rather often on the CLI these past
two releases.
This is due
Joe is right on the money. If the target is older than 13 it will fail to
compile which was detected elsewhere [1].
Also as detected on the other thread CLI is not actually [2] [3] delegating
the requirement checks to platform scripts for
Android and iOS. After this issue is resolved it will
I've added wp8 and windows8 support for Medic. Could someone review and merge?
David?
CB-5152 Medic. Add Windows Phone8 support
CB-5153 Medic. Add Windows related info to home page
https://github.com/apache/cordova-medic/pull/1
CB-5289 Medic. Can't be installed on Windows due to ios-deploy
Is there a JIRA for the serve issue? Josh recently added some content to
make the landing page functional.
Ripple integration sounds great. Gord - is there a way to make ripple run
chromeless for the app harness?
On Thu, Nov 7, 2013 at 7:54 AM, Gord Tanner gtan...@gmail.com wrote:
I can code
To be clear the goal for Cordova 3.2 is to set target 18 (Android 4.3) and
for Cordova 3.3 target 19 (Android 4.4) ?
We are about to release 3.2 so I want to be sure.
I vote to set target 19/4.4 (KitKat) for Cordova 3.3 (Allows time to
investigate, test, integrate, and document)
On Thu, Nov
On Thu, Nov 7, 2013 at 4:47 AM, Brian LeRoux b...@brian.io wrote:
I tend to agree. Keeping this as a standalone extension will give us a
clear 'thing' to allow devs to shim out if they want to be browser
compatible. Also, in favor in async.
Brings up a deeper philosphical discussion: should
Thanks Sergey !
Testing and CI contributions I consider big improvements!
On Thu, Nov 7, 2013 at 8:40 AM, Sergey Grebnov (Akvelon)
v-seg...@microsoft.com wrote:
I've added wp8 and windows8 support for Medic. Could someone review and
merge? David?
CB-5152 Medic. Add Windows Phone8 support
Gord Can you make shareable branch I want to contribute to effort also.
In addition of serving with ripple I would like to implement watch and
livereload for serve as user changes files in Project/www/ it calls
prepare and sends a livereload event to browser.
On Thu, Nov 7, 2013 at 8:54 AM,
That's correct. I only have an old Nexus 7 with an AOSP build I made
yesterday to test things on 4.4 while I wait for the Nexus 5 or the
official updates, and since I have no camera drivers working.
BTW: We still have a gallery, but I think the Camera plugin may be broken
in 4.4.
On Nov 7, 2013
I'm in the process of adding some additional resolutions to the BB10 splash
screens and noticed that the res folder has been moved out of www in hello
world.
Is the intention of this folder that all apps will get the same set of
default assets regardless of www template?
Has there been logic
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15046/
---
(Updated Nov. 7, 2013, 9:29 p.m.)
Review request for cordova.
Changes
---
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/15328/#review28455
---
Ship it!
Ship It!
- Braden Shepherdson
On Nov. 7, 2013, 9:59
Should the following commits should be included for 3.2 specially BB10
changes?
* d5e4e9e CB-5307 Remove references to Callback and Incubator
* 9740276 CB-5253 remove webworksready event
* 6568e94 CB-5253 remove webworks.exec
* 9bbf2b7 CB-5247 [BlackBerry10] Map blackberry.event to document
*
Alright, lets do it. Carlos, you want to retag the JS?
On Thu, Nov 7, 2013 at 2:49 PM, Jesse purplecabb...@gmail.com wrote:
I am a plus one, if these items are intended to be in 3.2.0.
Technically, all platforms should be updated so they are all built from the
same git commit.
cordova-js has been retagged
On Thu, Nov 7, 2013 at 3:01 PM, Steven Gill stevengil...@gmail.com wrote:
Alright I got this.
On Thu, Nov 7, 2013 at 2:58 PM, Carlos Santana csantan...@gmail.comwrote:
Steve can you go ahead merge amd retag I'm out right now on a cfa meeting.
--Carlos
On
Sweet. None of these require re-tagging cordova-js.
On Thu, Nov 7, 2013 at 3:50 PM, Josh Soref jso...@blackberry.com wrote:
Carlos wrote:
Should the following commits should be included for 3.2 specially
BB10 changes?
On the subject of changes designed for 3.2, this set (for CCB-5258) is
I can't find the original email in my archives, but here is an email
mentioning the availability of MSDN to apache commiters.[1]
You'll need to go to [2] with your svn credentials and fill out the form.
And I think you need to do it every year.
[1]
Thank you Steve !
On Thu, Nov 7, 2013 at 8:06 PM, Steven Gill stevengil...@gmail.com wrote:
Sweet. None of these require re-tagging cordova-js.
On Thu, Nov 7, 2013 at 3:50 PM, Josh Soref jso...@blackberry.com wrote:
Carlos wrote:
Should the following commits should be included for 3.2
And the js commits for blackberry did not change the js for other platforms!
Win win.
Sent from my iPhone
On Nov 7, 2013, at 6:56 PM, Carlos Santana csantan...@gmail.com wrote:
Thank you Steve !
On Thu, Nov 7, 2013 at 8:06 PM, Steven Gill stevengil...@gmail.com wrote:
Sweet. None
27 matches
Mail list logo
