config.xml - CB-888

[Joe Bowser <bo...@gmail.com>]

Hey

Are we just merging the blacklist and the cordova.xml to make it one
config.xml, or are we having a discussion about the format?   Given
the timeframe for this release, is this something that we want to have
for 2.0?

Joe

Re: config.xml - CB-888

[Patrick Mueller <pm...@gmail.com>]

On Thu, Jul 12, 2012 at 2:13 AM, Dave Johnson <da...@gmail.com>wrote:

> ...
> I think the first thing we need is to just have a cordova.xml file on
> all platforms that has the specifics for that platform that are needed
> at runtime ...
> That make any sense?


Sounds like a good thing to try.

But maybe JSON instead of XML?  Looking at my watch to see what year it is
again ...

Would it make sense to de-generalize the name, from "config" to something
that had "cordova" in it?

-- 
Patrick Mueller
http://muellerware.org

Re: config.xml - CB-888

[Dave Johnson <da...@gmail.com>]

The same is for android in that there are elements in the android
manifest that need to be there and will be duplicates of what's in a
config.xml (e.g. feature elements to permissions on android) so I
think the first thing we need is to just have a cordova.xml file on
all platforms that has the specifics for that platform that are needed
at runtime (e.g. to lookup a plugin mapping or whatever). That file
could be written easily by a developer building an app for a single
platform. Then the config.xml would be layered on top of that and we
would map out certain elements in the config.xml to both the
cordova.xml file on each platform (e.g. for plugins) as well as to the
platform specific config file (e.g. the app name or description).

That make any sense?

On Wed, Jul 11, 2012 at 11:44 AM, Anis KADRI <an...@gmail.com> wrote:
> Cool!
>
> On Wed, Jul 11, 2012 at 11:32 AM, Shazron <sh...@gmail.com> wrote:
>> iOS can switch completely for all settings in Cordova.plist. It's the
>> stuff in the Info.plist (tied to the app, and read by the .app) that
>> needs to be there, like orientations, icons, bundle name etc.
>>
>> On Wed, Jul 11, 2012 at 11:28 AM, Anis KADRI <an...@gmail.com> wrote:
>>> +1 transition period
>>> +1 using build config.xml as a reference point.
>>>
>>> Does iOS need to have both or can it eventually switch completely to
>>> config.xml ?
>>>
>>> On Tue, Jul 10, 2012 at 4:10 PM, Shazron <sh...@gmail.com> wrote:
>>>> For iOS:
>>>> +1 transition period.
>>>> +1 to changing Cordova.plist (which contains the whitelist, plugin
>>>> info, and app settings) into config.xml
>>>>
>>>> On Tue, Jul 10, 2012 at 10:18 AM, Simon MacDonald
>>>> <si...@gmail.com> wrote:
>>>>> +1 transition period.
>>>>> +1 to combining plugins.xml and cordova.xml into config.xml
>>>>>
>>>>> Simon Mac Donald
>>>>> http://hi.im/simonmacdonald
>>>>>
>>>>>
>>>>> On Tue, Jul 10, 2012 at 12:15 PM, Michael Brooks
>>>>> <mi...@michaelbrooks.ca> wrote:
>>>>>> +1 transition period.
>>>>>> +1 using build.phonegap.com/ docs as a reference point.
>>>>>>
>>>>>> We should take steps to feed out experiences and input back into the W3C
>>>>>> Community Group (Native Web group) and eventually see it pushed into the
>>>>>> main W3C Widget Configuration Document.
>>>>>>
>>>>>> Michael
>>>>>>
>>>>>> On Mon, Jul 9, 2012 at 10:59 PM, Filip Maj <fi...@adobe.com> wrote:
>>>>>>
>>>>>>> +1 transition period.
>>>>>>>
>>>>>>> But yes Joe, essentially plugins.xml + cordova.xml -> config.xml.
>>>>>>>
>>>>>>> We should definitely have a discussion about formatting! Starting point in
>>>>>>> my mind would be build.phonegap.com docs for their use of config.xml. Off
>>>>>>> the top of my head and from 35,000 feet:
>>>>>>>
>>>>>>> - <plugin> elements from plugins.xml map to <feature> elements in W3C
>>>>>>> config.xml.
>>>>>>> - <access> elements from cordova.xml already follow the <access> element
>>>>>>> in config.xml.
>>>>>>> - same for <preference>
>>>>>>>
>>>>>>> P.S. BlackBerry WebWorks already does all of this so we get it "for free."
>>>>>>>
>>>>>>> On 7/9/12 4:25 PM, "Brian LeRoux" <b...@brian.io> wrote:
>>>>>>>
>>>>>>> >thinking we should add support for config.xml before we remove
>>>>>>> >anything...have a transition period ala deprecation policy
>>>>>>> >
>>>>>>> >On Mon, Jul 9, 2012 at 12:58 PM, Joe Bowser <bo...@gmail.com> wrote:
>>>>>>> >> Hey
>>>>>>> >>
>>>>>>> >> Are we just merging the blacklist and the cordova.xml to make it one
>>>>>>> >> config.xml, or are we having a discussion about the format?   Given
>>>>>>> >> the timeframe for this release, is this something that we want to have
>>>>>>> >> for 2.0?
>>>>>>> >>
>>>>>>> >> Joe
>>>>>>>
>>>>>>>

