nifi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Tony Kurc <trk...@gmail.com>
Subject Re: [DISCUSS] Feature proposal: Read-only mode as default
Date Sat, 08 Aug 2015 17:41:10 GMT
Personally not a fan of the idea. Maybe something analogous to something
like 'lock the taskbar' in Windows that can have a system default setting
and a user preference of on or off.

On Sat, Aug 8, 2015 at 11:44 AM, johny casanova <computertech2124@gmail.com>
wrote:

> I agree it is easy to move it delete something by mistake. Some flows are
> huge or are using,more resources and are slower to load and you can
> accidently do something by mistake. I believe the "are yous sure u want to
> delete?" its a good start.
> On Aug 7, 2015 10:31 PM, "Joe Witt" <joe.witt@gmail.com> wrote:
>
> > Team,
> >
> > We've been hearing from users of nifi that it is too easy to
> > accidentally move something on the flow or delete large portions of
> > the flow.  This is the case when panning the screen for example and
> > accidentally having a processor selected instead.
> >
> > What is worth consideration then is the notion of making the flow
> > 'read-only' by default.  In this case the user would need to
> > explicitly 'enable edit mode'.  We would then also support a
> > confirmation dialog or similar construct whenever deleting components
> > on the flow.
> >
> > Anyone have a strong objection to this concept?  If so, do you have an
> > alternative in mind that would help avoid accidental movement?
> >
> > Thanks
> > Joe
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message