Re: [GRASS-dev] Structure of links for addons, manual pages etc.

About the manual urls, I have an opinion: Main manual for G7 to be linked to the SVN version (always updated). Old manuals fixed to released versions (not maintained). I understand how extreme it may be, but it may be very easy to maintain (only one version) 0.02c On 10 April 2014 07:21, Vacla

[GRASS-dev] Structure of links for addons, manual pages etc.

Hi, I think we need to rethink the structure of addresses/links to various things which we are putting online. The motivation are discussions "Linking Addons manual pages to core modules", "addons for windows", and "Addon manual pages not linked". For example, so far we were linking the trunk do

Re: [GRASS-dev] addons for windows

Hi, 2014-04-09 15:48 GMT+02:00 Markus Neteler : > On Tue, Apr 8, 2014 at 6:26 PM, Martin Landa wrote: > ... >> I will change addons builds for >> trunk to the same layout. Unfortunately it's not possible to fix it >> for beta1 (avoiding extra builds with locally applied patch). Let's >> wait for

Re: [GRASS-dev] [GRASS GIS] #2059: WorldView2 relative spectral response data for i.atcorr

#2059: WorldView2 relative spectral response data for i.atcorr --+- Reporter: nikosa| Owner: grass-dev@… Type: enhancement | Status: new Priori

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

Vaclav Petras wrote: > > And this .bat file specifies the script interpreter. Looks like a good > > solution to also select the correct Python version. > > > I'm afraid how will work for user scripts. Typical case will be that user > has some Python, so he or she will try to run from outside if

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

Markus Metz wrote: > > In spite of wxGUI, GRASS remains fundamentally a collection of > > command-line modules, more like a library than an application. > > I make use of this property daily. On MS Windows, GRASS should by > default behave like a stand-alone application. You can make use of the

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

Markus Metz wrote: > > I basically agree with user expectations you stated. But I would like to > > note that recently, I met several users which wanted and expected that GRASS > > script will run outside GRASS without any special environment setup in the > > script itself. > > AFAIK, GRASS scri

Re: [GRASS-dev] relbr6 - devbr6 differences

Benjamin Ducke wrote: > GEOS is a heavy C++ beast and difficult to compile using GCC > on Windows (at least if you want the result to pass all > validation tests). > > I would prefer to stick to C dependencies only for the core > modules, if only to avoid DLL hell when mixing Visual C++ > and GC

Re: [GRASS-dev] [GRASS GIS] #2249: handling manual pages with external links within the GUI

#2249: handling manual pages with external links within the GUI -+-- Reporter: madi | Owner: grass-dev@… Type: enhancement | Status: new Priority: normal

Re: [GRASS-dev] [GRASS GIS] #2251: highlight selected features and zoom - display not centered over the highlighted feature

#2251: highlight selected features and zoom - display not centered over the highlighted feature --+- Reporter: madi | Owner: grass-dev@… Type: defect| S

Re: [GRASS-dev] addons for windows

On Tue, Apr 8, 2014 at 6:26 PM, Martin Landa wrote: ... > I will change addons builds for > trunk to the same layout. Unfortunately it's not possible to fix it > for beta1 (avoiding extra builds with locally applied patch). Let's > wait for beta2. IMHO we should consider to tag beta2 soon. Marku

Re: [GRASS-dev] [GRASS GIS] #2249: handling manual pages with external links within the GUI

#2249: handling manual pages with external links within the GUI -+-- Reporter: madi | Owner: grass-dev@… Type: enhancement | Status: new Priority: normal

Re: [GRASS-dev] [GRASS-PSC] too many branches => retirement GRASS6.5.svn (=develbranch6)

>One Windows problem is that there is no package manager >who takes the user's hand which is the reason for these large >standalone applications on MS Windows. [...] >> >> Personally, I am a bit afraid that by going down the first route we >> concentrate much developer time that could be spent on

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

