[ 
https://issues.apache.org/jira/browse/NIFI-6504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16896326#comment-16896326
 ] 

Peter Wicks commented on NIFI-6504:
-----------------------------------

[~alopresto] I put some thought into this. My first thought was a pretty strong 
no.  But then I thought, what if we added a default color at the relationship 
level in the code, or we could tag relationships with an enum like 
"success/failure/unmodified/default" and then put the translation into the js 
code. Then, in the connection creation screen the color would show up with a 
checkbox next to it, so you can go with the default defined for that 
relationship type (red/green/blue). It could be unchecked by default (if 
multiple relationships are selected we default to black?).

This provides two things:

 - Existing connections remain black, keeping good backwards compat, and happy 
users
 - Users who want black don't have to do anything different than they do today.

I suppose you could go the extra mile and add a nifi property to control this 
checkbox's default state.

> Add Color to Connections
> ------------------------
>
>                 Key: NIFI-6504
>                 URL: https://issues.apache.org/jira/browse/NIFI-6504
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Core Framework, Core UI, Flow Versioning
>            Reporter: Peter Wicks
>            Assignee: Peter Wicks
>            Priority: Minor
>
> With so many connections overlapping on screen, it can be hard to trace where 
> different connections are going, and what they are used for.
> Adding color to connections would make this much easier.  It might be good to 
> add color to other components as well, such as the Funnel to help identify 
> their purpose using a color cue.
> Example:
> [https://photos.app.goo.gl/6NqZmM3PnCZRai6f9]
>  
> POC Branch: [https://github.com/patricker/nifi/tree/NIFI-6504]



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to