Re: Updating FileTransfer

2013-11-27 Thread Andrew Grieve
s to the published spec side of the disjunction. (But I'll let > Brian > > > >> clarify if I'm wrong) > > > >> > > > >> As far as I can tell, there isn't a FileTransfer.upload / > > > >> FileTransfer.download API anywher

Re: Updating FileTransfer

2013-11-25 Thread Jesse
anywhere else that's quite like the Cordova > > API. > > >> > > >> Ian > > >> > > >> > > >>> > > >>> "An API to read, write and navigate file system hierarchies, based on > > the > > >>> w3c fi

Re: Updating FileTransfer

2013-11-24 Thread Brian LeRoux
lse that's quite like the Cordova > API. > >> > >> Ian > >> > >> > >>> > >>> "An API to read, write and navigate file system hierarchies, based on > the > >>> w3c file api." > >>> > >>>

Re: Updating FileTransfer

2013-11-22 Thread Tommy-Carlos Williams
gt;> John M. Wargo >>> Twitter: @johnwargo >>> >>> >>> -Original Message- >>> From: brian.ler...@gmail.com [mailto:brian.ler...@gmail.com] On Behalf >> Of >>> Brian LeRoux >>> Sent: Monday, November 18, 2013 5:11 PM

Re: Updating FileTransfer

2013-11-22 Thread Brian LeRoux
navigate file system hierarchies, based on the > > w3c file api." > > > > John M. Wargo > > Twitter: @johnwargo > > > > > > -Original Message- > > From: brian.ler...@gmail.com [mailto:brian.ler...@gmail.com] On Behalf > Of >

Re: Updating FileTransfer

2013-11-22 Thread Ian Clelland
write and navigate file system hierarchies, based on the > w3c file api." > > John M. Wargo > Twitter: @johnwargo > > > -Original Message- > From: brian.ler...@gmail.com [mailto:brian.ler...@gmail.com] On Behalf Of > Brian LeRoux > Sent: Monday, Novembe

RE: Updating FileTransfer

2013-11-22 Thread Wargo, John
--Original Message- From: brian.ler...@gmail.com [mailto:brian.ler...@gmail.com] On Behalf Of Brian LeRoux Sent: Monday, November 18, 2013 5:11 PM To: dev@cordova.apache.org Subject: Re: Updating FileTransfer Answers inline. > Does FileTransfer implement any published standard, or is i

Re: Updating FileTransfer

2013-11-20 Thread Ian Clelland
On Wed, Nov 20, 2013 at 4:24 AM, Tommy Williams wrote: > Changes to the File API needs to be NOISY. According to the stats from the > plugin repository, it's one of the top downloaded plugins. > Agreed 100%. We don't want to just slip this in with no notice other than on the dev list. At the ve

Re: Updating FileTransfer

2013-11-20 Thread Tommy Williams
Nah.. Don't worry about an edge case like me! That was just an extreme example. I can always just re-do my changes to a new fork of the new hotness... ((I hate client certificate authentication, not you, heh)). I am just worried about fallout from users :( Changes to the File API needs to be NOIS

Re: Updating FileTransfer

2013-11-19 Thread Ian Clelland
Oh, don't hate me, man :) If I can manage, I'll try to make FileTransfer *just work* with whatever version of File you happen to have installed -- but that won't help you if you want to keep your modified version of FileTransfer working with the new version of File. It's unfortunate that it depen

Re: Updating FileTransfer

2013-11-18 Thread Michal Mocny
When Ian is done with his changes, even if we gave it a new name, almost certainly in practice we would stop supporting the old one. Just because no one would want to put the effort into the old version any more, doubly so because of the poor current state of those plugins and how much better this

Re: Updating FileTransfer

2013-11-18 Thread Tommy Williams
I'll hate you, but I guess I'll get over it (I have a plugin that is basically a modified fork of file-transfer.. . gonna be a pain updating it now, heh). What happened to the suggestions for this all being a new plugin of some kind? Though plugins are versioned, an old version gets no bug fixes..

Re: Updating FileTransfer

2013-11-18 Thread Brian LeRoux
Answers inline. > Does FileTransfer implement any published standard, or is it our own API? > > Nope. > Does it make sense for FileTransfer to continue to use raw FileSystem paths > (and *not* go through File at all?) given that the File API will soon be > returning only relative paths and fil