You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@nifi.apache.org by ski n <ra...@gmail.com> on 2019/07/26 13:45:59 UTC

UI Features

I was creating a flow and I noticed some things of the GUI that were
missing. Don’t know if there already plans/tickets for these items, but I
would like your opinion first.

If you think it’s a good idea and there is no ticket yet than I will create
one:

1)     It’s already possible to align flows, but sometimes it takes a lot
of time to make a flow look clean. I like if an automatically ordering
option of a flow (which calculate the best view). Ordering a flow from left
to right or ordering a flow from top to bottom.

2)     Double-click on the canvas to zoom in.

3)     Add possibility to use keyboard to move elements (for example
processors)

4)     Select multiple items with mouse (like MS Visio). Now you need the
shift key to do this.

5)     Moving step/flows into a process group. “Right-Click” on a flow step
(Move step to process group / Move flow to process group / Create process
group for this flow)

6)     Possibility to add links in labels (for example link to a process
group)

7)     Search box (to find and navigate to a process group/flow/flow step)

8)     Queues are highlighted yellow, while processors are highlight black
(Better both yellow, black is hard to see)

9)     Add Ctrl X / Cut

10)  Add Ctrl Z / Revert last change

11)  Sometimes the "apply" button navigates you directly back to the canvas
(for example with configuration), sometimes not (process group). Like to
have a 'save' button which means apply change and leave the popup, while
apply applies the change.

12)  Export canvas to image (jpeg/png)

13)  Links to file resources --> open the resource in an online editor

14) Option to edit the processor as XML (sometimes this goes faster). Now
you need to export/import the processor as a template.



Best regards,


Raymond

Re: UI Features

Posted by Rob Moran <rm...@gmail.com>.
Thanks for sharing your thoughts, Raymond.

Some of the items you call out have tickets already or there may be
similar/related ones. I will plan to go through each and reply back with my
findings.

Thanks again!

On Fri, Jul 26, 2019 at 9:46 AM ski n <ra...@gmail.com> wrote:

> I was creating a flow and I noticed some things of the GUI that were
> missing. Don’t know if there already plans/tickets for these items, but I
> would like your opinion first.
>
> If you think it’s a good idea and there is no ticket yet than I will create
> one:
>
> 1)     It’s already possible to align flows, but sometimes it takes a lot
> of time to make a flow look clean. I like if an automatically ordering
> option of a flow (which calculate the best view). Ordering a flow from left
> to right or ordering a flow from top to bottom.
>
> 2)     Double-click on the canvas to zoom in.
>
> 3)     Add possibility to use keyboard to move elements (for example
> processors)
>
> 4)     Select multiple items with mouse (like MS Visio). Now you need the
> shift key to do this.
>
> 5)     Moving step/flows into a process group. “Right-Click” on a flow step
> (Move step to process group / Move flow to process group / Create process
> group for this flow)
>
> 6)     Possibility to add links in labels (for example link to a process
> group)
>
> 7)     Search box (to find and navigate to a process group/flow/flow step)
>
> 8)     Queues are highlighted yellow, while processors are highlight black
> (Better both yellow, black is hard to see)
>
> 9)     Add Ctrl X / Cut
>
> 10)  Add Ctrl Z / Revert last change
>
> 11)  Sometimes the "apply" button navigates you directly back to the canvas
> (for example with configuration), sometimes not (process group). Like to
> have a 'save' button which means apply change and leave the popup, while
> apply applies the change.
>
> 12)  Export canvas to image (jpeg/png)
>
> 13)  Links to file resources --> open the resource in an online editor
>
> 14) Option to edit the processor as XML (sometimes this goes faster). Now
> you need to export/import the processor as a template.
>
>
>
> Best regards,
>
>
> Raymond
>