[wp-trac] [WordPress Trac] #22316: Plugin Dependencies (Yet Another Plugin Dependencies Ticket)

[WordPress Trac]

#22316: Plugin Dependencies (Yet Another Plugin Dependencies Ticket)
--------------------------+------------------------------
 Reporter:  Viper007Bond  |       Owner:
     Type:  enhancement   |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Plugins       |     Version:  3.4.2
 Severity:  normal        |  Resolution:
 Keywords:  dev-feedback  |
--------------------------+------------------------------

Comment (by MikeSchinkel):

 Replying to [comment:32 Viper007Bond]:
 > Why don't you test and see? ;)

 Isn't one of the benefits a community provides being to multiply the time
 and effort of its participants? It seems like a foolish waste of time to
 set up a benchmark when one question can potentially leverage the
 experience of someone else who has already evaluated.

 > Active plugins being loaded are just done via an <code>include()</code>
 or <code>require()</code>. There's basically no difference. For that
 matter the include itself has a trivial amount of overhead.
 >
 > As the saying goes, it's quality not quantity. You could run 500 plugins
 if you wanted to.

 My memory was that more happened during plugin load than it does ''(I just
 reviewed the code.)''  OTOH running 500 plugins would do 500 `include()`s
 for every page load whereas having the ability to load on demand would be
 useful for PHP files that provide supporting functionality to only
 selected URLs.

 Maybe a ''"Load"'' header for ''"on-demand"'' or ''"always"'' would be
 useful and then a ''"require_plugin()"'' function that would load if not
 already loaded?

 > But this is off-topic from this ticket. :)

 Really?  Seems a discussion of potential ramifications of dependencies
 would be on-topic.

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