[aerogear-dev] javascript api sync

Matthias Wessendorf matzew at apache.org
Tue Nov 19 05:41:22 EST 2013


On Tue, Nov 19, 2013 at 11:38 AM, Erik Jan de Wit <edewit at redhat.com> wrote:

> The cordova crypto plugin can't follow the javascript one-to-one as all
> the calls have to be asynchronous. So it's not as simple as a dependency,
> I'll have to change the javascript api of the plugin to follow the
> javascript. It's a bit dependency hell as it depends on everything iOS
> android and javascript. Perhaps it would be good for Cordova to have it's
> own deadline.
>

Thanks for the insights! This now also explains my first question: why not
'addressed' last week.

IMO this is really something we need to address... So yes, I am def. for a
separate release/life-cycle!


-Matthias


>
> Cheers,
> Erik Jan
>
> On 19 Nov,2013, at 11:14 , Matthias Wessendorf <matzew at apache.org> wrote:
>
> A few questions:
>
> * The best is to "suck in" the 'latest' JS dependency via npm (or similar,
> or by hand), right ?
>
> * If yes... doesn't it generally make sense to release the Cordova bits a
> bit AFTER its core dependencies ? On iOS we did the same (yesterday I moved
> the Crypto to CocoaPods, today Christos is sucking that in, via CocoaPods
> (on aerogear-ios)
>
>
> -Matthias
>
>
> On Tue, Nov 19, 2013 at 10:59 AM, Matthias Wessendorf <matzew at apache.org>wrote:
>
>>
>>
>>
>> On Tue, Nov 19, 2013 at 10:21 AM, Erik Jan de Wit <edewit at redhat.com>wrote:
>>
>>> Hi,
>>>
>>> Last tuesday the PR for the new javascript crypto api landed, because I
>>> developed the crypto cordova plugin based on the 'old' api there is now a
>>> discrepancy between the 'current' javascript crypto api and the cordova
>>> one. We could change that this week as there aren't that many people that
>>> use the crypto cordova plugin, but we have frozen so what is the point of a
>>> freeze when we change things regardless?
>>>
>>> Anyway I think we could still change this what do you think?
>>>
>>
>> yes, I think updating the Cordova bits makes sense.
>>
>> Quote from yesterdays team meeting:
>> <quote>
>> 15:22:50 <qmx> #info qmx proposes to freeze this friday (as an exception
>> to android), freeze this friday, release next week, announce after the
>> holiday"
>> </quote>
>>
>> So the freeze is this week, and IMO that's perfectly fine to update it.
>>
>>
>> That said, but I think the only question I really have is why this update
>> to reflect the 'new' API was not addressed already last week.
>>
>> Greetings,
>> Matthias
>>
>>
>>
>>>
>>> Cheers,
>>> Erik Jan
>>>
>>> p.s.
>>> have a look at the differences:
>>>
>>> current javascript api
>>>
>>> https://github.com/aerogear/aerogear-js/blob/master/tests/unit/crypto/aerogear.crypto.js
>>>
>>> current cordova api
>>>
>>> https://github.com/edewit/aerogear.org/blob/f2fe8a48b2f9d9c581e62292abeaf788c0c4338e/docs/guides/aerogear-cordova/AerogearCordovaCrypto.asciidoc
>>>
>>> _______________________________________________
>>> aerogear-dev mailing list
>>> aerogear-dev at lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>>
>>
>>
>>
>> --
>> Matthias Wessendorf
>>
>> blog: http://matthiaswessendorf.wordpress.com/
>> sessions: http://www.slideshare.net/mwessendorf
>> twitter: http://twitter.com/mwessendorf
>>
>
>
>
> --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20131119/6c3aa713/attachment.html 


More information about the aerogear-dev mailing list