A updated version of collection.php script from explan.tgz. Create 
documentation even for apis without "provides" configured in registry 
and notify that this methods can be called only locally with 
callByPackage().

Not really. But uses Horde_Reflection instead of its own class and is 
more configurable.

With Horde_Reflection in CVS, does the api.php script replace 
everything in explain.tgz?

Sounds like we should move this back to the Wicked queue.

It'd be great if this used Horde_Argv instead of Console_Getopt :)

A wiki script with Horde_Reflection from framework. Allows to specify 
the page prefix and to add or not the api version to pagename. Of 
course you should change it to swit your wishes.

I added the Horde_Document classes as a Horde_Relection package to the 
framework, including proper credits to Sergio Carvalho and a few 
coding style tweaks. The Wiki driver should still be changed to *not* 
mess with the method names. I see why this is necessary for the 
(external) API documentation, but it doesn't help if this should 
become a general purpose package. Instead, a subclass could hook into 
the method name processing.

I changed my mind and would like to see this script added to 
wicked/scripts/. By default, it could be run in any Horde installation 
to autogenerate API docs of the currently installed Horde apps.

I would like it to generate the following wiki page structure. The 
prefix should be editable in the script header, so that we would 
create everything below /Doc/Dev/Apis/, a sane default might be 
/HordeApis/:

Apis (or HordeApis) - contains the instructions how to call the api 
methods. The RPC package has more example that have just been added by 
Chuck. Additionally in contains a list to all application sub-pages, 
e.g.:
Apis/KronolithApi - contains a list of versions. The idea is to allow 
to keep track of different application versions. Thus the script 
should not rewrite this page completely, but only add new versions as 
it detects them.
Apis/KronolithApi/2.2-cvs - contains the actual API docs. This could 
safely be overwritten. If run on a stable version, it won't change 
anyway, and if run on a cvs version, it properly updates the docs.

- Handle multiple parameter types.
- Avoid warnings with no documentation.
- Tell if method has missing documentation.

I found it useful for outside partners not needing to look at the code 
or browse around for docs as they can find it on our partner pages. So 
I think it can be done the same here. Add them in the already existing 
crontab documentation update to update Horde Wiki pages or/and add 
them on the webpages as "External methods" in the documentation 
section (something like http://www.horde.org/imp/docs/?f=api.html)

This looks really nice! I wonder how/where we should integrate this 
though. And you probably need to update it because I changed the API 
methods a bit. The CSS links are no longer returned by the display 
method.

Rendered page example.

A set of batch script using PHP5 Reflection API to render horde 
modules API documentation in HTML or WIKI format. Using together with 
#6130 patch (also included) you can easy update/create wiki pages with 
API call descriptions.