In an earlier message, I had proposed two activation methods: 1) An admin form ~ admin/build/modules where the admin can toggle on or off a given plugin. 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.) 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. 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.) 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.). --Larry Garfield On Fri, 14 Sep 2007 08:51:41 -0700, "Kevin Reynen" <kreynen@gmail.com> wrote:
Forgive me if these have already been spelled out and I missed it, but with Earnie's vision for a jquery_plugin module...
Is the jquery_plugin module alerting users to updates of the JQuery plugins (that they would manually download (hopefully look at) and then upload)?
Is there any automated connection between the jquery_plugin module and modules that require the plug-ins or are modules that require JQuery plugins expected to check to see if the plugin are in the files/jquery/ directory and alert the site's admin to use jquery_plugin to upload the plugin if it's not there?
- Kevin
On 9/14/07, Earnie Boyd <earnie@users.sourceforge.net> wrote:
Quoting Jeff Eaton <jeff@viapositiva.net>:
On Sep 14, 2007, at 6:23 AM, Frando wrote:
I agree of course. What makes me wonder, though, don't we in Drupal 6 already include a javascript file in every request which is written
by
Drupal to the filesystem via the Javascript aggregator/compressor?
Isn't that exactly the same as allowing Drupal to save downloaded jQuery plugins in the file directory (not that I think this is good idea anyway)?
The difference is that the JS files that make up that aggregated JS file were all downloaded manually by an administrator and installed, not auto-downloaded from a remote server and installed by a 'smart' module.
Ok, I've gone back and reread parts of this thread. Let's put the argument against automating the jQuery plugin scripts behind us because it has been expressed and everyone understands that it is a bad idea.
Now let us discuss: the administrator is given the option in the jquery_plugin module to upload his jQuery plugin. The jquery_plugin module writes the uploaded file to files/jquery/ directory. The jquery_plugin module then serves the client visiting the site those files.
Earnie -- http://for-my-kids.com/ -- http://give-me-an-offer.com/