On Wed, Apr 9, 2014 at 2:16 AM, Markus Metz wrote: > On Wed, Apr 9, 2014 at 3:44 AM, Glynn Clements > wrote: > > > > Markus Metz wrote: > > > >> > All of this goes out the window if you want to provide a command-line > >> > environment, whether an interactive shell or the ability to execute > >>

Re: [GRASS-dev] [GRASS GIS] #1856: wxGUI with LANG=pl_PL.utf8 throws "'ascii' codec can't decode byte"

#1856: wxGUI with LANG=pl_PL.utf8 throws "'ascii' codec can't decode byte" --+- Reporter: msieczka | Owner: grass-dev@… Type: defect| Status: new Priority:

Re: [GRASS-dev] [GRASS GIS] #2120: wxgui: encoding errors

#2120: wxgui: encoding errors -+-- Reporter: mlennert | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 6.4.4

Re: [GRASS-dev] relbr6 - devbr6 differences

Has somebody here figured out yet how to compile GEOS using GCC on Windows (MinGW), so that it passes all of its own validation tests? That's where I am stuck at this point: http://gvsigce.sourceforge.net/wiki/index.php/Compiling_the_C/C%2B%2B_support_libraries#GEOS_.28currently_disabled.29 Cheer

[GRASS-dev] [GRASS GIS] #2252: wxGUI vector digitizer passing unescaped text to database

#2252: wxGUI vector digitizer passing unescaped text to database -+-- Reporter: marisn | Owner: grass-dev@… Type: defect | Status: new Priority: blocker

Re: [GRASS-dev] [GRASS GIS] #1681: WXGUI vector editing fails with python unicode error

#1681: WXGUI vector editing fails with python unicode error -+-- Reporter: marisn | Owner: grass-dev@… Type: defect | Status: new Priority: blocker |

Re: [GRASS-dev] [GRASS-PSC] too many branches => retirement GRASS6.5.svn (=develbranch6)

On 4/9/14, Yann Chemin wrote: > I used to start my GRASS GIS courses by saying to students that this is not > going to work if you do not read the instructions. Not sure about this. Was just teaching GRASS GIS 7.0.0beta1 and it worked pretty well. I would not 'threaten' them in the beginning. T

Re: [GRASS-dev] [GRASS GIS] #1739: Language switch on wxGUI doesn't affect all strings

#1739: Language switch on wxGUI doesn't affect all strings -+-- Reporter: MilenaN | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone:

Re: [GRASS-dev] [GRASS GIS] #1856: wxGUI with LANG=pl_PL.utf8 throws "'ascii' codec can't decode byte"

#1856: wxGUI with LANG=pl_PL.utf8 throws "'ascii' codec can't decode byte" --+- Reporter: msieczka | Owner: grass-dev@… Type: defect| Status: new Priority:

Re: [GRASS-dev] [GRASS GIS] #512: i18N Translation of welcome message in terminal not possible

#512: i18N Translation of welcome message in terminal not possible ---+ Reporter: neteler| Owner: grass-dev@… Type: defect | Status: new Priority

Re: [GRASS-dev] [GRASS GIS] #2210: unable to start GRASS GIS 7

#2210: unable to start GRASS GIS 7 -+-- Reporter: turek | Owner: grass-dev@… Type: defect | Status: reopened Priority: normal | Milestone: 7.0.0

Re: [GRASS-dev] [GRASS GIS] #2120: wxgui: encoding errors

#2120: wxgui: encoding errors -+-- Reporter: mlennert | Owner: grass-dev@… Type: defect | Status: new Priority: normal | Milestone: 6.4.4

Re: [GRASS-dev] relbr6 - devbr6 differences

Hi Martin, On Wed, 09. Apr 2014 at 11:52:34 +0200, Martin Landa wrote: > > That's why GEOS has a C API. Doesn't GRASS use that anyway? > of course the GRASS modules are based C-API. Martin That's what I thought - but I didn't have to build GRASS on Windows for a while. Thanks ;) Jürgen --

Re: [GRASS-dev] [GRASS GIS] #879: Add a "change language" option in GRASS GUI

