<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Sep 13, 2013 at 4:44 PM, Corinne Krych <span dir="ltr"><<a href="mailto:corinnekrych@gmail.com" target="_blank">corinnekrych@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">+1<br>
I've got a title for the blog post: "iOS polyfill on ..."<br>
could be a funny and nice blog post tbh<br></blockquote><div><br></div><div>+1 on blog post, like Summers suggested</div><div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="HOEnZb"><div class="h5">On Sep 13, 2013, at 4:34 PM, Summers Pittman <<a href="mailto:supittma@redhat.com">supittma@redhat.com</a>> wrote:<br>
<br>
> On Fri 13 Sep 2013 09:30:47 AM EDT, Tadeas Kriz wrote:<br>
>> Hey,<br>
>><br>
>> me again with another thing to share. On iOS, when the application is<br>
>> not in foreground, the system decides what to do with it. So I was<br>
>> thinking, that for Android, there might be some kind of example<br>
>> implementation of MessageHandler, that would behave similar to iOS.<br>
>><br>
>> It might use the "sound", "alert" and maybe even the "badge" properties.<br>
>><br>
><br>
> What if the message format is just a bunch of properties for a<br>
> notification builder and the handler tosses them into a notification<br>
> and pops it up for you?<br>
><br>
> My initial reaction is if a developer is only targetting Android we<br>
> probably shouldn't encourage them to use iOS terminology.<br>
><br>
> I like the idea this for a blog post / tutorial post instead of putting<br>
> it in the default project.<br>
><br>
>> I've made a ticket before, so more information can be found there:<br>
>><br>
>> <a href="https://issues.jboss.org/browse/AGDROID-118" target="_blank">https://issues.jboss.org/browse/AGDROID-118</a><br>
>><br>
>><br>
>> _______________________________________________<br>
>> aerogear-dev mailing list<br>
>> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
>> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
><br>
><br>
> _______________________________________________<br>
> aerogear-dev mailing list<br>
> <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
<br>
_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br>Matthias Wessendorf <br><br>blog: <a href="http://matthiaswessendorf.wordpress.com/" target="_blank">http://matthiaswessendorf.wordpress.com/</a><br>
sessions: <a href="http://www.slideshare.net/mwessendorf" target="_blank">http://www.slideshare.net/mwessendorf</a><br>twitter: <a href="http://twitter.com/mwessendorf" target="_blank">http://twitter.com/mwessendorf</a>
</div></div>