With the Cordova plugins please make sure that they do conform with the
Cordova plugin specification[1]. Our tools can only install such plugins to
the IDE . Also Cordova CLI can only work with them. I can help you with
their testing when you come to that point.
Our tools can discover plugins and install them if they are on a npmjs
registry, an example of such registry is
http://registry.cordova.io. I
suggest that if we end up with multiple plugins from Aerogear. We either
need to set up a npmjs registry for them or get them into
registry.cordova.io. If we have a single plugin and can not get that into
cordova's registry, it may still be worth to run that registry so that it
is discoverable (predictably Cordova CLI also uses npmjs registries).
As a note currently PushPlugin is not on any of the cordova plugin
registries. I am not even sure if there is a version of it that conforms to
Cordova plugin spec. It may be worth to give a hand to it to make it easier
for our users.
[1]
http://cordova.apache.org/docs/en/3.0.0/guide_hybrid_plugins_index.md.htm...
--
Gorkem
--
Gorkem
On Wed, Sep 18, 2013 at 8:22 AM, Lucas Holmquist <lholmqui(a)redhat.com>wrote:
On Sep 18, 2013, at 4:37 AM, Matthias Wessendorf <matzew(a)apache.org>
wrote:
The OTP bits might be a very good start.
+1. on the plane back from PhoneGap Day, i started the skeleton of what i
thought this could be.
Once we added OTP, our little community got some visibility. Having a
Cordova plugin that leverages our Android/iOS OTP bits would be super
awesome
-M
On Wed, Sep 18, 2013 at 9:40 AM, Erik Jan de Wit <edewit(a)redhat.com>wrote:
> Hi,
>
> As you all know cordova is a great way to use the native bits from
> android or iOS in a HTML5 / javascript application. There are already ideas
> [1] but we could create a cordova wrapper for all AeroGear functionality.
> The easiest way to start is use the AeroGear.js api as a start and then on
> the native side we use the native implementation.
>
> Also to start using unified push with cordova requires quite a lot of
> setup, we could make that a lot simpler if we incorporate that into our own
> plugin.
>
> [1]
https://issues.jboss.org/browse/AEROGEAR-772
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev(a)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
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev
_______________________________________________
aerogear-dev mailing list
aerogear-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/aerogear-dev