Hi Marco,<br><br><div class="gmail_quote">On Mon, May 7, 2012 at 10:52 AM, Marco Bernasocchi <span dir="ltr"><<a href="mailto:marco@bernawebdesign.ch" target="_blank">marco@bernawebdesign.ch</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p>Hi Larry, nice ! Is the code already available somewhere?<br>
Ciao<br></p></blockquote><div>Which code? My plugin, or the proposed doc tools? I'll make my private GitHub repository for Plugin Editor public when I do the first beta release. If you are referring to the plugin's documentation tools, they are currently in the design stage.<br>
<br>The ReText tool was mentioned earlier in the thread, though it currently seems to have issues with Sphinx-specific markup.<br><a href="http://sourceforge.net/p/retext/home/ReText/">http://sourceforge.net/p/retext/home/ReText/</a><br>
</div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><p></p><div class="gmail_quote">On May 7, 2012 6:43 PM, "Larry Shaffer" <<a href="mailto:larrys@dakotacarto.com" target="_blank">larrys@dakotacarto.com</a>> wrote:<br type="attribution">
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Paolo,<br><br><div class="gmail_quote">On Sun, May 6, 2012 at 10:31 AM, Paolo Cavallini <span dir="ltr"><<a href="mailto:cavallini@faunalia.it" target="_blank">cavallini@faunalia.it</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Il 06/05/2012 02:03, Larry Shaffer ha scritto:<br>
><br>
> For a large .rst project like the QGIS manual, it may not be much<br>
> different than using a separate text editor. Having Plugin Editor<br>
> embedded (installed) in QGIS offers the advantages of consistency of<br>
> interface/tools and portability, useful for new plugin developers and<br>
> teaching/seminar environments. There are many clever things you can do<br>
> with it, but if you are already an experienced developer, you may find<br>
> its features only occasionally useful compared with your current workflow.<br></blockquote><div> </div><blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
I'm now thinking more to the documentation writer, which is not<br>
necessarily a developer (most probably not). So anything we can do to<br>
make her/his life easier, the better documentation will have, I guess.<br>
I'm thinking of:<br>
- fetching automatically manual sources<br>
- emitting pull requests with a button, after manual production<br>
- preview of the compiled manual<br>
- automatically incorporating screenshots<br>
- etc.<br>
All the best.<span><font color="#888888"><br></font></span></blockquote><div><br>This is an interesting set of documentation tools that I am now going to add to Plugin Editor, and have adjusted the plugin's releases accordingly. The first release will be for other devs to beta-test the text editor and plugin tools. The second for beta-testing documentation tools and commenting on the embedded tutorial (created with Sphinx). Then, after re-working the plugin, finally a public release.<br>
<br>Here is what I am planning for regular (not plugin strings) documentation tools:<br><br>- Function for rst -> output generation<br>- Refresh-able graphic tool for previewing .rst files (ala ReText or temp Sphinx builds)<br>
- Function for generating translation .pot files<br>- Function for viewing translations (see your plugin in another language)<br>- Tool for capturing screeshots of the QGIS interface window(s) (using QPixmap static methods [0][1]), dumping to correct screenshots folder, then copying doc-folder-relative link to clipboard (is this what you meant by 'automatically incorporating screenshots'?) <br>
<br>Concerning source control, I have specifically not designed anything into Plugin Editor, except for one button to launch your SCM app of choice (GitHub for Mac, for example). So, source control is managed outside of the Editor.<br>
<br>My main design focus of the plugin is to ensure portability and, ultimately, to require no additional installs beyond QGIS and Qt dev tools. This means zero (or optional) reliance upon command line tools like 'make', etc., relying instead upon mostly pure Python solutions.<br>
<br>[0] <a href="http://qt-project.org/doc/qt-4.8/qpixmap.html#grabWidget" target="_blank">http://qt-project.org/doc/qt-4.8/qpixmap.html#grabWidget</a><br>[1] <a href="http://doc.qt.nokia.com/main-snapshot/desktop-screenshot.html" target="_blank">http://doc.qt.nokia.com/main-snapshot/desktop-screenshot.html</a><br>
<br>Regards,<br><br>Larry Shaffer<br>Dakota Cartography<br>Black Hills, South Dakota <br></div></div>
<br>_______________________________________________<br>
Qgis-developer mailing list<br>
<a href="mailto:Qgis-developer@lists.osgeo.org" target="_blank">Qgis-developer@lists.osgeo.org</a><br>
<a href="http://lists.osgeo.org/mailman/listinfo/qgis-developer" target="_blank">http://lists.osgeo.org/mailman/listinfo/qgis-developer</a><br>
<br></blockquote></div>
</blockquote></div><br>