<div>Hi Friends,</div>
<div>l would like to help with information on the above mentioned subject.</div>
<div>looking forward to hear from you.</div>
<div>Yours <br><br></div>
<div class="gmail_quote">On Thu, Feb 26, 2009 at 11:29 AM, Steven Jones <span dir="ltr"><<a href="mailto:darthsteven@gmail.com" target="_blank">darthsteven@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">Hi Sameer,<br><br>I actually was just the last person to edit that page, the content is<br>down to Steven Peck.<br>
<br>In any case I'm not sure that documenting FormAPI like that is the<br>best way to go. Like you I've wanted to document FormAPI better for a<br>while now, but I'm not sure the best way to approach it. Maybe we<br>
could gather a few interested parties at Drupalcon D.C. and have a<br>little chat about the best way forward.<br><br>Are the any other's who'd be interested in helping out with FormAPI docs?<br><br>Regards<br>Steven Jones<br>
ComputerMinds ltd - Perfect Drupal Websites<br><br>Phone : 0121 288 0434<br>Mobile : 07951 270 026<br><a href="http://www.computerminds.co.uk/" target="_blank">http://www.computerminds.co.uk</a><br><br><br><br>2009/2/26 Sameer Siruguri <<a href="mailto:siruguri@gmail.com" target="_blank">siruguri@gmail.com</a>>:<br>
<div>
<div></div>
<div>> Hi,<br>><br>> I have been interested in fleshing out, and collating, the documentation for<br>> the Forms API for some time now, and recently got started on writing out the<br>> material that would go under the headings that Steven Jones wrote out on<br>
> this page: <a href="http://drupal.org/node/204270" target="_blank">http://drupal.org/node/204270</a> (Here's a page I wrote, with one<br>> child: <a href="http://drupal.org/node/384120" target="_blank">http://drupal.org/node/384120</a>)<br>
><br>> Here's the problem I ran into: After writing some pages down, I sheepishly<br>> realized that some material already existed as child pages. But I don't have<br>> edit permissions to the top level of those child pages, which makes it hard<br>
> to incorporate some of my changes and esp. to consolidate all the material<br>> at the top level.<br>><br>> Here are some solutions: I could go ahead and build out all the material and<br>> then propose a consolidation. I could build it on my own website and find<br>
> some way to export the book to be imported into Drupal.org. I could have<br>> access to the top level pages. I could do something during DrupalCon.<br>><br>> I am open to suggestions. Thanks!<br>> Sameer.<br>
><br>><br></div></div>
<div>
<div></div>
<div>> --<br>> Pending work: <a href="http://drupal.org/project/issues/documentation/" target="_blank">http://drupal.org/project/issues/documentation/</a><br>> List archives: <a href="http://lists.drupal.org/pipermail/documentation/" target="_blank">http://lists.drupal.org/pipermail/documentation/</a><br>
><br>--<br>Pending work: <a href="http://drupal.org/project/issues/documentation/" target="_blank">http://drupal.org/project/issues/documentation/</a><br>List archives: <a href="http://lists.drupal.org/pipermail/documentation/" target="_blank">http://lists.drupal.org/pipermail/documentation/</a><br>
</div></div></blockquote></div><br>