#879: Add a "change language" option in GRASS GUI ---+ Reporter: antoniorocha | Owner: lucadelu Type: enhancement | Status: closed Priority: major | Milestone: 7.0

Re: [GRASS-dev] relbr6 - devbr6 differences

Hi, 2014-04-09 8:35 GMT+02:00 Martin Landa : > 2014-04-09 8:28 GMT+02:00 Markus Metz : > >> - wxGUI backport? > > will take a look... > > [...] > >> - v.buffer differs, but is broken in both branches. Only the >> GEOS-enabled version in G7 works. Since this is a bugfix, I would >> suggest to backp

Re: [GRASS-dev] relbr6 - devbr6 differences

Hi, 2014-04-09 10:52 GMT+02:00 Benjamin Ducke : > GEOS is a heavy C++ beast and difficult to compile using GCC > on Windows (at least if you want the result to pass all > validation tests). > > I would prefer to stick to C dependencies only for the core > modules, if only to avoid DLL hell when mi

Re: [GRASS-dev] relbr6 - devbr6 differences

HI, 2014-04-09 11:44 GMT+02:00 Jürgen E. : [...] > That's why GEOS has a C API. Doesn't GRASS use that anyway? of course the GRASS modules are based C-API. Martin -- Martin Landa * http://geo.fsv.cvut.cz/gwiki/Landa ___ grass-dev mailing list grass

Re: [GRASS-dev] relbr6 - devbr6 differences

Hi, On Wed, 09. Apr 2014 at 10:52:59 +0200, Benjamin Ducke wrote: > GEOS is a heavy C++ beast and difficult to compile using GCC > on Windows (at least if you want the result to pass all > validation tests). > > I would prefer to stick to C dependencies only for the core > modules, if only to avo

Re: [GRASS-dev] relbr6 - devbr6 differences

GEOS is a heavy C++ beast and difficult to compile using GCC on Windows (at least if you want the result to pass all validation tests). I would prefer to stick to C dependencies only for the core modules, if only to avoid DLL hell when mixing Visual C++ and GCC DLLs on Windows (different name mang

Re: [GRASS-dev] [GRASS-PSC] too many branches => retirement GRASS6.5.svn (=develbranch6)

On Wed, Apr 9, 2014 at 9:21 AM, Moritz Lennert wrote: > On 09/04/14 03:17, Vaclav Petras wrote: >> >> >> On Tue, Apr 8, 2014 at 9:09 PM, Glynn Clements > > wrote: >> >> If there's no Python installed, the installer can install it. If >> Python is installed

Re: [GRASS-dev] [GRASS-PSC] too many branches => retirement GRASS6.5.svn (=develbranch6)

Agreeing with Moritz, "In other words, there are some types of users (those that don't read anything provided by the developers) for whom I am sometimes tempted to just say "RTFM" instead of trying to find ways to make it possible for them to still use GRASS" I used to start my GRASS GIS courses

Re: [GRASS-dev] relbr6 - devbr6 differences

On 09/04/14 08:35, Martin Landa wrote: Hi Markus, 2014-04-09 8:28 GMT+02:00 Markus Metz : - wxGUI backport? will take a look... [...] - v.buffer differs, but is broken in both branches. Only the GEOS-enabled version in G7 works. Since this is a bugfix, I would suggest to backport v.buffer

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

On 09/04/14 08:16, Markus Metz wrote: On Wed, Apr 9, 2014 at 3:44 AM, Glynn Clements wrote: [...] In spite of wxGUI, GRASS remains fundamentally a collection of command-line modules, more like a library than an application. I make use of this property daily. On MS Windows, GRASS should by de

Re: [GRASS-dev] [GRASS-PSC] too many branches => retirement GRASS6.5.svn (=develbranch6)

On 09/04/14 03:17, Vaclav Petras wrote: On Tue, Apr 8, 2014 at 9:09 PM, Glynn Clements mailto:gl...@gclements.plus.com>> wrote: If there's no Python installed, the installer can install it. If Python is installed and the version is compatible, the installer can install any required