[wp-trac] Re: [WordPress Trac] #10190: Plugin Dependency Class API

[WordPress Trac]

#10190: Plugin Dependency Class API
----------------------------+-----------------------------------------------
 Reporter:  ShaneF          |       Owner:  ShaneF
     Type:  task (blessed)  |      Status:  new   
 Priority:  normal          |   Milestone:  2.9   
Component:  Plugins         |     Version:  2.9   
 Severity:  normal          |    Keywords:        
----------------------------+-----------------------------------------------

Comment(by mikeschinkel):

 @Denis-de-Bernardy: I defintely agree that adding a header field in the
 plugin is the proper way to notate the existence of a dependency. I even
 stated so here on an email send earlier than your reply above:

 http://groups.google.com/group/wp-hackers/msg/901897eb28ebb4b2

 Differences from what I read in your comments are 1.) I'm proposing the
 header field to denote the name to be used to bootstrap validation code
 (vs. writing prose in a readme) and 2.) I'm proposing more granular named
 "interfaces" vs. simple "dependencies." Those differences, documented in
 the thread, add a significant number of capabilities over mere prose.

 @ShaneF: I also replied on the wp-hackers list:

 http://groups.google.com/group/wp-hackers/msg/1195e1c980cce436

 In summary I think it'd be best to revisit your concept and join forces
 using your dependency work with the "interfaces" concept we've been
 discussing on the wp-hackers list.

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