Re: [GRASS-dev] natural neighbor in G7?

2014-04-14 Thread Moritz Lennert
On 14/04/14 17:34, Moritz Lennert wrote: On 08/04/14 14:03, Martin Landa wrote: Hi all, potentially I have a student who could spend some time on this topic. Currently we have for G6 an addons module (bash script) [1] which depends on nn-c library [2]. This library is distributed under MIT lice

Re: [GRASS-dev] natural neighbor in G7?

2014-04-14 Thread Moritz Lennert
On 08/04/14 14:03, Martin Landa wrote: Hi all, potentially I have a student who could spend some time on this topic. Currently we have for G6 an addons module (bash script) [1] which depends on nn-c library [2]. This library is distributed under MIT licence, but partly it's depending on tringle

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

2014-04-14 Thread Glynn Clements
Helmut Kudrnovsky wrote: > not including python, have a look here: > > http://trac.osgeo.org/grass/browser/grass/trunk/mswindows/GRASS-Packager.bat.tmpl#L113 > > @echo Copy Python content to PACKAGE_DIR\Python27 > > and then maybe you have to adapt the starting script and all other ?! I

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

2014-04-14 Thread Glynn Clements
Moritz Lennert wrote: > the argument that GRASS4Win should be a different beast > than GRASS4NIX in that it should become a monolithic integrated > application, which, IMHO, fundamentally alters the very nature of what > GRASS is. There's no fundamental reason why we can't have "Lite" and "Fu

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

2014-04-14 Thread Helmut Kudrnovsky
>So, there is a vision by some that for the reasons of apparent >"incompatibility" between the way GRASS works and Windows, >GRASS has to >be different on windows. I.e. that GRASS has to become a monolithic >application on Windows. I wouldn't call it incompatibility and I think GRASS hasn't to b

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

2014-04-14 Thread Martin Landa
2014-04-14 9:53 GMT+02:00 Moritz Lennert : > There is quite a large margin between creating a monolithic application with > everything bundled and leaving the user alone... > > To answer Martin's call for concrete action: how difficult would it be for > you, Helmut, to create a GRASS installer with

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

2014-04-14 Thread Moritz Lennert
On 14/04/14 00:21, Helmut Kudrnovsky wrote: Hi Moritz, 1) Should GRASS be the same (i.e. feature parity) on all platforms ? for sure, why not? Not to single out MarkusM, but just since he formulated it so clearly: >On 09/04/14 08:16, Markus Metz wrote: >> On Windows, GRASS should behave li

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

2014-04-14 Thread Moritz Lennert
On 13/04/14 20:33, Martin Landa wrote: 2014-04-13 17:03 GMT+02:00 Moritz Lennert : On 11/04/14 13:05, Martin Landa wrote: I don't think this a very helpful attitude. This whole debate is not about one bad guy keeping the rest of the good guys from moving forward. First of all, Glynn is not alone

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

2014-04-14 Thread Moritz Lennert
On 13/04/14 20:32, Jürgen E. Fischer wrote: And IMHO the broader topics would have been better addressed in (a) separate thread(s) and not side-track this one. Your original problem got out of focus, but still isn't solved, is it? IMHO, the broader topics are the core of this thread ! ;-) Mor