Re: config.xml - CB-888

[Anis KADRI <an...@gmail.com>]

Cool!

On Wed, Jul 11, 2012 at 11:32 AM, Shazron <sh...@gmail.com> wrote:
> iOS can switch completely for all settings in Cordova.plist. It's the
> stuff in the Info.plist (tied to the app, and read by the .app) that
> needs to be there, like orientations, icons, bundle name etc.
>
> On Wed, Jul 11, 2012 at 11:28 AM, Anis KADRI <an...@gmail.com> wrote:
>> +1 transition period
>> +1 using build config.xml as a reference point.
>>
>> Does iOS need to have both or can it eventually switch completely to
>> config.xml ?
>>
>> On Tue, Jul 10, 2012 at 4:10 PM, Shazron <sh...@gmail.com> wrote:
>>> For iOS:
>>> +1 transition period.
>>> +1 to changing Cordova.plist (which contains the whitelist, plugin
>>> info, and app settings) into config.xml
>>>
>>> On Tue, Jul 10, 2012 at 10:18 AM, Simon MacDonald
>>> <si...@gmail.com> wrote:
>>>> +1 transition period.
>>>> +1 to combining plugins.xml and cordova.xml into config.xml
>>>>
>>>> Simon Mac Donald
>>>> http://hi.im/simonmacdonald
>>>>
>>>>
>>>> On Tue, Jul 10, 2012 at 12:15 PM, Michael Brooks
>>>> <mi...@michaelbrooks.ca> wrote:
>>>>> +1 transition period.
>>>>> +1 using build.phonegap.com/ docs as a reference point.
>>>>>
>>>>> We should take steps to feed out experiences and input back into the W3C
>>>>> Community Group (Native Web group) and eventually see it pushed into the
>>>>> main W3C Widget Configuration Document.
>>>>>
>>>>> Michael
>>>>>
>>>>> On Mon, Jul 9, 2012 at 10:59 PM, Filip Maj <fi...@adobe.com> wrote:
>>>>>
>>>>>> +1 transition period.
>>>>>>
>>>>>> But yes Joe, essentially plugins.xml + cordova.xml -> config.xml.
>>>>>>
>>>>>> We should definitely have a discussion about formatting! Starting point in
>>>>>> my mind would be build.phonegap.com docs for their use of config.xml. Off
>>>>>> the top of my head and from 35,000 feet:
>>>>>>
>>>>>> - <plugin> elements from plugins.xml map to <feature> elements in W3C
>>>>>> config.xml.
>>>>>> - <access> elements from cordova.xml already follow the <access> element
>>>>>> in config.xml.
>>>>>> - same for <preference>
>>>>>>
>>>>>> P.S. BlackBerry WebWorks already does all of this so we get it "for free."
>>>>>>
>>>>>> On 7/9/12 4:25 PM, "Brian LeRoux" <b...@brian.io> wrote:
>>>>>>
>>>>>> >thinking we should add support for config.xml before we remove
>>>>>> >anything...have a transition period ala deprecation policy
>>>>>> >
>>>>>> >On Mon, Jul 9, 2012 at 12:58 PM, Joe Bowser <bo...@gmail.com> wrote:
>>>>>> >> Hey
>>>>>> >>
>>>>>> >> Are we just merging the blacklist and the cordova.xml to make it one
>>>>>> >> config.xml, or are we having a discussion about the format?   Given
>>>>>> >> the timeframe for this release, is this something that we want to have
>>>>>> >> for 2.0?
>>>>>> >>
>>>>>> >> Joe
>>>>>>
>>>>>>

Re: config.xml - CB-888

[Shazron <sh...@gmail.com>]

