incubator-bloodhound-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Apache Bloodhound" <bloodhound-...@incubator.apache.org>
Subject Re: [Apache Bloodhound] #146: Inline editing of objects
Date Fri, 07 Dec 2012 08:11:32 GMT
#146: Inline editing of objects
--------------------------+--------------------------------
  Reporter:  jdreimann    |      Owner:  olemis
      Type:  enhancement  |     Status:  accepted
  Priority:  critical     |  Milestone:  Release 4
 Component:  dashboard    |    Version:
Resolution:               |   Keywords:  inplace bheditable
--------------------------+--------------------------------

Comment (by olemis):

 The new approach to in-place editing in ticket view is not compatible with
 jEditable afaics . Hence I've built everything from scratch . Attached
 patches against theme plugin add the following features :

   1. Enhanced ticket fields list updated according to responsive mockups
   2. Enhanced scroll spy nav bar implemented with Bootstrap button groups
      like sketched in responsive mockups
   3. Modify ticket section is gone
   4. On clicking Modify Ticket button in scroll spy nav bar , ticket view
      enters editable state (suggested by jure)

 Patches should be applied against bloodhound_theme @ r1418195 in the
 following order :

 {{{
 #!sh

 $ hg qapplied
 t146/t146_r1418195_scrollspy_btn.diff
 t146/t146_r1418195_ticket_header.diff
 t146/t146_r1418195_inplace_ticket_fields.diff

 }}}

 Issues found so far :

   1. In editable state scroll spy does not activate nav item accurately.
      This happens because heights are different (e.g. wiki toolbar added
      on top of some textarea elements , etc ...) to the values when
      scroll spy was installed.

 ... /me figuring out how to fix .

 After all this ticket view will look like shown below in view mode ...

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

 ... and in editable mode ...

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

 Still there are many open questions :

   1. What happens after ticket enters editable state ?
   2. What about workflow actions now that Modify Ticket section is gone?
   3. Should description, keywords and summary be put into editable
      as well (... IMO they should , I'm just looking for
      confirmation ...) ?

 Feedback is welcome .

-- 
Ticket URL: <https://issues.apache.org/bloodhound/ticket/146#comment:27>
Apache Bloodhound <https://issues.apache.org/bloodhound/>
The Apache Bloodhound (incubating) issue tracker

Mime
View raw message