Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: callback-dev@incubator.apache.org
Received-SPF: pass (athena.apache.org: domain of purdrew@gmail.com designates
 209.85.214.47 as permitted sender)
Received-SPF: pass (google.com: domain of purdrew@gmail.com designates
 10.204.150.69 as permitted sender) client-ip=10.204.150.69;
MIME-Version: 1.0
Sender: purdrew@gmail.com
In-Reply-To: 
 <CAM1AYQAE7JpN6YYUdk3ZepZevvxEBzzWAMMwBzYVmkZP3=A4Ng@mail.gmail.com>
References: 
 <CAM1AYQBpaGFTc522=v64nhW5h2vChbWpXHpjpWuLrS+vMFZ3fw@mail.gmail.com>
 <CB63F058.53A2%fil@adobe.com>
 <CAM1AYQAE7JpN6YYUdk3ZepZevvxEBzzWAMMwBzYVmkZP3=A4Ng@mail.gmail.com>
From: Drew Walters <deedubbu@gmail.com>
Date: Wed, 22 Feb 2012 11:33:17 -0600
Message-ID: 
 <CAO_65gwxRuYU4ouKnfVAULg1cn6q005K4fWnkx8d=M=DdfGXNQ@mail.gmail.com>
Subject: Re: Changes to File API
To: callback-dev@incubator.apache.org
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

mimetype is not a parameter of toURL either though right?

On Wed, Feb 22, 2012 at 11:30 AM, Simon MacDonald
<simon.macdonald@gmail.com> wrote:
> Okay, I've just put a change that adds toURI back into the Entry class fo=
r
> backwards compatibility. I also removed the success/error parameters from
> toURL as they are not according spec and they are never used.
>
> Take a look at the change and let me know if anything else is needed:
>
> https://github.com/macdonst/callback-js/commit/de67a919af0aa5bdc81ab3c2ee=
ce1ed17a7fd9de
>
> If I get a +1 I'll merge the code into the Apache cordova-js repo.
>
> Simon Mac Donald
> http://hi.im/simonmacdonald
>
>
> On Fri, Feb 17, 2012 at 2:55 PM, Filip Maj <fil@adobe.com> wrote:
>
>> I like that idea, Simon. Simple to add a method copy from toURL -> toURI=
,
>> add a console.log, tag for 1.5, done.
>>
>> As for updating the error codes - can we shelve that for 1.6?
>>
>> On 12-02-17 11:52 AM, "Simon MacDonald" <simon.macdonald@gmail.com> wrot=
e:
>>
>> >For the 1.5.0 release can we support <Entry>.toURI() and <Entry>.toURL(=
)?
>> >We'll mark toURI as deprecated and remove it in 1.6.0 or 1.7.0. What do
>> >you
>> >think?
>> >
>> >As for the FileError codes. Grrrrr...why did they have to change them.
>> >
>> >Simon Mac Donald
>> >http://hi.im/simonmacdonald
>> >
>> >
>> >On Fri, Feb 17, 2012 at 2:36 PM, Becky Gibson
>> ><gibson.becky@gmail.com>wrote:
>> >
>> >> I was running the mobile-spec after Shaz completed and checked in the
>> >>iOS
>> >> name change (THANKS, Shaz!) and found that several file tests fail. T=
he
>> >> issue is the name change of the <Entry>.toURI() api to <Entry>.toURL(=
).
>> >> Checking on the W3C File API: Directories and Systems spec. this API =
was
>> >> indeed renamed from the October, 2010, version of the spec that we
>> >> implemented to the April and May, 2011 versions. =A0 The FileError co=
des
>> >>have
>> >> also been reassigned - although that has not been updated in the
>> >>unified-js
>> >> implementation.
>> >>
>> >> Other than the API name change and FileError code reassignments, I do=
n't
>> >> see major changes in the specification. =A0However, this will certain=
ly
>> >>break
>> >> existing apps and I question making that change. =A0 I realize it has=
 to
>> >>be
>> >> made sooner or later, but it might be best to wait for the api to be
>> >> finalized. =A0 If we are going to make this api change, then we shoul=
d
>> >> probably also make the FileError changes to be consistent. =A0And upd=
ate
>> >>the
>> >> docs and make sure this is well documented.
>> >>
>> >> my two cents,
>> >> -becky
>> >>
>>
>>