Hi Jeff,

I would like to apply to become a co-maintainer of the jQuery Plugin Handler module. I use the module a lot. 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. In my opinion your plugin handler module is the best solution for handling plugins, and it has, or should have, much potential. As I see in the issue queue, I assume you do not have much time for maintaining the module, so I'd really much would like to help you here. Lets make this module the best jQuery plugin handler module of all!!!

Best regards,

Philip

Comments

jjeff’s picture

jjeff commented

Awesome!

I was just thinking about this module this morning. It could *really* use a release.

Also I should post some feature ideas that I have for:

* hook_jqp(), which would allow modules to distribute along with their own plugins. hook_jqp() would allow them to let JQP know what they've got and where to find it.

* The ability to use .info files to add files or alter the plugin registry. So, for instance, if a plugin came along with an important .html file (or more likely images) which were key to its functionality, those could be added into the .info file so that JQP would know about them.

* .info files could also potentially be used to standardize (or alias) file names -- so for instance, the .info file could alias jquery.js to the file jquery-1.2.6.js

* a settings page (or maybe just a section of the admin/reports/status page) to show which .js and .css files have been found and where.. and a link to refresh the cache -- for when admins drop new plugins into the 'plugins' directory

I would LOVE to have a collaborator on this module. I've given you CVS access to the module.

Just remember the mantra for this module:
- keep it simple
- the less the administrator knows that this module exists, the better

You should also be aware of this issue to move some kind of plugin manager into core: http://drupal.org/node/315100

I think that the approach this module takes is the most Drupal-like (sort of) mirroring the way the module system works. Feel free to hop into that thread. It would be really great to get a solution into Drupal 7.

Thanks for your help!

skilip’s picture

skilip commented

Since we should be focussing on porting a plugin manager into core, and we therefore need to take account complete libraries into account, things are getting complicated whether we like it or not :(. I'ill post a mockup of some of my ideas asap and will let you know.

skilip’s picture

skilip commented

http://drupal.org/node/315100#comment-1191841

skilip’s picture

skilip commented
Status: Active » Closed (fixed)