bloodhound-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Apache Bloodhound" <>
Subject Re: [Apache Bloodhound] #138: Widgets wiki macro
Date Fri, 20 Jul 2012 20:22:56 GMT
#138: Widgets wiki macro
  Reporter:  olemis     |      Owner:  olemis
      Type:  task       |     Status:  accepted
  Priority:  major      |  Milestone:  Release 2
 Component:  dashboard  |    Version:
Resolution:             |   Keywords:  wiki macro embed widgets

Comment (by olemis):

 Replying to [comment:9 jdreimann]:
 > Replying to [comment:8 olemis]:
 > > Replying to [comment:5 jdreimann]:
 > > > I would be more comfortable with an approach that whitelists widgets
 that can be added in this way
 > >
 > > -1 IMO . If there's something that needs to be improved then let's
 create tickets
 > See above for the risks of the current approach. Also, 'let's create
 tickets' means we're essentially committing to a unknown amount of future
 work to maintain and improve this functionality (and the expectation that
 this will be dealt with).

 Not exactly . We can decide how far we will improve the widgets delivered
 by ''Bloodhound'' project and, if others want to enhance what we achieve
 then they can :

   1. send a patch
   2. develop their own visualizations

 > That would be fine if we had strong community support for this feature,

 you are right , but please read above .

 > ie it's much requested and used, but until then we're just creating
 future commitments that divert attention from the things we really need to
 focus on.

 That depends on the decisions we make . We can make those requests sleep
 for a while until there will be a chance to get vthem done . Indeed all
 the work we are doing now in ''multiproduct'' plugin has been delayed
 since so long in t.e.o issue tracker. It wasn't until now that there's
 real progress on that direction . So even if you are right about the fact
 that we are lacking of human resources , afaics your reasns don't mean
 neither that we will commit to develop all possible widgets so perfect to
 satisfy everybody's expectations nor that we shall decide to entangle with
 these when there are higher priority tasks .

 > > > until we have a solid framework within which to allow all to be
 > >
 > > What does this mean exactly ?
 > For example a clear way for 'hacks' to provide widgets,

 By implementing ''IWidgetProvider'' interface

 > how version changes in widgets will be dealt with,

 Just like any other ''Trac'' plugin out there, I guess , unless I'm
 missing something in your previous statement

 > permissions of who can embed them,

 Embedding widgets is not a target for TracPermissions . Permissions are
 granted to edit data and fields supporting WikiFormatting , and that's the
 only thing needed to use WidgetMacro. On the other hand widgets are
 responsible for ensuring that permissions are applied when rendering
 contents. This already happens under-the-hood in the widgets included in
 the project . For instance, ticket query, stats and report widgets check
 that users have read permissions on a given ticket before rendering
 related widget contents.

 > how they can be discovered without needing to refer to documentation,

 that's a different conversation , so we should follow it in #152 ''';)'''

 > how the documentation itself will be extended by hacks.

 Just like it happens with WikiMacros and ''!MacroList'' today . That's the
 macro to be developed as part of #139 .

 > Ultimately this doesn't seem like a core feature of Bloodhound to me
 yet, but rather something a plugin should provide, if it's done in the
 near future.

 -1 . It looks like a core feature . Everything we have done so far
 regarding UI has been possible thanks to widgets and layouts (<= mainly
 the former ''';)''' . WidgetMacro is the next step if we want to reuse
 them so that they may be shown everywhere , i.e. without requiring a
 plugin defining ''Genshi'' templates , and tons of code in several places
 just for gathering data . Yes, widgets are also about productivity and
 developing complex visualizations quickly ''';)''' .

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

View raw message