Return-Path: X-Original-To: apmail-incubator-callback-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-callback-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AB7A39F0C for ; Tue, 29 May 2012 18:57:55 +0000 (UTC) Received: (qmail 77975 invoked by uid 500); 29 May 2012 18:57:55 -0000 Delivered-To: apmail-incubator-callback-dev-archive@incubator.apache.org Received: (qmail 77939 invoked by uid 500); 29 May 2012 18:57:55 -0000 Mailing-List: contact callback-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: callback-dev@incubator.apache.org Delivered-To: mailing list callback-dev@incubator.apache.org Received: (qmail 77930 invoked by uid 99); 29 May 2012 18:57:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 May 2012 18:57:55 +0000 X-ASF-Spam-Status: No, hits=-1.3 required=5.0 tests=FRT_ADOBE2,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of fil@adobe.com designates 64.18.1.21 as permitted sender) Received: from [64.18.1.21] (HELO exprod6og108.obsmtp.com) (64.18.1.21) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 29 May 2012 18:57:50 +0000 Received: from outbound-smtp-2.corp.adobe.com ([193.104.215.16]) by exprod6ob108.postini.com ([64.18.5.12]) with SMTP ID DSNKT8UcGYkyZpOQuTjdlQH4Gp0GbDp7K60g@postini.com; Tue, 29 May 2012 11:57:30 PDT Received: from inner-relay-1.corp.adobe.com (inner-relay-1.corp.adobe.com [153.32.1.51]) by outbound-smtp-2.corp.adobe.com (8.12.10/8.12.10) with ESMTP id q4TIvRIf003759 for ; Tue, 29 May 2012 11:57:28 -0700 (PDT) Received: from nahub02.corp.adobe.com (nahub02.corp.adobe.com [10.8.189.98]) by inner-relay-1.corp.adobe.com (8.12.10/8.12.10) with ESMTP id q4TIvRvm011101 for ; Tue, 29 May 2012 11:57:27 -0700 (PDT) Received: from nambxv01a.corp.adobe.com ([10.8.189.95]) by nahub02.corp.adobe.com ([10.8.189.98]) with mapi; Tue, 29 May 2012 11:57:27 -0700 From: Filip Maj To: "callback-dev@incubator.apache.org" Date: Tue, 29 May 2012 11:57:27 -0700 Subject: Re: Cordova and config.xml Thread-Topic: Cordova and config.xml Thread-Index: Ac09zOOndEf4pYcWSaWDbQqH3+0rdg== Message-ID: In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: user-agent: Microsoft-MacOutlook/14.2.2.120421 acceptlanguage: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org I'm still waiting for the first standards joke in this thread. On 5/29/12 11:55 AM, "Gord Tanner" wrote: >Also we have npm's package.json as a manifest "standard" as well: >http://npmjs.org/doc/json.html > > > >On Tue, May 29, 2012 at 2:50 PM, Drew Walters wrote: > >> I was curious of the compatibility between Mozilla's App Manifest and >> Google's Chrome Store Manifest. Found this handy comparison table >> which I thought others might find useful: >> >> https://wiki.mozilla.org/Apps/ManfiestFormatComparison >> >> On Tue, May 29, 2012 at 1:26 PM, Michael Brooks >> wrote: >> > @Fil thanks for pointing out the Mozilla's App Manfiest! >> > >> > @Ken I think prudent that Apache Cordova listen to BlackBerry's >> experience >> > with the widget spec. We're both using it in similar ways and Apache >> > Cordova will likely hit the same areas for customization. Ken, can you >> > elaborate on how BB10 will be deviating even further? Is there a link >>out >> > there? >> > >> > Regardless of what we choose, we don't want to invent our own app >> manifest >> > "standard" and so it's worth reviewing the two that are out there. >>Below >> > are the spec links. >> > >> > W3C Configuration Document (config.xml): >> > http://www.w3.org/TR/widgets/#configuration-document >> > >> > BlackBerry WebWorks config.xml: >> > >>=20 >>https://developer.blackberry.com/html5/documentation/ww_developing/workin >>g_with_config_xml_file_1866970_11.html >> > >> > Mozilla App Manifest: >> > https://developer.mozilla.org/en/Apps/Manifest >> > >> > Michael >> > >> > On Tue, May 29, 2012 at 11:13 AM, Ken Wallis wrote: >> > >> >> Laurent and I were just chatting about this. Certainly feel that we >> >> should have a common shared format for application metadata. Default >> >> option would be to look at the W3C widget spec which we all are or >> already >> >> have done in RIM's case. ;) >> >> >> >> That said, you know that we have gone past the spec already, and with >> BB10 >> >> we will have to go even farther down the custom namespace route. We >> (RIM) >> >> may need to actively diverge on some concepts that might have Widget >> >> equivalents but just don't map properly (Not sure yet, but starting >>to >> get >> >> a feeling...) I would suspect that Cordova will need custom >>elements as >> >> well. >> >> >> >> Do we ask the question then, is this still the right choice, use >>widget >> >> spec as a basis and expand where needed? Use it as inspiration, but >> not be >> >> beholden to it? Something completely custom, or aligned with other >> >> initiatives like Mozilla? >> >> >> >> Lots of questions... ;) >> >> -- >> >> >> >> Ken Wallis >> >> >> >> Product Manager =AD BlackBerry WebWorks >> >> >> >> Research In Motion >> >> >> >> (905) 629-4746 x14369 >> >> >> >> ________________________________________ >> >> From: Filip Maj [fil@adobe.com] >> >> Sent: Tuesday, May 29, 2012 2:02 PM >> >> To: callback-dev@incubator.apache.org >> >> Subject: Re: Cordova and config.xml >> >> >> >> Just want to point out too that mozilla has/is working on their >> equivalent >> >> of config.xml >> >> >> >> https://developer.mozilla.org/en/Apps/Manifest >> >> >> >> >> >> JSON! :r >> >> >> >> On 5/29/12 10:57 AM, "Shazron" wrote: >> >> >> >> >I concur - we had this discussion sometime ago but with respect to >>the >> >> >whitelist, and eventually decided to support access tags in >>config.xml >> to >> >> >consolidate all the platforms. We didn't have a plan then on when to >> >> >include this feature. Not seeing it in the Roadmap though pre-2.0 or >> even >> >> >for 2.0: http://wiki.apache.org/cordova/RoadmapProjects >> >> > >> >> >On Tue, May 29, 2012 at 9:49 AM, Michael Brooks >> >> >wrote: >> >> > >> >> >> From my understanding, yes. >> >> >> >> >> >> PhoneGap Build currently uses it (not as extensively as BB) to >> describe >> >> >>the >> >> >> app's metadata and configuration (access, permissions, etc). >> >> >> >> >> >> My understanding is that as we build out the CLI for Apache >>Cordova, >> >> >>then >> >> >> config.xml support will be added. >> >> >> >> >> >> Michael >> >> >> >> >> >> On Mon, May 28, 2012 at 1:12 PM, Gord Tanner >> wrote: >> >> >> >> >> >> > Hey, >> >> >> > >> >> >> > I am wondering if cordova is going to continue aligning to the >>W3C >> >> >> > config.xml? >> >> >> > >> >> >> > Unless I am mistaken it looks like BlackBerry and PlayBook are >>the >> >> >>only >> >> >> > platforms that are currently using it. Is there plans to use >> >> >>config.xml >> >> >> > more cross platform? >> >> >> > >> >> >> >> >> >> >> >> >> --------------------------------------------------------------------- >> >> 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. >> >> >> > > > >--=20 >Gord Tanner >Senior Developer / Code Poet >tinyHippos Inc. >@tinyhippos