Sam Collett wrote: > On 22/08/06, Christian Bach <[EMAIL PROTECTED]> wrote: >> Hi All, >> >> I have put together a very simple package regarding plugin documentation. >> >> The package includes: >> >> Build.xml - The ant build file containing two tasks "docs" and "clean". >> Plugin.xml - A simple xml based documentation for plugins >> build - Dir containing the css file and xsl stylesheet. >> >> The Plugin.xml is converted to a html file using a xsl stylesheet >> located in build/docs/. >> >> To generate the docs file, Just run "ant docs" >> >> This is just a sample example of what could be done to ease plugin >> development. >> >> /christian >> > Is there a way to generate the Plugin.xml through parsing the source > code of the plugin?
Yes, you can parse the source code using some js and rhino, as John does. The only down side is that rhino needs to be included, weighing in around 600kb. In my opinion this is a bit overkill for a simple plugin. Perhaps we need a new way?! /c _______________________________________________ jQuery mailing list [email protected] http://jquery.com/discuss/
