[aerogear-dev] Issues with Aerogear on Cordova

[Miguel Lemos]

Dear Matthias,

According to the information posted in the url below, I can send (and read)
several parameters / keys in the scope of the notification service (as it
should be...):

http://aerogear.org/docs/specs/aerogear-push-messages/

According to the values on it, the receiver should have the capacity to
decide what to do next.

First, and the easiest thing: don't show  the "Alert" text, but any other
part of  content received and / or change "Alert" to  another language, for
instance.

Second, if I create (for instance) a lat, lon and rad parameters, I can
decide if I show the notification immediately, or only when the user
reaches a matchable location, within a given radius.
This is just an example of the freedom that must be available to decide
what to do according to a given parameter that the software on the client's
side can interpret. The message itself may not be the most important part
of the whole thing...

So, the question is: how can I read those parameters / keys before deciding
to do with the notification? Through a "regular" object keys iterator?
Thank you very much again. If there's some place in the documentation where
I can understand that, please let me know.

Miguel



On Wed, Feb 19, 2014 at 1:34 PM, Matthias Wessendorf <matzew at apache.org>wrote:

> Awesome,
>
> we are interested in hearing your feedback.
>
> Good luck w/ the development process!
>
> -Matthias
>
>
> On Wed, Feb 19, 2014 at 2:29 PM, Miguel Lemos <miguel21op at gmail.com>wrote:
>
>> Thanks. Of course I'll give you my feedback ;-)
>>
>> I've some questions about the service as a whole, but I'll make some more
>> testing and then I'll let you know.
>>
>> Thank you very much again for your attention.
>>
>> All the best,
>>
>> Miguel
>>
>>
>> On Wed, Feb 19, 2014 at 1:25 PM, Matthias Wessendorf <matzew at apache.org>wrote:
>>
>>>
>>>
>>>
>>> On Wed, Feb 19, 2014 at 2:18 PM, Miguel Lemos <miguel21op at gmail.com>wrote:
>>>
>>>> Hi Matthias,
>>>>
>>>> One of the biggest reasons I'm testing this solutions is because iOS!
>>>>
>>>> Once we already developed a full native Android push (considering
>>>> geofencing)  notification service. The issue is to port our solution to iOS
>>>> (not only the notifications, but everything). That's why I'm personally
>>>> testing Cordova on Android and already partially on IOS. So far so good..
>>>>
>>>
>>> Sounds very interesting. If you are interested, let us know how it goes.
>>>
>>>
>>>>
>>>> I'm starting with Android because it's easier to me. But next week I
>>>> want to test your solution  with iOS. Why? Is there any problem?
>>>>
>>>
>>> No problem there at all :-) I was just curious if you target Android
>>> first/only.
>>>
>>> Greetings,
>>> Matthias
>>>
>>>
>>>>
>>>> Thanks
>>>>
>>>> Miguel
>>>>
>>>>
>>>>
>>>> On Wed, Feb 19, 2014 at 1:04 PM, Matthias Wessendorf <matzew at apache.org
>>>> > wrote:
>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Wed, Feb 19, 2014 at 1:20 PM, Miguel Lemos <miguel21op at gmail.com>wrote:
>>>>>
>>>>>> Hi all,
>>>>>>
>>>>>> I tested and now it works, thanks.
>>>>>>
>>>>>
>>>>> glad it all worked out
>>>>>
>>>>>
>>>>>>
>>>>>> When I tried for  the first time, I tried with the function global,
>>>>>> reflecting the Github example. But as it didn't work (because of the "damn"
>>>>>> URL issue...) I tried several things, one of them being put the alert
>>>>>> function inside the deviceready event. Of course, when I solved the URL
>>>>>> thing I never more remembered to put it outside again...
>>>>>>
>>>>>
>>>>> Things like that might happen.
>>>>>
>>>>> Regarding the URL, we will try to update the OpenShift blog post.
>>>>>
>>>>> I just checkout project documentation, and it looks like they are
>>>>> already 'right'.
>>>>>
>>>>>
>>>>>
>>>>> Wondering: Are you building Cordova clients for Android only, or do
>>>>> you plan to use the iOS platform as well ?
>>>>>
>>>>> Greetings,
>>>>> Matthias
>>>>>
>>>>>
>>>>>>
>>>>>>
>>>>>> _______________________________________________
>>>>>> 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
>>>>>
>>>>> _______________________________________________
>>>>> 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
>>>
>>> _______________________________________________
>>> 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
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140219/1fb0cc53/attachment-0001.html