[wp-trac] [WordPress Trac] #15042: plugin.php functions (filters) should be available to all pluggable components (wpdb, object cache)

WordPress Trac wp-trac at lists.automattic.com
Wed Oct 6 16:49:26 UTC 2010


#15042: plugin.php functions (filters) should be available to all pluggable
components (wpdb, object cache)
-------------------------+--------------------------------------------------
 Reporter:  andy         |       Owner:                
     Type:  enhancement  |      Status:  new           
 Priority:  normal       |   Milestone:  3.1           
Component:  Plugins      |     Version:                
 Severity:  normal       |    Keywords:  filter, plugin
-------------------------+--------------------------------------------------
Changes (by jacobsantos):

  * type:  defect (bug) => enhancement


Comment:

 Question: How would one actually hook into these functions? No plugins
 would be loaded, because the DB will not have access to load those plugins
 yet. Is the assumption that a future feature will be added that autoloads
 for these requirements?

 Question: How do the mentioned classes reimplement the plugin API?

 Further Technical Details needed: Basically, the reasoning behind this is
 internal and contained component usage of the plugin API.

 Counter-argument: You are using an pattern that is not appropriate for an
 Object-Oriented paradigm for simplicity and convenience sake only.
 Appropriate patterns already exist for what I assume you wish to use the
 Plugin API for in these classes.

 Dissent: You are basically making a decision that will have lasting design
 decisions on the forward progress of the object-oriented paradigm within
 WordPress, without public debate and without initial discussion on the
 reasoning and purpose.

 Reasoning: WordPress stands above other web applications for its great use
 of procedural code. Others may learn from its implementation. The same is
 not true for the objects within WordPress and it is getting worse.

 There are no design decisions and most happen on a whim from independent
 minds based on individual skill, expertise and OO dogma. Given the elitist
 stances most OO programmers have, I suppose the "grounded" nature focusing
 on simplicity and ease of development is emphasized over more practical
 designs which limit rewrites and obsoleting classes; which since this
 never happens simply means more manure has to be shoveled on top of what
 is currently existing.

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


More information about the wp-trac mailing list