iOS can switch completely for all settings in Cordova.plist. It's the
stuff in the Info.plist (tied to the app, and read by the .app) that
needs to be there, like orientations, icons, bundle name etc.

On Wed, Jul 11, 2012 at 11:28 AM, Anis KADRI <an...@gmail.com> wrote:
> +1 transition period
> +1 using build config.xml as a reference point.
>
> Does iOS need to have both or can it eventually switch completely to
> config.xml ?
>
> On Tue, Jul 10, 2012 at 4:10 PM, Shazron <sh...@gmail.com> wrote:
>> For iOS:
>> +1 transition period.
>> +1 to changing Cordova.plist (which contains the whitelist, plugin
>> info, and app settings) into config.xml
>>
>> On Tue, Jul 10, 2012 at 10:18 AM, Simon MacDonald
>> <si...@gmail.com> wrote:
>>> +1 transition period.
>>> +1 to combining plugins.xml and cordova.xml into config.xml
>>>
>>> Simon Mac Donald
>>> http://hi.im/simonmacdonald
>>>
>>>
>>> On Tue, Jul 10, 2012 at 12:15 PM, Michael Brooks
>>> <mi...@michaelbrooks.ca> wrote:
>>>> +1 transition period.
>>>> +1 using build.phonegap.com/ docs as a reference point.
>>>>
>>>> We should take steps to feed out experiences and input back into the W3C
>>>> Community Group (Native Web group) and eventually see it pushed into the
>>>> main W3C Widget Configuration Document.
>>>>
>>>> Michael
>>>>
>>>> On Mon, Jul 9, 2012 at 10:59 PM, Filip Maj <fi...@adobe.com> wrote:
>>>>
>>>>> +1 transition period.
>>>>>
>>>>> But yes Joe, essentially plugins.xml + cordova.xml -> config.xml.
>>>>>
>>>>> We should definitely have a discussion about formatting! Starting point in
>>>>> my mind would be build.phonegap.com docs for their use of config.xml. Off
>>>>> the top of my head and from 35,000 feet:
>>>>>
>>>>> - <plugin> elements from plugins.xml map to <feature> elements in W3C
>>>>> config.xml.
>>>>> - <access> elements from cordova.xml already follow the <access> element
>>>>> in config.xml.
>>>>> - same for <preference>
>>>>>
>>>>> P.S. BlackBerry WebWorks already does all of this so we get it "for free."
>>>>>
>>>>> On 7/9/12 4:25 PM, "Brian LeRoux" <b...@brian.io> wrote:
>>>>>
>>>>> >thinking we should add support for config.xml before we remove
>>>>> >anything...have a transition period ala deprecation policy
>>>>> >
>>>>> >On Mon, Jul 9, 2012 at 12:58 PM, Joe Bowser <bo...@gmail.com> wrote:
>>>>> >> Hey
>>>>> >>
>>>>> >> Are we just merging the blacklist and the cordova.xml to make it one
>>>>> >> config.xml, or are we having a discussion about the format?   Given
>>>>> >> the timeframe for this release, is this something that we want to have
>>>>> >> for 2.0?
>>>>> >>
>>>>> >> Joe
>>>>>
>>>>>

Re: config.xml - CB-888

[Anis KADRI <an...@gmail.com>]

+1 transition period
+1 using build config.xml as a reference point.

Does iOS need to have both or can it eventually switch completely to
config.xml ?

