<html><head><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body dir="auto"><div><br><br>Envoyé de mon iPhone</div><div><br>Le 2 févr. 2015 à 16:28, Lucas Holmquist <<a href="mailto:lholmqui@redhat.com">lholmqui@redhat.com</a>> a écrit :<br><br></div><blockquote type="cite"><div><meta http-equiv="Content-Type" content="text/html charset=utf-8"><br class=""><div><blockquote type="cite" class=""><div class="">On Feb 2, 2015, at 10:20 AM, Sebastien Blanc <<a href="mailto:scm.blanc@gmail.com" class="">scm.blanc@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class="">Hi,<div class=""><br class=""></div><div class="">Just bumping up this thread since <a href="https://github.com/aerogear/aerogear-unifiedpush-server/pull/483" class="">https://github.com/aerogear/aerogear-unifiedpush-server/pull/483</a> has been merged .</div><div class="">Do we still plan to change also the wording/flow for the now called variant "Android" ? To something like GCM ? (Check this thread) </div><div class="">Is this the related jira <a href="https://issues.jboss.org/browse/AGPUSH-928" class="">https://issues.jboss.org/browse/AGPUSH-928</a> ?</div></div></div></blockquote><div><br class=""></div><div>Me and matzew discussed this a bit and i think it no longer makes sense to change it. I think the effort to change this and migrate is not worth it.</div></div></div></blockquote>Make sense. Same for APNs with Safari/macOS I presume ? <br><blockquote type="cite"><div><div><div><br class=""></div></div></div></blockquote><br><blockquote type="cite"><div><div><div><br class=""></div><div> </div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div dir="ltr" class=""><div class=""><br class=""></div><div class="">Sebi</div><div class=""><br class=""></div><div class=""><br class=""></div></div><div class="gmail_extra"><br class=""><div class="gmail_quote">On Fri, Sep 5, 2014 at 12:38 PM, Daniel Passos <span dir="ltr" class=""><<a href="mailto:daniel@passos.me" target="_blank" class="">daniel@passos.me</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr" class="">+1 to GCM logo</p><div class="HOEnZb"><div class="h5">
<div class="gmail_quote">On Sep 3, 2014 5:28 PM, "Sébastien Blanc" <<a href="mailto:scm.blanc@gmail.com" target="_blank" class="">scm.blanc@gmail.com</a>> wrote:<br type="attribution" class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto" class=""><div class="">Looks like there is a gcm logo but it is not really nice and I can not find it with a decent resolution </div><div class=""><span id="cid:095D0914-6BAB-48D7-85E6-AA61DA2545A3"><logo.png></span><br class=""><br class="">Envoyé de mon iPhone</div><div class=""><br class="">Le 3 sept. 2014 à 21:32, Lukáš Fryč <<a href="mailto:lukas.fryc@gmail.com" target="_blank" class="">lukas.fryc@gmail.com</a>> a écrit :<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><div dir="ltr" class="">From the UI perspective, Android/Chrome merge has few options:<div class=""><br class=""></div><div class="">1. merged half-Android / half-Chrome logo (+ "Android / Chrome" as a description)</div><div class=""><br class=""></div><div class="">2. use one radio button, but two rows with two logos (Android, Chrome)<br class="">
</div><div class=""><br class=""></div><div class="">3. use Google logo ("G"? [1]) (and "Google Cloud Messaging" description)</div><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Anyway, in any case it won't be as nice and polished as it is now. :-)</div>
<div class=""><br class=""></div><div class=""><br class=""></div><div class="">[1] <a href="https://www.google.com/search?q=g+google&source=lnms&tbm=isch&sa=X&ei=kWsHVILKJsn8yQSO9IDoCQ&ved=0CAoQ_AUoAw&biw=1283&bih=861" target="_blank" class="">https://www.google.com/search?q=g+google&source=lnms&tbm=isch&sa=X&ei=kWsHVILKJsn8yQSO9IDoCQ&ved=0CAoQ_AUoAw&biw=1283&bih=861</a><br class="">
<div class="gmail_extra"><br class=""><br class=""><div class="gmail_quote">On Wed, Sep 3, 2014 at 7:48 PM, Lucas Holmquist <span dir="ltr" class=""><<a href="mailto:lholmqui@redhat.com" target="_blank" class="">lholmqui@redhat.com</a>></span> wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word" class=""><div class="">So to follow up on this,</div>
<div class=""><br class=""></div><div class=""><br class=""></div><div class="">Chrome Packaged Applications, no recommend to use the same GCM network for Android when sending push notifications.</div><div class=""><br class=""></div><div class="">Currently in the UnifiedPush Server, a user can use the Android variant to use this new API now. </div>
<div class=""><br class=""></div><div class="">I think we should rename the AndroidVariant.class and related stuff to GCMVariant . </div><div class=""><br class=""></div><div class="">I created this Task to track the changes, <a href="https://issues.jboss.org/browse/AGPUSH-928" target="_blank" class="">https://issues.jboss.org/browse/AGPUSH-928</a> since we need to deprecate the current Chrome implementation and update the UI’s for the new way.</div>
<div class=""><br class=""></div><div class="">i’m wondering for the “Create Variant” dialog, for Android, we would need to change the name to GCM, but for the icon’s i wonder how it would look to put both Android and Chrome icons, side by side</div>
<div class=""><div class=""><div class=""><br class=""></div><br class=""><div class=""><div class="">On Aug 27, 2014, at 2:19 PM, Lucas Holmquist <<a href="mailto:lholmqui@redhat.com" target="_blank" class="">lholmqui@redhat.com</a>> wrote:</div><br class=""><blockquote type="cite" class=""><div style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="">
<div class=""><br class="">On Aug 27, 2014, at 2:15 PM, Lukáš Fryč <<a href="mailto:lukas.fryc@gmail.com" target="_blank" class="">lukas.fryc@gmail.com</a>> wrote:</div><br class=""><blockquote type="cite" class=""><div dir="ltr" class="">Hey Luke,<div class=""><br class=""></div><div class="">
ad) Variants</div>
<div class=""><br class=""></div><div class="">it would be ideal if we could just use the same variant!</div></div></blockquote><div class=""><br class=""></div>yea, it’s looking like it will be the same thing, we might just have to make a note of it on the UI<br class="">
<blockquote type="cite" class=""><div dir="ltr" class=""><div class=""><br class=""></div><div class=""><br class=""></div><div class="">ad) Compatibility</div><div class=""><br class=""></div><div class="">I would say we should preserve the compatibility with 1.x as long as it does not make much efforts to keep both supported.</div>
</div></blockquote><blockquote type="cite" class=""><div dir="ltr" class=""><div class=""><br class=""></div><div class="">If it would be too much hassle, let's remove it in 1.1.</div><div class="">Chrome is updated pro-actively anyway, so no one will hear about the old API in few months.</div>
</div></blockquote><div class=""><br class=""></div>exactly, so maybe a warning or something<br class=""><blockquote type="cite" class=""><div dir="ltr" class=""><div class=""><br class=""></div><div class=""><br class=""></div><div class="">Cheers,</div><div class=""><br class=""></div><div class="">~ Lukas</div></div><div class="gmail_extra">
<br class=""><br class=""><div class="gmail_quote">On Wed, Aug 27, 2014 at 3:28 PM, Lucas Holmquist<span class=""> </span><span dir="ltr" class=""><<a href="mailto:lholmqui@redhat.com" target="_blank" class="">lholmqui@redhat.com</a>></span><span class=""> </span>wrote:<br class="">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div style="word-wrap:break-word" class="">Hello,<div class=""><br class=""></div><div class="">
now that the 1.0.0-final is pretty much out for the UnifiedPush Server, i’m starting to look at the new API that Chrome apps use for sending push notifications.</div><div class=""><br class=""></div><div class="">the TL;DR of it is, it’s basically the same as Android now.( no more refresh tokens and access tokens and such )</div>
<div class=""><br class=""></div><div class="">So the question is, do we need to have a deprecation period on what is currently there?</div><div class=""><br class=""></div><div class="">The v1 of the chrome pushMessaging api has become legacy and it is recommended to use the new stuff. <a href="https://developer.chrome.com/apps/cloudMessagingV1" target="_blank" class="">https://developer.chrome.com/apps/cloudMessagingV1</a></div>
<div class=""><br class=""></div><div class="">While i have looked to deeply, it’s possible we can use the same “Variant” structure for Chrome Apps, Since they will be using the same Network</div><div class=""><br class=""></div><div class="">wdyt?</div><div class=""><br class=""></div><div class="">
-Luke</div></div><br class="">_______________________________________________<br class="">aerogear-dev mailing list<br class=""><a href="mailto:aerogear-dev@lists.jboss.org" target="_blank" class="">aerogear-dev@lists.jboss.org</a><br class=""><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank" class="">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br class="">
</blockquote></div><br class=""></div>_______________________________________________<br class="">aerogear-dev mailing list<br class=""><a href="mailto:aerogear-dev@lists.jboss.org" target="_blank" class="">aerogear-dev@lists.jboss.org</a><br class=""><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank" class="">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></blockquote>
</div><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="">
<span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important" class="">_______________________________________________</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="">
<span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important" class="">aerogear-dev mailing list</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="">
<a href="mailto:aerogear-dev@lists.jboss.org" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank" class="">aerogear-dev@lists.jboss.org</a><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" class="">
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px" target="_blank" class="">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></blockquote>
</div><br class=""></div></div></div><br class="">_______________________________________________<br class="">
aerogear-dev mailing list<br class="">
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank" class="">aerogear-dev@lists.jboss.org</a><br class="">
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank" class="">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br class=""></blockquote></div><br class=""></div></div></div>
</div></blockquote><blockquote type="cite" class=""><div class=""><span class="">_______________________________________________</span><br class=""><span class="">aerogear-dev mailing list</span><br class=""><span class=""><a href="mailto:aerogear-dev@lists.jboss.org" target="_blank" class="">aerogear-dev@lists.jboss.org</a></span><br class=""><span class=""><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank" class="">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></span></div></blockquote></div><br class="">_______________________________________________<br class="">
aerogear-dev mailing list<br class="">
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank" class="">aerogear-dev@lists.jboss.org</a><br class="">
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank" class="">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br class=""></blockquote></div>
</div></div><br class="">_______________________________________________<br class="">
aerogear-dev mailing list<br class="">
<a href="mailto:aerogear-dev@lists.jboss.org" class="">aerogear-dev@lists.jboss.org</a><br class="">
<a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank" class="">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br class=""></blockquote></div><br class=""></div>
_______________________________________________<br class="">aerogear-dev mailing list<br class=""><a href="mailto:aerogear-dev@lists.jboss.org" class="">aerogear-dev@lists.jboss.org</a><br class=""><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></div></blockquote></div><br class=""></div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>aerogear-dev mailing list</span><br><span><a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a></span><br><span><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></span></div></blockquote></body></html>