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 dan.silivestru@gmail.com
 designates 74.125.82.43 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <CBEA6A1A.6EE2%fil@adobe.com>
References: 
 <CAESi+4_=1DAKXe7XDOe1w8ecqF23KfBRAPmRaO=jhVAzJWL6AQ@mail.gmail.com>
 <CBEA6A1A.6EE2%fil@adobe.com>
From: Dan Silivestru <dan.silivestru@gmail.com>
Date: Tue, 29 May 2012 14:59:41 -0400
Message-ID: 
 <CAGfeOkdZsncJQnsOhPC0Fr+ta_KKppRqR92x5qJcndjQTiOh4Q@mail.gmail.com>
Subject: Re: Cordova and config.xml
To: callback-dev@incubator.apache.org
Content-Type: multipart/alternative; boundary=0016e6d99a9211094a04c1317140

--0016e6d99a9211094a04c1317140
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Damn it! I was just typing it up... I'll have to wait for the next
opportunity now :-)

On Tue, May 29, 2012 at 2:57 PM, Filip Maj <fil@adobe.com> wrote:

> I'm still waiting for the first standards joke in this thread.
>
> On 5/29/12 11:55 AM, "Gord Tanner" <gord@tinyhippos.com> 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 <deedubbu@gmail.com> 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
> >> <michael@michaelbrooks.ca> 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 y=
ou
> >> > elaborate on how BB10 will be deviating even further? Is there a lin=
k
> >>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:
> >> >
> >>
> >>
> 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 <kwallis@rim.com> wrote=
:
> >> >
> >> >> Laurent and I were just chatting about this.  Certainly feel that w=
e
> >> >> should have a common shared format for application metadata.  Defau=
lt
> >> >> 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 wi=
th
> >> BB10
> >> >> we will have to go even farther down the custom namespace route.  W=
e
> >> (RIM)
> >> >> may need to actively diverge on some concepts that might have Widge=
t
> >> >> 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, bu=
t
> >> 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" <shazron@gmail.com> 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
> >> >> ><michael@michaelbrooks.ca>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 <gtanner@gmail.com>
> >> 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 t=
he
> >> >> 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.
> >> >>
> >>
> >
> >
> >
> >--
> >Gord Tanner
> >Senior Developer / Code Poet
> >tinyHippos Inc.
> >@tinyhippos
>
>


--=20
Dan Silivestru
+1 (519) 589-3624

--0016e6d99a9211094a04c1317140--