<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jun 29, 2015 at 2:19 PM, Andres Galante <span dir="ltr"><<a href="mailto:agalante@redhat.com" target="_blank">agalante@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hi Matthias and Lukas,<div><br></div><div>During the user research time I've learn that there are almost none use case where the user uses this information stand alone. The user would just copy and paste the code snippet.</div></div></blockquote><div><br></div><div>well, that does not always work (e.g. sligthly different structure of code).</div><div>Even our own Android HelloWorld Demo is not able to use the snippets and paste them in (due to different code structure - which is good).</div><div><br></div><div>Having them visible give a bit more appreciation to these IDs (or call em API keys), so it's easy to get the desired info quickly</div><div><br></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 dir="ltr"><div><br></div><div>We use it a lot because we test it and set it up a bunch of times UPS. We already have the code set up and we end up knowing where to look for the data. Luke bring this same issue to me during Summit. </div><div><br></div><div>Let me think of a good way to highlight that information to make the expert user life easier.</div><div><br></div><div><br></div></div><div class="HOEnZb"><div class="h5"><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jun 24, 2015 at 2:12 PM, Lukáš Fryč <span dir="ltr"><<a href="mailto:lukas@fryc.eu" target="_blank">lukas@fryc.eu</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Basically it is something that we "agreed on" (or rather didn't catch) during mockup reviews and that never changed from that time.<div><div><div><div><br></div><div>@Andres: did it have some reason to hide the details?</div></div></div></div><div><br></div><div>I'm all for exposing it more visibly.</div><br><div class="gmail_quote"><div dir="ltr">st 24. 6. 2015 v 17:21 odesílatel Matthias Wessendorf <<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>> napsal:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr">Hi,<div><br></div><div>on our old design the PushApplicationID/MasterSecret was very good to notice:</div><div><a href="https://aerogear.org/docs/unifiedpush/ups_userguide//img/applications_variant.png" target="_blank">https://aerogear.org/docs/unifiedpush/ups_userguide//img/applications_variant.png</a><br></div><div><br></div><div>Now it's a bit more hidden (one has to click on the "Sender API" tab of the Application).</div><div><br></div><div>Similar w/ the VariantID/Secret pair, IMO it is also a bit hidden, since this is only visible in the source snippets for the variant.</div><div><br></div><div>They used to be a bit more present:</div><div><a href="https://aerogear.org/docs/unifiedpush/ups_userguide//img/applications_variant_details.png" target="_blank">https://aerogear.org/docs/unifiedpush/ups_userguide//img/applications_variant_details.png</a><br clear="all"><div><br></div><div>Since I find that suboptimal, I am wondering if that's done for a good reason, or if something (in a future version?) should be changed ? <br></div><div><br></div><div>-M</div><div><br></div>-- <br><div>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></div></div></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" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a></blockquote></div></div>
</blockquote></div><br></div>
</div></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" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">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></div>