<p dir="ltr">+1 to GCM logo</p>
<div class="gmail_quote">On Sep 3, 2014 5:28 PM, "Sébastien Blanc" <<a href="mailto:scm.blanc@gmail.com">scm.blanc@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="auto"><div>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><img src="cid:095D0914-6BAB-48D7-85E6-AA61DA2545A3" alt="logo.png"><br><br>Envoyé de mon iPhone</div><div><br>Le 3 sept. 2014 à 21:32, Lukáš Fryč <<a href="mailto:lukas.fryc@gmail.com" target="_blank">lukas.fryc@gmail.com</a>> a écrit :<br><br></div><blockquote type="cite"><div><div dir="ltr">From the UI perspective, Android/Chrome merge has few options:<div><br></div><div>1. merged half-Android / half-Chrome logo (+ "Android / Chrome" as a description)</div><div><br></div><div>2. use one radio button, but two rows with two logos (Android, Chrome)<br>
</div><div><br></div><div>3. use Google logo ("G"? [1]) (and "Google Cloud Messaging" description)</div><div><br></div><div><br></div><div>Anyway, in any case it won't be as nice and polished as it is now. :-)</div>
<div><br></div><div><br></div><div>[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">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>
<div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Sep 3, 2014 at 7:48 PM, Lucas Holmquist <span dir="ltr"><<a href="mailto:lholmqui@redhat.com" target="_blank">lholmqui@redhat.com</a>></span> wrote:<br>
<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"><div>So to follow up on this,</div>
<div><br></div><div><br></div><div>Chrome Packaged Applications, no recommend to use the same GCM network for Android when sending push notifications.</div><div><br></div><div>Currently in the UnifiedPush Server, a user can use the Android variant to use this new API now. </div>
<div><br></div><div>I think we should rename the AndroidVariant.class and related stuff to GCMVariant . </div><div><br></div><div>I created this Task to track the changes, <a href="https://issues.jboss.org/browse/AGPUSH-928" target="_blank">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><br></div><div>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><div><div><br></div><br><div><div>On Aug 27, 2014, at 2:19 PM, Lucas Holmquist <<a href="mailto:lholmqui@redhat.com" target="_blank">lholmqui@redhat.com</a>> wrote:</div><br><blockquote type="cite"><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">
<div><br>On Aug 27, 2014, at 2:15 PM, Lukáš Fryč <<a href="mailto:lukas.fryc@gmail.com" target="_blank">lukas.fryc@gmail.com</a>> wrote:</div><br><blockquote type="cite"><div dir="ltr">Hey Luke,<div><br></div><div>
ad) Variants</div>
<div><br></div><div>it would be ideal if we could just use the same variant!</div></div></blockquote><div><br></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>
<blockquote type="cite"><div dir="ltr"><div><br></div><div><br></div><div>ad) Compatibility</div><div><br></div><div>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"><div dir="ltr"><div><br></div><div>If it would be too much hassle, let's remove it in 1.1.</div><div>Chrome is updated pro-actively anyway, so no one will hear about the old API in few months.</div>
</div></blockquote><div><br></div>exactly, so maybe a warning or something<br><blockquote type="cite"><div dir="ltr"><div><br></div><div><br></div><div>Cheers,</div><div><br></div><div>~ Lukas</div></div><div class="gmail_extra">
<br><br><div class="gmail_quote">On Wed, Aug 27, 2014 at 3:28 PM, Lucas Holmquist<span> </span><span dir="ltr"><<a href="mailto:lholmqui@redhat.com" target="_blank">lholmqui@redhat.com</a>></span><span> </span>wrote:<br>
<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">Hello,<div><br></div><div>
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><br></div><div>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><br></div><div>So the question is, do we need to have a deprecation period on what is currently there?</div><div><br></div><div>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">https://developer.chrome.com/apps/cloudMessagingV1</a></div>
<div><br></div><div>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><br></div><div>wdyt?</div><div><br></div><div>
-Luke</div></div><br>_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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>
</blockquote></div><br></div>_______________________________________________<br>aerogear-dev mailing list<br><a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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></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">
<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">_______________________________________________</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">
<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">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">
<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">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">
<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">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></blockquote>
</div><br></div></div></div><br>_______________________________________________<br>
aerogear-dev mailing list<br>
<a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">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></blockquote></div><br></div></div></div>
</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" target="_blank">aerogear-dev@lists.jboss.org</a></span><br><span><a href="https://lists.jboss.org/mailman/listinfo/aerogear-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></span></div></blockquote></div><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></blockquote></div>