I'm up for anything that would make this process easier for new people. plugin dependencies are a pain to deal with!
It might make coding easier too - create a new plugin, and list some starting dependencies. On your local test page, use <script src="generateScripts.cfm?scripts=jquery,.myplugin"> then if you need to add other plugin features, just go to myplugin's repository page and add the dependency there. On the next call it would/should load the new script so you can start testing. Flags like &recheck=true to have it recheck the dependency info for the plugins you listed on each load would be useful, and possibly &packed=true/false or debug=true/false. debug true would include the .debug script of your choice and make it unpacked, debug missing or false would pack all scripts. Another thing that would make this system interesting is something like a form of introspection that would show a dev if another registered plugin has conflicts such as identically named public properties or methods. There are a lot of ways you could go with something like this... Jörn Zaefferer wrote: > > > Daemach2 wrote: >> Here's an idea: If the newly created official plugin repository could be >> the home for the plugins themselves, and had a "publishing" interface >> that >> could make its data available to other servers via a web service or >> json/xml >> download, perhaps the community could create a local application in >> several >> different versions - php, cfml, asp/x, perl, etc. that would pull all of >> the >> metadata and dependency info from the central server on a regular basis, >> then did all the assembly and serving of scripts locally. >> > Did anybody say "jqueryforge"? In the end a dependency management like > apt or gems would be really perfect... > > -- > Jörn Zaefferer > > http://bassistance.de > > > -- View this message in context: http://www.nabble.com/New-Plugin-Repository-tf3944529s15494.html#a11296913 Sent from the JQuery mailing list archive at Nabble.com.
