Fix the system for autogenerating the component docs

[GoogleCodeExporter]

Putting the component documentation on the drupal server as awkward and 
error-prone.   Fix the method for autogenerating this documentation.  This 
might involve modifying the Python code that generates the HTML, and installing 
a "one button" system places the HTML on the drupal server.

Original issue reported on code.google.com by halatmit...@gmail.com on 2 Jan 2013 at 2:24

[GoogleCodeExporter]

Oops, just saw this after commenting on the other issue. I think modifying the 
Python code makes sense, so that it actually generates the multiple pages of 
component documentation that we need. I'm not sure the one-button system is 
necessary. Putting a lump of HTML onto a drupal page is easy - the problems 
come with having to manually edit parts of multiple pages and make sure you 
don't miss some change or mess up other parts. Depends how much time a 
one-button solution would take to implement.

Who can I work with to spec out the python scripting and have them build it 
out? Unfortunately, I've never coded in Python before...

Original comment by josheshe...@gmail.com on 2 Jan 2013 at 3:25

[GoogleCodeExporter]

Correction:  It's Java code, not Python
see

appinventor/components/src/com/google/appinventor/components/scripts/Documentati
onGenerator.java

Original comment by halatmit...@gmail.com on 2 Jan 2013 at 5:10

[GoogleCodeExporter]

Josh:

Andrew or I can look at this with you, but take  look by yourself first.  I 
think there are only a few small methods that need to be changed.

Let us know when you need help.

Also see the Google Doc on How to regenerate the documentation:

https://docs.google.com/document/d/1hgSbmjrtBE7JFgShahuz7tW02rjLx7U0Zvkpm706cRk/
edit#heading=h.u6ocf9qqyrze

Original comment by halatmit...@gmail.com on 2 Jan 2013 at 5:13