Let's fade the connection slowly to an inverted if backpressure engages?
On Tue, Sep 20, 2016, 1:17 PM Rob Moran <rmo...@gmail.com> wrote:
> Agreed – thanks for calling that out, Andy.
> On Tue, Sep 20, 2016 at 1:13 PM, Andy LoPresto <alopre...@apache.org>
>> In this and other UI discussions going on, I would request that everyone
>> keep in mind the usability of the software by people with visual and other
>> impairments. The US Federal Government has guidelines referred to as
>> “Section 508”  which cover the design and usability of softwares
>> specifically to ensure access for as many people as possible. Now, NiFi is
>> not explicitly governed by these rules, but it seems to me that we should
>> work towards accessibility from the beginning, not as a bolt-on effort.
>> In that vein, one of the simplest and easiest rules is “color is great as
>> a secondary indicator, but should not be the *only* indicator”. In practice
>> — changing the color of a connection to indicate back pressure is a great
>> feature, but there should be another indicator of back pressure that does
>> not require the ability to discern color.
>> Andy LoPresto
>> *alopresto.apa...@gmail.com <alopresto.apa...@gmail.com>*
>> PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D EF69
>> On Sep 20, 2016, at 8:28 AM, Andrew Grande <apere...@gmail.com> wrote:
>> I like the tooltip addition of yours.
>> For more interactive feedback on the canvas I can immediately think of 2
>> 1. Indicator for when backpressure was configured on a connection
>> (although it's now always added by default, maybe less useful).
>> 2. Changing the color of a connection when backpressure has engaged could
>> go a long way. Can go further, gradient color based on how close the
>> connection backlog is to triggering the backpressure controls. Immediately
>> highlights hotspots visually.
>> On Tue, Sep 20, 2016, 9:40 AM Rob Moran <rmo...@gmail.com> wrote:
>>> Thanks for the feedback on the status bar. Separation between each item
>>> helps but realize after your comments how it can not feel like a single,
>>> cohesive group of items. We could probably tighten things up a bit.
>>> I think another part of this that could help would be to address some of
>>> the discussion around awareness of stats updating. Being able to call more
>>> attention (without being too intrusive) when stats change could help ease
>>> some of the burden of having to routinely scan the status bar to look for
>>> Also related, I would like to see us get a tooltip that is seen when you
>>> hover anywhere on the status bar. That tooltip would provide more
>>> descriptive text about what each item means. It would help new users learn
>>> as well as provide detail and follow-on action when something is alerted.
>>> Let's see what others think and then I can work on filing a jira to
>>> capture thoughts.
>>> On Mon, Sep 19, 2016 at 6:22 PM, Andrew Grande <apere...@gmail.com>
>>>> Hi All,
>>>> I'd like to provide some feedback on the NiFi 1.0 UI now that I had a
>>>> chance to use it for a while, as well as pass along what I heard directly
>>>> from other end users.
>>>> Attached is a screenshot of a status bar right above the main flow
>>>> canvas. The biggest difference from the 0.x UI is how much whitespace it
>>>> now has between elements. To a point where it's not possible to quickly
>>>> scan the state with a glance.
>>>> Does anyone have other opinions? Can we adjust things slightly so they
>>>> are easier on the eye an have less horizontal friction?