[wp-trac] [WordPress Trac] #26571: Increase flexibility of "At a Glance" Dashboard Widget to match "Right Now" Widget

[WordPress Trac]

#26571: Increase flexibility of "At a Glance" Dashboard Widget to match "Right Now"
Widget
----------------------------+------------------------------
 Reporter:  mrwweb          |       Owner:
     Type:  defect (bug)    |      Status:  new
 Priority:  normal          |   Milestone:  Awaiting Review
Component:  Administration  |     Version:  3.8
 Severity:  normal          |  Resolution:
 Keywords:                  |
----------------------------+------------------------------

Comment (by mrwweb):

 Replying to [comment:5 Latz]:
 > Replying to [comment:4 toscho]:
 > Of course you're right, Toscho's always right :-). Just for the record:

 This isn't really the place to discuss hacks. (But while we're at it,
 [http://plugins.trac.wordpress.org/browser/post-status-menu-
 items/tags/1.3.0/cms_post_status_menu.php#L330 here's what I'm doing].
 Empty list elements before and after but still technically using the
 filter.)

 Getting this back on track... What do we need to remedy this situation so
 that we have roughly the same amount of flexibility as previously?

 I'd propose:

 1. A `dashboard_glance_items_after` action that runs immediately after the
 `</ul>` of the glance items list.
 1. A modified `dashboard_glance_items` filter that can handle classes. I
 assume that would be by passing an array. Either `array( '{class}' =>
 '{list item html}'` OR `array( 'class' => '{class}', 'li' => '{list item
 html}'`.

 So questions:

 1. Any objections to change 1 above? (name, placement, use case)
 1. Does anyone have examples of a similar filter somewhere else in core to
 model this after? There was talk in #26495 of passing the core list items
 to the filter as well which would need to be considered.
 1. How much do we need to consider backwards compatibility for 3.8? Seeing
 that #26495 ignored it for ALL PREVIOUS VERSIONS, I'm tempted to say "not
 much" but a second opinion would be good.

 I've never submitted a patch before but I'll step up on this one if people
 can help me think through the best route for the filter.

--
Ticket URL: <http://core.trac.wordpress.org/ticket/26571#comment:6>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software