[GRASS-dev] TOC in the manual

2014-04-11 Thread Martin Landa
Hi all, in r59673 I introduced simple mechanism to add TOC to the manual pages. It needs some testing, anyway it seems to work. TOC is now fixed and width of body part is 80%, see eg. [1]. Since wxPython widget doesn't support most of css, it's shown before DESCRIPTION and not as fixed. Martin

Re: [GRASS-dev] TOC in the manual

2014-04-11 Thread Margherita Di Leo
Hi Martin, On Fri, Apr 11, 2014 at 10:38 AM, Martin Landa landa.mar...@gmail.comwrote: Hi all, in r59673 I introduced simple mechanism to add TOC to the manual pages. It needs some testing, anyway it seems to work. TOC is now fixed and width of body part is 80%, see eg. [1]. Since

Re: [GRASS-dev] TOC in the manual

2014-04-11 Thread Martin Landa
Hi, 2014-04-11 10:44 GMT+02:00 Margherita Di Leo dileomargher...@gmail.com: Talking about documentation, since GRASS has strong ties with academia, what do you think about adding also a section cite as for the relevant modules? why not, it could generated automatically by mkhtml.py. Martin

Re: [GRASS-dev] TOC in the manual

2014-04-11 Thread Martin Landa
Hi, 2014-04-11 10:38 GMT+02:00 Martin Landa landa.mar...@gmail.com: body part is 80%, see eg. [1]. Since wxPython widget doesn't support most of css, it's shown before DESCRIPTION and not as fixed. the question is whether to hide manual tab and just to provide button which opens manual in the

Re: [GRASS-dev] Handling of Python scripts on MS Windows

2014-04-11 Thread Jürgen E . Fischer
Hi Helmut, On Thu, 10. Apr 2014 at 14:34:04 -0700, Helmut Kudrnovsky wrote: although the architecture may differ, we may get some inspiration for python windows handling from other GIS projects like QGIS? in QGIS python is also in heavy use, e.g. QGIS processing framework, python addons,

Re: [GRASS-dev] TOC in the manual

2014-04-11 Thread Yann Chemin
Did not have an opinion fixed, so went back to work, opened a module, pressed on the manual tab and did have to wait a bit because of rendering... If it was to open in a default web browser, I could have continued looking around the module. +1 for button to external browser On 11 April 2014

Re: [GRASS-dev] Handling of Python scripts on MS Windows

2014-04-11 Thread Martin Landa
Hi Jurgen, 2014-04-11 12:42 GMT+02:00 Jürgen E. j...@norbit.de: although the architecture may differ, we may get some inspiration for python windows handling from other GIS projects like QGIS? in QGIS python is also in heavy use, e.g. QGIS processing framework, python addons, integrated

Re: [GRASS-dev] relbr6 - devbr6 differences

2014-04-11 Thread Benjamin Ducke
And that's why I love this mailing list: There are insights here that are simply impossible to get elsewhere. Thanks for this one, Glynn! Ben On 09/04/14 17:18, Glynn Clements wrote: Benjamin Ducke wrote: GEOS is a heavy C++ beast and difficult to compile using GCC on Windows (at least if

Re: [GRASS-dev] Handling of Python scripts on MS Windows

2014-04-11 Thread Glynn Clements
Helmut Kudrnovsky wrote: although the architecture may differ, we may get some inspiration for python windows handling from other GIS projects like QGIS? in QGIS python is also in heavy use, e.g. QGIS processing framework, python addons, integrated python shell, etc. AFAIK they're

Re: [GRASS-dev] TOC in the manual

2014-04-11 Thread Anna Petrášová
Note, that on Windows and on Ubuntu with wxPython 3, the manual page in the tab is loaded immediately. I believe we should keep the manual in the tab, I think people are more likely to look at the manual there than pressing Help button. Personally I try to avoid pressing Help button in any

Re: [GRASS-dev] TOC in the manual

2014-04-11 Thread Yann Chemin
+1 On 12 April 2014 03:57, Anna Petrášová kratocha...@gmail.com wrote: Note, that on Windows and on Ubuntu with wxPython 3, the manual page in the tab is loaded immediately. I believe we should keep the manual in the tab, I think people are more likely to look at the manual there than