Cordova Push - 1.0.3 release (was: Re: Push plugin for Cordova)
by Matthias Wessendorf
Hi,
now that we merged the PR from Martin, and the given fact that the old
plugin registry is read-only, starting tomorrow, I'd like to push a release
of the 1.0.3 version, using this branch:
https://github.com/aerogear/aerogear-cordova-push/tree/1.0.x
Any thoughts?
On Tue, Jul 14, 2015 at 1:35 PM, Martin Murphy <mmurphy(a)redhat.com> wrote:
>
> On 14 Jul 2015, at 12:16, Matthias Wessendorf <matzew(a)apache.org> wrote:
>
>
>
> On Tue, Jul 14, 2015 at 1:11 PM, Martin Murphy <mmurphy(a)redhat.com> wrote:
>
>> Hi Matthias,
>> That would do, however I was think more of this way:
>>
>> https://github.com/mmurphy/aerogear-cordova-push/commit/73198edf6364c93ca...
>> to avoid the risk of pointing at a changing repo.
>>
>
> sounds good!
>
>
>>
>> Can use the one you mentioned, or a combination of them?
>>
>> I can certainly do the PR.
>>
>
> that would be awesome
>
>
> Is this sufficient?
> https://github.com/aerogear/aerogear-cordova-push/pull/74
>
>
>
>>
>>
>> Best Regards,
>> Martin Murphy.
>>
>>
>> On 14 Jul 2015, at 11:59, Matthias Wessendorf <matzew(a)apache.org> wrote:
>>
>> Hi Martin,
>>
>> so - it's basically porting this commit over to the 1.0x branch:
>>
>> https://github.com/aerogear/aerogear-cordova-push/commit/ac1bcc624db98d5a...
>>
>> right ?
>>
>> Mind sending a PR ?
>>
>> On Mon, Jul 13, 2015 at 5:59 PM, Martin Murphy <mmurphy(a)redhat.com>
>> wrote:
>>
>>> Hi folks,
>>> we have a Cordova application that’s using Codrova 3.3.
>>> The application uses org.jboss.aerogear.cordova.push 1.0.2
>>>
>>> When preparing for an android build, there seems to be an problem
>>> installing one of the dependencies of the aurora plugin
>>> An id has been updated: com.vladstirbu.cordova.promise, now has a
>>> different id: es6-promise-plugin.
>>>
>>> The newer plugin 2.0.2 is in the npm registry.
>>>
>>> Is it possible to add a fix and deploy to the old cordova registry so
>>> that it’s usable in 3.x
>>> Is the newer plugin 2.0.2 backward compatible with 1.0.2
>>>
>>> I understand that the ideal approach would be to use a more up-to-date
>>> version of Cordova, and use the latest aurora plugin, however it will take
>>> some time before I will be able to do that.
>>> I’m open to other suggestions also.
>>>
>>> Best Regards,
>>> Martin Murphy.
>>>
>>>
>>>
>>> _______________________________________________
>>> 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
>>
>
>
>
> --
> 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
>
--
Matthias Wessendorf
blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
9 years, 10 months
Push plugin for Cordova
by Martin Murphy
Hi folks,
we have a Cordova application that’s using Codrova 3.3.
The application uses org.jboss.aerogear.cordova.push 1.0.2
When preparing for an android build, there seems to be an problem installing one of the dependencies of the aurora plugin
An id has been updated: com.vladstirbu.cordova.promise, now has a different id: es6-promise-plugin.
The newer plugin 2.0.2 is in the npm registry.
Is it possible to add a fix and deploy to the old cordova registry so that it’s usable in 3.x
Is the newer plugin 2.0.2 backward compatible with 1.0.2
I understand that the ideal approach would be to use a more up-to-date version of Cordova, and use the latest aurora plugin, however it will take some time before I will be able to do that.
I’m open to other suggestions also.
Best Regards,
Martin Murphy.
9 years, 10 months
AGDroid 3.0 improvements
by Summers Pittman
One of the things passos and I have discussed in the past is using
dependency injection (possibly dagger) to reduce a lot of the boiler plate
that is in AGDroid projects (think those nasty config blocks in the
quickstarts which exist for EVERY pipe, oauthmodule, push module, etc). We
decided not to do that in the past because to make it work we would need to
use a gradle plugin, extend all the activity and fragment classes to
interrupt the normal lifecycle, or require the user to call magic methods.
This felt out of touch with the "style" of programming Google was
advocating at the time.
With Google play services 7.5 Google is preparing a gradle plugin which
will consume a services file and provide those values to code via static
variables. (Specifically it injects them into the value.xml file which aidl
turns into values in the Resources object). So we've decided to revisit
the issue.
See Epic : https://issues.jboss.org/browse/AGDROID-476
We want to create a Gradle plugin which will parse ups and keycloak json
files and provide convenient tools for managing interactions with those
objects. These tools right now will consist of providing annotations to
inject modules and interaction with the Activity lifecycle.
In the Push Issue on the Jira I have a quick sample of how the code might
look. You can see there is a LOT less boiler plate. The idea is that all
of the values in the PushRegistrar were parsed from json config file
automatically and the PushRegistrar was instantiated and managed
transparently.
wdyt? What are pain points you've had with AGDroid this style of tool
could help? Should we also make plugins for maven applications?
9 years, 10 months
Index on device tokens
by Douglas Campos
Howdy y'all
While I was doing the migration work I've noticed there's an index for
device tokens on the installation table. The problem is that MySQL InnoDB
doesn't support indexes for VARCHAR columns wider than 255 chars.
Any ideas on how to fix this? Was this really a point of contention? What
motivated the index addition?
Thanks!
9 years, 10 months
Re: [aerogear-dev] UPS Node Sender client categories issue?
by Fink, Miles
Hmm, looks like I emailed to soon. It appears I have a version mix match and that my openshift UPS is on the 1.0.x branch and the Node sender release for that branch doesn’t include an options object for including categories?
-Miles
From: <Fink>, mfink <mfink(a)email.unc.edu<mailto:mfink@email.unc.edu>>
Reply-To: AeroGear Developer Mailing List <aerogear-dev(a)lists.jboss.org<mailto:aerogear-dev@lists.jboss.org>>
Date: Thursday, July 9, 2015 at 1:22 PM
To: "aerogear-dev(a)lists.jboss.org<mailto:aerogear-dev@lists.jboss.org>" <aerogear-dev(a)lists.jboss.org<mailto:aerogear-dev@lists.jboss.org>>
Subject: [aerogear-dev] UPS Node Sender client categories issue?
Hi,
I’m just starting out with UPS (which is awesome btw!) and the Node.js sender client. One thing I’ve noticed is that a message sent from the dashboard with a particular category is sent to only those installations that have that category listed. This works great and is expected. I’m glad there is a way to target specific notification channels, etc.
Sending a notification via the Node Sender client however appears to be sending to everyone’s installation regardless of the categories sent with the message. Here’s a pastie of what my node client call looks like: http://pastie.org/10282358
I’m using:
Unifiedpush Node Sender version 0.8.0-beta1
UPS is the setup via the openshift cartridge, from https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/opensh...
Any pointers would be greatly appreciated. Very well could be me doing it wrong… ;-)
Thanks,
Miles
9 years, 10 months
Rename AGDROID Jira components
by Daniel Passos
Hi Guys,
As you (maybe) know Summers and I started plan and create some Jiras for
the next AeroGear Android release (3.0.0)[1]. We also did some organized in
Jira, one of that was rename some components do be more close to the name
of the GH repos. See the list below
OLD NEW Datamanager Store Datasync Sync Pipeline Pipe OAuth2
Authorization UnifiedPush Push Crypto Security
[1] https://issues.jboss.org/browse/AGDROID/fixforversion/12327585
--
-- Passos
9 years, 10 months
Push Registration with multiple Senders (Android)
by Summers Pittman
Previously GCM allowed multiple senders to be registered with a single
registrationId. Now with the new APIs each senderId gets its own
registration token.
I don't think we ever supported this use case with UPS, we never really
documented an example using multiple senders, and the developer can have a
different registrar for each sender if she needs this feature with the new
(GCM 3.0) APIs.
Because we are already using a major version jump for dropping JDK6, I
propose we change the push registrar to only accept a single senderId
instead of allowing multiple sender Ids. This more accurately reflects
what the service (GCM) is doing under the hood now anyway.
If someone has an objection let me know and we can discuss it. Otherwise
I'll continue down this path.
XOXO,
Summers
9 years, 10 months
