24x sounds better to me
On Wed, Oct 31, 2012 at 3:57 PM, Andrew Grieve agri...@chromium.org wrote:
The 25x is based on the mobile-spec benchmark Braden mentioned. That's for
non-synchronous plugins. There are lots of details in the bug (
issues.cordova.io/638). The 25x is based on the
I am with Fil, I never use it, and the first thing I do is * it.
I think it also gives developers the impression that they just load
arbitrary untrusted content into their apps, and the whitelist will
protect them.
Untrusted content will always need to be sanitized, however, having
the whitelist
I have relaxed my position, as I can work around whatever the choice is.
It might be prudent to ask our users though.
On Mon, Nov 5, 2012 at 3:22 PM, Anis KADRI anis.ka...@gmail.com wrote:
I guess the consensus is to whitelist everything (*) all the time.
My opinion is that there should be
On Wed, Nov 7, 2012 at 10:54 AM, Anis KADRI anis.ka...@gmail.com wrote:
On Wed, Nov 7, 2012 at 10:33 AM, Jesse MacFadyen
purplecabb...@gmail.comwrote:
# get a list of devices
./bin/emulate -devices
# launch emulator with index of 2
./bin/emulate -d:2
Sure if you can select the one you
I would go cold turkey.
Not sure why you need to write a cli tool, just instruct users that in
version 2.3 and beyond, they must use config.xml, and tell them if
they are migrating, they will have to put their data in the new
format.
Not sure why we keep insisting on doing everything for
Yet another windows vs unix path building issue.
https://github.com/apache/incubator-cordova-js/blob/ce50b72632cc861014a58db563becea48c426772/build/packager.js#L40
On Wed, Nov 14, 2012 at 6:07 PM, Anis KADRI anis.ka...@gmail.com wrote:
...with:
building commit
Actually, it was here:
https://github.com/apache/incubator-cordova-js/blob/master/Jakefile#L73
I have pushed the fix.
Cheers,
Jesse
On Wed, Nov 14, 2012 at 10:14 PM, Jesse purplecabb...@gmail.com wrote:
Yet another windows vs unix path building issue.
https://github.com/apache/incubator
, Jesse MacFadyen
purplecabb...@gmail.comwrote:
Not using it, but the build was broken for windows devs.
Cheers,
Jesse
Sent from my iPhone5
On 2012-11-15, at 6:19 AM, Gord Tanner gtan...@gmail.com wrote:
Yeah, I moved the debug versions of Cordova.js into a debug folder.
What
very strongly that we should NOT be building this into our
framework, and forcing developers to use this approach. I think this
is definitely something that we should vote on before developing
further if the goal is inclusion in cordova.
Cheers,
Jesse
On Thu, Nov 22, 2012 at 2:34 AM, Brian
Yeah, I likely also have commits that need to be included in the tag.
On Mon, Nov 26, 2012 at 1:52 PM, Anis KADRI anis.ka...@gmail.com wrote:
I actually did run jake after changing the VERSION file but I didn't commit
the files that were modified. Re-tagged now. Sorry for the inconvenience.
tagged wp7, wp8 and windows repos
I still have some doc updates to come ... most likely tomorrow morn ...
On Mon, Nov 26, 2012 at 6:12 PM, Shazron shaz...@gmail.com wrote:
Updating iOS js, re-testing and re-tagging
On Mon, Nov 26, 2012 at 2:51 PM, Jesse purplecabb...@gmail.com wrote:
okay
many people on this list have
installed Windows 8 + the Windows Phone 8 SDK tools?
TIA
Cheers,
Jesse
--
@purplecabbage
risingj.com
, Jesse purplecabb...@gmail.com wrote:
I need some confirmation that this template works for someone other than
me.
Please import this template into the folder:
Documents\Visual Studio 2012\Templates\ProjectTemplates
Then attempt to create a new project with it.
Build and Run, and report please
Have the AppDelegate raise events when things like
'didReceiveLocalNotification' happen.
Have plugins subscribe to the event.
Party.
On Thu, Nov 29, 2012 at 1:30 PM, Anis KADRI anis.ka...@gmail.com wrote:
It's tricky exactly because of that reason (i.e multiple plugins editing
the same
Log:Received
Event: deviceready
PS. I'll check tomorrow if it correctly handles local files access via
XmlHttpRequest
Thx!
Sergei
-Original Message-
From: Jesse [mailto:purplecabb...@gmail.com]
Sent: Friday, November 30, 2012 1:24 AM
To: dev@cordova.apache.org
Subject: Re: Test WP8
WP7 app is loaded from x-wmapp1:/
WP8 app is loaded from x-wmapp0:/
So file:// will not work
There are probably numerous other approches ...
deviceready will/should never fire, but that is difficult to test for,
because it could just be taking a real long time.
I see many issues with this
and may break in a future platform version, but since each
platform requires its own cordova.js -- then each platform could define its
own cordova.isWebView?
wp7 is x-wmapp
iOS is file://
BB is http://localhost
Android is ?
On Fri, Nov 30, 2012 at 3:49 PM, Jesse purplecabb...@gmail.com wrote
Please remember Windows users in your decision making.
Not sure if it makes a difference, but how cross platform is the
suggested solution?
On Wed, Dec 5, 2012 at 12:30 PM, Drew Walters deedu...@gmail.com wrote:
So, if the WebWorks SDK itself needs to provide native code for
functionality, how
+me
Also, 2.3.0 final will be the last release of the year with everyone
hopefully enjoying some time off.
Many of the Adobe+Cordova committers will be otherwise occupied much
of next week, so it may be best to push the release of 2.3.0 to the
middle of the following week, on like the 18th or
I would like to push 2.3.0 out before the break as well, before the end of
the week.
2.3.0 adds support for WP8, and while it IS currently available in rc2, it
would be nice if it was available as part of the download from phonegap.com,
which means a release. As it is, Microsoft and I will have
into holiday mode early :P
On 12/20/12 12:35 PM, Jesse MacFadyen purplecabb...@gmail.com
wrote:
Here's the chance to prove it doesn't take a week. Let's release 2.3.0
!
Today!
Cheers,
Jesse
On 2012-12-19, at 12:05 PM, Jesse purplecabb...@gmail.com wrote:
I would like
Some important criteria in my mind:
- are there recent contributions, and active contributors?
- is there a getting-started guide, and are quirks for existing APIs
documented?
- is there a jira component that people can submit defects under?
Ultimately I don't see value in defining things any
.
On Tue, Jan 8, 2013 at 4:48 PM, Jesse purplecabb...@gmail.com wrote:
There are still 41 unresolved issues 'scheduled' for 2.3.0
I suspect most are complete, but I'm not sure.
https://issues.apache.org/jira/issues/?jql=project%20%3D%20CB%20AND%20resolution%20%3D%20Unresolved%20AND
This is also dependent on the developer's code being able to detect if
there is a front facing camera, (or ass facing), which means it should
likely happen after we finalize a capabilities api.
I believe the issues Simon mentions are issues regardless. There is
nothing in that issue that states
already is a requirement of every platform, no?
Could you describe your solution Jesse? Saying you don't agree w/
something but failing to back it up is kinda passive aggressive.
On Wed, Jan 9, 2013 at 11:23 AM, Jesse purplecabb...@gmail.com wrote:
Andrew,
The approach you mention makes
Where do you see it overwriting things? I see a few clobbers / merges
...
Sorry, off topic ...
Are you sure? I just tested this ...
Yeah, I was wrong about cordova.plugin, I thought I saw it somewhere, but
indeed, they are destroyed when bootstrapped.
One thing I did notice is that our API
I have noticed this as well, while implementing for Windows Phone.
There are also issues with the iOS implementation [1]
There are multiple string replacements that replace eachother ...
First we replace the *. with (\\s{0}|*.)
Then, we replace . with \\.
and * with .*
The problem is that the .
um, yeah.
We also need to do some work to get things consistent ... there are
differences between Android/iOS/WP7+8 that have come up in the last few
days while adding support for WP7+8
I will be creating tasks for more unification, especially for whitelisting.
On Tue, Jan 22, 2013 at 1:54 PM,
+1
Do it and move on to the next one.
On Wed, Jan 23, 2013 at 10:35 AM, Brian LeRoux b...@brian.io wrote:
Lets do it.
On Wed, Jan 23, 2013 at 12:27 PM, Filip Maj f...@adobe.com wrote:
As Andrew brought up in an earlier e-mail, we didn't socialize the
tagging
of the next release. My
the release and another for
main development is a lot of bureaucracy.
It is not, the 'branch must be named x' is mainly where I have concerns.
Really I just want things simple.
On Thu, Jan 24, 2013 at 1:57 PM, Jesse MacFadyen purplecabb...@gmail.com
wrote:
I have been quietly listening
('next');
mergeBranch('next').into('master');
}
else {
commitToBranch('master');
}
On Thu, Jan 24, 2013 at 12:29 PM, Andrew Grieve agri...@chromium.orgwrote:
Just to clarify - there should be *no* using of the git cherry-picking
command, only git merge.
Jesse - not sure what you're
No reason to exist there, other than that is the way it used to be.
I would rather just see :
var myRef = Instagram.install();
myRef.share( ... )
I'll fork it.
Also, I think we need to educate people on the use of objectsprototypes,
by example.
We too have multiple places where we define a
( ... )
On Mon, Jan 28, 2013 at 12:51 PM, Jesse purplecabb...@gmail.com
wrote:
No reason to exist there, other than that is the way it used to be.
I would rather just see :
var myRef = Instagram.install();
myRef.share( ... )
I'll fork it.
Also, I think we need
+1
On Mon, Jan 28, 2013 at 11:42 AM, Becky Gibson gibson.be...@gmail.comwrote:
+1 to Monday, Feb 4. Thanks for clarification.
On Mon, Jan 28, 2013 at 2:33 PM, Michael Brooks mich...@michaelbrooks.ca
wrote:
I haven't heard any major blockers, so Monday Feb 4th seems good.
Michael
Not yet. This will likely be looked at when we have consistent plugin
installation across all projects.
You can try the google group to see if someone has begun work on it :
https://groups.google.com/forum/?fromgroups=#!forum/phonegap
Cheers,
Jesse
On Mon, Jan 28, 2013 at 12:53 PM, Lap Ming
command names) on the same machine.
-1 for path
+1 for prompting
Sent from my iPhone
On 2013-01-28, at 6:22 PM, Jesse MacFadyen purplecabb...@gmail.com
wrote:
+1 path and configuration for credentials.
-1 prompting for values, or confirming previous values.
I think the tool
Actually the recent checkins break the existing File API that is already
there on Windows 8 and Windows Phone 8.
Both of these platforms already support ArrayBuffers, Blobs, Typed Arrays,
et al ...
On Mon, Jan 28, 2013 at 5:09 PM, Andrew Grieve agri...@chromium.org wrote:
The goal of the
There are places where the built in FileReader is overwritten, and does not
function, I had some failing tests that I am going to investigate when I
get time.
On Mon, Jan 28, 2013 at 7:07 PM, Andrew Grieve agri...@chromium.org wrote:
Jesse - what's broken about it?
On Mon, Jan 28, 2013
The original interface was simply to allow the host code to monitor
location changes. This allows for oauth workflows.
Data can(?) be passed back and forth via a query string param *afaik*.
Supporting window.opener is full of blockers, not just async issues, but
also security.
I think the
it is a security break regardless, and you can do much more than play rogue
audio. For example send data in the url
On Fri, Feb 1, 2013 at 12:27 PM, Shazron shaz...@gmail.com wrote:
Seems like a harmless thing for now for us to fix and re-tag, since the
most this does is allow people to
/browse/CB-2342#comment-13569099
On Fri, Feb 1, 2013 at 1:00 PM, Shazron shaz...@gmail.com wrote:
No this is totally restricted to playing audio and the plugin. I suppose if
there is a problem with Apple's media playing code, sure
On Fri, Feb 1, 2013 at 12:57 PM, Jesse purplecabb...@gmail.com
, Feb 1, 2013 at 1:29 PM, Jesse purplecabb...@gmail.com wrote:
My point was, can't a 3rd party library from a trusted+allowed domain
play
audio from an untrusted domain, and send data via the querystring?
new Media(http://untrusted/file.mp3?userdata=...,win,lose).play();
I have
+1, I agree on the separate repositories.
I still contend that nothing should need to be 'built' and there should be
NO dependencies on the plugins from cordova-js, ( aside from device.js +
network.js which are both required pre device ready, and I think should
remain in the cordova-js repo )
I am leaning towards Fil's points.
The advantage of script tags is everyone understands how they work. Only
use magic when magic is required.
On Wed, Feb 6, 2013 at 12:45 PM, Braden Shepherdson bra...@chromium.orgwrote:
I think it's fine to have the default behavior be to inject script tags.
This is good enough. That was my oversight.
On Wed, Feb 13, 2013 at 10:45 AM, Marcel Kinard cmarc...@gmail.com wrote:
I was contacted by someone using Cordova 2.3 on Windows desktop 8, and
they said that device.cordova was returning 2.2.0 instead of the expected
2.3.0.
Sure enough,
seems to me, temp should be whatever is returned by getCacheDir
and persistent should be Internal Storage [1]
AFAIK all other platforms consider the file storage location to be private
to the application.
[1]
http://developer.android.com/guide/topics/data/data-storage.html#filesInternal
On Tue,
Current status,
Investigating why absolutely nothing is working in WP7 an WP8 with recent
updates to cordova-js. DeviceReady is not even firing
On Wed, Feb 20, 2013 at 12:44 PM, Shazron shaz...@gmail.com wrote:
The FileTransfer errors should go away once I check in the updated js,
which
Knowing the implication of your changes is pretty critical.
IMHO everyone who commits to the generic portions of cordova-js should be
prepared to at least smoke test in WP7or8, Android, iOS, and BB. Or at a
bare minimum have extreme confidence that your change will not affect them.
On Wed, Feb
CompassHeading is not an exposed API, and I had planned to remove the tests
for it.
However, there are numerous places where it is used ( throughout
cordova-js, I don't believe any native code depends on it's existence )
https://issues.apache.org/jira/browse/CB-1583
ideally duck typing of the
will check in the cordova-js for iOS for 2.5.0rc1,
and tag iOS 2.5.0rc1.
On Wed, Feb 20, 2013 at 1:27 PM, Jesse purplecabb...@gmail.com wrote:
CompassHeading is not an exposed API, and I had planned to remove the
tests
for it.
However, there are numerous places where it is used ( throughout
As an aside, WebSQL is a deprecated storage spec, and is not supported on
WP7, WP8, or Windows 8.
WP8 and Win8 do however support IndexedDB, and apparently BB10 does too.
On Thu, Feb 21, 2013 at 11:27 AM, Joe Bowser bows...@gmail.com wrote:
OK, here's some annoying crap that the Android team
I think compiled distribution should be an option, that we support.
In WP7+8 one of the new project options includes all Cordova native code in
a compiled dll.
The dll is duplicated for each project ( not truly a shared dynamic library
), but it does allows for a simplified user project structure.
spec tests
don't
deal
well with having cordova.js injected after page load. This is
solvable
but
I'll shelve it until I get more feedback/interest expressed.
-Michal
On Mon, Feb 25, 2013 at 2:43 PM, Jesse MacFadyen
purplecabb...@gmail.com
Do we have a time set for this?
I won't be able to attend in person, but I will be in the hangout.
Cheers,
Jesse
On Wed, Feb 27, 2013 at 4:42 PM, Al Harding alharding...@gmail.com wrote:
...and the BlackBerry guys! :)
On Wed, Feb 27, 2013 at 4:37 PM, Jeffrey Heifetz jheif...@rim.com
I agree with Anis, and your easy wins Fil!
emulate is confusing, unless emulate is 'ripple only!'
I think run should take a parameter which specifies where it should run,
defaulting to an attached device perhaps.
The cordova-deploy tool for Windows Phone 8 and Windows Phone 7 ( same API,
We already discussed this, here:
http://apache.markmail.org/search/?q=Testing+MobileSpecTest#query:Testing%20MobileSpecTest%20order%3Adate-backward+page:1+mid:v2l55glnckhcqyob+state:results
I fixed it by wrapping a try/catch around the XHR which fails to load
android or ios, and continues on load
renaming stuff is easy.
Does it make sense to log without running? or does log also launch? where?
Sounds to me like logging is an option attached to a run command.
What is the point of cleaning if you're not going to build right after?
trying to free up hard drive space? anal much? or is clean
-picked your commit into master and pushed it, so that's
sorted.
If you tried to merge (in either direction) then no, it wouldn't work, and
we should never do that.
Braden
On Wed, Mar 27, 2013 at 2:46 PM, Jesse purplecabb...@gmail.com wrote:
I just tried, seems I have pulled in the other
* it is not critical that is fixed before I am back
to work in a couple days.
@purplecabbage
risingj.com
On Tue, Mar 26, 2013 at 8:57 AM, Brian LeRoux b...@brian.io wrote:
Jesse, while I respect our mutual disdain for the Bruins fan that is Mapes,
it would be more helpful for all of us to know those
perfect, thanks.
@purplecabbage
risingj.com
On Wed, Mar 27, 2013 at 1:00 PM, Filip Maj f...@adobe.com wrote:
Yes. I'll retag the JS and re-open the other tag issues in JIRA to re-copy
the JS and and re-tag once that is done on the 2.6.x branch.
On 3/27/13 12:11 PM, Jesse purplecabb
merging most likely, set up a filter.
I commit to master, checkout 2.6.x, pull master, push 2.6.x because I want
all the work I am doing in 2.6.0
https://github.com/purplecabbage/cordova-wp8/network
Looks good to me ...
@purplecabbage
risingj.com
On Tue, Apr 2, 2013 at 12:52 PM, Andrew Grieve
manually add ids (with namespacing it won't be too
much of a problem).
On Thu, Apr 4, 2013 at 11:32 AM, Lorin Beer lorin.beer@gmail.com
wrote:
on our morning scrum call, Jesse made the excellent suggestion of unique
test id's for each unit test in Mobile Spec. This would allow us
Similarly, 2 writes are required on WP7 + 8 as well, since there is no
navigable url from the application to the camera-roll.
@purplecabbage
risingj.com
On Mon, Apr 8, 2013 at 1:39 PM, Becky Gibson gibson.be...@gmail.com wrote:
Yeah, saveToPhotoAlbum was an iOS only option for awhile. It
+1 to the sanity plea of devgeek Tommy
Also, if it didn't happen on this list,
'Consensus' should always be tracked back to a thread here, regardless of
meetings, hangouts, irc, bbs, ...
@purplecabbage
risingj.com
On Tue, Apr 9, 2013 at 1:48 PM, tommy-carlos Williams
I am completely in favor of removing whitelisting as well. I believe it
gives developers a false sense of security.
imho the only sure way to protect access to the bridge is to only ever load
code that you control. We should be pushing developers towards
best-practices.
Some of the whitelist
,
Jesse
@purplecabbage
risingj.com
On Mon, Apr 15, 2013 at 9:23 PM, Don Coleman don.cole...@gmail.com wrote:
BaseCommand.InvokeCustomScript is marked as obsolete in cordova-wp8.
My plugin has native code fire a JavaScript event. On Android I do this
with plugin.webView.sendJavascript(command
but requires API breaking change to my plugin across
all platforms. It seems like I need to do that at some point. Can you give
me a heads up before you remove InvokeCustomScript?
On Tue, Apr 16, 2013 at 1:14 PM, Jesse purplecabb...@gmail.com wrote:
Hi Don,
There is not a specific replacement
RE: the permission element
Looks good for wp7 + wp8
I assume if some platform requires extra data in the permission tag it can
have it, the same way that the blackberry version has the system attribute.
@purplecabbage
risingj.com
On Wed, Apr 17, 2013 at 11:48 AM, Jeffrey Heifetz
-for-a-great-customer-experience.aspx
@purplecabbage
risingj.com
On Wed, Apr 17, 2013 at 12:04 PM, Filip Maj f...@adobe.com wrote:
Good call, sound rule of thumb
On 4/17/13 12:03 PM, Jesse purplecabb...@gmail.com wrote:
RE: the permission element
Looks good for wp7 + wp8
I assume if some platform
encapsulate Windows Phone requirements as permission elements in
plugin.xml, and have tooling be smart enough to parse wp7 + wp8 platform
permission elements and drop them into the Windows Phone manifest as
whatever elements they need to be?
On 4/17/13 12:16 PM, Jesse purplecabb...@gmail.com wrote
/
AFAIK android:required=true only effects Google Play listings.
Plugman should set the features and permissions. I think adding hardware
restrictions is a decision that needs to be made by the app developer.
On Wed, Apr 17, 2013 at 3:41 PM, Jesse purplecabb...@gmail.com wrote:
I could
I think we do have consensus on permission, you can ignore the entire
discussion of requirements as it is up to the app developer to 'require'
and not the plugin developer.
However, I do not think that removing permissions will end well. Looking
at the bigger picture, I can think of many cases
The use case is any app that has any additional native functionality added
by the developer. ( every app I have ever written )
Otherwise we force an all or nothing stance with cordova use, Android,
iOS, wp7, wp8 all support using cordova as a view in an otherwise strictly
native app, or adding a
around it.
On 4/17/13 3:55 PM, Jesse purplecabb...@gmail.com wrote:
The use case is any app that has any additional native functionality added
by the developer. ( every app I have ever written )
Otherwise we force an all or nothing stance with cordova use, Android,
iOS, wp7, wp8 all support
at any time by a new browser.
Cheers,
Jesse
[1]
http://www.w3.org/TR/pointerevents/
[2]
https://github.com/purplecabbage/cordova-wp7/blob/master/templates/standalone/cordovalib/BrowserMouseHelper.cs
@purplecabbage
risingj.com
On Thu, Apr 18, 2013 at 10:08 AM, jbo...@openmv.com jbo
We shouldn't insist if we don't have to. Me thinks.
@purplecabbage
risingj.com
On Thu, Apr 18, 2013 at 1:58 PM, Filip Maj f...@adobe.com wrote:
The android:required=true tidbit might make it necessary to special
case permissions.
E.g. the app sets a permission with required=true, then a
Hurry! It's Friday.
@purplecabbage
risingj.com
On Fri, Apr 19, 2013 at 5:19 PM, Tim Kim timki...@gmail.com wrote:
NOOO
On 19 April 2013 17:15, Shazron shaz...@gmail.com wrote:
You checked in merge conflicts. e.g.
+ HEAD
2.5.0
+===
+2.7.0rc1
+
On Fri, Apr 19,
rc1 tag is on master but not the 2.7.x branch
@purplecabbage
risingj.com
On Fri, Apr 19, 2013 at 5:27 PM, Shazron shaz...@gmail.com wrote:
Hey it's no so bad, just find the chevrons and pick the right section. If
you gtg I can take care of it
On Fri, Apr 19, 2013 at 5:24 PM, Jesse
:
Oh turns out I just didn't push up the 2.7.x changes :)
Thought something crazier was going on. OK - I think it should be good
now!
*crosses fingers*
On 19 April 2013 17:37, Tim Kim timki...@gmail.com wrote:
Ya...I just realised. Arg.
On 19 April 2013 17:35, Jesse
that?
On Fri, Apr 19, 2013 at 9:01 PM, Jesse purplecabb...@gmail.com wrote:
continuous instigation?
@purplecabbage
risingj.com
On Fri, Apr 19, 2013 at 5:57 PM, Joe Bowser bows...@gmail.com wrote:
I've re-tagged Android with the new JS.
WORST RELEASE PROCESS EVER!
On Fri, Apr
How about we let it sit, and plan for 2.7.0 release on Monday?
@purplecabbage
risingj.com
On Thu, Apr 25, 2013 at 11:23 AM, Lorin Beer lorin.beer@gmail.comwrote:
+1
On Thu, Apr 25, 2013 at 11:20 AM, Joe Bowser bows...@gmail.com wrote:
Actually, let's just do a release.
On Thu,
, Jesse purplecabb...@gmail.com wrote:
How about we let it sit, and plan for 2.7.0 release on Monday?
@purplecabbage
risingj.com
On Thu, Apr 25, 2013 at 11:23 AM, Lorin Beer lorin.beer@gmail.com
wrote:
+1
On Thu, Apr 25, 2013 at 11:20 AM, Joe Bowser bows...@gmail.com
Why was this added? Is it required?
@purplecabbage
risingj.com
On Mon, Apr 29, 2013 at 10:58 AM, Joe Bowser bows...@gmail.com wrote:
I've updated our NOTICE file indicating that we're using OkHTTP as per
the Apache Licence. I think that's good enough, and I noticed the
headers were not
at the application level; you need fix them at the HTTP level.
Ian
On Mon, Apr 29, 2013 at 2:18 PM, Jesse purplecabb...@gmail.com wrote:
Why was this added? Is it required?
@purplecabbage
risingj.com
On Mon, Apr 29, 2013 at 10:58 AM, Joe Bowser bows...@gmail.com wrote:
I've
+1
@purplecabbage
risingj.com
On Tue, Apr 30, 2013 at 1:04 PM, Shazron shaz...@gmail.com wrote:
+1
On Tue, Apr 30, 2013 at 12:54 PM, James Jong wjamesj...@gmail.com wrote:
+1 Cleaner. Thanks Andrew!
-James Jong
On Apr 30, 2013, at 3:31 PM, Lorin Beer lorin.beer@gmail.com
Not just iOS + Android ... https://issues.apache.org/jira/browse/CB-2428
@purplecabbage
risingj.com
On Thu, May 2, 2013 at 4:56 PM, Joe Bowser bows...@gmail.com wrote:
Applicable Android counterpart:
https://issues.apache.org/jira/browse/CB-2962
On Thu, May 2, 2013 at 4:54 PM, Joe Bowser
and Human-friendly, ANSI-colored output.
@purplecabbage
risingj.com
On Fri, May 3, 2013 at 12:33 PM, Shazron shaz...@gmail.com wrote:
Mainly I can see using the testing for CI or just locally:
https://github.com/facebook/xctool#testing
We have unit-tests in iOS, but we run this manually
Welcome Richard,
Happy to have more hands! I have responded to your pull request directly[1]
Cheers,
Jesse
aka @purplecabbage
[1]
https://github.com/apache/cordova-firefoxos/pull/1
@purplecabbage
risingj.com
On Mon, May 13, 2013 at 9:10 AM, Brian LeRoux b...@brian.io wrote:
Welcome
console.log is pretty useful.
This technically isn't our API, but a polyfill for platforms where
console.log goes nowhere.
WP7+8 have this broken into the DebugConsole plugin, and clobber
window.console as well as navigator.console.
modulemapper.clobbers('cordova/plugin/windowsphone/console',
I am looking to add preference support to WP7 + WP8 for overscroll but
which way should I go?
[1] iOS default config.xml
preference name=DisallowOverscroll value=false /
[2] Android version ( commented by default )
preference name=disallowOverscroll value=true /
Here is some conversation on the
, 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 purplecabb...@gmail.com wrote:
I am looking to add preference support to WP7 + WP8 for overscroll but
which way should I go?
[1] iOS
.
On 5/14/13 5:52 PM, Jesse purplecabb...@gmail.com 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, Filip Maj f...@adobe.com wrote:
That kind
+1, and another point: make sure your native bits continue to load from
both plugin/ and feature/ until the deprecation window slams shut.
@purplecabbage
risingj.com
On Thu, May 16, 2013 at 12:56 PM, Benn Mapes benn.ma...@gmail.com wrote:
+1 to leave in an empty plugin/ until deprecation time
Other platforms still need to be sure not to remove plugins/ though.
@purplecabbage
risingj.com
On Thu, May 16, 2013 at 2:29 PM, Filip Maj f...@adobe.com wrote:
Filed 3416: https://issues.apache.org/jira/browse/CB-3416
Affects only android and iOS on master.
On 5/16/13 1:30 PM, Jesse
Should we be aiming to ship 2.8.0 with a unified version of config.xml in
the template, and the project created by the CLI? In adding the feature tag
support to WP7, I have been using a config.xml that has elements like this:
feature name=Device
param name=android-package
as an
additional script that would load and do the right thing. No impact on end
users, no need for them to add additional script tags, reduced complexity
and no failing local XHRs.
@purplecabbage
risingj.com
On Thu, May 16, 2013 at 4:35 PM, Filip Maj f...@adobe.com wrote:
Hey Jesse
I am satisfied with the added error checking.
Please review the changes to plugin loading [1]
If possible I would like this in 2.8.0rc1, but perhaps more importantly, we
should do 2.8.0rc1 today.
Cheers,
Jesse
[1] https://github.com/purplecabbage/cordova-js/tree/PL
@purplecabbage
:
http://wiki.apache.org/cordova/CuttingReleases
and just keep adding comments to the JIRA bugs whenever someone does any
of
the steps.
I'm out to a movie tonight, but will be back 9ish EST. I'll look to
branch
tag then.
On Wed, May 22, 2013 at 2:22 PM, Jesse purplecabb
:
Awesome stuff! Getting cutting now.
On Wed, May 22, 2013 at 5:09 PM, Jesse purplecabb...@gmail.com
wrote:
Fixed CB-3307 for WP7, WP8, and Windows 8;
@purplecabbage
risingj.com
On Wed, May 22, 2013 at 1:46 PM, Shazron shaz...@gmail.com wrote:
Fixed the OS X
. On a branch.
On 5/23/13 10:28 AM, Jesse purplecabb...@gmail.com wrote:
So are we going with the tagged version?
Should I push off the plugin-loader changes until 2.9.0?
@purplecabbage
risingj.com
On Thu, May 23, 2013 at 10:11 AM, Steven Gill
stevengil...@gmail.comwrote
1 - 100 of 1335 matches
Mail list logo
