Re: 3.2.0 released

So I have gone ahead and merged in your changes for the CLI, Plugman and cordova-amazon-fireos into the apache repos. Cordova-amazon-fireos repos has no history currently and I am not planning on spending anymore time trying to migrate it over. CLI & Plugman are both on a fireos branch. They both

Re: cordova-plugins repo release

the problem wasn't isolated to the repo (there were many problems) but suffice to say lack of shared issue tracking was a key point of failure and inability to discreetly version changesets created more suffering than good On Mon, Nov 25, 2013 at 3:20 PM, Josh Soref wrote: > Lindsey Simon wrote

Re: cordova-plugins repo release

Lindsey Simon wrote: > It seems like a shared repo is just a recipe for the troubles of the last > shared repo. For those of us who didn't live through the last shared repo, is there a document describing what happened?  There's a great writeup from some Github using group who accidentally force

Re: cordova-plugins repo release

It seems like a shared repo is just a recipe for the troubles of the last shared repo. On Mon, Nov 25, 2013 at 1:17 PM, Jesse wrote: > All of this is fine. > > I also see no reason why you cannot hack in your own repo, just ensure you > start with the right license. Nothing says that the apach

Re: cordova-plugins repo release

All of this is fine. I also see no reason why you cannot hack in your own repo, just ensure you start with the right license. Nothing says that the apache git has to be the origin of code. @purplecabbage risingj.com On Mon, Nov 25, 2013 at 1:01 PM, Anis KADRI wrote: > It sounds like we all

Re: cordova-plugins repo release

It sounds like we all agree. Start hacking on cordova-plugins and if/when it's mature move it to its own repository. Publishig from cordova-plugins should not be an issue. On Mon, Nov 25, 2013 at 11:52 AM, Braden Shepherdson wrote: > I'm not sure if I was clear: I am content with the current repo

Re: Cordova Debug Mode

+1 On 26 Nov 2013, at 6:46 am, Brian LeRoux wrote: > Proposal: > > 1. We open bugs to document how to create release software for all the > platforms. > 2. We review to see if there is anything common we can abstract > > Cool? > > > > > On Mon, Nov 25, 2013 at 11:36 AM, Michal Mocny wrote

Re: cordova-plugins repo release

I'm not sure if I was clear: I am content with the current repo setup and argue for keeping it as it is. The main core plugins are in their own repos and I support that. On the other hand I support having the cordova-plugins repo as an incubator for experimental projects that either die or graduate

Re: Refactoring the CLI tests

I think they're ready to go, yeah. Remember not to rebase the branch, since it's shared; just merge. Braden On Mon, Nov 25, 2013 at 2:15 PM, Mark Koudritsky wrote: > Would it be ok to merge the e2e tests to master now? > I did a change last week and a tes

Re: Cordova Debug Mode