On Tue, Jul 10, 2012 at 4:10 PM, Shazron <sh...@gmail.com> wrote:
> For iOS:
> +1 transition period.
> +1 to changing Cordova.plist (which contains the whitelist, plugin
> info, and app settings) into config.xml
>
> On Tue, Jul 10, 2012 at 10:18 AM, Simon MacDonald
> <si...@gmail.com> wrote:
>> +1 transition period.
>> +1 to combining plugins.xml and cordova.xml into config.xml
>>
>> Simon Mac Donald
>> http://hi.im/simonmacdonald
>>
>>
>> On Tue, Jul 10, 2012 at 12:15 PM, Michael Brooks
>> <mi...@michaelbrooks.ca> wrote:
>>> +1 transition period.
>>> +1 using build.phonegap.com/ docs as a reference point.
>>>
>>> We should take steps to feed out experiences and input back into the W3C
>>> Community Group (Native Web group) and eventually see it pushed into the
>>> main W3C Widget Configuration Document.
>>>
>>> Michael
>>>
>>> On Mon, Jul 9, 2012 at 10:59 PM, Filip Maj <fi...@adobe.com> wrote:
>>>
>>>> +1 transition period.
>>>>
>>>> But yes Joe, essentially plugins.xml + cordova.xml -> config.xml.
>>>>
>>>> We should definitely have a discussion about formatting! Starting point in
>>>> my mind would be build.phonegap.com docs for their use of config.xml. Off
>>>> the top of my head and from 35,000 feet:
>>>>
>>>> - <plugin> elements from plugins.xml map to <feature> elements in W3C
>>>> config.xml.
>>>> - <access> elements from cordova.xml already follow the <access> element
>>>> in config.xml.
>>>> - same for <preference>
>>>>
>>>> P.S. BlackBerry WebWorks already does all of this so we get it "for free."
>>>>
>>>> On 7/9/12 4:25 PM, "Brian LeRoux" <b...@brian.io> wrote:
>>>>
>>>> >thinking we should add support for config.xml before we remove
>>>> >anything...have a transition period ala deprecation policy
>>>> >
>>>> >On Mon, Jul 9, 2012 at 12:58 PM, Joe Bowser <bo...@gmail.com> wrote:
>>>> >> Hey
>>>> >>
>>>> >> Are we just merging the blacklist and the cordova.xml to make it one
>>>> >> config.xml, or are we having a discussion about the format?   Given
>>>> >> the timeframe for this release, is this something that we want to have
>>>> >> for 2.0?
>>>> >>
>>>> >> Joe
>>>>
>>>>

Re: config.xml - CB-888

[Shazron <sh...@gmail.com>]

For iOS:
+1 transition period.
+1 to changing Cordova.plist (which contains the whitelist, plugin
info, and app settings) into config.xml

On Tue, Jul 10, 2012 at 10:18 AM, Simon MacDonald
<si...@gmail.com> wrote:
> +1 transition period.
> +1 to combining plugins.xml and cordova.xml into config.xml
>
> Simon Mac Donald
> http://hi.im/simonmacdonald
>
>
> On Tue, Jul 10, 2012 at 12:15 PM, Michael Brooks
> <mi...@michaelbrooks.ca> wrote:
>> +1 transition period.
>> +1 using build.phonegap.com/ docs as a reference point.
>>
>> We should take steps to feed out experiences and input back into the W3C
>> Community Group (Native Web group) and eventually see it pushed into the
>> main W3C Widget Configuration Document.
>>
>> Michael
>>
>> On Mon, Jul 9, 2012 at 10:59 PM, Filip Maj <fi...@adobe.com> wrote:
>>
>>> +1 transition period.
>>>
>>> But yes Joe, essentially plugins.xml + cordova.xml -> config.xml.
>>>
>>> We should definitely have a discussion about formatting! Starting point in
>>> my mind would be build.phonegap.com docs for their use of config.xml. Off
>>> the top of my head and from 35,000 feet:
>>>
>>> - <plugin> elements from plugins.xml map to <feature> elements in W3C
>>> config.xml.
>>> - <access> elements from cordova.xml already follow the <access> element
>>> in config.xml.
>>> - same for <preference>
>>>
>>> P.S. BlackBerry WebWorks already does all of this so we get it "for free."
>>>
>>> On 7/9/12 4:25 PM, "Brian LeRoux" <b...@brian.io> wrote:
>>>
>>> >thinking we should add support for config.xml before we remove
>>> >anything...have a transition period ala deprecation policy
>>> >
>>> >On Mon, Jul 9, 2012 at 12:58 PM, Joe Bowser <bo...@gmail.com> wrote:
>>> >> Hey
>>> >>
>>> >> Are we just merging the blacklist and the cordova.xml to make it one
>>> >> config.xml, or are we having a discussion about the format?   Given
>>> >> the timeframe for this release, is this something that we want to have
>>> >> for 2.0?
>>> >>
>>> >> Joe
>>>
>>>

Re: config.xml - CB-888

[Simon MacDonald <si...@gmail.com>]

+1 transition period.
+1 to combining plugins.xml and cordova.xml into config.xml

Simon Mac Donald
http://hi.im/simonmacdonald


