Having missed most of the discussion, I wanted to at least throw in some existing resources on the topic.
For one, the Plugin Authoring guide covers a few of the requirements that Matt listed: http://docs.jquery.com/Plugins/Authoring On the topic of extending plugins, I covered one approach to that in my The Onion talk: http://www.slideshare.net/joern.zaefferer/the-onion-147705 On building robust plugins in general: http://www.slideshare.net/joern.zaefferer/building-robust-jquery-plugins-presentation (click the notes tab below the slides to get the notes for each slide) I still think that making plugins extensible isn't something you can throw a generic solution at. Finding extension points, exposing and documenting them is a unique process for every problem. My favorite example for such an extension point are custom methods for the validation plugin. There is a documented API (http://docs.jquery.com/Plugins/Validation/Validator/addMethod) to add methods, which makes the plugin very extensible in one direction. Jörn --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "jQuery Development" group. To post to this group, send email to jquery-dev@googlegroups.com To unsubscribe from this group, send email to jquery-dev+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/jquery-dev?hl=en -~----------~----~----~----~------~----~------~--~---
