Posted by skilip on December 12, 2008 at 10:39am
Jump to:
| Project: | jQuery plugins |
| Version: | 6.x-1.6 |
| Component: | Miscellaneous |
| Category: | support request |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed (fixed) |
Issue Summary
I would like to apply to become a co-maintainer of the jQuery Plugins module. I use the module a lot and have made some minor but important improvements to it (#344309: Plugin exists function, #271934: Add a plugin folder). Most of the modules which I ported, and are waiting to be ported, are depending on jquery plugins, so I'm very committed to the project.
Comments
#1
Let's try to work thru those issues. I looked at a couple of your modules and I think part of the reason you are having issues is you ask the user to download the jQuery plugins into the jquery_plugin directory. That's not actually how this module was intended to work, it was intended to provide a home for jQuery plugins in cvs.drupal.org. I believe there are other Drupal modules that specialize in allowing users to download jQuery plugins (although I don't use them so I forget the name(s) at the moment). One thing to consider would be actually adding the plugins your module uses to this module, assuming they are GPL. Also, you have users download jQuery UI and put it in jquery_plugin, but couldn't you use the jQuery UI module instead?
#2
Hey mfb!
Thanks for your reply and sorry for my ignorance. I thought the module was intended to be a central point for all jQuery plugins. I wish I found JQP module before :(. Regretfully there are already too many modules with overlapping functionality on this matter. (jQuery UI module, jQuery Plugin Handler, Plugins and jQ). IMHO we should join forces in making a (core) module which suits all needs. How do you feel about this?
All the best!
#3
I guess I have limited requirements so I don't get any mileage out of all those modules. I'm really only interested in maintaining javascript in a repository just like the PHP code, not in manually downloading it. I like parking the plugins I use with Drupal on cvs.drupal.org because it means I have one place to retrieve up-to-date code for all my sites whether it is PHP or JS.
I do see some potential to tie in to the plugins.jquery.com site to check for out of date plugins similar to the Drupal update status module, but that would first require a more systematic plugin repository on the jquery.com side of things.
#4
Still it's confusing for non-core Drupallers having several jQuery plugin manager modules and dozens of jQuery plugin wrapper modules (what a sentence). I think we all should separate the jQuery scripts from the Drupal modules. One module should provide an API for other modules to add their required plugins.
#5
But there seems to be some difference of opinion on how that central module should do it.
I want to put the plugins on cvs.drupal.org. Others want to have the users manually download the plugin. Others want the plugin to be automatically downloaded when it's needed by a module.
And one of those modules, jQ, doesn't make any plugins available itself, it just gives administrators a UI to turn jQuery plugins provided by other modules on and off (which for me would just break the site so I don't like that idea ;)
#6
I'm thinking from a newbie point of view (usability). Seeing all those jQuery modules is just overwhelming. And most of them are not more than wrapper modules. While there is no core module for this functionality, I guess it will be impossible to get all heads in the same direction. Maybe it's an idea to let our usability guys think about this. I'll start a topic on g.d.o.
#7
There's already a couple related threads going.
#8
I found that the module jqp suits my needs best. Thanks for your advice mfb!