On Tue, Jul 10, 2012 at 12:15 PM, Michael Brooks
<mi...@michaelbrooks.ca> wrote:
> +1 transition period.
> +1 using build.phonegap.com/ docs as a reference point.
>
> We should take steps to feed out experiences and input back into the W3C
> Community Group (Native Web group) and eventually see it pushed into the
> main W3C Widget Configuration Document.
>
> Michael
>
> On Mon, Jul 9, 2012 at 10:59 PM, Filip Maj <fi...@adobe.com> wrote:
>
>> +1 transition period.
>>
>> But yes Joe, essentially plugins.xml + cordova.xml -> config.xml.
>>
>> We should definitely have a discussion about formatting! Starting point in
>> my mind would be build.phonegap.com docs for their use of config.xml. Off
>> the top of my head and from 35,000 feet:
>>
>> - <plugin> elements from plugins.xml map to <feature> elements in W3C
>> config.xml.
>> - <access> elements from cordova.xml already follow the <access> element
>> in config.xml.
>> - same for <preference>
>>
>> P.S. BlackBerry WebWorks already does all of this so we get it "for free."
>>
>> On 7/9/12 4:25 PM, "Brian LeRoux" <b...@brian.io> wrote:
>>
>> >thinking we should add support for config.xml before we remove
>> >anything...have a transition period ala deprecation policy
>> >
>> >On Mon, Jul 9, 2012 at 12:58 PM, Joe Bowser <bo...@gmail.com> wrote:
>> >> Hey
>> >>
>> >> Are we just merging the blacklist and the cordova.xml to make it one
>> >> config.xml, or are we having a discussion about the format?   Given
>> >> the timeframe for this release, is this something that we want to have
>> >> for 2.0?
>> >>
>> >> Joe
>>
>>

Re: config.xml - CB-888

[Michael Brooks <mi...@michaelbrooks.ca>]

+1 transition period.
+1 using build.phonegap.com/ docs as a reference point.

We should take steps to feed out experiences and input back into the W3C
Community Group (Native Web group) and eventually see it pushed into the
main W3C Widget Configuration Document.

Michael

On Mon, Jul 9, 2012 at 10:59 PM, Filip Maj <fi...@adobe.com> wrote:

> +1 transition period.
>
> But yes Joe, essentially plugins.xml + cordova.xml -> config.xml.
>
> We should definitely have a discussion about formatting! Starting point in
> my mind would be build.phonegap.com docs for their use of config.xml. Off
> the top of my head and from 35,000 feet:
>
> - <plugin> elements from plugins.xml map to <feature> elements in W3C
> config.xml.
> - <access> elements from cordova.xml already follow the <access> element
> in config.xml.
> - same for <preference>
>
> P.S. BlackBerry WebWorks already does all of this so we get it "for free."
>
> On 7/9/12 4:25 PM, "Brian LeRoux" <b...@brian.io> wrote:
>
> >thinking we should add support for config.xml before we remove
> >anything...have a transition period ala deprecation policy
> >
> >On Mon, Jul 9, 2012 at 12:58 PM, Joe Bowser <bo...@gmail.com> wrote:
> >> Hey
> >>
> >> Are we just merging the blacklist and the cordova.xml to make it one
> >> config.xml, or are we having a discussion about the format?   Given
> >> the timeframe for this release, is this something that we want to have
> >> for 2.0?
> >>
> >> Joe
>
>

Re: config.xml - CB-888

[Filip Maj <fi...@adobe.com>]

+1 transition period.

But yes Joe, essentially plugins.xml + cordova.xml -> config.xml.

We should definitely have a discussion about formatting! Starting point in
my mind would be build.phonegap.com docs for their use of config.xml. Off
the top of my head and from 35,000 feet:

- <plugin> elements from plugins.xml map to <feature> elements in W3C
config.xml.
- <access> elements from cordova.xml already follow the <access> element
in config.xml.
- same for <preference>

P.S. BlackBerry WebWorks already does all of this so we get it "for free."

On 7/9/12 4:25 PM, "Brian LeRoux" <b...@brian.io> wrote:

>thinking we should add support for config.xml before we remove
>anything...have a transition period ala deprecation policy
>
>On Mon, Jul 9, 2012 at 12:58 PM, Joe Bowser <bo...@gmail.com> wrote:
>> Hey
>>
>> Are we just merging the blacklist and the cordova.xml to make it one
>> config.xml, or are we having a discussion about the format?   Given
>> the timeframe for this release, is this something that we want to have
>> for 2.0?
>>
>> Joe

Re: config.xml - CB-888

[Brian LeRoux <b...@brian.io>]

thinking we should add support for config.xml before we remove
anything...have a transition period ala deprecation policy

On Mon, Jul 9, 2012 at 12:58 PM, Joe Bowser <bo...@gmail.com> wrote:
> Hey
>
> Are we just merging the blacklist and the cordova.xml to make it one
> config.xml, or are we having a discussion about the format?   Given
> the timeframe for this release, is this something that we want to have
> for 2.0?
>
> Joe