<br>I'm either not asking the second question clearly or I'm not understanding your answer about <span class="q" id="q_11504f2ec460c091_2">the connection between the jquery_plugin module and modules that require the JQuery plug-ins
</span>. I'm not asking about activating the plugin when the module is called (which I think 2 and 3 answer) or getting the JQuery plugins from <a href="http://jquery.com">jquery.com</a> to the Drupal install, but simply getting a module with a JQuery plugin dependency installed.
<br><br>Let's say I've developed a module that requires a jquery plugin. You want to use the module, but don't have the required JQuery plugin. What happens? <br><br>Obviously the module would have a dependency of jquery_update module, but how does a module with a jquery plugin dependency indicate to the site admin that an additional jquery plugin is required for the module to function?
<br><br>I'd love to see the process for installing modules that require two step installs standardized. <br><br>- Kevin Reynen<br><br><div><span class="gmail_quote">On 9/14/07, <b class="gmail_sendername">Larry Garfield
</b> <<a href="mailto:larry@garfieldtech.com">larry@garfieldtech.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>In an earlier message, I had proposed two activation methods:<br><br>1) An admin form ~ admin/build/modules where the admin can toggle on or off a given plugin.<br><br>2) A hook_jquery() that modules can implement to specify which they require. The jquery module can then auto-activate those that are requested, and do some sort of error reporting if it is not available. (This method does require a hard naming convention, which is probably OK since jQuery has an informal convention.)
<br><br>3) Nobody expects the Spanish Inquisition! I guess there's no reason we couldn't do both, with hook-requested plugins always-on and the admin able to activate more at his leisure.<br><br>Plugins used only by a theme probably wouldn't need this, as they already have a scripts key in their info file. (Say, how come we didn't enable scripts and styles keywords for module .info files? Bah. Drupal 7.)
<br><br>That would be a separate question from how the plugin gets on the server and where it lives (FTP, http upload, FTP-loopback routine, etc.).<br><br>--Larry Garfield<br><br>On Fri, 14 Sep 2007 08:51:41 -0700, "Kevin Reynen" <
<a href="mailto:kreynen@gmail.com">kreynen@gmail.com</a>> wrote:<br>> Forgive me if these have already been spelled out and I missed it, but with<br>> Earnie's vision for a jquery_plugin module...<br>><br>
> Is the jquery_plugin module alerting users to updates of the JQuery<br>> plugins<br>> (that they would manually download (hopefully look at) and then upload)?<br>><br>> Is there any automated connection between the jquery_plugin module and
<br>> modules that require the plug-ins or are modules that require JQuery<br>> plugins<br>> expected to check to see if the plugin are in the files/jquery/ directory<br>> and alert the site's admin to use jquery_plugin to upload the plugin if
<br>> it's<br>> not there?<br>><br>> - Kevin<br>><br>> On 9/14/07, Earnie Boyd <<a href="mailto:earnie@users.sourceforge.net">earnie@users.sourceforge.net</a>> wrote:<br>>><br>>> Quoting Jeff Eaton <
<a href="mailto:jeff@viapositiva.net">jeff@viapositiva.net</a>>:<br>>><br>>> > On Sep 14, 2007, at 6:23 AM, Frando wrote:<br>>> ><br>>> >> I agree of course. What makes me wonder, though, don't we in Drupal 6
<br>>> >> already include a javascript file in every request which is written<br>> by<br>>> >> Drupal to the filesystem via the Javascript aggregator/compressor?<br>>> >><br>>> >> Isn't that exactly the same as allowing Drupal to save
<br>>> downloaded jQuery<br>>> >> plugins in the file directory (not that I think this is good<br>>> idea anyway)?<br>>> ><br>>> > The difference is that the JS files that make up that aggregated JS
<br>>> > file were all downloaded manually by an administrator and installed,<br>>> > not auto-downloaded from a remote server and installed by a 'smart'<br>>> > module.<br>>> >
<br>>><br>>> Ok, I've gone back and reread parts of this thread. Let's put the<br>>> argument against automating the jQuery plugin scripts behind us because<br>>> it has been expressed and everyone understands that it is a bad idea.
<br>>><br>>> Now let us discuss: the administrator is given the option in the<br>>> jquery_plugin module to upload his jQuery plugin. The jquery_plugin<br>>> module writes the uploaded file to files/jquery/ directory. The
<br>>> jquery_plugin module then serves the client visiting the site those<br>>> files.<br>>><br>>> Earnie -- <a href="http://for-my-kids.com/">http://for-my-kids.com/</a><br>>> -- <a href="http://give-me-an-offer.com/">
http://give-me-an-offer.com/</a><br>>><br>>><br>><br>><br><br></blockquote></div><br>