ubuntu-phone team mailing list archive

[Robert Park <robert.park@xxxxxxxxxxxxx>]

On Thu, Aug 27, 2015 at 4:07 AM, Łukasz 'sil2100' Zemczak <
lukasz.zemczak@xxxxxxxxxxxxx> wrote:
> Hey Robert,
>
> Looking nice so far, thanks for the enhancements!

You're welcome!

>
> Some ideas for improvement that might also help out with one of the
> issues that Michael mentioned below:
>
> The generall idea is to de-clutter the bileto interface. The hover
> overlay menu is a step in the right direction, but I was actually
> thinking of doing something different. What if each bileto landing could
> be click-to-expand?

Generally speaking, i think a true click-to-expand would be a lot more
trouble than it's worth.

However, i think the dashboard has some good inspiration here: currently in
the dashboard, if you view all silos, the MPs are hidden. If you search,
fewer silos are displayed and then the merges appear.

Similarly, it would be easy to set some kind of threshold, say if more than
5 requests are visible, then some fields are hidden, but if 5 or less are
visible then display all fields.

This way, you could simulate "click to expand" by clicking on the permalink
or narrowing your search. Would also be nicer for users who only have a few
requests seeing everything.

The raises a few questions in my mind:

1. Which fields can be hidden?

2. What do we do with the new request form at the top? It doubles as a
header to explain what fields your seeing, it would be weird if it
displayed fields that were hidden, but it would also be weird if fields
were hidden when you try to use it.

3. If we minimize the number of fields displayed, does it still make sense
to use a full-width row to represent a request? Maybe the requests could be
displayed in a "card" style like the dashboard is. Again this gives me
reservations about how the new request form would adapt to these changes.

>
> The good ol' Issue Tracker I once made has something similar, but
> not-too-fancy as it has no animations of the expanding:
> http://people.canonical.com/~lzemczak/issues/
>
> This was also basically the main idea of the CI Airline UI we were
> preparing.
>
> On the spreadsheet there was no other choice but include ALL the
> required data in the main row - with our custom tools we should only
> show the most important, and leave the rest visible to only those that
> want to see it.

Well, there is already some hidden data. Bileto doesn't display
pkgversionlist for instance ;-)

> Then things like 'what merges are actually configured'
> or all the comments for a silo etc. could be in the details. Then we
> could only show the top-most comment on the main view.
>
> What do you think?

Yeah, i agree we need to declutter for sure, i think it's going to take
some iterations until we get it right.