Oops!)
>
> Andrew
>
> From: Charlie Frasure <charliefras...@gmail.com>
> Reply-To: "users@nifi.apache.org" <users@nifi.apache.org>
> Date: Friday, November 13, 2015 at 9:13 AM
> To: "users@nifi.apache.org" <users@nifi.apache.org>
> Subject:
istent experience across all
>>>> deployments (just imaging if someone swapped start/stop and an operator
>>>> expected a Props screen. Oops!)
>>>>
>>>> Andrew
>>>>
>>>> From: Charlie Frasure <charliefras...@gmail.com>
>>>>
;>>> I am against making the action customizable, though. This is a case
>>>>> where less is more for a UX and provides a consistent experience across
>>>>> all
>>>>> deployments (just imaging if someone swapped start/stop and an operator
>>
There has been recent discussion around UI enhancements with the goal of
streamlining visual flow design. Please consider the following enhancements
and concepts for proposed solutions. Do you have any objections? If so,
please share your thoughts and ideas for alternate solutions to streamline
I also think 1 and 2 seem like good ideas but having built hundreds of
flows, I would not want a configuration window to open automatically when a
processor is added to the graph. From an operations standpoint, you are
designing the flow was you add and remove the processor to work through
Rob,
I also like enhancements 1 & 2. For the ability to pin processors or pull
recent/popular processors from a user-generated list, can we make that
something that is expandable/collapsible? While building a flow, I think
people might want that type of thing open. But then later, while working
does nothing,
so it seems to be available, if that’s its best use.
Thanks for writing this proposal up and circulating it, Rob.
Rick
From: Rob Moran [mailto:rmo...@gmail.com]
Sent: Thursday, September 10, 2015 11:56 AM
To: users@nifi.apache.org
Subject: [DISCUSS] Feature proposal: Streamline
