<br><br><div class="gmail_quote">On Thu, May 22, 2008 at 11:21 AM, Tim Golden <<a href="mailto:mail@timgolden.me.uk">mail@timgolden.me.uk</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I have a request of the python-win32 community. Have a look at:<br>
<br>
<a href="http://timgolden.me.uk/python-on-windows/" target="_blank">http://timgolden.me.uk/python-on-windows/</a><br>
</blockquote><div><br>Wow, Tim! Thanks for doing this.<br> <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
In particular, click through to the section on the Registry (which is the only section which has anything useful in it!)<br>
and then tell me what you think. About anything. The contents,<br>
the style, the colours, the colors, the depth of examples, the<br>
notes. What should be there? What shouldn't? How much overlap<br>
there should be with other sources of documentation? How much<br>
should just be links across? Should I reproduce the pywin32 docs<br>
verbatim. (Difficult: I've got a branch which is trying. Very trying).<br>
Anything.<br>
</blockquote><div><br>I'd like to see a little more prose to go with the examples, not just code. <br>No too much, but enough that the reader can understand WHY a certain task i<br>s done a certain way (and maybe why you would want to do it in the first place).<br>
<br>I do like the fact that it's more of a "cookbook" than "stereo instructions". <br>I think focusing on examples is right on target (and I love your other Py-win HOWTO pages BTW)<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Points to bear in mind:<br>
<br>
* This is very alpha<br>
* I'm using Sphinx but I've done very little with its capabilities</blockquote><div> <br>Sphinx can auto-create "Prev" and "Next" links, which might be useful.<br><br></div></div>Kevin Horn<br>