<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;">Not that you asked me but :-)<div><br></div><div>+1 on the horizontal "dashboard" section</div><div>+1 to the concern related to "status" - the first time I saw it I felt it only addressed errors - not all possible but recent "activity"</div><div>I think the word "Log" or "Activity" would be better</div><div><br></div><div><div><div>On May 21, 2014, at 8:45 AM, Matthias Wessendorf <<a href="mailto:matzew@apache.org">matzew@apache.org</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div dir="ltr">Hylke,<div><br></div><div>any comments on Matt's reply?</div><div><br></div><div>Or is this the final draft:</div><div><a href="https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png">https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png</a><br>
</div><div><br></div><div>-Matthias</div><div><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, May 19, 2014 at 5:48 PM, Matt Carrano <span dir="ltr"><<a href="mailto:mcarrano@redhat.com" target="_blank">mcarrano@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">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>
<span class="HOEnZb"><font color="#888888"><br>
-Matt<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
----- Original Message -----<br>
From: "Hylke Bons" <<a href="mailto:hbons@redhat.com">hbons@redhat.com</a>><br>
To: <a href="mailto:aerogear-dev@lists.jboss.org">aerogear-dev@lists.jboss.org</a><br>
Cc: "Matt Carrano" <<a href="mailto:mcarrano@redhat.com">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">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>
</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" target="_blank">https://lists.jboss.org/mailman/listinfo/aerogear-dev</a><br></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">aerogear-dev@lists.jboss.org</a><br>https://lists.jboss.org/mailman/listinfo/aerogear-dev</blockquote></div><br></div></body></html>