[Android] W3C Widget Spec Work: Changing Plugin to Feature

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

Hey

I know that this is getting annoying, but I've changed the plugins to
use the W3C feature syntax so that in theory you can take a config.xml
document from a build project and put it in the Cordova project and as
long as you have the plugins Service and Namespace values specified,
the plugins should load.  This is based on the work in CB-1108 and can
be found in my repo here:

https://github.com/infil00p/callback-android/tree/widget_work

I added the old hooks so that things don't break, but this should give
us most of what we need.  Please feel free to look at this, and let me
know whether it should go in or just be junked.

Joe

Re: [Android] W3C Widget Spec Work: Changing Plugin to Feature

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

This makes sense to me if all the platforms are moving towards the
same config.xml as the syntax should be consistent. I also like that
it does not break if someone hasn't upgraded their config.xml to the
new scheme.

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


On Tue, Jul 31, 2012 at 8:55 PM, Brian LeRoux <b...@brian.io> wrote:
> I'm for it. I know its looking like plugins themselves will use a
> package.json but, as Ralph Waldo Emerson would say:
>
> "A foolish consistency is the hobgoblin of little minds, adored by
> little statesmen and philosophers and divines."
>
> A consistent native project metafile is needed. The format, we can
> polish up later.
>
> On Mon, Jul 30, 2012 at 4:35 PM, Joe Bowser <bo...@gmail.com> wrote:
>> Hey
>>
>> I know that this is getting annoying, but I've changed the plugins to
>> use the W3C feature syntax so that in theory you can take a config.xml
>> document from a build project and put it in the Cordova project and as
>> long as you have the plugins Service and Namespace values specified,
>> the plugins should load.  This is based on the work in CB-1108 and can
>> be found in my repo here:
>>
>> https://github.com/infil00p/callback-android/tree/widget_work
>>
>> I added the old hooks so that things don't break, but this should give
>> us most of what we need.  Please feel free to look at this, and let me
>> know whether it should go in or just be junked.
>>
>> Joe

Re: [Android] W3C Widget Spec Work: Changing Plugin to Feature

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

I'm for it. I know its looking like plugins themselves will use a
package.json but, as Ralph Waldo Emerson would say:

"A foolish consistency is the hobgoblin of little minds, adored by
little statesmen and philosophers and divines."

A consistent native project metafile is needed. The format, we can
polish up later.

On Mon, Jul 30, 2012 at 4:35 PM, Joe Bowser <bo...@gmail.com> wrote:
> Hey
>
> I know that this is getting annoying, but I've changed the plugins to
> use the W3C feature syntax so that in theory you can take a config.xml
> document from a build project and put it in the Cordova project and as
> long as you have the plugins Service and Namespace values specified,
> the plugins should load.  This is based on the work in CB-1108 and can
> be found in my repo here:
>
> https://github.com/infil00p/callback-android/tree/widget_work
>
> I added the old hooks so that things don't break, but this should give
> us most of what we need.  Please feel free to look at this, and let me
> know whether it should go in or just be junked.
>
> Joe

Re: [Android] W3C Widget Spec Work: Changing Plugin to Feature

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

Great - iOS will take its cue from Android's transition since we never
had a config.xml in the first place...

On Wed, Aug 29, 2012 at 10:37 AM, Filip Maj <fi...@adobe.com> wrote:
> Nice work Joe!
>
> Next steps would be to start moving to include stuff like app name,
> description, icon, etc. in there.
>
> On 7/31/12 1:35 AM, "Joe Bowser" <bo...@gmail.com> wrote:
>
>>Hey
>>
>>I know that this is getting annoying, but I've changed the plugins to
>>use the W3C feature syntax so that in theory you can take a config.xml
>>document from a build project and put it in the Cordova project and as
>>long as you have the plugins Service and Namespace values specified,
>>the plugins should load.  This is based on the work in CB-1108 and can
>>be found in my repo here:
>>
>>https://github.com/infil00p/callback-android/tree/widget_work
>>
>>I added the old hooks so that things don't break, but this should give
>>us most of what we need.  Please feel free to look at this, and let me
>>know whether it should go in or just be junked.
>>
>>Joe
>

Re: [Android] W3C Widget Spec Work: Changing Plugin to Feature

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

Nice work Joe!

Next steps would be to start moving to include stuff like app name,
description, icon, etc. in there.

On 7/31/12 1:35 AM, "Joe Bowser" <bo...@gmail.com> wrote:

>Hey
>
>I know that this is getting annoying, but I've changed the plugins to
>use the W3C feature syntax so that in theory you can take a config.xml
>document from a build project and put it in the Cordova project and as
>long as you have the plugins Service and Namespace values specified,
>the plugins should load.  This is based on the work in CB-1108 and can
>be found in my repo here:
>
>https://github.com/infil00p/callback-android/tree/widget_work
>
>I added the old hooks so that things don't break, but this should give
>us most of what we need.  Please feel free to look at this, and let me
>know whether it should go in or just be junked.
>
>Joe