incubator-bloodhound-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Apache Bloodhound" <>
Subject Re: [Apache Bloodhound] #146: Inline editing of objects
Date Fri, 21 Sep 2012 14:10:27 GMT
#146: Inline editing of objects
  Reporter:  jdreimann    |      Owner:  olemis
      Type:  enhancement  |     Status:  accepted
  Priority:  critical     |  Milestone:  Release 2
 Component:  dashboard    |    Version:
Resolution:               |   Keywords:

Comment (by olemis):

 Replying to [comment:11 jdreimann]:
 > Replying to [comment:10 olemis]:
 > > The following screenshot illustrates what it looks like . Feedback is
 welcome .
 > I assume the button with the check mark is to confirm the selection and
 'commit' it?


 > This should not be required.

 ok. I'll remove that for select fields .

 > Part of the case for inline editing is that confirmation is only
 required when
 > 1. It's difficult (time, effort) or impossible to revert fully.
 > 1. Automatically saved information would be incomplete.
 > An example for 1. is when a ticket is when stuff gets deleted. An
 example for 2. is changing a ticket description, which you probably
 wouldn't want to change for everyone before you're done typing.

 IMO submit button does need to be required for all kinds of text fields
 (i.e. raw &wiki textarea, raw and wiki text field ) . Consider the case
 when user starts typing but suddenly decides it's all wrong . Hence there
 should be a way to revert in place edits (e.g. Submit + Cancel button ?)

 > I think we'll get closer to a proper definition by trial and error, but
 I think our default approach should be to not ask for confirmation unless
 in cases of grave danger.

 ... and when there's a need to cancel / undo in place modifications , like
 is the case for text fields .

Ticket URL: <>
Apache Bloodhound <>
The Apache Bloodhound (incubating) issue tracker

View raw message