I've implemented "asset reports" as a way to use the API to do the equivalent of what SQL reports do when they query the WebGUI database. But this is much easier and uses the stable API rather than the mutable database.
Here's the contribution:
There is still some more work to be done on this, I'm sure, but I use it on a few of our sites already and it basically works. I've based it on the Navigation asset.
It has help, i18n, and a template installation script. What else does it need for inclusion in the core?
If it doesn't already, it will need a help file, POD, made to conform to WebGUI Best Practices, and then finally will need to be reviewed by a plain black staff member.
Now you're probably going to say that the original Nav asset that you created it from didn't have some of those things. But that is because the Nav asset was developed under our old dev practices. Since this is a new asset, you need to follow the new rules.
