cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tommy-Carlos Williams <to...@devgeeks.org>
Subject Re: Android - Removing the .api namespace
Date Tue, 30 Jul 2013 19:24:25 GMT
Shazron,

As always, you rule.. 

Also, as an aside, how did I not know about this questions repo. Such a good resource.

- tommy



On 30/07/2013, at 12:18 PM, Shazron <shazron@gmail.com> wrote:

> I would - I'll see if I can write up a blog post later today based on my
> answer here: https://github.com/shazron/phonegap-questions/issues/13
> 
> 
> 
> 
> On Tue, Jul 30, 2013 at 12:12 PM, Tommy-Carlos Williams
> <tommy@devgeeks.org>wrote:
> 
>> I don't wanna sound like I am being a pain, but really… the whole
>> deprecation policy thing is a bit pointless if it's not followed, and not
>> noisy.
>> 
>> Most people who use plugins, use other people's plugins, they don't build
>> them themselves.
>> 
>> The use of plugins so far in the life of Cordova has been one of massive
>> pain when in fact it should have been one of Cordova's shining lights.
>> 
>> As one of the people that *does* face developer/end user wrath when this
>> stuff gets broken every few months, it would be really nice if the Cordova
>> devs doing the breaking could also be those to help the fixing.
>> 
>> Blog posts. We need more. I can try to help on this and it's right up my
>> alley, but I am also in the middle of trying to ship an app, so time is
>> tight.
>> 
>> I'll try to write a post on taking a 2.x plugin (say an example from
>> phonegap/phonegap-plugins) and turning it into a working 3.x plugin when I
>> get back to Australia. However, if a week has gone by and I haven't been
>> able to, can anyone put their hand up to do it in my stead? Realistically
>> it needs to cover Android and iOS at a minimum (the plugin ecosystem for
>> the other platforms is much smaller).
>> 
>> Any takers?
>> 
>> - tommy
>> 
>> On 30/07/2013, at 11:57 AM, Joe Bowser <bowserj@gmail.com> wrote:
>> 
>>> So, yeah, remember how I fought this, and then suddenly we came to
>>> consensus because it's better to break everything all at once?
>>> 
>>> https://issues.apache.org/jira/browse/CB-4454
>>> 
>>> Can we actually follow our deprecation policy from now on? There's
>>> people there who are being unreasonable and asking for us to extend
>>> deprecation times to be a year in length because we do things like
>>> this.
>>> 
>>> 
>>> On Wed, Jul 10, 2013 at 12:58 PM, Simon MacDonald
>>> <simon.macdonald@gmail.com> wrote:
>>>> Yup, break everything at once.
>>>> 
>>>> 
>>>> Simon Mac Donald
>>>> http://hi.im/simonmacdonald
>>>> 
>>>> 
>>>> On Wed, Jul 10, 2013 at 3:55 PM, Marcel Kinard <cmarcelk@gmail.com>
>> wrote:
>>>> 
>>>>> Normally being very averse to changing pubic API's, I'm with Andrew and
>>>>> Ian on this. If we are going to be making breaking changes, especially
>> if
>>>>> they are small, do them all at once.
>>>>> 
>>>>> On Jul 9, 2013, at 11:06 PM, Joe Bowser <bowserj@gmail.com> wrote:
>>>>> 
>>>>>> So far, we've asked plugin developers to migrate from the old-style
>>>>>> plugins to CordovaPlugin so that their plugins will work with 3.0.0.
>>>>>> Many plugin developers have already done that.
>>>>> 
>>>>> We have migrated our plugins, but have third-party plugins done the
>> same?
>>>>> Or do they wait for us to release the breaking change and then they are
>>>>> "forced" to update their plugin? I'm guessing the latter, but that is
>> just
>>>>> a guess.
>>>>> 
>>>>> I think what would help here is a Plugin Migration Guide in
>> cordova-docs
>>>>> that gives a nice list of what the plugin developer needs to do. Most
>>>>> plugin devs are probably OK with making changes, as long as we tell
>> them
>>>>> what they need to know.
>>>>> 
>>>>> If there is a third-party plugin that an app developer needs that is
>>>>> abandonware, then they can stick with 2.9.x until the plugin gets
>> updated.
>>>>> 
>>>>> 
>> 
>> 


Mime
View raw message