<div><font>Hi,<br></font></div><div><font><br></font></div><div><font>I got Sphinx installed now (docs at <a href="http://underdark.wordpress.com/2011/12/26/how-to-install-sphinx/">http://underdark.wordpress.com/2011/12/26/how-to-install-sphinx/</a>) and building the Cookbook worked fine.<br>
</font></div><div><font><br></font></div><div><font>I'll add Alexander's notes and then send a pull request.<br></font></div><div><font><br></font></div><div><font>Best wishes,<br></font></div><div><font><br></font></div>
<div><font>Anita<br></font></div><div><font><br></font></div><br><div class="gmail_quote">On Mon, Dec 26, 2011 at 2:17 PM, Martin Dobias <span dir="ltr"><<a href="mailto:wonder.sk@gmail.com">wonder.sk@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On Sun, Dec 25, 2011 at 2:32 PM, Anita Graser <<a href="mailto:anitagraser@gmx.at">anitagraser@gmx.at</a>> wrote:<br>
> Hi,<br>
><br>
> I think it's time to think about how we want to organize (plugin) developer<br>
> documentation in the future. Currently, we have information spread over the<br>
> wiki, PyQGIS Cookbook and the main API documentation itself.<br>
><br>
> Imho, we should decide if we want to have that kind of information in wiki<br>
> or the cookbook. Keeping both up to date produces unnecessary work and<br>
> confuses those who are willing to learn plugin development.<br>
<br>
</div>Hi Anita<br>
<br>
I would prefer to keep the cookbook as a reference guide for the<br>
developers and merge the interesting stuff from wiki to the cookbook.<br>
The "rst" format is better for this kind of developer documentation,<br>
additionally sphinx (the docs generator) allows also creation of other<br>
output formats.<br>
<div class="im"><br>
<br>
> The advantage of the wiki approach certainly is that everyone with an OSGeo<br>
> account can edit it without much effort. The cookbook on the other hand<br>
> already contains much more information.<br>
<br>
</div>We could add a short section to cookbook on how to contribute (fork,<br>
edit, make pull request).<br>
<br>
Regards<br>
<span class="HOEnZb"><font color="#888888">Martin<br>
</font></span></blockquote></div><br>