Hi Nathan, On Wed, Mar 28, 2012 at 3:08 AM, Nathan Woodrow <[email protected]> wrote: > Why don't we just make the author have a README file using plain text > or reStructedText which we can then render it on the plugin site like > what GitHub does.
+1 for reStructedText As a new plugin developer with many documentation pages to write, it was fortuitous when I saw Tim's post about Sphinx's support for using gettext to produce .po files that can be translated in Qt Linguist. I was struggling with the idea of how to localize my documentation; but being my plugin is Python-based, Sphinx, with eventual Linguist support, turned out to be the clear choice. Has anyone actually tried this approach yet? I also use GitHub and like it's .rst support for displaying READMEs. +1 for that type of support on hub/plugins.qgis.org as well. On a simmilar note. What about 1-3 screen shots as 8-bit pngs, restricted within some pixel area (like 1024 x 1024)? They could have a standard naming convention like: screen_1.png -> screen_3.png. I think this would also help users to 'see' plugins with GUIs, prior to installation. Could be on hub/plugins.qgis.org, and supported in Installer as well. Regards, Larry Shaffer Dakota Cartography Black Hills, South Dakota _______________________________________________ Qgis-developer mailing list [email protected] http://lists.osgeo.org/mailman/listinfo/qgis-developer
