cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ken Wallis <kwal...@blackberry.com>
Subject Re: Naming: cordova-2.8.0.js --> cordova.js
Date Tue, 30 Apr 2013 18:38:45 GMT
+1. We moved away from that in WebWorks a while back and just had the packaging tool copy in
the compatible version.

Sent from my BlackBerry Z10 smartphone on the Bell network.
From: Michael Brooks
Sent: Tuesday, April 30, 2013 1:36 PM
To: dev@cordova.apache.org
Reply To: dev@cordova.apache.org
Subject: Re: Naming: cordova-2.8.0.js --> cordova.js


+1 cordova.js with version as a header comment


On Tue, Apr 30, 2013 at 11:31 AM, Filip Maj <fil@adobe.com> wrote:

> If I recall correctly the original reason was because putting the version
> in after the lib name in the JS filename was what "other libraries did"
> aka jQuery.
>
> +1 from me.
>
> On 4/30/13 11:24 AM, "tommy-carlos Williams" <tommy@devgeeks.org> wrote:
>
> >+1
> >
> >Wouldn't this make mobile spec easier too?
> >
> >On 01/05/2013, at 4:20, Andrew Grieve <agrieve@chromium.org> wrote:
> >
> >> This has been brought up a few times, but I'm not sure there's been a
> >> decisive answer here yet...
> >>
> >> iOS now uses "cordova.ios.js"
> >> Android uses "cordova.android.js", but renames it in a build step to
> >>add in
> >> the version number.
> >> CLI normalizes to "cordova.js"
> >>
> >> The version number is now stamped at the top of the file in a code
> >>comment,
> >> and I feel that having it in the file name just makes work for us and
> >>our
> >> users. I'd like to change all repos to just use "cordova.js".
> >>
> >> Any objections?
> >>
> >> Andrew
>
>

---------------------------------------------------------------------
This transmission (including any attachments) may contain confidential information, privileged
material (including material protected by the solicitor-client or other applicable privileges),
or constitute non-public information. Any use of this information by anyone other than the
intended recipient is prohibited. If you have received this transmission in error, please
immediately reply to the sender and delete this information from your system. Use, dissemination,
distribution, or reproduction of this transmission by unintended recipients is not authorized
and may be unlawful.

Mime
View raw message