[development] jQuery 1.2 is released
kreynen at gmail.com
Fri Sep 14 17:48:55 UTC 2007
I'm either not asking the second question clearly or I'm not understanding
your answer about the connection between the jquery_plugin module and
modules that require the JQuery plug-ins. 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 jquery.com to the Drupal install, but simply
getting a module with a JQuery plugin dependency installed.
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
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?
I'd love to see the process for installing modules that require two step
- Kevin Reynen
On 9/14/07, Larry Garfield <larry at garfieldtech.com> wrote:
> 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 at gmail.com>
> > Forgive me if these have already been spelled out and I missed it, but
> > 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/
> > 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 at users.sourceforge.net> wrote:
> >> Quoting Jeff Eaton <jeff at 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
> > by
> >> >>
> >> >> 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/
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the development