[aerogear-dev] First go at stats/activity wireframes

[Matthias Wessendorf]

On Wed, May 28, 2014 at 6:26 PM, Hylke Bons <hbons at redhat.com> wrote:

>  That's fine, we won't do it for this cycle then.
>

perfect!



>
> Thanks,
>
> Hylke
>
>
> On 28/05/2014 17:14, Matthias Wessendorf wrote:
>
>
>
>
> On Wed, May 28, 2014 at 5:59 PM, Hylke Bons <hbons at redhat.com> wrote:
>
>> Hey,
>>
>> I've made a couple of small changes to the wireframes. Matt had some
>> good feedback about the dashboard table showing 'recent' errors: it
>> wasn't really clear what kind of time period it covered, and error
>> messages could be hidden due to the table pagination in the log table.
>>
>> These are the changes that try to address the above issues compared to
>> the agreed upon previous design:
>> - Dashboard area: "Status" -> "Warnings"
>>
>
>  we can say that a it has failed for the variant;
> As said before, we can not (technically) say that just three messages
> failed
>
>
>
>> - "Clear All" link/button to clear the list of errors on the dashboard
>>
>
>  hrm ... why? We will _not_ persist that 'clear' - it will be visible on
> next loop to the page;
> IMO useless button ...
>
>
>> - The log table has a tab showing "Failed" vs. "All" messages.
>>
>
>  not sure, we really need this, ATM
>
>  remember.... we talked about a 'simple' overview... and now with the
> dashboard being added, we already have have more,
> and this is even more of that ...
>
>  Not sure ...
>
>
>>
>>
>> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>>
>> Let me know if this is ok and at all still possible to still do in the
>> current timeframe ("Clear All" seems to require extra backend logic).
>>
>
>  yep, will NOT be implemented for 1.0.0
>
>
>>
>> Thanks,
>>
>> Hylke
>>
>>
>>
>>
>> On 15/05/2014 16:19, Hylke Bons wrote:
>>  > Hey,
>> >
>> > Here's an initial version:
>> >
>> https://raw.githubusercontent.com/hbons/aerogear-design/master/Unified%20Push%20Server/activity-spec.png
>> >
>> > I tried to incorporate most wishes expressed in the other thread.
>> >
>> > Most notable things:
>> > - Landing page with an overview of stats, most active apps, and error
>> > messages
>> > - Activity table shows both registration and notification events
>> > - Activity table is per variant, and not all activity on the server.
>> > Unless there's a usecase to have every event for every app/variant in a
>> > table I don't think we actually need it. The important thing is to get
>> > to error messages easily.
>> >
>> > Things to do/think about:
>> > - links/entry points to the activity table
>> > - filtering the activity table
>> >
>> > This is just the first iteration and we will improve on this.
>> > Let me know what you think.
>> >
>> > Thanks,
>> >
>> > Hylke
>> > _______________________________________________
>> > aerogear-dev mailing list
>> > aerogear-dev at lists.jboss.org
>> > https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>> _______________________________________________
>> aerogear-dev mailing list
>> aerogear-dev at lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>>
>
>
>
>  --
> Matthias Wessendorf
>
> blog: http://matthiaswessendorf.wordpress.com/
> sessions: http://www.slideshare.net/mwessendorf
> twitter: http://twitter.com/mwessendorf
>
>
> _______________________________________________
> aerogear-dev mailing listaerogear-dev at lists.jboss.orghttps://lists.jboss.org/mailman/listinfo/aerogear-dev
>
>
>
> _______________________________________________
> aerogear-dev mailing list
> aerogear-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/aerogear-dev
>



-- 
Matthias Wessendorf

blog: http://matthiaswessendorf.wordpress.com/
sessions: http://www.slideshare.net/mwessendorf
twitter: http://twitter.com/mwessendorf
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/aerogear-dev/attachments/20140528/d8ef29be/attachment.html