Oh, don’t get me wrong. I *have* shipped an app that is otherwise completely dictated by the CLI workflow (and has been since the CLI was in beta… we drink the Kool-Aid). We have just had to document internally how to do it. But if releasing is possible from the terminal (at least on Android, i

Re: Cordova Debug Mode

Proposal: 1. We open bugs to document how to create release software for all the platforms. 2. We review to see if there is anything common we can abstract Cool? On Mon, Nov 25, 2013 at 11:36 AM, Michal Mocny wrote: > Lets distinguish between "CLI" as (a) one of two potential cordova > work

Re: cordova-plugins repo release

Okay -- while I do agree with Braden -- in the interests of not debating again, I'll concede to not publishing core plugins from a shared repo (if for no other reason than for consistency with the other core plugins). But I think its still worth having a cordova-plugins repo for early experiments/

Re: Cordova Debug Mode

OK, we're straying way too far from the subject. That being said, cordova build --debug and cordova build --release don't really make sense since --release may not be possible on all platforms. I think we can get consensus on that currently. What DOES make sense is if the platforms detected wheth

Re: Cordova Debug Mode

Lets distinguish between "CLI" as (a) one of two potential cordova workflows vs (b) typing commands into a terminal using an easy & documented & unsurprising syntax for users of the cordova tool. So: How would you release from "the CLI"? (a) The same ways you would using the platform workflow (b)

Re: Cordova Debug Mode

I tend to agree w/ Joe here. Abstracting ./release is a nice idea on the surface but this should really live in our docs as the process is far more manual and store specific than can be automated in a useful manner. On Mon, Nov 25, 2013 at 11:26 AM, Joe Bowser wrote: > Accidentally didn't send

Re: Cordova Debug Mode

How would you release from the CLI? On what platforms? In was not aware of any way in the CLI workflow to avoid going into Xcode (in the case of iOS), or typing 'ant release' (after setting up your release keys) in the case of Android. BB10 does have flags... But the others? Have I missed someth

Re: Cordova Debug Mode

(..And my reply.) On Mon, Nov 25, 2013 at 11:16 AM, Michal Mocny wrote: > Okay, I agree with you, this is difficult and poorly documented. This is > something we in mobile-chrome-apps team are annoyed with right as we > prepare to advocate cordova to chrome app devs more prominently. We here

Fwd: Cordova Debug Mode

Accidentally didn't send this to the list: -- Forwarded message -- From: Joe Bowser Date: Mon, Nov 25, 2013 at 11:03 AM Subject: Re: Cordova Debug Mode To: Michal Mocny On Fri, Nov 22, 2013 at 10:18 AM, Michal Mocny wrote: > > What do we mean that the CLI doesn't have a way t

Re: Refactoring the CLI tests

Would it be ok to merge the e2e tests to master now? I did a change last week and a test for it will be much better and easier in the e2e tests (got it ready locally). So I'm starting to depend on the e2e tests. On Thu, Nov 14, 2013 at 2:02 PM, Jonathan Bond-

Re: 3.2.0 released

Sure can! I plan on merging fireos + ubuntu for the next release. Will get on that today. On Mon, Nov 25, 2013 at 9:45 AM, Naik, Archana wrote: > Congratulations guys!! > > Hi, Steven > > Now that this release is out, is there any chance you or someone could > look at cordova-amazon-fireos repo

Re: Cordova Debug Mode

FWIW, BB10 does respect --debug (default) and --release flags passed into build. In debug mode, remote web inspector is enabled and the app is not signed. On Mon, Nov 25, 2013 at 1:48 PM, Michal Mocny wrote: > You have to explicitly enable remote debugging for kitkat chrome-based > webview: >

Re: Updating FileTransfer

Well, according to the caniuse link, it is already available in all current platforms. Of course we will need to investigate permissions when uploading from file:// to server:// as there are always some hoops, but having an available browser implementation to patch is a great start. @purplecabbage

Re: Cordova Debug Mode

You have to explicitly enable remote debugging for kitkat chrome-based webview: https://developers.google.com/chrome-developer-tools/docs/remote-debugging#debugging-webviews Existing cordova platforms do not do this. I think it would be a good preference to add for the android platform for 3.3, b

Re: cordova-plugins repo release

Super disagree about putting src into a single big repo. I get why we do that. I do not buy that we 'have too many repos' or that complexity is minimized by combining. Anyhow: not a discussion I think is even worth us having AGAIN. =/ On Mon, Nov 25, 2013 at 10:32 AM, Braden Shepherdson wrote: >

Re: cordova-plugins repo release

Hang on a second: The release you send to the plugman registry doesn't care about git. You point it at a (sub)directory and it uploads the plugin. The version is set by the plugin.xml of that plugin. If we want tags for when those plugins were pushed to npm, what's wrong with tags like "whateverp

3.2.0 released

Congratulations guys!! Hi, Steven Now that this release is out, is there any chance you or someone could look at cordova-amazon-fireos repo problem? Would love to have the port merged before next release. Thanks for your help. Archana

RE: Cordova Debug Mode

@Jan Remote debugging is possible with for example https://www.jshybugger.com/ On Android 4.4 It is possible to debug without a plugin. Sent from my Windows Phone From: Jan Becicka Sent: ‎11/‎25/‎2013 17:05 To: dev@cordova.apache.org

Re: cordova-plugins repo release

Would that only be true if you shared readable tag names between plugins? If we used tags unique to each plugin, perhaps by prefixing tags with the target plugins' name, then plugin releases would be isolated, right? -Michal On Fri, Nov 22, 2013 at 8:02 PM, Jesse wrote: > The issue that if us

Re: Cordova Debug Mode

> * Enabling the remote debugger in Android 4.4+ Btw does cordova support remote debugging on Android? Is there a way how to enable it for cordova apps? I tried to google it, but I failed. Thanks, Jan