I did ask about this a few days back. Take a look here: <a href="http://tgmpluginactivation.com/">http://tgmpluginactivation.com/</a>. Using the code here you will be able to set dependencies on other plugins, making them "required" for certain functionality to work or "recommended" for better suitability with your theme. <br>
<br><div class="gmail_quote">On Tue, Feb 21, 2012 at 12:09 AM, jay Cauvain <span dir="ltr"><<a href="mailto:wp@stormfire.me">wp@stormfire.me</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p>Only if there are conditionals, so that the theme will function without the plugin, in case the user decides that they don't want the plugin.</p>
<div class="gmail_quote">On Feb 21, 2012 1:09 AM, "Maximilian von Wortdrücken" <<a href="mailto:max.wortdrucken@gmail.com" target="_blank">max.wortdrucken@gmail.com</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>I thought about this possibility, but it left me with more questions/problems:</div><div><ol><li>Are plugins held to different standards with regards to making connections to other servers and/or downloading and unpacking files from those servers?</li>
<li>One of the goals is to create an environment where child theme developers can rely on the availability of this functionality (and thus be freed from having to bundle 3rd party libraries with their themes). In order to meet that goal, I would have to make the theme framework dependent on a plugin. What are the WP theme review guidelines concerning this? Will WordPress reviewers accept a theme framework that is dependent on certain plugins?</li>
</ol></div><div><br></div><br><br><div class="gmail_quote">On Mon, Feb 20, 2012 at 3:52 PM, Simon Prosser <span dir="ltr"><<a href="mailto:pross@pross.org.uk" target="_blank">pross@pross.org.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Why not just host the libs in a plugin? Then you can update that<br>
whenever you like and the theme will not need updating.<br>
<br>
2012/2/20 Maximilian von Wortdrücken <<a href="mailto:max.wortdrucken@gmail.com" target="_blank">max.wortdrucken@gmail.com</a>>:<br>
<div><div>> Hi all,<br>
><br>
> I am working on a WP theme framework that will have a large number of<br>
> dependencies on 3rd party code libraries. My intent is to provide theme<br>
> developers with a simple interface (in the WP Admin dashboard) that allows<br>
> them to easily import/include/update/delete 3rd party libraries--both server<br>
> side *and* front end code libraries.<br>
><br>
> I'm envisioning a system similar to a Linux package manager. With a system<br>
> like this in place, theme developers using my framework could have easy<br>
> access to all their favorite libs (above and beyond what is available from<br>
> the WordPress default options), but I wouldn't have to bundle those libs<br>
> with the theme. Additionally, this system would provide a standard API that<br>
> child themes could use to verify dependencies upon being activated (and<br>
> prompt the administrator to update or download those dependencies if need<br>
> be).<br>
><br>
> So my general question is: how can I build this functionality into my theme<br>
> framework without it being rejected by the official WP theme review process?<br>
><br>
><br>
><br>
> Here are the requirements:<br>
><br>
> Theme developers can import and update 3rd party libraries independently.<br>
> That is, without updating the theme framework itself.<br>
> Child themes and the theme framework can check for dependencies before<br>
> proceeding with certain actions.<br>
> Developers and site admins can view a list of installed libraries and be<br>
> notified of available updates.<br>
> 3rd party libraries are limited only by whether or not they're publicly<br>
> accessible on the Web.<br>
> The theme framework would not come with any 3rd party libs installed.<br>
> Instead, each library would be defined as a subclass of some base class that<br>
> manages details like:<br>
><br>
> name of lib<br>
> remote address to connect to for downloading<br>
> routine for connecting to server<br>
> routine for unpacking / writing files to the file system<br>
> installation path<br>
> routine for determining version<br>
><br>
> Theme framework would maintain a master list of all 3rd party libraries by<br>
> maintaining the directory of subclasses. If a developer encounters the need<br>
> for a particular library that isn't defined, she can easily create her own<br>
> custom connector object (and submit it for inclusion in the next framework<br>
> release).<br>
><br>
><br>
><br>
> Here are some specific concerns:<br>
><br>
> What are the rules regarding WP themes making connections to other servers<br>
> (e.g., svn repos, github repos, etc.) ?<br>
> What are the rules regarding WP themes downloading and unpacking files<br>
> (e.g., a new version of some code library) from other servers?<br>
> Does WordPress provide any kind of standard API for this already?<br>
><br>
><br>
><br>
> Thanks in advance for your help and consideration.<br>
><br>
><br>
</div></div>> _______________________________________________<br>
> theme-reviewers mailing list<br>
> <a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
> <a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
><br>
<span><font color="#888888"><br>
<br>
<br>
--<br>
My Blog: <a href="http://pross.org.uk/" target="_blank">http://pross.org.uk/</a><br>
Plugins : <a href="http://pross.org.uk/plugins/" target="_blank">http://pross.org.uk/plugins/</a><br>
Themes: <a href="http://wordpress.org/extend/themes/profile/pross" target="_blank">http://wordpress.org/extend/themes/profile/pross</a><br>
_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
</font></span></blockquote></div><br>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org" target="_blank">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div>
<br>_______________________________________________<br>
theme-reviewers mailing list<br>
<a href="mailto:theme-reviewers@lists.wordpress.org">theme-reviewers@lists.wordpress.org</a><br>
<a href="http://lists.wordpress.org/mailman/listinfo/theme-reviewers" target="_blank">http://lists.wordpress.org/mailman/listinfo/theme-reviewers</a><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>Sayontan Sinha<br><a href="http://mynethome.net" target="_blank">http://mynethome.net</a> | <a href="http://mynethome.net/blog" target="_blank">http://mynethome.net/blog</a><br>
--<br>Beating Australia in Cricket is like killing a celebrity. The death gets more coverage than the crime.<br><br>