[
https://issues.apache.org/jira/browse/CB-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13552630#comment-13552630
]
Frederico Costa Galvão commented on CB-1978:
I can confirm this problem still
Hello,
I hope you are doing great !
I have implemented the inAppPurchase functionality with phoneGap 1.3.0 and its
working fine but last few days i have update the phoneGap 1.3.0 to Cordova
2.3.0 and also update all library and plugins but my inAppPurchase
functionality not working so could
Michael Fry created CB-2212:
---
Summary: FileSystem getFile() call never finds file on WP8 as
isolated storage is empty
Key: CB-2212
URL: https://issues.apache.org/jira/browse/CB-2212
Project: Apache Cordova
Would it make sense to host a copy of the docs on cordova.apache.org?
Other Apache projects have their docs online at their apache.org site.
A couple possibilities:
1) build the html files and zip them up, so a consumer needs to only
download and unzip and point their browser at their local
It not only makes sense I would consider it a priority. Having the only
source of docs on a third party website is a no-go as far as I'm concerned.
I raised this issue during incubation and was assured it was a transitional
thing.
Ross
Sent from a mobile device, please excuse mistakes and
Hi Marcel,
I've got this one my roadmap of tasks.
The short-term goal is to have http://docs.cordova.io host our
documentation and we'll link to it off http://cordova.io.
The longer-term goal is to have the generator and possibly templates
decoupled from the documentation. At that time, we'll
[
https://issues.apache.org/jira/browse/CB-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Grieve reopened CB-1978:
---
Thanks for bringing this to our attention. I'll have a look into it. Would it
be possible to upload a
Hello Rajeev,
We encourage PhoneGap questions to be posted on the PhoneGap Google Groups
[1].
The Apache Cordova mailing list is more centered around contributing to
Apache Cordova and less around support.
Congrats on the big upgrade from 1.3.0-2.3.0. That's no small step. A quick
search shows
@Andrew I was thinking S3 so that a service can auto-update on each commit.
From Yohei's experience with the cordova.apache.org SVN setup, it looks
like automating that is a headache.
Michael
On Mon, Jan 14, 2013 at 9:16 AM, Andrew Grieve agri...@chromium.org wrote:
cordova.io is a bunch of
Welcome Marcel!
On Fri, Jan 11, 2013 at 4:03 PM, Filip Maj f...@adobe.com wrote:
Marcel got voted in as a committer and PMC member for Apache Cordova last
week. Marcel did a ton of work on this project across a few platforms
leading up to his voting in.
Marcel: congratulations and thank you
Please come! Submit talks and meet the people using your code!
On Fri, Jan 11, 2013 at 3:46 PM, Brian LeRoux b...@brian.io wrote:
http://goo.gl/fYW3J
I agree with Ross that it should be on Apache's servers and not somewhere
else (like Amazon S3). At most some dev could locally install Jenkins and
run a CI server with a script that can auto update the SVN repo (using
their creds), or something - until we can get a permanent solution
On Mon,
I've sent a pull request that adds a third option to the
Camera.DestinationType and returns not supported errors in the relevant
methods (for now).
On Fri, Jan 11, 2013 at 3:03 PM, Shazron shaz...@gmail.com wrote:
I like it. I seem to remember we discussed something related, like
document://
[
https://issues.apache.org/jira/browse/CB-2212?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13552959#comment-13552959
]
Jesse MacFadyen commented on CB-2212:
-
Thanks Michael
Can you post a brief example
Max Woghiren created CB-2213:
Summary: Add support for native URIs
Key: CB-2213
URL: https://issues.apache.org/jira/browse/CB-2213
Project: Apache Cordova
Issue Type: New Feature
[
https://issues.apache.org/jira/browse/CB-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse MacFadyen resolved CB-2087.
-
Resolution: Unresolved
This appears to be an issue only with the 2.2 template. Please retest in
[
https://issues.apache.org/jira/browse/CB-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13552971#comment-13552971
]
Max Woghiren commented on CB-2213:
--
I've submitted a preliminary pull request here:
Done and done
On 1/14/13 10:33 AM, Max Woghiren m...@chromium.org wrote:
Hi there,
Can someone please give me the ability to update JIRA bugs?
Thanks!
-Max
Thanks Max!
https://github.com/apache/cordova-ios/pull/6
On Mon, Jan 14, 2013 at 10:22 AM, Max Woghiren m...@chromium.org wrote:
I've sent a pull request that adds a third option to the
Camera.DestinationType and returns not supported errors in the relevant
methods (for now).
On Fri, Jan
[
https://issues.apache.org/jira/browse/CB-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13553016#comment-13553016
]
Joe Bowser commented on CB-2213:
On Android, the File System is where the pictures are
Orientation bugs for ios6 were fixed in 2.1 (see
https://issues.apache.org/jira/browse/CB-1182).
On Mon, Jan 14, 2013 at 8:08 AM, Rajeev Singh rajeev6...@gmail.com wrote:
Hello,
I had developed the project in phoneGap 1.3.0 and orientation is working
fine in iOS 5.0,5.1,and 4.3 but not
Jesse, thanks for the explanation. Certainly my experience is just with
Android iOS, so it's good to get opinions from the other platforms.
I took a look at WebOS, but pkg/cordova.webos.js does seem to pull in all
of the shared plugin modules and hooks them up with the common bootstrap.
Why do
[
https://issues.apache.org/jira/browse/CB-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13553034#comment-13553034
]
Max Woghiren commented on CB-2213:
--
On Android, when Camera.getPicture is called with
Andrew Grieve created CB-2214:
-
Summary: Refactor JS files to be more ready to move into their own
repositories
Key: CB-2214
URL: https://issues.apache.org/jira/browse/CB-2214
Project: Apache Cordova
Created a bug for the file moving part (CB-2214), but we can
continue discussing here.
On Mon, Jan 14, 2013 at 2:39 PM, Andrew Grieve agri...@chromium.org wrote:
Jesse, thanks for the explanation. Certainly my experience is just with
Android iOS, so it's good to get opinions from the other
[
https://issues.apache.org/jira/browse/CB-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13553036#comment-13553036
]
Max Woghiren commented on CB-2213:
--
Also, Joe, this was assigned to you by default—I don't
[
https://issues.apache.org/jira/browse/CB-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13553041#comment-13553041
]
Max Woghiren commented on CB-2213:
--
Never mind—Fil gave me access. Thanks Fil!
Thanks!
On Mon, Jan 14, 2013 at 2:07 PM, Filip Maj f...@adobe.com wrote:
Done and done
On 1/14/13 10:33 AM, Max Woghiren m...@chromium.org wrote:
Hi there,
Can someone please give me the ability to update JIRA bugs?
Thanks!
-Max
[
https://issues.apache.org/jira/browse/CB-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13553049#comment-13553049
]
Andrew Grieve commented on CB-2213:
---
Joe - Wouldn't this map to content:// URIs on Android?
[
https://issues.apache.org/jira/browse/CB-2213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13553052#comment-13553052
]
Simon MacDonald commented on CB-2213:
-
[~agrieve] I added some code to
Yes,
BlackBerry is really 3 platforms in one. We used to have them as 3
seperate platforms but was a headache for writing apps and ensuring that
you had the right javascript file in the right place.
Since I wrote most of the module stuff I agree I have abused it a little
with some of the tricks
Ok. Lets go at this from a workflow perspective. One thing I'd like to
note is the two classifications of branch.
There are canonical branches:
- Dev (or Master)
- Unstable (or Next)
- Stable
And then there are feature branches.
Feature branches merge into Canonical branches as appropriate.
[
https://issues.apache.org/jira/browse/CB-1978?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Frederico Costa Galvão updated CB-1978:
---
Attachment: www.tar.gz
Sure.
All needed www's files, except for cordova-2.3.0.js. Just
Michal Mocny created CB-2215:
Summary: Support ArrayBuffer arguments from native to js over exec
bridge
Key: CB-2215
URL: https://issues.apache.org/jira/browse/CB-2215
Project: Apache Cordova
On Mon, Jan 14, 2013 at 4:04 PM, Gord Tanner gtan...@gmail.com wrote:
Yes,
BlackBerry is really 3 platforms in one. We used to have them as 3
seperate platforms but was a headache for writing apps and ensuring that
you had the right javascript file in the right place.
Just so I understand
I was envisioning this working closer to the node_modules pattern.
Ideally with a module loading framework you should be able to XHR these
modules over at require time.
Here is where the debate of commonJS vrs AMD will heat up. CommonJS will
require sync XHR because of it's ties to node (which
On Mon, Jan 14, 2013 at 3:41 PM, Jesse purplecabb...@gmail.com wrote:
Comments inline below.
On Mon, Jan 14, 2013 at 11:43 AM, Andrew Grieve agri...@chromium.org
wrote:
Created a bug for the file moving part (CB-2214), but we can
continue discussing here.
On Mon, Jan 14, 2013 at
But do Canonical branches merge into each other? I'm thinking no.
My understanding:
- work goes into feature branches
- when contributor(s) deem feature is ready, merge into Unstable, which
then gets vetted (test!)
- at some point unstable merges into Next
- when tagging, we merge Next into
On Mon, Jan 14, 2013 at 4:54 PM, Filip Maj f...@adobe.com wrote:
But do Canonical branches merge into each other? I'm thinking no.
My understanding:
- work goes into feature branches
- when contributor(s) deem feature is ready, merge into Unstable, which
then gets vetted (test!)
- at
[
https://issues.apache.org/jira/browse/CB-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13553175#comment-13553175
]
Michal Mocny commented on CB-2215:
--
js:
[
https://issues.apache.org/jira/browse/CB-2215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michal Mocny resolved CB-2215.
--
Resolution: Fixed
Support ArrayBuffer arguments from native to js over exec bridge
[
https://issues.apache.org/jira/browse/CB-2216?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13553185#comment-13553185
]
Michal Mocny commented on CB-2216:
--
Commit:
So, what if Canonical branches only received merges from Feature branches...?
On Mon, Jan 14, 2013 at 2:02 PM, Andrew Grieve agri...@chromium.org wrote:
On Mon, Jan 14, 2013 at 4:54 PM, Filip Maj f...@adobe.com wrote:
But do Canonical branches merge into each other? I'm thinking no.
My
Andrew beat me to it. I don't see how feature branches can be practical. We
would have to keep track of all the feature branches on the server, and
their current merged state.
I think it makes sense for all new commits to go into unstable, whether
they be urgent bug fixes or new features or
From doing the exec bridge benchmark:
- Joe wrote a version of it that used Jasmine, but it didn't show the same
timing results as the hand-coded one. I don't think Jasmine is a good
option for benchmarks
- I wrote a version of the exec benchmark that used benchmark.js. Found it
worked really well
My ideal here is to get to a point where there is something, whatever
it is, that we want to denote as a release. That something should not
require a whole bunch of coordination. There should be a working
branch, whatever we call it, ready for a tag and nothing else on any
arbitrary date to be
My ideal here is to get to a point where there is something, whatever
it is, that we want to denote as a release. That something should not
require a whole bunch of coordination. There should be a working
branch, whatever we call it, ready for a tag and nothing else on any
arbitrary date to
Aside from the extra overhead and coordination, which I think are a major
problem, this is a recipe for disaster with merge commits. This doesn't
require manual conflict resolution to be a problem. Just that, if feature
branches A and B are merged into dev/unstable and a merge commit is
created,
Hey shawn, feel free to kick up a new thread about Windows Phone dev.
We'd love your help. You can read how we'd like you to work w/ us
here:
http://wiki.apache.org/cordova/ContributorWorkflow
On Mon, Jan 14, 2013 at 2:33 PM, Shawn Wildermuth
shawn.li...@agilitrain.com wrote:
Anyone actively
Oh, yes, that is true. I was assuming (naively) that this wouldn't be
a likely case if we were diligent about rebasing before commits
landing.
So, the real trick here is, a workflow of:
feature -- dev -- unstable -- stable
When, and more importantly who, does the Canonical brach to Canonical
Filip Maj created CB-2219:
-
Summary: Add checks for minimum Android requirements after cli
install
Key: CB-2219
URL: https://issues.apache.org/jira/browse/CB-2219
Project: Apache Cordova
Issue
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
Shawn, be aware that there are separate git repos for Windows desktop 8,
WP7, and WP8.
On 1/14/2013 5:33 PM, Shawn Wildermuth wrote:
- Upgrade it to support WP8
Sorry if this got asked before, but does a feature branch get deleted
after it is merged? Just wondering about branch clutter over a long
period, or if this is just the same as a topic branch using today's
committer workflow.
On 1/14/2013 5:34 PM, Brian LeRoux wrote:
You work on a Feature
[
https://issues.apache.org/jira/browse/CB-2183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrew Grieve resolved CB-2183.
---
Resolution: Fixed
Assignee: Andrew Grieve (was: Shazron Abdullah)
iOS fix:
Okay gentlemen, I think there have been countless good points made from all
parties, but also some bike-shedding.
Perhaps it is time to schedule some face-time to better articulate some of
the finer points, and to help come to some consensus?
-Michal
On Mon, Jan 14, 2013 at 9:40 PM, Marcel
Albert Jack created CB-2220:
---
Summary: iOS version Splash Screen function has problem on iPhone
4 and iTouch 4
Key: CB-2220
URL: https://issues.apache.org/jira/browse/CB-2220
Project: Apache Cordova
[
https://issues.apache.org/jira/browse/CB-478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shazron Abdullah resolved CB-478.
-
Resolution: Fixed
Fix commit - http://git-wip-us.apache.org/repos/asf/cordova-ios/commit/adf22687
[
https://issues.apache.org/jira/browse/CB-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13553550#comment-13553550
]
Shazron Abdullah edited comment on CB-478 at 1/15/13 6:43 AM:
--
[
https://issues.apache.org/jira/browse/CB-478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13553550#comment-13553550
]
Shazron Abdullah commented on CB-478:
-
Tested this on a self-signed cert:
Martin Ambrus created CB-:
-
Summary: JSCallback Server Closed: Stopping callbacks
Key: CB-
URL: https://issues.apache.org/jira/browse/CB-
Project: Apache Cordova
Issue Type: Bug
61 matches
Mail list logo
