incubator-callback-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Filip Maj <>
Subject Re: Consistent implementation of the whitelist
Date Tue, 31 Jan 2012 21:46:12 GMT
Here is the w3c one: it covers 95% of cases

Here is how PhoneGap Build employs config.xml:

The phonegap build docs are an excellent starting point, I think.

On 12-01-31 12:33 PM, "Laurent Hasson" <> wrote:

>One configuration file to rule them all... Is the idea to still remain
>"as faithful as possible" to the Widget's config.xml spec, or are we now
>taking more liberties? I think that spec is pretty much done, and
>wondering if there is any other implementation out there. More pointedly,
>where is the spec for our config.xml?
>Thank You
>- LDH (Laurent Hasson)                         -
>- Technical Director, BlackBerry Web Platform  -
>- Research In Motion                           -
>- Email:                       -
>- Mobile: 646-460-7066                         -
>- Twitter: @ldhasson
>"Ha ha ha... He doesn't know how to use the three seashells!" - Erwin
>-----Original Message-----
>From: Patrick Mueller []
>Sent: Tuesday, January 31, 2012 3:31 PM
>Subject: Re: Consistent implementation of the whitelist
>On Tue, Jan 31, 2012 at 15:21, Shazron <> wrote:
>> So let's all agree on the structure of the plugins and whitelist in
>> config.xml (if we all decide to go this route that is).
>sounds good!  What XML parsers do people use w/node.js?
>> We could modify the iOS Info.plist during build time, yes - by running
>> a script post-build (this is part of a project's Build Phase).
>As much as is possible/reasonable, I'd love to head in this direction -
>build out platform-specific stuff (iOS .plist's) based on the One True
>Configuration FileT during "build" stages.
>Patrick Mueller
>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.

View raw message