[wp-trac] [WordPress Trac] #11160: Inconsistancies in Naming and Using Sidebar Names and IDs.

[WordPress Trac]

#11160: Inconsistancies in Naming and Using Sidebar Names and IDs.
-----------------------------+----------------------------------------------
 Reporter:  CharlesClarkson  |       Owner:  azaozz                 
     Type:  defect (bug)     |      Status:  new                    
 Priority:  normal           |   Milestone:  3.0                    
Component:  Widgets          |     Version:  2.9                    
 Severity:  normal           |    Keywords:  has-patch needs-testing
-----------------------------+----------------------------------------------

Comment(by jimisaacs):

 Many people are talking about backwards compatibility with functions that
 are most likely a little too old to worry about.

 I believe the Widget API needs an overall like the next guy, but I don't
 believe it requires consistently trying to revamp something that is
 destined for eventual depreciation.

 I say lets look to the future for the Widget API, and similarly to how the
 WP_Widget class standardized a lot with how plugins utilize the API.

 I believe there is a hole that needs to be filled with the API that
 something like a class WP_WidgetArea would fill quite nicely.

 The factory pattern is used for Widgets, while widget areas are still
 trapped in global "sidebar" variables and functions.
 I believe that a WP_WidgetArea class would create a nice transition to a
 more secure and consistent API. We leave the current "sidebar" functions
 and variables the way they are, while utilizing a new API for 3.0

 Anybody on the same page here?

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