incubator-bloodhound-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Apache Bloodhound" <>
Subject Re: [Apache Bloodhound] #77: Wrong version of bootstrap in dashboard plugins
Date Fri, 15 Jun 2012 10:49:03 GMT
#77: Wrong version of bootstrap in dashboard plugins
  Reporter:  gjm        |      Owner:  olemis
      Type:  defect     |     Status:  accepted
  Priority:  critical   |  Milestone:  RC1 for initial release
 Component:  dashboard  |    Version:
Resolution:             |   Keywords:

Comment (by gjm):

 Good point, in that I had forgotten what the radio behaviour was across,
 but I feel we are still subverting the meaning of the {{{.btn-group}}}

 If we really need to separate those groups we could do something like

   <div class="btn-toolbar">
     <div class="btn-group offset1" data-toggle="buttons-radio">
       <py:with vars="max_idx = len(layout.toolbar) - 1">
       <py:for each="idx, g in enumerate(layout.toolbar)" >
       <py:for each="tb_item in g" >
       <button data-target="#tb-item-${}" data-toggle="tab"
           disabled="${tb_item.widget is None and 'true' or None}"
           class="btn ${tb_item.widget is None and 'disabled' or None}
 ${ and 'active' or None}">
       <py:if test="idx != max_idx">
         <button disabled="true" class="btn disabled invisible">

 Perhaps not a perfect reproduction of course.

 Finally, this conversation seems a little useless because if you look at
 the [
 templates/product.html product template] (or the
 templates/dashboard.html dashboard template] if you prefer) I do not
 believe that we are working with radio buttons in that way any more.

 There is nothing stopping you from raising the issue with bootstrap of

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

View raw message