I've used this technique before and find it very helpful in compiling documentation. The resulting API has an entire topic devoted to FormsAPI calls, which makes finding forms simple.<br><br>I can spare a few patch cycles if we decide to go forward.
<br><br>- Ken Rickard<br>agentrickard<br><br><div><span class="gmail_quote">On 7/13/07, <b class="gmail_sendername">Earl Miles</b> <<a href="mailto:email@example.com">firstname.lastname@example.org</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I would like propose that Drupal 6 (and forward) adopts the following<br>documentation standard:<br><br>For all functions that are meant to be used in as an argument for<br>drupal_get_form, we document them with @ingroup forms (note that actual form
<br>code is documented via @ingroup form) and we put a description of what the form<br>is meant to be used for. That will make it a little easier to for users to<br>discover what forms are available and find their way to the code that generates
<br>the forms.<br><br>(Could also use volunteers to help apply documentation patches to get this done).<br></blockquote></div><br>