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 Sat, 15 Dec 2012 16:29:37 GMT
#146: Inline editing of objects
  Reporter:  jdreimann    |      Owner:  jdreimann
      Type:  enhancement  |     Status:  review
  Priority:  critical     |  Milestone:  Release 4
 Component:  dashboard    |    Version:
Resolution:               |   Keywords:  inplace bheditable
Changes (by olemis):

 * owner:  olemis => jdreimann
 * status:  accepted => review


 After comment:32 I have refreshed previous patches and attached new patch
 implementing ticket submission . Patch order in comment:27 updated
 accordingly . Other minor enhancements have been added consisting of :

 summary:     BH Theme #146 : In-place submit form . Sticky panel relocated
 and other minor changes
 summary:     BH Theme #146 : Discard inline modifications
 summary:     BH Theme #146 : Tooltips for workflow actions
 summary:     BH Theme #146 : Edit mode not reentrant plus .editing =>
 summary:     BH Theme #146 : Workflow drop down visible on affix
 summary:     BH Theme #146 : Use JS templates to render in-place submit
 summary:     BH Theme #146 : Ticket in-plece submit controls

 Anyway , after all this editable state will look like shown below :

 [[Image(bh_theme_x_91_ticket_responsive_submit_workflow.png, width=600)]]

 I'm forwarding ticket for further review of workflow drop down menu from a
 UI/UX perspective .

 A few comments on that subject .

   1. Update / cancel buttons placed in sticky panel so that they'll
     always be handy in edit mode
   2. Update button highlighted (`btn-primary`) because it has to
     be that relevant on edit mode . Otherwise it's hard to notice
     since it shows up out of nowhere .
   3. Reduced space => reduced visibility of action hints (i.e. tooltips)
   4. Selected workflow action appended to ''Update'' label to allow
     one click edits . Otherwise it is obscured the intentions and
     to figure out what's gonna happen with ticket in the end .

 Beyond this , there should be some room for enhancements . That's sure . I
 suggest to tackle improvements on separate tickets .

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

View raw message