<div dir="ltr">Hylke ,<div><br></div><div>do you have some of the HTML based mock-ups already ? E.g. for the dashboard ? </div><div><br></div><div>Thanks!</div><div>Matthias</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">
On Wed, May 21, 2014 at 10:24 PM, Matthias Wessendorf <span dir="ltr"><<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</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"><br><div class="gmail_extra"><br><br><div class="gmail_quote"><div class="">On Wed, May 21, 2014 at 9:55 PM, Burr Sutter <span dir="ltr"><<a href="mailto:bsutter@redhat.com" target="_blank">bsutter@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"><br><div><div><div>
On May 21, 2014, at 3:43 PM, Matthias Wessendorf <<a href="mailto:matzew@apache.org" target="_blank">matzew@apache.org</a>> wrote:</div><br><blockquote type="cite"><div dir="ltr">BTW. on the top box (first screen), I am querying the DB per user:<div>
- "my" applications (the active is worthless)</div></div></blockquote></div>OK - so the "5" in the wireframe would be the "Total of My Apps"?</div></div></blockquote><div><br></div></div><div>
yes </div><div class="">
<div><br></div><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><div>
<br><blockquote type="cite"><div dir="ltr"><div>- notifications delivered by "my" apps</div></div></blockquote></div>Yes, that makes sense</div><div><div><br><blockquote type="cite"><div dir="ltr"><div>
- devices registered with "my" apps</div></div></blockquote><div><br></div></div>And when did we add the concept of "my" apps, I thought there was only "super-user" who sees all apps.</div></div>
</blockquote><div><br></div></div><div>we had that already on the 'agenda' for the initial user-management - but we skipped our own impl. due to Keycloak adpotion;</div><div><br></div><div>A recent thread:</div><div>
<a href="http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007783.html" target="_blank">http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007783.html</a><br>
</div><div><br></div><div><br></div><div>In here I describe a 'super-user' and a 'PushAdmin':</div><div><a href="http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007784.html" target="_blank">http://lists.jboss.org/pipermail/aerogear-dev/2014-May/007784.html</a><br>
</div><div><br></div><div><br></div><div>Or do you think a 'shared' super-user is good enough? IMO it would be odd if HR Manager and Marketing Manager would be seeing each others apps;</div><div><br></div><div>Feel free to chime in on that related thread </div>
<div><div class="h5">
<div><br></div><div><br></div><div> </div><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><div><div><br><blockquote type="cite"><div dir="ltr">
<div><br></div><div><a href="https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png" target="_blank">https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png</a><br>
</div><div><br></div><div>It would be odd if I see how many apps are on the entire server etc ;-) </div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, May 21, 2014 at 8:41 PM, Burr Sutter <span dir="ltr"><<a href="mailto:bsutter@redhat.com" target="_blank">bsutter@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><br>
On May 21, 2014, at 12:19 PM, Hylke Bons <<a href="mailto:hbons@redhat.com" target="_blank">hbons@redhat.com</a>> wrote:<br>
<br>
> Hey,<br>
><br>
> The "Status" column only show errors. If there are none it will say<br>
> something amongst the lines of "Everything is fine".<br>
</div>I guess what threw me off was that the Status box links to the Activity page - at least based on how I read that orange arrow connecting the two.<br>
<div><div><br>
<br>
><br>
> About the graphic: Sure, it's just the wireframe and may still change in<br>
> the visual design depending on what looks good.<br>
><br>
> Thanks,<br>
><br>
> Hylke<br>
><br>
> On 19/05/2014 16:48, Matt Carrano wrote:<br>
>> Hey Hylke,<br>
>><br>
>> This is looking good. I had a few minor comments/questions about the layout and labeling. Take a look at the marked up wireframe (attached).<br>
>><br>
>> -Matt<br>
>><br>
>> ----- Original Message -----<br>
>> From: "Hylke Bons" <<a href="mailto:hbons@redhat.com" target="_blank">hbons@redhat.com</a>><br>
>> To: <a href="mailto:aerogear-dev@lists.jboss.org" target="_blank">aerogear-dev@lists.jboss.org</a><br>
>> Cc: "Matt Carrano" <<a href="mailto:mcarrano@redhat.com" target="_blank">mcarrano@redhat.com</a>><br>
>> Sent: Monday, May 19, 2014 8:03:13 AM<br>
>> Subject: Re: [aerogear-dev] First go at stats/activity wireframes<br>
>><br>
>> Hello,<br>
>><br>
>> Here are some updates based on the feedback from the meetings:<br>
>> <a href="https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png" target="_blank">https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png</a><br>
>> - Simplified dashboard stats<br>
>> - Apps notifications table<br>
>> - Defined entry points<br>
>><br>
>> Let me know what you think. I hope that covers everything.<br>
>><br>
>> Thanks,<br>
>><br>
>> Hylke<br>
>><br>
>><br>
>><br>
>> On 15/05/2014 16:19, Hylke Bons wrote:<br>
>>> Hey,<br>
>>><br>
>>> Here's an initial version:<br>
>>> <a href="https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png" target="_blank">https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png</a><br>
>>><br>
>>> I tried to incorporate most wishes expressed in the other thread.<br>
>>><br>
>>> Most notable things:<br>
>>> - Landing page with an overview of stats, most active apps, and error<br>
>>> messages<br>
>>> - Activity table shows both registration and notification events<br>
>>> - Activity table is per variant, and not all activity on the server.<br>
>>> Unless there's a usecase to have every event for every app/variant in a<br>
>>> table I don't think we actually need it. The important thing is to get<br>
>>> to error messages easily.<br>
>>><br>
>>> Things to do/think about:<br>
>>> - links/entry points to the activity table<br>
>>> - filtering the activity table<br>
>>><br>
>>> This is just the first iteration and we will improve on this.<br>
>>> Let me know what you think.<br>
>>><br>
>>> Thanks,<br>
>>><br>
>>> Hylke<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>
><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>
<br>
<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>
</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>
_______________________________________________<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></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></div></div><div><div class="h5"><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></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>