incubator-bloodhound-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Apache Bloodhound" <>
Subject Re: [Apache Bloodhound] #94: Activity area to automatically filter to show entries relevant for the view
Date Tue, 24 Jul 2012 03:10:26 GMT
#94: Activity area to automatically filter to show entries relevant for the view
  Reporter:  gjm          |      Owner:  olemis
      Type:  enhancement  |     Status:  accepted
  Priority:  major        |  Milestone:  Release 2
 Component:  dashboard    |    Version:
Resolution:               |   Keywords:

Comment (by olemis):

 Attached patches filter timeline according to resource set in active
 rendering context.

 ==== Dashboard ====

 attachment:t94_r1362098_timeline_filters_api.diff is the most important
 patch. It introduces two important enhamcements . Firstly , it ensures
 that the widget is rendered in the same context of the target view. This
 implies some minor changes in dashboard and widgets API consisting in
 mainly using a `RenderingContext` object instead of a web `Request` and
 also propagation of the former through a path starting from view/template
 code until it finally gets processed by core widget rendering engine. In
 second place , it adds a whole new API to filter timeline events. In order
 to make it work without patching ''Trac'' source code it was necessary to
 override parts of the timeline engine in non-trivial ways . That's mainly
 why it took so long to figure this out . Please consider reviewing all
 this . My only suggestion would be to '''move the whole timeline filters
 infrastructure onto a new module''' (e.g. `bhdashboard.timeline`) in order
 to allow for reusing it beyond activity widget source code.

 The other two patches implement the code needed to only show relevant
 ticket events in milestone view. They should be applied in the following


 $ hg qapplied


 The solution is generic enough and may be reused in other scenarios for
 models associated to tickets via ticket fields. Two remarkable examples
 are version pages (i.e. #109) and product view . The filter currently
 relies on existing resources API to do its job. That means that afaics '''
 `IResourceManager` interface must be implemented for both products and
 versions'''. After that work needed to upgrade activity feed is relatively
 simple. Should a new ticket be created in order to implement products and
 versions resource manager?

 Finally , installer has to enable filter components at installation time
 in order to make all this magic happen .

 ==== Theme ====

 Just a super tiny patch in attachment:t94_r1361192_milestone_typo.diff

 I look forward to your comments .

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

View raw message