<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, May 28, 2014 at 5:59 PM, Hylke Bons <span dir="ltr"><<a href="mailto:hbons@redhat.com" target="_blank">hbons@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,<br>
<br>
I've made a couple of small changes to the wireframes. Matt had some<br>
good feedback about the dashboard table showing 'recent' errors: it<br>
wasn't really clear what kind of time period it covered, and error<br>
messages could be hidden due to the table pagination in the log table.<br>
<br>
These are the changes that try to address the above issues compared to<br>
the agreed upon previous design:<br>
- Dashboard area: "Status" -> "Warnings"<br></blockquote><div><br></div><div>we can say that a it has failed for the variant;</div><div>As said before, we can not (technically) say that just three messages failed</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
- "Clear All" link/button to clear the list of errors on the dashboard<br></blockquote><div><br></div><div>hrm ... why? We will _not_ persist that 'clear' - it will be visible on next loop to the page;</div>
<div>IMO useless button ...</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
- The log table has a tab showing "Failed" vs. "All" messages.<br></blockquote><div><br></div><div>not sure, we really need this, ATM</div><div><br></div><div>remember.... we talked about a 'simple' overview... and now with the dashboard being added, we already have have more,</div>
<div>and this is even more of that ... </div><div><br></div><div>Not sure ...</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<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>
Let me know if this is ok and at all still possible to still do in the<br>
current timeframe ("Clear All" seems to require extra backend logic).<br></blockquote><div><br></div><div>yep, will NOT be implemented for 1.0.0 </div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div class="im HOEnZb"><br>
Thanks,<br>
<br>
Hylke<br>
<br>
<br>
<br>
<br>
On 15/05/2014 16:19, Hylke Bons wrote:<br>
</div><div class="HOEnZb"><div class="h5">> 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>
_______________________________________________<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>
</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></div>