Re: [GRASS-dev] pygrass documentation

2014-04-28 Thread Luca Delucchi
On 28 April 2014 07:39, Markus Neteler nete...@osgeo.org wrote: ... Sphinx issue solved on server (it was an issue in the cronjob script). Now available: The PyGRASS manual (Sphinx based), updated weekly: http://grass.osgeo.org/programming7/pygrass/ Thanks, At this point we may consider

Re: [GRASS-dev] pygrass documentation

2014-04-28 Thread Vaclav Petras
On Mon, Apr 28, 2014 at 1:39 AM, Markus Neteler nete...@osgeo.org wrote: At this point we may consider to document all Python API in reST (rather than using doxygen for http://grass.osgeo.org/programming7/pygrasslib.html ) +1 Doxygen does not work well for Python and from what I understood

Re: [GRASS-dev] pygrass documentation

2014-04-28 Thread Pietro
Hi Markus and Martin, sorry for the late reply but I'm without connection on these days... On Mon, Apr 28, 2014 at 7:39 AM, Markus Neteler nete...@osgeo.org wrote: ... Sphinx issue solved on server (it was an issue in the cronjob script). Now available: The PyGRASS manual (Sphinx based),

Re: [GRASS-dev] pygrass documentation

2014-04-28 Thread Pietro
On Mon, Apr 28, 2014 at 2:57 PM, Vaclav Petras wenzesl...@gmail.com wrote: [cut] I'm also afraid of introducing another markup (we have now HTML for doc and HTML+Markdown+Doxygen+Doxygen-LaTeX-like for programming), although reStructuredText is almost Python standard. But anyway, I think that

Re: [GRASS-dev] pygrass documentation

2014-04-28 Thread Vaclav Petras
On Mon, Apr 28, 2014 at 9:23 AM, Pietro peter.z...@gmail.com wrote: On Mon, Apr 28, 2014 at 2:57 PM, Vaclav Petras wenzesl...@gmail.com wrote: [cut] I'm also afraid of introducing another markup (we have now HTML for doc and HTML+Markdown+Doxygen+Doxygen-LaTeX-like for programming),

Re: [GRASS-dev] pygrass documentation

2014-04-27 Thread Markus Neteler
(back to list) On Sun, Apr 27, 2014 at 11:18 PM, Vaclav Petras wenzesl...@gmail.com wrote: On Sun, Apr 27, 2014 at 4:57 PM, Markus Neteler nete...@osgeo.org wrote: it works on my Fedora 20 box. Just Debian does not behave. Are you sure you are in a GRASS session? Sure, thanks to

Re: [GRASS-dev] pygrass documentation

2014-04-27 Thread Markus Neteler
... Sphinx issue solved on server (it was an issue in the cronjob script). Now available: The PyGRASS manual (Sphinx based), updated weekly: http://grass.osgeo.org/programming7/pygrass/ At this point we may consider to document all Python API in reST (rather than using doxygen for

Re: [GRASS-dev] pygrass documentation

2014-04-26 Thread Markus Neteler
On Fri, Mar 1, 2013 at 6:50 PM, Vaclav Petras wenzesl...@gmail.com wrote: ... For now, I would leave pygrass doc in the ReST (both the py and rst files). That's fine. Martin and me have fixed the sphinx compilation, this now works on more recent systems: cd lib/python/pygrass/docs/ make html

Re: [GRASS-dev] pygrass documentation

2013-03-01 Thread Vaclav Petras
Hi, was browsing through Python parts (lib/python and gui) in Doxygen documentation and I got the impression that the Python support in Doxygen is very bad, especially for more advanced things (e.g., classes and functions are ok but properties do not) but also some basic things are badly

[GRASS-dev] pygrass documentation

2013-01-16 Thread Luca Delucchi
Hi all, I'm with Pietro and we are speaking about pygrass documentation. At the moment it is in ReST and it need sphinx to be build. We would like to improve it but we would like to know what is the best solution for it. We tough two different solution - kept the actual documentation and add a

Re: [GRASS-dev] pygrass documentation

2013-01-16 Thread Vaclav Petras
Hi, just some brief ideas for now. Firstly, we have general problem with Doxygen in Python because we use non-documented Doxygen feature. Read this doxygen ml thread [1] for details. Secondly, I think that GRASS documentation should use only one solution/language. Doxygen supports Doxygen